From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sergiu Cuciurean <sergiu.cuciurean@analog.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
gregkh@linuxfoundation.org, simon@nikanor.nu,
chandra627@gmail.com, fabian.krueger@fau.de, gneukum1@gmail.com,
michael.scheiderer@fau.de
Subject: Re: [PATCH] staging: kpc2000: kpc2000_spi: Use new structure for SPI transfer delays
Date: Mon, 2 Mar 2020 10:45:42 +0300 [thread overview]
Message-ID: <20200302074542.GB4140@kadam> (raw)
In-Reply-To: <20200227144643.23195-1-sergiu.cuciurean@analog.com>
On Thu, Feb 27, 2020 at 04:46:43PM +0200, Sergiu Cuciurean wrote:
> In a recent change to the SPI subsystem [1], a new `delay` struct was added
Don't do [1] footnote, just say "SPI subsystem in commit bebcfd272df6
("spi: introduce `delay` field for `spi_transfer` + spi_transfer_delay_exec()")
You can use footnotes for URLs if you want (not required).
> to replace the `delay_usecs`. This change replaces the current
> `delay_usecs` with `delay` for this driver.
>
> The `spi_transfer_delay_exec()` function [in the SPI framework] makes sure
> that both `delay_usecs` & `delay` are used (in this order to preserve
> backwards compatibility).
>
> [1] commit bebcfd272df6 ("spi: introduce `delay` field for
> `spi_transfer` + spi_transfer_delay_exec()")
>
> Signed-off-by: Sergiu Cuciurean <sergiu.cuciurean@analog.com>
> ---
> drivers/staging/kpc2000/kpc2000_spi.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/kpc2000/kpc2000_spi.c b/drivers/staging/kpc2000/kpc2000_spi.c
> index 1c360daa703d..cc9b147fd437 100644
> --- a/drivers/staging/kpc2000/kpc2000_spi.c
> +++ b/drivers/staging/kpc2000/kpc2000_spi.c
> @@ -386,8 +386,9 @@ kp_spi_transfer_one_message(struct spi_master *master, struct spi_message *m)
> }
> }
>
> - if (transfer->delay_usecs)
> - udelay(transfer->delay_usecs);
> + if (transfer->delay.value &&
> + (transfer->delay.unit == SPI_DELAY_UNIT_USECS))
> + udelay(transfer->delay.value);
What if the units are in USEC now? We should probably not just ignore
it right?
regards,
dan carpenter
next prev parent reply other threads:[~2020-03-02 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 14:46 [PATCH] staging: kpc2000: kpc2000_spi: Use new structure for SPI transfer delays Sergiu Cuciurean
2020-03-02 7:45 ` Dan Carpenter [this message]
2020-03-04 7:37 ` [PATCH v2] " Sergiu Cuciurean
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=20200302074542.GB4140@kadam \
--to=dan.carpenter@oracle.com \
--cc=chandra627@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=fabian.krueger@fau.de \
--cc=gneukum1@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.scheiderer@fau.de \
--cc=sergiu.cuciurean@analog.com \
--cc=simon@nikanor.nu \
/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