From: Shawn Guo <shawnguo@kernel.org>
To: eu@felipetonello.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Sascha Hauer <kernel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH] ARM: dts: fix usb pin control for imx-rex dts
Date: Thu, 24 Sep 2015 05:15:15 -0700 [thread overview]
Message-ID: <20150924121514.GO3529@tiger> (raw)
In-Reply-To: <1442425232-21451-1-git-send-email-eu@felipetonello.com>
On Wed, Sep 16, 2015 at 06:40:32PM +0100, eu@felipetonello.com wrote:
> From: "Felipe F. Tonello" <eu@felipetonello.com>
>
> This fixes a duplicated pin control causing this error:
>
> imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_GPIO_1 already
> requested by regulators:regulator@2; cannot claim for 2184000.usb
> imx6q-pinctrl 20e0000.iomuxc: pin-137 (2184000.usb) status -22
> imx6q-pinctrl 20e0000.iomuxc: could not request pin 137
> (MX6Q_PAD_GPIO_1) from group usbotggrp on device 20e0000.iomuxc
> imx_usb 2184000.usb: Error applying setting, reverse things
> back
> imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_EIM_D31 already
> requested by regulators:regulator@1; cannot claim for 2184200.usb
> imx6q-pinctrl 20e0000.iomuxc: pin-52 (2184200.usb) status -22
> imx6q-pinctrl 20e0000.iomuxc: could not request pin 52 (MX6Q_PAD_EIM_D31)
> from group usbh1grp on device 20e0000.iomuxc
> imx_usb 2184200.usb: Error applying setting, reverse things
> back
>
> Signed-off-by: Felipe F. Tonello <eu@felipetonello.com>
Applied and copied stable, thanks.
prev parent reply other threads:[~2015-09-24 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 17:40 eu
2015-09-21 8:17 ` Felipe Tonello
2015-09-23 15:37 ` Felipe Tonello
2015-09-24 12:15 ` 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=20150924121514.GO3529@tiger \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eu@felipetonello.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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
Powered by JetHome