linux-gbmc: i2c-ast2600.c: fix two special cases during master xfer

There are two special cases (describled in b/378795666#comment3 and
b/378795666#comment4) which will make ast2600_i2c_master_xfer return -16
or -71 even though I2C controller already sends out the packet. Here we
handle these two special cases and return correct return code so upper
layer won't retry the packet.

Tested:
b/378795666#comment6
Platforms-Affected: all platforms
Fusion-Link:
platform11: https://fusion2.corp.google.com/bfbab31d-b695-301a-9b56-9b391a936751 (not related)
platform5:  https://fusion2.corp.google.com/276874c2-d2ff-3a24-a852-13601ce09a08 (known failure b/379855075)
platform15: https://fusion2.corp.google.com/2ee0bb2d-239b-37db-a653-378d32b4f134 (passed)
Google-Bug-Id: 378795666
Change-Id: Ic4ac31e46a19649577f231ba3cc1b5bb5f351b53
Signed-off-by: Jinliang Wang <jinliangw@google.com>
(cherry picked from commit 16de73df192c683e1f6fdcad2a4cf4f136f853d5)
2 files changed
tree: 1fb096c558e9975a5ddc07b6c90ca222bcf2f1dd
  1. classes/
  2. conf/
  3. dynamic-layers/
  4. recipes-bsp/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-google/
  10. recipes-kernel/
  11. recipes-phosphor/
  12. recipes-support/
  13. recipes-tpm1/
  14. recipes-tpm2/
  15. LICENSE
  16. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.