mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: John Watts <contact@jookia.org>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] I2C: i.MX: early: Use a custom delay on i.MX6
Date: Thu, 2 Feb 2023 08:35:27 +0100	[thread overview]
Message-ID: <20230202073527.GK13319@pengutronix.de> (raw)
In-Reply-To: <20230201094435.1228362-1-contact@jookia.org>

On Wed, Feb 01, 2023 at 08:44:35PM +1100, John Watts wrote:
> The i.MX early I2C code requires waiting for the controller to settle
> after configuration. This is currently done using udelay which is
> supported on ARMv8 but not on ARMv7.
> 
> For the i.MX6 we will have to use a custom delay. This was only
> tested on the i.MX6Q but should work on all other i.MX6 chips.
> 
> Signed-off-by: John Watts <contact@jookia.org>
> ---
>  drivers/i2c/busses/i2c-imx-early.c | 24 +++++++++++++++++++++++-
>  1 file changed, 23 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/i2c/busses/i2c-imx-early.c b/drivers/i2c/busses/i2c-imx-early.c
> index 6c8bdc7904..30cc65ca86 100644
> --- a/drivers/i2c/busses/i2c-imx-early.c
> +++ b/drivers/i2c/busses/i2c-imx-early.c
> @@ -90,6 +90,28 @@ static int i2c_fsl_acked(struct fsl_i2c *fsl_i2c)
>  	return i2c_fsl_poll_status(fsl_i2c, 0, I2SR_RXAK);
>  }
>  
> +static void i2c_fsl_settle(struct fsl_i2c *fsl_i2c)
> +{
> +#ifdef CPU_ARCH_ARMv8
> +	udelay(100);
> +#else
> +	/*
> +	 * We lack udelay on the i.MX6 prebootloader, so delay
> +	 * manually: On an i.MX6 with a 66Mhz I2C peripheral clock
> +	 * one cycle of this loop takes 1.30us,
> +	 * this means we have to wait for 76.9 microseconds.
> +	 *
> +	 * This clock may be 44Mhz if the BT_FREQ eFUSE is set,
> +	 * this just means it will take 150 microseconds.
> +	 */

I rounded up to 100 cycles and rephrased this to be a little less i.MX6
centric:

	/*
	 * We lack udelay on the 32bit i.MX SoCs, so delay manually: On an
	 * i.MX6 with a 66Mhz I2C peripheral clock one cycle of this loop
	 * takes 1.30us. Let's be generous and round up to 100 cycles. Other
	 * i.MX SoCs do not have a higher peripheral clock, so we should be
	 * safe here as well.
	 */

In the end it doesn't hurt when it takes a little longer.

Applied, thanks

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2023-02-02  7:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01  9:44 John Watts
2023-02-02  7:35 ` Sascha Hauer [this message]
2023-02-02  7:58   ` John Watts

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-all 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=20230202073527.GK13319@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=contact@jookia.org \
    /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