From: Brian Norris <computersforpeace@gmail.com>
To: Yuan Yao <yao.yuan@freescale.com>
Cc: dwmw2@infradead.org, han.xu@freescale.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
yao.yuan@nxp.com
Subject: Re: [PATCH v3 1/3] mtd: spi-nor: fsl-quadspi: add big-endian support
Date: Sat, 23 Jan 2016 13:11:52 -0800 [thread overview]
Message-ID: <20160123211152.GD35559@google.com> (raw)
In-Reply-To: <1453362836-44377-2-git-send-email-yao.yuan@freescale.com>
On Thu, Jan 21, 2016 at 03:53:54PM +0800, Yuan Yao wrote:
> Add R/W functions for big- or little-endian registers:
> The qSPI controller's endian is independent of the CPU core's endian.
> So far, the qSPI have two versions for big-endian and little-endian.
>
> Signed-off-by: Yuan Yao <yao.yuan@nxp.com>
> Acked-by: Han xu <han.xu@freescale.com>
> ---
...
> @@ -954,6 +990,7 @@ static int fsl_qspi_probe(struct platform_device *pdev)
> if (IS_ERR(q->iobase))
> return PTR_ERR(q->iobase);
>
> + q->big_endian = of_property_read_bool(np, "big-endian");
> res = platform_get_resource_byname(pdev, IORESOURCE_MEM,
> "QuadSPI-memory");
> if (!devm_request_mem_region(dev, res->start, resource_size(res),
Still no documentation for this property?? You're trying my patience.
We've had the same request since November, and you haven't managed to
satisfy it.
next prev parent reply other threads:[~2016-01-23 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 7:53 mtd: spi-nor: fsl-quadspi: add support for ls1021a Yuan Yao
2016-01-21 7:53 ` [PATCH v3 1/3] mtd: spi-nor: fsl-quadspi: add big-endian support Yuan Yao
2016-01-23 21:11 ` Brian Norris [this message]
2016-01-21 7:53 ` [PATCH v3 2/3] mtd: spi-nor: fsl-quadspi: add support for ls1021a Yuan Yao
2016-01-21 7:53 ` [PATCH v3 3/3] mtd: spi-nor: fsl-quadspi: add support for layerscape Yuan Yao
2016-01-21 15:42 ` mtd: spi-nor: fsl-quadspi: add support for ls1021a Han Xu
2016-01-22 9:01 ` Yao Yuan
2016-01-22 17:30 ` Han Xu
2016-01-23 21:17 ` Brian Norris
2016-01-24 4:16 ` Yao Yuan
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=20160123211152.GD35559@google.com \
--to=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=han.xu@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=yao.yuan@freescale.com \
--cc=yao.yuan@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.