From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Schrempf Frieder <frieder.schrempf@kontron.de>
Cc: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/5] spi: spi-mem: Add driver for NXP FlexSPI controller
Date: Mon, 10 Dec 2018 11:36:09 +0100 [thread overview]
Message-ID: <20181210113609.59355f12@bbrezillon> (raw)
In-Reply-To: <f51ab7b2-bc23-1a8f-5970-18c2d200eb6a@kontron.de>
On Mon, 10 Dec 2018 10:31:57 +0000
Schrempf Frieder <frieder.schrempf@kontron.de> wrote:
> >> Yes, I need to validate op->addr.nbytes else LUT would going to be programmed for 0 addrlen.
> >> I have checked this on the target.
> >
> > Also agree there. Some operations have 0 address bytes. We could also
> > test addr.buswidth, but I'm fine with the addr.nbytes test too.
>
> The "if (op->addr.nbytes)" is needed of course, but I think the default
> case in the switch statement (and for other reasons the whole switch
> statement) is not needed and rather a check for op->addr.nbytes > 4
> should be added to nxp_fspi_supports_op(). I wrongly assumed this check
> already exists in nxp_fspi_supports_op().
Ok, then this check on the max number of address bytes should indeed be
moved to the supports_op() implementation.
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Schrempf Frieder <frieder.schrempf@kontron.de>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>,
"robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 1/5] spi: spi-mem: Add driver for NXP FlexSPI controller
Date: Mon, 10 Dec 2018 11:36:09 +0100 [thread overview]
Message-ID: <20181210113609.59355f12@bbrezillon> (raw)
In-Reply-To: <f51ab7b2-bc23-1a8f-5970-18c2d200eb6a@kontron.de>
On Mon, 10 Dec 2018 10:31:57 +0000
Schrempf Frieder <frieder.schrempf@kontron.de> wrote:
> >> Yes, I need to validate op->addr.nbytes else LUT would going to be programmed for 0 addrlen.
> >> I have checked this on the target.
> >
> > Also agree there. Some operations have 0 address bytes. We could also
> > test addr.buswidth, but I'm fine with the addr.nbytes test too.
>
> The "if (op->addr.nbytes)" is needed of course, but I think the default
> case in the switch statement (and for other reasons the whole switch
> statement) is not needed and rather a check for op->addr.nbytes > 4
> should be added to nxp_fspi_supports_op(). I wrongly assumed this check
> already exists in nxp_fspi_supports_op().
Ok, then this check on the max number of address bytes should indeed be
moved to the supports_op() implementation.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-10 10:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 11:13 [PATCH v5 0/5] spi: spi-mem: Add driver for NXP FlexSPI controller Yogesh Narayan Gaur
2018-11-16 11:13 ` Yogesh Narayan Gaur
2018-11-16 11:13 ` [PATCH v5 1/5] " Yogesh Narayan Gaur
2018-11-16 11:13 ` Yogesh Narayan Gaur
2018-12-06 9:22 ` Schrempf Frieder
2018-12-06 9:22 ` Schrempf Frieder
2018-12-10 9:41 ` Yogesh Narayan Gaur
2018-12-10 9:41 ` Yogesh Narayan Gaur
2018-12-10 9:41 ` Yogesh Narayan Gaur
2018-12-10 10:19 ` Boris Brezillon
2018-12-10 10:19 ` Boris Brezillon
2018-12-10 10:31 ` Schrempf Frieder
2018-12-10 10:31 ` Schrempf Frieder
2018-12-10 10:36 ` Boris Brezillon [this message]
2018-12-10 10:36 ` Boris Brezillon
2018-12-10 10:43 ` Yogesh Narayan Gaur
2018-12-10 10:43 ` Yogesh Narayan Gaur
2018-12-10 10:50 ` Boris Brezillon
2018-12-10 10:50 ` Boris Brezillon
2018-12-10 10:59 ` Yogesh Narayan Gaur
2018-12-10 10:59 ` Yogesh Narayan Gaur
2018-12-10 11:03 ` Boris Brezillon
2018-12-10 11:03 ` Boris Brezillon
2018-12-10 11:09 ` Boris Brezillon
2018-12-10 11:09 ` Boris Brezillon
2018-12-10 11:25 ` Yogesh Narayan Gaur
2018-12-10 11:25 ` Yogesh Narayan Gaur
2018-12-10 11:25 ` Yogesh Narayan Gaur
2018-12-10 12:11 ` Boris Brezillon
2018-12-10 12:11 ` Boris Brezillon
2018-12-10 10:35 ` Schrempf Frieder
2018-12-10 10:35 ` Schrempf Frieder
2018-12-10 10:41 ` Boris Brezillon
2018-12-10 10:41 ` Boris Brezillon
2018-11-16 11:13 ` [PATCH v5 2/5] dt-bindings: spi: add binding file " Yogesh Narayan Gaur
2018-11-16 11:13 ` Yogesh Narayan Gaur
2018-11-16 11:14 ` [PATCH v5 3/5] arm64: dts: lx2160a: add FlexSPI node property Yogesh Narayan Gaur
2018-11-16 11:14 ` Yogesh Narayan Gaur
2018-12-12 8:15 ` Pankaj Bansal
2018-12-12 8:15 ` Pankaj Bansal
2018-12-12 8:15 ` Pankaj Bansal
2018-11-16 11:14 ` [PATCH v5 4/5] arm64: defconfig: enable NXP FlexSPI driver Yogesh Narayan Gaur
2018-11-16 11:14 ` Yogesh Narayan Gaur
2018-11-16 11:14 ` [PATCH v5 5/5] MAINTAINERS: add maintainers for the " Yogesh Narayan Gaur
2018-11-16 11:14 ` Yogesh Narayan Gaur
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=20181210113609.59355f12@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frieder.schrempf@kontron.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=yogeshnarayan.gaur@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.