From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 05/11] ARM: shmobile: r8a7778: cleanup registration of i2c
Date: Thu, 11 Jul 2013 11:35:28 +0000 [thread overview]
Message-ID: <51DE9880.5020302@cogentembedded.com> (raw)
In-Reply-To: <87fvvlfqen.wl%kuninori.morimoto.gx@renesas.com>
Hello.
On 11-07-2013 12:32, Kuninori Morimoto wrote:
> i2c-rcar driver which doesn't need platform data at the time of
> registration can be registerd on SoC.
> And, registering these drivers in the SoC code can avoid
> unwanted device numbering issue.
> (ex. the i2c3 device number will be i2c.0 if i2c3 only registered)
> This patch registers it on SoC code as cleanup C code
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
How about pinmux? If you register all 4 I2C controllers at the SoC
level (that's what our patch was doing), you'll need to register all the
I2C pin groups in the board file, no?
WBR, Sergei
prev parent reply other threads:[~2013-07-11 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 8:32 [PATCH 05/11] ARM: shmobile: r8a7778: cleanup registration of i2c Kuninori Morimoto
2013-07-11 11:35 ` 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=51DE9880.5020302@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;
as well as URLs for NNTP newsgroup(s).