From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: marzen pinctl conflict for renesas-next-20130515v2 + v3.10-rc1
Date: Wed, 15 May 2013 12:52:23 +0000 [thread overview]
Message-ID: <51938507.8010306@cogentembedded.com> (raw)
In-Reply-To: <20130515084658.GA19115@verge.net.au>
Hello.
On 15-05-2013 16:38, Laurent Pinchart wrote:
>>> I am preparing to rebase the branches of the renesas tree which
>>> are targeted for v3.11 on top of v3.10-rc1. In the course of
>>> doing so I have noticed a problem on the marzen board which appears
>>> to be related to pinmux.
>>> On boot, using the default config I see the following:
>>> sh-pfc pfc-r8a7779: pin GP_4_22 already requested by sh-hspi.0; cannot
>>> claim for ehci-platform.0 sh-pfc pfc-r8a7779: pin-150 (ehci-platform.0)
>>> status -22
>>> sh-pfc pfc-r8a7779: could not request pin 150 on device sh-pfc
>> I have already reported this. Laurent prepared a fix, which I somewhat
>> criticized, but he never published a second version.
> I've posted v2 earlier today.
Saw it after replying to Simon, thanks.
WBR, Sergei
prev parent reply other threads:[~2013-05-15 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 8:46 marzen pinctl conflict for renesas-next-20130515v2 + v3.10-rc1 Simon Horman
2013-05-15 12:36 ` Sergei Shtylyov
2013-05-15 12:38 ` Laurent Pinchart
2013-05-15 12:52 ` Sergei Shtylyov [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=51938507.8010306@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-sh@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