From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mach-shmobile: r8a7790: add SATA support
Date: Fri, 24 May 2013 12:44:20 +0900 [thread overview]
Message-ID: <20130524034418.GG10536@verge.net.au> (raw)
In-Reply-To: <8761y92htl.wl%kuninori.morimoto.gx@renesas.com>
On Thu, May 23, 2013 at 08:11:05PM -0700, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > Because the lager board only seems to expose SATA1 and I was
> > interested in something I could test.
> >
> > I am happy to start caring about SATA0 if you think it is
> > a good idea.
>
> Caring both SATA0/1 are nice IMO :)
>
> > > Can you use like this ?
> > >
> > > static __init void r8a7790_register_sata(int id);
> >
> > Sure, but I'm unsure how you want r8a7790_register_sata to handle id.
> >
> > Is it just for the id field of struct platform_device_info pdevinfo?
> > Or also to switch between resources somehow?
>
> can you check r8a7778_sdhi_init(int id, xxx) ?
> It is caring both id field and resources.
Thanks, I will look at that.
> > > BTW, we need to decide "driver registration function naming" ?
> > > In r8a7778 case, it is using
> > >
> > > r8a7778_add_xxx_device()
> > > r8a7778_add_xxx_devices()
> > >
> > > but r8a7778_register_xxx seems nice naming :)
> >
> > I chose register as it seemed to be consistent with the
> > existing contents of r8a7790_add_standard_devices().
>
> OK, nice.
>
> Do you think other chip (= r8a7778) should follow same naming?
I think it is not so important.
next prev parent reply other threads:[~2013-05-24 3:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 2:06 [PATCH] ARM: mach-shmobile: r8a7790: add SATA support Simon Horman
2013-05-24 2:17 ` Kuninori Morimoto
2013-05-24 2:21 ` Kuninori Morimoto
2013-05-24 2:59 ` Simon Horman
2013-05-24 3:11 ` Kuninori Morimoto
2013-05-24 3:44 ` Simon Horman [this message]
2013-05-24 14:02 ` Sergei Shtylyov
2013-05-25 1:03 ` Simon Horman
2013-05-25 18:32 ` Sergei Shtylyov
2013-05-26 13:25 ` 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=20130524034418.GG10536@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).