SUPERH platform development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: r8a7779: Add PCIe clock support
Date: Mon, 18 Mar 2013 17:24:00 +0000	[thread overview]
Message-ID: <51474DB0.2010705@cogentembedded.com> (raw)
In-Reply-To: <1363624732-24660-1-git-send-email-phil.edworthy@renesas.com>

Hello.

On 18-03-2013 21:20, phil.edworthy@renesas.com wrote:

>>> Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
>>> ---
>>> Depends on "r8a7779: Add Display Unit clock support"

>>>    arch/arm/mach-shmobile/clock-r8a7779.c |    3 +++
>>>    1 files changed, 3 insertions(+), 0 deletions(-)

>>> diff --git a/arch/arm/mach-shmobile/clock-r8a7779.c b/arch/arm/
>> mach-shmobile/clock-r8a7779.c
>>> index 9ea6087..a017418 100644
>>> --- a/arch/arm/mach-shmobile/clock-r8a7779.c
>>> +++ b/arch/arm/mach-shmobile/clock-r8a7779.c
>> [...]
>>> @@ -182,6 +184,7 @@ static struct clk_lookup lookups[] = {
>>>       CLKDEV_DEV_ID("sh_mobile_sdhi.2", &mstp_clks[MSTP321]), /* SDHI2
> */
>>>       CLKDEV_DEV_ID("sh_mobile_sdhi.3", &mstp_clks[MSTP320]), /* SDHI3
> */
>>>       CLKDEV_DEV_ID("rcar-du.0", &mstp_clks[MSTP103]), /* DU */
>>> +   CLKDEV_DEV_ID("rcar-pcie.0", &mstp_clks[MSTP116]), /* PCIe */

>>     Hm, why this name? Is there going to be a driver somewhere in
>> drivers/pci/,
>> and is there goiung to be more than one instance of PCIe?

> Yes, I am writing a PCIe driver at the moment,

    But I assume it will live under arch/arm/mach-shmobile/, and will it be a 
true driver?

> the same hardware is used
> on a number of R-Car devices. For r8a7779 there is only one instance,

    Then remove ".0" please, and use 'id' field of -1 in the platform device 
(if there's going to be any).

> Thanks
> Phil

WBR, Sergei


  parent reply	other threads:[~2013-03-18 17:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 16:38 [PATCH] ARM: shmobile: r8a7779: Add PCIe clock support Phil Edworthy
2013-03-18 17:13 ` Sergei Shtylyov
2013-03-18 17:20 ` phil.edworthy
2013-03-18 17:24 ` Sergei Shtylyov [this message]
2013-03-19  0:30 ` Simon Horman
2013-03-19  8:58 ` phil.edworthy
2013-03-19  9:08 ` phil.edworthy

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=51474DB0.2010705@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