From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Pratyush Yadav <p.yadav@ti.com>
Cc: Mark Brown <broonie@kernel.org>, <linux-spi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <zhengxunli@mxic.com.tw>
Subject: Re: [PATCH 1/2] spi: spi-mem: add spi_mem_dtr_supports_op()
Date: Fri, 5 Feb 2021 10:44:13 +0100 [thread overview]
Message-ID: <20210205104413.5e873c0e@xps13> (raw)
In-Reply-To: <20210204141218.32229-1-p.yadav@ti.com>
Hi Pratyush,
Pratyush Yadav <p.yadav@ti.com> wrote on Thu, 4 Feb 2021 19:42:17 +0530:
> spi_mem_default_supports_op() rejects DTR ops by default to ensure that
> the controller drivers that haven't been updated with DTR support
> continue to reject them. It also makes sure that controllers that don't
> support DTR mode at all (which is most of them at the moment) also
> reject them.
>
> This means that controller drivers that want to support DTR mode can't
> use spi_mem_default_supports_op(). Driver authors have to roll their own
> supports_op() function and mimic the buswidth checks. See
> spi-cadence-quadspi.c for example. Or even worse, driver authors might
> skip it completely or get it wrong.
>
> Add spi_mem_dtr_supports_op(). It provides a basic sanity check for DTR
> ops and performs the buswidth requirement check. Move the logic for
> checking buswidth in spi_mem_default_supports_op() to a separate
> function so the logic is not repeated twice.
>
> Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
I am not a SPI-NOR expert but for what I know this approach looks good
to me. Let's see what other maintainers think.
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
Thanks,
Miquèl
next prev parent reply other threads:[~2021-02-05 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 14:12 [PATCH 1/2] spi: spi-mem: add spi_mem_dtr_supports_op() Pratyush Yadav
2021-02-04 14:12 ` [PATCH 2/2] spi: cadence-quadspi: Use spi_mem_dtr_supports_op() Pratyush Yadav
2021-02-05 9:44 ` Miquel Raynal [this message]
2021-02-11 16:26 ` [PATCH 1/2] spi: spi-mem: add spi_mem_dtr_supports_op() Mark Brown
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=20210205104413.5e873c0e@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=p.yadav@ti.com \
--cc=zhengxunli@mxic.com.tw \
/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;
as well as URLs for NNTP newsgroup(s).