From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Yogesh Gaur <yogeshnarayan.gaur@nxp.com>
Cc: linux-mtd@lists.infradead.org, marek.vasut@gmail.com,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, mark.rutland@arm.com, shawnguo@kernel.org,
linux-arm-kernel@lists.infradead.org,
computersforpeace@gmail.com, frieder.schrempf@exceet.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] spi: spi-mem: Add driver for NXP FlexSPI controller
Date: Mon, 17 Sep 2018 13:37:51 +0200 [thread overview]
Message-ID: <20180917133751.453ea6ed@bbrezillon> (raw)
In-Reply-To: <1537177710-9379-2-git-send-email-yogeshnarayan.gaur@nxp.com>
Hi Yogesh,
On Mon, 17 Sep 2018 15:18:26 +0530
Yogesh Gaur <yogeshnarayan.gaur@nxp.com> wrote:
> +
> + /*
> + * R/W functions for big- or little-endian registers:
> + * The FSPI controller's endianness is independent of
> + * the CPU core's endianness. So far, although the CPU
> + * core is little-endian the FSPI controller can use
> + * big-endian or little-endian.
> + */
> + if (of_property_read_bool(np, "big-endian")) {
> + f->write = fspi_writel_be;
> + f->read = fspi_readl_be;
> + } else {
> + f->write = fspi_writel;
> + f->read = fspi_readl;
> + }
Hm, isn't it something you can extract from the compatible string? I'd
rather not allow users to set that in their DT if it's not something
you can change.
Regards,
Boris
next prev parent reply other threads:[~2018-09-17 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 9:48 [PATCH v2 0/5] spi: spi-mem: Add driver for NXP FlexSPI controller Yogesh Gaur
2018-09-17 9:48 ` [PATCH v2 1/5] " Yogesh Gaur
2018-09-17 11:37 ` Boris Brezillon [this message]
2018-09-18 8:22 ` Frieder Schrempf
2018-09-18 8:28 ` Yogesh Narayan Gaur
2018-09-18 10:21 ` Frieder Schrempf
2018-09-18 11:34 ` Yogesh Narayan Gaur
2018-09-18 12:52 ` Boris Brezillon
2018-09-19 10:51 ` Yogesh Narayan Gaur
2018-09-17 9:48 ` [PATCH v2 2/5] dt-bindings: spi: add binding file " Yogesh Gaur
2018-09-17 9:48 ` [PATCH v2 3/5] arm64: dts: lx2160a: add FlexSPI node property Yogesh Gaur
2018-09-17 9:48 ` [PATCH v2 4/5] arm64: defconfig: enable NXP FlexSPI driver Yogesh Gaur
2018-09-17 9:48 ` [PATCH v2 5/5] MAINTAINERS: add maintainers for the " Yogesh 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=20180917133751.453ea6ed@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frieder.schrempf@exceet.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 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).