From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] spi: Add Socionext F_OSPI SPI flash controller driver
Date: Wed, 30 Nov 2022 09:46:47 +0100 [thread overview]
Message-ID: <CAMuHMdWa06ND-Tud1_bYTYAVbmo1qMnU3i0bETZo6FVehvLZhg@mail.gmail.com> (raw)
In-Reply-To: <6c423f87-1187-b2d6-8b70-c8cd709f3ea0@socionext.com>
Hi Hayashi-san,
On Wed, Nov 30, 2022 at 1:47 AM Kunihiko Hayashi
<hayashi.kunihiko@socionext.com> wrote:
> On 2022/11/30 1:49, Geert Uytterhoeven wrote:
> > On Thu, Nov 24, 2022 at 1:36 AM Kunihiko Hayashi
> > <hayashi.kunihiko@socionext.com> wrote:
> >> Introduce Socionext F_OSPI controller driver. This controller is used to
> >> communicate with slave devices such as SPI Flash memories. It supports
> >> 4 slave devices and up to 8-bit wide bus, but supports master mode only.
> >>
> >> This driver uses spi-mem framework for SPI flash memory access, and
> >> can only operate indirect access mode and single data rate mode.
> >>
> >> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> >> --- a/drivers/spi/Kconfig
> >> +++ b/drivers/spi/Kconfig
> >> @@ -906,6 +906,15 @@ config SPI_SLAVE_MT27XX
> >> say Y or M here.If you are not sure, say N.
> >> SPI slave drivers for Mediatek MT27XX series ARM SoCs.
> >>
> >> +config SPI_SN_F_OSPI
> >> + tristate "Socionext F_OSPI SPI flash controller"
> >> + depends on OF && HAS_IOMEM
> >> + depends on SPI_MEM
> >
> > On which systems is this hardware block found?
> > Perhaps this should depend on ARCH_UNIPHIER || COMPILE_TEST?
>
> This IP doesn't depend on ARCH_UNIPHIER, so I expect that it can be widely
> applied not only to ARCH_UNIPHIER.
OK.
> If COMPILE_TEST is required, the dependency is like SPI_CADENCE_XSPI:
> depends on (OF || COMPILE_TEST) && HAS_IOMEM
While this is not a hard requirement, it would be nice to have.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2022-11-30 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 0:33 [PATCH v3 0/2] Introduce Socionext F_OSPI SPI flash controller Kunihiko Hayashi
2022-11-24 0:33 ` [PATCH v3 1/2] dt-bindings: spi: Add Socionext F_OSPI controller Kunihiko Hayashi
2022-11-24 0:33 ` [PATCH v3 2/2] spi: Add Socionext F_OSPI SPI flash controller driver Kunihiko Hayashi
2022-11-29 16:49 ` Geert Uytterhoeven
2022-11-30 0:47 ` Kunihiko Hayashi
2022-11-30 8:46 ` Geert Uytterhoeven [this message]
2022-11-24 13:27 ` [PATCH v3 0/2] Introduce Socionext F_OSPI SPI flash controller 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=CAMuHMdWa06ND-Tud1_bYTYAVbmo1qMnU3i0bETZo6FVehvLZhg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).