From: "Théo Lebrun" <theo.lebrun@bootlin.com>
To: "Mark Brown" <broonie@kernel.org>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Vaishnav Achath" <vaishnav.a@ti.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Rob Herring" <robh@kernel.org>, <linux-spi@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mips@vger.kernel.org>,
"Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
"Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Tawfik Bayouk" <tawfik.bayouk@mobileye.com>
Subject: Re: [PATCH v3 4/9] spi: cadence-qspi: allow FIFO depth detection
Date: Thu, 11 Apr 2024 11:27:43 +0200 [thread overview]
Message-ID: <D0H6QDTNE0FO.27IGZ1AWYO11S@bootlin.com> (raw)
In-Reply-To: <161eebc1-9417-4ab0-ad8c-c1b17be119b4@sirena.org.uk>
Hello,
On Wed Apr 10, 2024 at 10:03 PM CEST, Mark Brown wrote:
> On Wed, Apr 10, 2024 at 11:29:07AM +0200, Théo Lebrun wrote:
>
> > If FIFO depth DT property is provided, check it matches what hardware
> > reports and warn otherwise. Else, use hardware provided value.
> >
> > Hardware exposes FIFO depth indirectly because
> > CQSPI_REG_SRAMPARTITION is partially read-only.
>
> This breaks an allmodconfig build:
>
> /build/stage/linux/drivers/spi/spi-cadence-quadspi.c: In function ‘cqspi_of_get_
> pdata’:
> /build/stage/linux/drivers/spi/spi-cadence-quadspi.c:1506:45: error: unused vari
> able ‘ddata’ [-Werror=unused-variable]
> 1506 | const struct cqspi_driver_platdata *ddata = cqspi->ddata;
> | ^~~~~
> /build/stage/linux/drivers/spi/spi-cadence-quadspi.c: In function ‘cqspi_control
> ler_detect_fifo_depth’:
> /build/stage/linux/drivers/spi/spi-cadence-quadspi.c:1582:45: error: unused vari
> able ‘ddata’ [-Werror=unused-variable]
> 1582 | const struct cqspi_driver_platdata *ddata = cqspi->ddata;
> | ^~~~~
> cc1: all warnings being treated as errors
I really should fix my kernel compiler warnings. Sorry about that.
Will fix next revision.
Regards,
--
Théo Lebrun, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-04-11 9:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 9:29 [PATCH v3 0/9] spi: cadence-qspi: add Mobileye EyeQ5 support Théo Lebrun
2024-04-10 9:29 ` [PATCH v3 1/9] spi: dt-bindings: cdns,qspi-nor: sort compatibles alphabetically Théo Lebrun
2024-04-10 9:29 ` [PATCH v3 2/9] spi: dt-bindings: cdns,qspi-nor: add mobileye,eyeq5-ospi compatible Théo Lebrun
2024-04-10 9:29 ` [PATCH v3 3/9] spi: dt-bindings: cdns,qspi-nor: make cdns,fifo-depth optional Théo Lebrun
2024-04-10 20:22 ` Rob Herring
2024-04-10 9:29 ` [PATCH v3 4/9] spi: cadence-qspi: allow FIFO depth detection Théo Lebrun
2024-04-10 20:03 ` Mark Brown
2024-04-11 9:27 ` Théo Lebrun [this message]
2024-04-10 9:29 ` [PATCH v3 5/9] spi: cadence-qspi: add no-IRQ mode to indirect reads Théo Lebrun
2024-04-10 9:29 ` [PATCH v3 6/9] spi: cadence-qspi: add early busywait to cqspi_wait_for_bit() Théo Lebrun
2024-04-10 9:29 ` [PATCH v3 7/9] spi: cadence-qspi: add mobileye,eyeq5-ospi compatible Théo Lebrun
2024-04-10 9:29 ` [PATCH v3 8/9] MIPS: mobileye: eyeq5: Add SPI-NOR controller node Théo Lebrun
2024-04-10 9:29 ` [PATCH v3 9/9] MIPS: mobileye: eyeq5: add octal flash node to eval board DTS Théo Lebrun
2024-04-10 17:47 ` [PATCH v3 0/9] spi: cadence-qspi: add Mobileye EyeQ5 support Mark Brown
2024-04-11 12:03 ` (subset) " Mark Brown
2024-04-22 16:52 ` Théo Lebrun
2024-04-23 5:00 ` Mark Brown
2024-04-23 10:04 ` Théo Lebrun
2024-04-23 10:25 ` Krzysztof Kozlowski
2024-04-23 13:08 ` Théo Lebrun
2024-04-23 17:23 ` Conor Dooley
2024-04-24 1:01 ` Mark Brown
2024-04-24 19:53 ` Konstantin Ryabitsev
2024-04-25 0:19 ` 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=D0H6QDTNE0FO.27IGZ1AWYO11S@bootlin.com \
--to=theo.lebrun@bootlin.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tawfik.bayouk@mobileye.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tsbogend@alpha.franken.de \
--cc=vaishnav.a@ti.com \
--cc=vladimir.kondratiev@mobileye.com \
/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).