mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "open list:BAREBOX" <barebox@lists.infradead.org>
Subject: Re: [PATCH 1/3] spi: spi-gpio: actually delay in spidelay()
Date: Thu, 26 Sep 2024 09:05:52 +0200	[thread overview]
Message-ID: <ZvUH0B4IvKxXyMcA@pengutronix.de> (raw)
In-Reply-To: <334cf766-bf60-494a-8ba2-71006286ff3c@pengutronix.de>

On Thu, Sep 26, 2024 at 07:55:35AM +0200, Ahmad Fatoum wrote:
> On 25.09.24 16:06, Sascha Hauer wrote:
> > spidelay() currently only is a no-op dummy function. Actually delay in
> > this function to avoid spi-gpio being faster than specified.
> > 
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > ---
> >  drivers/spi/gpio_spi.c | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/spi/gpio_spi.c b/drivers/spi/gpio_spi.c
> > index e5664df3fe..a71b4eddab 100644
> > --- a/drivers/spi/gpio_spi.c
> > +++ b/drivers/spi/gpio_spi.c
> > @@ -48,7 +48,10 @@ static inline int getmiso(const struct spi_device *spi)
> >  	return !!gpio_get_value(priv->data->miso);
> >  }
> >  
> > -#define spidelay(nsecs) do { } while (0)
> > +static inline void spidelay(unsigned int nsecs)
> > +{
> > +	udelay(max(1U, nsecs / 1000));
> 
> Why delay 1us at least? Why not use ndelay?

I was under the assumption that we don't have ndelay(). We do have it,
will use it instead.

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:[~2024-09-26  7:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 14:06 [PATCH 0/3] spi-gpio updates Sascha Hauer
2024-09-25 14:06 ` [PATCH 1/3] spi: spi-gpio: actually delay in spidelay() Sascha Hauer
2024-09-26  5:55   ` Ahmad Fatoum
2024-09-26  7:05     ` Sascha Hauer [this message]
2024-09-25 14:06 ` [PATCH 2/3] spi: spi-gpio: support different word widths Sascha Hauer
2024-09-26  6:07   ` Ahmad Fatoum
2024-09-26  7:16     ` Sascha Hauer
2024-09-25 14:06 ` [PATCH 3/3] spi: spi-gpio: switch to new gpio binding Sascha Hauer
2024-09-26  6:09   ` Ahmad Fatoum
2024-09-26  8:19     ` Sascha Hauer

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=ZvUH0B4IvKxXyMcA@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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