From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>,
Gaku Inami <gaku.inami.xw@bp.renesas.com>,
linux-i2c@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: koelsch: Remove non-existent i2c6 pinmux
Date: Tue, 12 Aug 2014 22:36:22 +0900 [thread overview]
Message-ID: <20140812133622.GC10875@verge.net.au> (raw)
In-Reply-To: <1407848593-23040-1-git-send-email-geert+renesas@glider.be>
On Tue, Aug 12, 2014 at 03:03:13PM +0200, Geert Uytterhoeven wrote:
> On r8a7791, i2c6 (aka iic3) doesn't need pinmux, but the koelsch dts
> refers to non-existent pinmux configuration data:
>
> pinmux core: sh-pfc does not support function i2c6
> sh-pfc e6060000.pfc: invalid function i2c6 in map table
>
> Remove it to fix this.
>
> Fixes: commit 1d41f36a68c0f4e9b01d563ce33bab5201858b54 ("ARM: shmobile:
> koelsch dts: Add VDD MPU regulator for DVFS")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Thanks Geert. Does this manifest as a run-time problem?
Regardless, it looks like I should queue this up as
a fix for v3.17. Is that your thinking too?
> ---
> arch/arm/boot/dts/r8a7791-koelsch.dts | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/arch/arm/boot/dts/r8a7791-koelsch.dts b/arch/arm/boot/dts/r8a7791-koelsch.dts
> index 7966dace64ce..951a5c55003e 100644
> --- a/arch/arm/boot/dts/r8a7791-koelsch.dts
> +++ b/arch/arm/boot/dts/r8a7791-koelsch.dts
> @@ -275,11 +275,6 @@
> renesas,function = "msiof0";
> };
>
> - i2c6_pins: i2c6 {
> - renesas,groups = "i2c6";
> - renesas,function = "i2c6";
> - };
> -
> usb0_pins: usb0 {
> renesas,groups = "usb0";
> renesas,function = "usb0";
> @@ -477,8 +472,6 @@
> };
>
> &i2c6 {
> - pinctrl-names = "default";
> - pinctrl-0 = <&i2c6_pins>;
> status = "okay";
> clock-frequency = <100000>;
>
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-08-12 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 13:03 [PATCH] ARM: shmobile: koelsch: Remove non-existent i2c6 pinmux Geert Uytterhoeven
2014-08-12 13:36 ` Simon Horman [this message]
[not found] ` <20140812133622.GC10875-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2014-08-12 13:48 ` Geert Uytterhoeven
[not found] ` <CAMuHMdXif88Tdo-4doF=B6x5zdrcP8banSLOBVgZd59_EEXspA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-13 8:04 ` Simon Horman
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=20140812133622.GC10875@verge.net.au \
--to=horms@verge.net.au \
--cc=gaku.inami.xw@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=wsa@the-dreams.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: 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).