From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 5/6 v2] ARM: shmobile: r8a7778: cleanup registration of hspi
Date: Fri, 26 Jul 2013 13:18:59 +0000 [thread overview]
Message-ID: <51F27743.1010005@cogentembedded.com> (raw)
In-Reply-To: <87zjt9bwp7.wl%kuninori.morimoto.gx@renesas.com>
Hello.
On 26-07-2013 11:35, Kuninori Morimoto wrote:
> sh-hspi driver which doesn't need platform data at the time of
> registration can be registerd on SoC.
I repeat my question about the pinmux settings.
> And, registering these drivers in the SoC code can avoid
> unwanted device numbering issue.
> (ex. the hspi2 device number will be spi.0 if hspi2 only registered)
This IMHO is a non-issue.
> This patch registers it on SoC code as cleanup C code
Why not call the patch ARM: shmobile: r8a7778: register HSPI in SoC code"
then?
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
WBR, Sergei
next prev parent reply other threads:[~2013-07-26 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 7:35 [PATCH 5/6 v2] ARM: shmobile: r8a7778: cleanup registration of hspi Kuninori Morimoto
2013-07-26 13:18 ` Sergei Shtylyov [this message]
2013-07-30 2:36 ` 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=51F27743.1010005@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).