From: Cory Tusar <Cory.Tusar@zii.aero>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] spi: Enable Freescale QSPI controller driver for VF610
Date: Tue, 14 May 2019 13:30:57 +0000 [thread overview]
Message-ID: <20190514133054.GA13606@zii.aero> (raw)
In-Reply-To: <20190514113226.eon3i5irb5btxtjm@pengutronix.de>
On Tue, May 14, 2019 at 01:32:26PM +0200, Sascha Hauer wrote:
> On Mon, May 13, 2019 at 04:59:44PM -0700, Andrey Smirnov wrote:
> > VF610 is supported by this driver, so modify its Kconfig entry to
> > reflect that.
> >
> > Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
> > ---
> > drivers/spi/Kconfig | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
> > index d687105ea..2e57457dc 100644
> > --- a/drivers/spi/Kconfig
> > +++ b/drivers/spi/Kconfig
> > @@ -27,7 +27,7 @@ config DRIVER_SPI_ATMEL
> >
> > config DRIVER_SPI_FSL_QUADSPI
> > bool "Freescale QSPI controller"
> > -depends on ARCH_IMX25 || ARCH_IMX31 || ARCH_IMX35 || ARCH_IMX50 || ARCH_IMX53 || ARCH_LAYERSCAPE
> > +depends on ARCH_IMX25 || ARCH_IMX31 || ARCH_IMX35 || ARCH_IMX50 || ARCH_IMX53 || ARCH_LAYERSCAPE || ARCH_VF610
>
> Not your fault, but this list is bogus. None of the i.MX SoCs actually
> has this hardware and the ones that have it are not in the list. We
> should rather remove this line entirely.
Should be ARCH_MX6SX || ARCH_MX7 || ARCH_VF610 at the very least, no?
I believe some of the the Layerscape SoCs use the same / very similar
hardware block, but I don't know which ones off the top of my head.
-Cory
--
Cory Tusar
Senior Software Engineer
Zodiac Inflight Innovations
2929 E Imperial Hwy, Suite 170
Brea, CA 92821
(714) 203-0519
www.safran-aerosystems.com
________________________________
This email and any files transmitted with it are confidential & proprietary to Zodiac Inflight Innovations. This information is intended solely for the use of the individual or entity to which it is addressed. Access or transmittal of the information contained in this e-mail, in full or in part, to any other organization or persons is not authorized.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-05-14 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 23:59 Andrey Smirnov
2019-05-14 11:32 ` Sascha Hauer
2019-05-14 13:30 ` Cory Tusar [this message]
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=20190514133054.GA13606@zii.aero \
--to=cory.tusar@zii.aero \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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