public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif@nuviainc.com>
To: Masami Hiramatsu <masami.hiramatsu@linaro.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	devel@edk2.groups.io,
	Kazuhiko Sakamoto <sakamoto.kazuhiko@socionext.com>,
	Masahisa Kojima <masahisa.kojima@linaro.org>
Subject: Re: [PATCH 1/5] [RESEND][edk2-platforms] Silicon/SynQuacerI2cDxe: Wait for bus busy
Date: Fri, 26 Nov 2021 17:47:47 +0000	[thread overview]
Message-ID: <YaEdw1/PBpbLKMTk@leviathan> (raw)
In-Reply-To: <163610420797.391624.17492204385268340229.stgit@localhost>

On Fri, Nov 05, 2021 at 18:23:28 +0900, Masami Hiramatsu wrote:
> If an EFI application frequently repeats SetTime and GetTime,
> the I2C bus can be busy and failed to start. To fix this issue,
> add waiting loop for the bus busy status. (Usually, it is
> enough to read 3 times for checking, but for safety this
> sets 10 for timeout.)
>
> This also clean up the code path a bit so that it is easy to
> understand what should do on each combinations of BSR.BB and
> BCR.MSS.
> 
> Signed-off-by: Masami Hiramatsu <masami.hiramatsu@linaro.org>
> Reported-by: Kazuhiko Sakamoto <sakamoto.kazuhiko@socionext.com>
> ---
>  .../Drivers/SynQuacerI2cDxe/SynQuacerI2cDxe.c      |   38 ++++++++++++++------
>  1 file changed, 26 insertions(+), 12 deletions(-)
> 
> diff --git a/Silicon/Socionext/SynQuacer/Drivers/SynQuacerI2cDxe/SynQuacerI2cDxe.c b/Silicon/Socionext/SynQuacer/Drivers/SynQuacerI2cDxe/SynQuacerI2cDxe.c
> index 31f6e3072f..380eba8059 100644
> --- a/Silicon/Socionext/SynQuacer/Drivers/SynQuacerI2cDxe/SynQuacerI2cDxe.c
> +++ b/Silicon/Socionext/SynQuacer/Drivers/SynQuacerI2cDxe/SynQuacerI2cDxe.c
> @@ -16,6 +16,8 @@
>  //
>  #define WAIT_FOR_INTERRUPT_TIMEOUT    50000
>  
> +#define WAIT_FOR_BUS_BUSY_TIMEOUT        10
> +

I think it would be more clear English to say that we are waiting
_for_ the bus to be *ready* - meaning that we are waiting _while_ the
bus is *busy*.

So I suggest
WAIT_FOR_BUS_BUSY_TIMEOUT ->
WAIT_FOR_BUS_READY_TIMEOUT

>  /**
>    Set the frequency for the I2C clock line.
>  
> @@ -152,6 +154,7 @@ SynQuacerI2cMasterStart (
>    IN  EFI_I2C_OPERATION           *Op
>    )
>  {
> +  UINTN                   Timeout = WAIT_FOR_BUS_BUSY_TIMEOUT;

This indentation does not match the subsequent lines.

/
    Leif

>    UINT8                       Bsr;
>    UINT8                       Bcr;
>  
> @@ -167,24 +170,35 @@ SynQuacerI2cMasterStart (
>    Bsr = MmioRead8 (I2c->MmioBase + F_I2C_REG_BSR);
>    Bcr = MmioRead8 (I2c->MmioBase + F_I2C_REG_BCR);
>  
> -  if ((Bsr & F_I2C_BSR_BB) && !(Bcr & F_I2C_BCR_MSS)) {
> -    DEBUG ((DEBUG_INFO, "%a: bus is busy\n", __FUNCTION__));
> -    return EFI_ALREADY_STARTED;
> -  }
> +  if (!(Bcr & F_I2C_BCR_MSS)) {
>  
> -  if (Bsr & F_I2C_BSR_BB) { // Bus is busy
> -    DEBUG ((DEBUG_INFO, "%a: Continuous Start\n", __FUNCTION__));
> -    MmioWrite8 (I2c->MmioBase + F_I2C_REG_BCR, Bcr | F_I2C_BCR_SCC);
> -  } else {
> -    if (Bcr & F_I2C_BCR_MSS) {
> -      DEBUG ((DEBUG_WARN,
> -        "%a: is not in master mode\n", __FUNCTION__));
> -      return EFI_DEVICE_ERROR;
> +    if (Bsr & F_I2C_BSR_BB) { // Bus is busy
> +        do {
> +          Bsr = MmioRead8 (I2c->MmioBase + F_I2C_REG_BSR);
> +        } while (Timeout-- && (Bsr & F_I2C_BSR_BB));
> +
> +        if (Bsr & F_I2C_BSR_BB) {
> +          DEBUG ((DEBUG_INFO, "%a: bus is busy\n", __FUNCTION__));
> +          return EFI_ALREADY_STARTED;
> +        }
>      }
> +
>      DEBUG ((DEBUG_INFO, "%a: Start Condition\n", __FUNCTION__));
>      MmioWrite8 (I2c->MmioBase + F_I2C_REG_BCR,
>                  Bcr | F_I2C_BCR_MSS | F_I2C_BCR_INTE | F_I2C_BCR_BEIE);
> +
> +  } else { // F_I2C_BCR_MSS is set
> +
> +    if (!(Bsr & F_I2C_BSR_BB)) {
> +      DEBUG ((DEBUG_WARN,
> +        "%a: is not in master mode\n", __FUNCTION__));
> +      return EFI_DEVICE_ERROR;
> +    }
> +
> +    DEBUG ((DEBUG_INFO, "%a: Continuous Start\n", __FUNCTION__));
> +    MmioWrite8 (I2c->MmioBase + F_I2C_REG_BCR, Bcr | F_I2C_BCR_SCC);
>    }
> +
>    return EFI_SUCCESS;
>  }
>  
> 

  reply	other threads:[~2021-11-26 17:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05  9:23 [PATCH 0/5] Series short description Masami Hiramatsu
2021-11-05  9:23 ` [PATCH 1/5] [RESEND][edk2-platforms] Silicon/SynQuacerI2cDxe: Wait for bus busy Masami Hiramatsu
2021-11-26 17:47   ` Leif Lindholm [this message]
2021-11-27  2:45     ` Masami Hiramatsu
2021-11-05  9:23 ` [PATCH 2/5] [edk2-platforms] Silicon/Socionext/SynQuacer: Fix GenericWatchdog interrupt number Masami Hiramatsu
2021-11-26 17:50   ` Leif Lindholm
2021-11-27  4:43     ` Masami Hiramatsu
2021-11-05  9:23 ` [PATCH 3/5] [edk2-platforms] Silicon/SynQuacerPlatformFlashAccessLib: Fix the number of erase blocks Masami Hiramatsu
2021-11-26 17:52   ` Leif Lindholm
2021-11-05  9:23 ` [PATCH 4/5] [edk2-platforms] Silicon/SynQuacer: add DBG2 ACPI table Masami Hiramatsu
2021-11-26 18:10   ` Leif Lindholm
2021-11-27  7:52     ` Masami Hiramatsu
2021-11-05  9:24 ` [PATCH 5/5] [edk2-platforms] Platform/DeveloperBox: Expand NvStorage sizes Masami Hiramatsu
2021-11-26 18:19   ` Leif Lindholm
2021-11-27  7:48     ` Masami Hiramatsu
2021-11-29 13:42       ` Leif Lindholm
2021-11-29 22:33         ` Masami Hiramatsu
     [not found]         ` <16BC25260C31EA7F.23256@groups.io>
2021-12-03  6:17           ` [edk2-devel] " Masami Hiramatsu
2021-11-25 11:19 ` [PATCH 0/5] Series short description Masami Hiramatsu
2021-11-25 16:40   ` Leif Lindholm
2021-11-26  0:58     ` Masami Hiramatsu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YaEdw1/PBpbLKMTk@leviathan \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox