From: Shawn Guo <shawnguo@kernel.org> To: BOUGH CHEN <haibo.chen@nxp.com> Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>, "robh+dt@kernel.org" <robh+dt@kernel.org>, dl-linux-imx <linux-imx@nxp.com>, "kernel@pengutronix.de" <kernel@pengutronix.de>, Fabio Estevam <fabio.estevam@nxp.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH 1/2] arm: dts: imx7d-sdb: add SD3.0 support for usdhc1 Date: Sun, 13 Jan 2019 10:32:45 +0800 [thread overview] Message-ID: <20190113023243.GC11426@dragon> (raw) In-Reply-To: <20181228093558.18434-1-haibo.chen@nxp.com> On Fri, Dec 28, 2018 at 09:28:30AM +0000, BOUGH CHEN wrote: > Add usdhc1 support SD3.0. > > Besides, add fsl,tuning-start-tap for all usdhc, imx usdhc IP > logic require the tuning-start-tap larger than 10, to make > sure the tuning logical can work normal. > > Signed-off-by: Haibo Chen <haibo.chen@nxp.com> For i.MX arm32 dts, please use prefix 'ARM: dts: ...'. > --- > arch/arm/boot/dts/imx7d-sdb.dts | 55 +++++++++++++++++++++++++++------ > arch/arm/boot/dts/imx7s.dtsi | 6 ++++ > 2 files changed, 52 insertions(+), 9 deletions(-) > > diff --git a/arch/arm/boot/dts/imx7d-sdb.dts b/arch/arm/boot/dts/imx7d-sdb.dts > index 202922ed3754..ded43decf46c 100644 > --- a/arch/arm/boot/dts/imx7d-sdb.dts > +++ b/arch/arm/boot/dts/imx7d-sdb.dts > @@ -87,6 +87,16 @@ > regulator-max-microvolt = <1800000>; > }; > > + reg_sd1_vmmc: regulator-sd1-vmmc { > + compatible = "regulator-fixed"; > + regulator-name = "VDD_SD1"; > + regulator-min-microvolt = <3300000>; > + regulator-max-microvolt = <3300000>; > + gpio = <&gpio5 2 GPIO_ACTIVE_HIGH>; > + startup-delay-us = <200000>; > + enable-active-high; > + }; > + > reg_brcm: regulator-brcm { > compatible = "regulator-fixed"; > gpio = <&gpio4 21 GPIO_ACTIVE_HIGH>; > @@ -408,12 +418,13 @@ > }; > > &usdhc1 { > - pinctrl-names = "default"; > - pinctrl-0 = <&pinctrl_usdhc1>; > + pinctrl-names = "default", "state_100mhz", "state_200mhz"; > + pinctrl-0 = <&pinctrl_usdhc1>, <&pinctrl_usdhc1_gpio>; > + pinctrl-1 = <&pinctrl_usdhc1_100mhz>, <&pinctrl_usdhc1_gpio>; > + pinctrl-2 = <&pinctrl_usdhc1_200mhz>, <&pinctrl_usdhc1_gpio>; > cd-gpios = <&gpio5 0 GPIO_ACTIVE_LOW>; > wp-gpios = <&gpio5 1 GPIO_ACTIVE_HIGH>; > - wakeup-source; > - keep-power-in-suspend; Why these changes? > + vmmc-supply = <®_sd1_vmmc>; > status = "okay"; > }; > > @@ -426,7 +437,6 @@ > keep-power-in-suspend; > non-removable; > vmmc-supply = <®_brcm>; > - fsl,tuning-step = <2>; > status = "okay"; > }; > > @@ -438,7 +448,6 @@ > assigned-clocks = <&clks IMX7D_USDHC3_ROOT_CLK>; > assigned-clock-rates = <400000000>; > bus-width = <8>; > - fsl,tuning-step = <2>; > non-removable; > status = "okay"; > }; > @@ -638,6 +647,15 @@ > >; > }; > > + pinctrl_usdhc1_gpio: usdhc1_gpiogrp { > + fsl,pins = < > + MX7D_PAD_SD1_CD_B__GPIO5_IO0 0x59 /* CD */ > + MX7D_PAD_SD1_WP__GPIO5_IO1 0x59 /* WP */ > + MX7D_PAD_SD1_RESET_B__GPIO5_IO2 0x59 /* vmmc */ > + MX7D_PAD_GPIO1_IO08__SD1_VSELECT 0x59 /* VSELECT */ > + >; > + }; > + > pinctrl_usdhc1: usdhc1grp { > fsl,pins = < > MX7D_PAD_SD1_CMD__SD1_CMD 0x59 > @@ -646,9 +664,28 @@ > MX7D_PAD_SD1_DATA1__SD1_DATA1 0x59 > MX7D_PAD_SD1_DATA2__SD1_DATA2 0x59 > MX7D_PAD_SD1_DATA3__SD1_DATA3 0x59 > - MX7D_PAD_SD1_CD_B__GPIO5_IO0 0x59 /* CD */ > - MX7D_PAD_SD1_WP__GPIO5_IO1 0x59 /* WP */ > - MX7D_PAD_SD1_RESET_B__GPIO5_IO2 0x59 /* vmmc */ > + >; > + }; > + > + pinctrl_usdhc1_100mhz: usdhc1grp_100mhz { > + fsl,pins = < > + MX7D_PAD_SD1_CMD__SD1_CMD 0x5a > + MX7D_PAD_SD1_CLK__SD1_CLK 0x1a > + MX7D_PAD_SD1_DATA0__SD1_DATA0 0x5a > + MX7D_PAD_SD1_DATA1__SD1_DATA1 0x5a > + MX7D_PAD_SD1_DATA2__SD1_DATA2 0x5a > + MX7D_PAD_SD1_DATA3__SD1_DATA3 0x5a > + >; > + }; > + > + pinctrl_usdhc1_200mhz: usdhc1grp_200mhz { > + fsl,pins = < > + MX7D_PAD_SD1_CMD__SD1_CMD 0x5b > + MX7D_PAD_SD1_CLK__SD1_CLK 0x1b > + MX7D_PAD_SD1_DATA0__SD1_DATA0 0x5b > + MX7D_PAD_SD1_DATA1__SD1_DATA1 0x5b > + MX7D_PAD_SD1_DATA2__SD1_DATA2 0x5b > + MX7D_PAD_SD1_DATA3__SD1_DATA3 0x5b > >; > }; > > diff --git a/arch/arm/boot/dts/imx7s.dtsi b/arch/arm/boot/dts/imx7s.dtsi > index e88f53a4c7f4..bee8dc2f614b 100644 > --- a/arch/arm/boot/dts/imx7s.dtsi > +++ b/arch/arm/boot/dts/imx7s.dtsi > @@ -1036,6 +1036,8 @@ > <&clks IMX7D_USDHC1_ROOT_CLK>; > clock-names = "ipg", "ahb", "per"; > bus-width = <4>; > + fsl,tuning-step = <2>; The commit log should mention the move of fsl,tuning-step from board level dts to SoC level. Shawn > + fsl,tuning-start-tap = <20>; > status = "disabled"; > }; > > @@ -1048,6 +1050,8 @@ > <&clks IMX7D_USDHC2_ROOT_CLK>; > clock-names = "ipg", "ahb", "per"; > bus-width = <4>; > + fsl,tuning-step = <2>; > + fsl,tuning-start-tap = <20>; > status = "disabled"; > }; > > @@ -1060,6 +1064,8 @@ > <&clks IMX7D_USDHC3_ROOT_CLK>; > clock-names = "ipg", "ahb", "per"; > bus-width = <4>; > + fsl,tuning-step = <2>; > + fsl,tuning-start-tap = <20>; > status = "disabled"; > }; > > -- > 2.17.1 >
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org> To: BOUGH CHEN <haibo.chen@nxp.com> Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>, "robh+dt@kernel.org" <robh+dt@kernel.org>, dl-linux-imx <linux-imx@nxp.com>, "kernel@pengutronix.de" <kernel@pengutronix.de>, Fabio Estevam <fabio.estevam@nxp.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH 1/2] arm: dts: imx7d-sdb: add SD3.0 support for usdhc1 Date: Sun, 13 Jan 2019 10:32:45 +0800 [thread overview] Message-ID: <20190113023243.GC11426@dragon> (raw) In-Reply-To: <20181228093558.18434-1-haibo.chen@nxp.com> On Fri, Dec 28, 2018 at 09:28:30AM +0000, BOUGH CHEN wrote: > Add usdhc1 support SD3.0. > > Besides, add fsl,tuning-start-tap for all usdhc, imx usdhc IP > logic require the tuning-start-tap larger than 10, to make > sure the tuning logical can work normal. > > Signed-off-by: Haibo Chen <haibo.chen@nxp.com> For i.MX arm32 dts, please use prefix 'ARM: dts: ...'. > --- > arch/arm/boot/dts/imx7d-sdb.dts | 55 +++++++++++++++++++++++++++------ > arch/arm/boot/dts/imx7s.dtsi | 6 ++++ > 2 files changed, 52 insertions(+), 9 deletions(-) > > diff --git a/arch/arm/boot/dts/imx7d-sdb.dts b/arch/arm/boot/dts/imx7d-sdb.dts > index 202922ed3754..ded43decf46c 100644 > --- a/arch/arm/boot/dts/imx7d-sdb.dts > +++ b/arch/arm/boot/dts/imx7d-sdb.dts > @@ -87,6 +87,16 @@ > regulator-max-microvolt = <1800000>; > }; > > + reg_sd1_vmmc: regulator-sd1-vmmc { > + compatible = "regulator-fixed"; > + regulator-name = "VDD_SD1"; > + regulator-min-microvolt = <3300000>; > + regulator-max-microvolt = <3300000>; > + gpio = <&gpio5 2 GPIO_ACTIVE_HIGH>; > + startup-delay-us = <200000>; > + enable-active-high; > + }; > + > reg_brcm: regulator-brcm { > compatible = "regulator-fixed"; > gpio = <&gpio4 21 GPIO_ACTIVE_HIGH>; > @@ -408,12 +418,13 @@ > }; > > &usdhc1 { > - pinctrl-names = "default"; > - pinctrl-0 = <&pinctrl_usdhc1>; > + pinctrl-names = "default", "state_100mhz", "state_200mhz"; > + pinctrl-0 = <&pinctrl_usdhc1>, <&pinctrl_usdhc1_gpio>; > + pinctrl-1 = <&pinctrl_usdhc1_100mhz>, <&pinctrl_usdhc1_gpio>; > + pinctrl-2 = <&pinctrl_usdhc1_200mhz>, <&pinctrl_usdhc1_gpio>; > cd-gpios = <&gpio5 0 GPIO_ACTIVE_LOW>; > wp-gpios = <&gpio5 1 GPIO_ACTIVE_HIGH>; > - wakeup-source; > - keep-power-in-suspend; Why these changes? > + vmmc-supply = <®_sd1_vmmc>; > status = "okay"; > }; > > @@ -426,7 +437,6 @@ > keep-power-in-suspend; > non-removable; > vmmc-supply = <®_brcm>; > - fsl,tuning-step = <2>; > status = "okay"; > }; > > @@ -438,7 +448,6 @@ > assigned-clocks = <&clks IMX7D_USDHC3_ROOT_CLK>; > assigned-clock-rates = <400000000>; > bus-width = <8>; > - fsl,tuning-step = <2>; > non-removable; > status = "okay"; > }; > @@ -638,6 +647,15 @@ > >; > }; > > + pinctrl_usdhc1_gpio: usdhc1_gpiogrp { > + fsl,pins = < > + MX7D_PAD_SD1_CD_B__GPIO5_IO0 0x59 /* CD */ > + MX7D_PAD_SD1_WP__GPIO5_IO1 0x59 /* WP */ > + MX7D_PAD_SD1_RESET_B__GPIO5_IO2 0x59 /* vmmc */ > + MX7D_PAD_GPIO1_IO08__SD1_VSELECT 0x59 /* VSELECT */ > + >; > + }; > + > pinctrl_usdhc1: usdhc1grp { > fsl,pins = < > MX7D_PAD_SD1_CMD__SD1_CMD 0x59 > @@ -646,9 +664,28 @@ > MX7D_PAD_SD1_DATA1__SD1_DATA1 0x59 > MX7D_PAD_SD1_DATA2__SD1_DATA2 0x59 > MX7D_PAD_SD1_DATA3__SD1_DATA3 0x59 > - MX7D_PAD_SD1_CD_B__GPIO5_IO0 0x59 /* CD */ > - MX7D_PAD_SD1_WP__GPIO5_IO1 0x59 /* WP */ > - MX7D_PAD_SD1_RESET_B__GPIO5_IO2 0x59 /* vmmc */ > + >; > + }; > + > + pinctrl_usdhc1_100mhz: usdhc1grp_100mhz { > + fsl,pins = < > + MX7D_PAD_SD1_CMD__SD1_CMD 0x5a > + MX7D_PAD_SD1_CLK__SD1_CLK 0x1a > + MX7D_PAD_SD1_DATA0__SD1_DATA0 0x5a > + MX7D_PAD_SD1_DATA1__SD1_DATA1 0x5a > + MX7D_PAD_SD1_DATA2__SD1_DATA2 0x5a > + MX7D_PAD_SD1_DATA3__SD1_DATA3 0x5a > + >; > + }; > + > + pinctrl_usdhc1_200mhz: usdhc1grp_200mhz { > + fsl,pins = < > + MX7D_PAD_SD1_CMD__SD1_CMD 0x5b > + MX7D_PAD_SD1_CLK__SD1_CLK 0x1b > + MX7D_PAD_SD1_DATA0__SD1_DATA0 0x5b > + MX7D_PAD_SD1_DATA1__SD1_DATA1 0x5b > + MX7D_PAD_SD1_DATA2__SD1_DATA2 0x5b > + MX7D_PAD_SD1_DATA3__SD1_DATA3 0x5b > >; > }; > > diff --git a/arch/arm/boot/dts/imx7s.dtsi b/arch/arm/boot/dts/imx7s.dtsi > index e88f53a4c7f4..bee8dc2f614b 100644 > --- a/arch/arm/boot/dts/imx7s.dtsi > +++ b/arch/arm/boot/dts/imx7s.dtsi > @@ -1036,6 +1036,8 @@ > <&clks IMX7D_USDHC1_ROOT_CLK>; > clock-names = "ipg", "ahb", "per"; > bus-width = <4>; > + fsl,tuning-step = <2>; The commit log should mention the move of fsl,tuning-step from board level dts to SoC level. Shawn > + fsl,tuning-start-tap = <20>; > status = "disabled"; > }; > > @@ -1048,6 +1050,8 @@ > <&clks IMX7D_USDHC2_ROOT_CLK>; > clock-names = "ipg", "ahb", "per"; > bus-width = <4>; > + fsl,tuning-step = <2>; > + fsl,tuning-start-tap = <20>; > status = "disabled"; > }; > > @@ -1060,6 +1064,8 @@ > <&clks IMX7D_USDHC3_ROOT_CLK>; > clock-names = "ipg", "ahb", "per"; > bus-width = <4>; > + fsl,tuning-step = <2>; > + fsl,tuning-start-tap = <20>; > status = "disabled"; > }; > > -- > 2.17.1 > _______________________________________________ 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:[~2019-01-13 2:32 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-28 9:28 [PATCH 1/2] arm: dts: imx7d-sdb: add SD3.0 support for usdhc1 BOUGH CHEN 2018-12-28 9:28 ` BOUGH CHEN 2018-12-28 9:28 ` [PATCH 2/2] arm: dts: imx6sx/imx6ul: set the tuning step and start tap for usdhc BOUGH CHEN 2018-12-28 9:28 ` BOUGH CHEN 2019-01-13 2:32 ` Shawn Guo [this message] 2019-01-13 2:32 ` [PATCH 1/2] arm: dts: imx7d-sdb: add SD3.0 support for usdhc1 Shawn Guo
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=20190113023243.GC11426@dragon \ --to=shawnguo@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=fabio.estevam@nxp.com \ --cc=haibo.chen@nxp.com \ --cc=kernel@pengutronix.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=mark.rutland@arm.com \ --cc=robh+dt@kernel.org \ --cc=s.hauer@pengutronix.de \ /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: linkBe 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.