From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx6q-apalis: mux RESET_MOCI# signal
Date: Mon, 10 Sep 2018 09:09:14 +0800 [thread overview]
Message-ID: <20180910010913.GD21992@dragon> (raw)
In-Reply-To: <20180906234658.12205-1-stefan@agner.ch>
On Thu, Sep 06, 2018 at 04:46:58PM -0700, Stefan Agner wrote:
> The pinctrl properties on the IOMUXC node get overwritten by the
> carrier board level device tree, hence the pinctrl_reset_moci
> pinctrl does not get applied.
>
> Associate the pinctrl_reset_moci pinctrl with the PCIe node where
> we also make use of the pin as a reset GPIO.
>
> Since the pin is muxed as a GPIO by default not muxing it explicitly
> worked fine in practise.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Stefan Agner <stefan@agner.ch>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
marcel.ziswiler@toradex.com, s.hauer@pengutronix.de,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
max.krummenacher@toradex.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: imx6q-apalis: mux RESET_MOCI# signal
Date: Mon, 10 Sep 2018 09:09:14 +0800 [thread overview]
Message-ID: <20180910010913.GD21992@dragon> (raw)
In-Reply-To: <20180906234658.12205-1-stefan@agner.ch>
On Thu, Sep 06, 2018 at 04:46:58PM -0700, Stefan Agner wrote:
> The pinctrl properties on the IOMUXC node get overwritten by the
> carrier board level device tree, hence the pinctrl_reset_moci
> pinctrl does not get applied.
>
> Associate the pinctrl_reset_moci pinctrl with the PCIe node where
> we also make use of the pin as a reset GPIO.
>
> Since the pin is muxed as a GPIO by default not muxing it explicitly
> worked fine in practise.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Stefan Agner <stefan@agner.ch>
Cc: s.hauer@pengutronix.de, robh+dt@kernel.org, mark.rutland@arm.com,
marcel.ziswiler@toradex.com, max.krummenacher@toradex.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: imx6q-apalis: mux RESET_MOCI# signal
Date: Mon, 10 Sep 2018 09:09:14 +0800 [thread overview]
Message-ID: <20180910010913.GD21992@dragon> (raw)
In-Reply-To: <20180906234658.12205-1-stefan@agner.ch>
On Thu, Sep 06, 2018 at 04:46:58PM -0700, Stefan Agner wrote:
> The pinctrl properties on the IOMUXC node get overwritten by the
> carrier board level device tree, hence the pinctrl_reset_moci
> pinctrl does not get applied.
>
> Associate the pinctrl_reset_moci pinctrl with the PCIe node where
> we also make use of the pin as a reset GPIO.
>
> Since the pin is muxed as a GPIO by default not muxing it explicitly
> worked fine in practise.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
Applied, thanks.
next prev parent reply other threads:[~2018-09-10 1:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 23:46 [PATCH] ARM: dts: imx6q-apalis: mux RESET_MOCI# signal Stefan Agner
2018-09-06 23:46 ` Stefan Agner
2018-09-10 1:09 ` Shawn Guo [this message]
2018-09-10 1:09 ` Shawn Guo
2018-09-10 1:09 ` 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=20180910010913.GD21992@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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 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.