From: Shawn Guo <shawnguo@kernel.org>
To: Ken Lin <yungching0725@gmail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, inux@armlinux.org.uk,
robh+dt@kernel.org, akshay.bhat@timesys.com,
kernel@pengutronix.de, fabio.estevam@nxp.com,
linux-arm-kernel@lists.infradead.org, peter.stretz@advantech.com
Subject: Re: [PATCH] ARM: dts: imx6q-bx50v3/imx6q-b450v3/imx6q-b650v3: fix at25 spi-clk frequency issue
Date: Tue, 14 Mar 2017 15:28:48 +0800 [thread overview]
Message-ID: <20170314072846.GJ3618@dragon> (raw)
In-Reply-To: <20170303212032.31725-1-yungching0725@gmail.com>
On Sat, Mar 04, 2017 at 05:20:32AM +0800, Ken Lin wrote:
> Change the maxium spi clock frequency from 20MHz to 10MHz to meet the operation voltage range requirement recommended in AT25 datasheet
The commit log should be wrapped around column 72 to make it easier for
read.
The subject prefix is unnecessarily too long, as it only changes
imx6q-bx50v3.dtsi.
I fixed them this time, and apply the patch.
Shawn
>
> Signed-off-by: Ken Lin <yungching0725@gmail.com>
> ---
> arch/arm/boot/dts/imx6q-bx50v3.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/imx6q-bx50v3.dtsi b/arch/arm/boot/dts/imx6q-bx50v3.dtsi
> index f99e6efda3e2..614c40e5f772 100644
> --- a/arch/arm/boot/dts/imx6q-bx50v3.dtsi
> +++ b/arch/arm/boot/dts/imx6q-bx50v3.dtsi
> @@ -103,7 +103,7 @@
>
> m25_eeprom: m25p80@0 {
> compatible = "atmel,at25";
> - spi-max-frequency = <20000000>;
> + spi-max-frequency = <10000000>;
> size = <0x8000>;
> pagesize = <64>;
> reg = <0>;
> --
> 2.11.0
>
prev parent reply other threads:[~2017-03-14 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 21:20 [PATCH] ARM: dts: imx6q-bx50v3/imx6q-b450v3/imx6q-b650v3: fix at25 spi-clk frequency issue Ken Lin
2017-03-14 7:28 ` Shawn Guo [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=20170314072846.GJ3618@dragon \
--to=shawnguo@kernel.org \
--cc=akshay.bhat@timesys.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=inux@armlinux.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peter.stretz@advantech.com \
--cc=robh+dt@kernel.org \
--cc=yungching0725@gmail.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).