linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Richard Zhu <r65037@freescale.com>
Cc: linux-pci-owner@vger.kernel.org, stable@vger.kernel.org,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] PCI: imx6: enable pcie on imx6qdl sabresd and sabreauto
Date: Mon, 22 Sep 2014 11:36:16 +0200	[thread overview]
Message-ID: <1411378576.2599.3.camel@pengutronix.de> (raw)
In-Reply-To: <1411376498-14653-2-git-send-email-r65037@freescale.com>

Am Montag, den 22.09.2014, 17:01 +0800 schrieb Richard Zhu:
> - enable pcie support on imx6qdl sabresd and asbreauto boards.
> - sabresd board has the pcie power on and reset gpios, but
> sabreauto doesn't have these two gpios.
> 
> Signed-off-by: Richard Zhu <r65037@freescale.com>
> ---
>  arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 4 ++++
>  arch/arm/boot/dts/imx6qdl-sabresd.dtsi   | 2 ++
>  2 files changed, 6 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/imx6qdl-sabreauto.dtsi b/arch/arm/boot/dts/imx6qdl-sabreauto.dtsi
> index 009abd6..d6040a5 100644
> --- a/arch/arm/boot/dts/imx6qdl-sabreauto.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl-sabreauto.dtsi
> @@ -410,6 +410,10 @@
>  	};
>  };
>  
> +&pcie {
> +	status = "okay";
> +};
> +
>  &pwm3 {
>  	pinctrl-names = "default";
>  	pinctrl-0 = <&pinctrl_pwm3>;
> diff --git a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> index ec43dde..c2d3224 100644
> --- a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> @@ -396,6 +396,7 @@
>  
>  		pinctrl_pcie: pciegrp {
>  			fsl,pins = <
> +				MX6QDL_PAD_EIM_D19__GPIO3_IO19	0x80000000
>  				MX6QDL_PAD_GPIO_17__GPIO7_IO12	0x80000000
>  			>;
>  		};
> @@ -502,6 +503,7 @@
>  &pcie {
>  	pinctrl-names = "default";
>  	pinctrl-0 = <&pinctrl_pcie>;
> +	power-on-gpio = <&gpio3 19 0>;
>  	reset-gpio = <&gpio7 12 0>;
>  	status = "okay";
>  };

This hunk is wrong. There is no "power-on-gpio" in the binding anymore.
Also there is already a change in Shawns tree to model this as a
always-on regulator. If we really want to control pci bus power this
needs to be done through this regulator, not some arbitrary gpio hack.

Also I don't see why this would be stable material.

Regards,
Lucas
-- 
Pengutronix e.K.             | Lucas Stach                 |
Industrial Linux Solutions   | http://www.pengutronix.de/  |


  reply	other threads:[~2014-09-22  9:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22  9:01 Richard Zhu
2014-09-22  9:01 ` [PATCH RFC 1/2] PCI: imx6: enable pcie on imx6qdl sabresd and sabreauto Richard Zhu
2014-09-22  9:36   ` Lucas Stach [this message]
2014-09-22  9:55     ` Hong-Xing.Zhu
2014-09-22 13:15   ` Greg KH
2014-09-23  3:11     ` Hong-Xing.Zhu
2014-09-22  9:01 ` [PATCH RFC 2/2] PCI: imx6: add imx6sx pcie support Richard Zhu
2014-09-22 10:02   ` Lucas Stach
2014-09-22 10:31     ` Hong-Xing.Zhu
2014-09-22 10:48     ` Hong-Xing.Zhu
2014-09-22 13:15   ` Greg KH
2014-09-23  3:11     ` Hong-Xing.Zhu

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=1411378576.2599.3.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=linux-pci-owner@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=r65037@freescale.com \
    --cc=stable@vger.kernel.org \
    /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).