linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valentine <valentine.barshak@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 3/6] arm: shmobile: Add internal PCI support to RCAR Gen2
Date: Wed, 02 Oct 2013 12:16:21 +0000	[thread overview]
Message-ID: <524C0E95.9020001@cogentembedded.com> (raw)
In-Reply-To: <1380652251-8143-4-git-send-email-valentine.barshak@cogentembedded.com>

On 10/02/2013 04:13 AM, Kuninori Morimoto wrote:
>
> Hi Valentine
>

Hi Morimoto-san,

>> This adds internal PCI controller support to RCAR Gen2 platform.
>> There are 3 PCI controllers available with only a EHCI/OHCI
>> device present on each one. The controllers do not support
>> I/O port space mapping and it is not needed here.
>>
>> Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
>> ---
>>
>>   arch/arm/mach-shmobile/Kconfig         |   1 +
>>   arch/arm/mach-shmobile/Makefile        |   4 +
>>   arch/arm/mach-shmobile/pci-rcar-gen2.c | 339 +++++++++++++++++++++++++++++++++
>>   3 files changed, 344 insertions(+)
> (snip)
>> +static struct platform_driver rcar_pci_driver = {
>> +	.driver = {
>> +		.name = "pci-rcar-gen2",
>> +	},
>> +};
>> +
>> +static int __init rcar_pci_init(void)
>> +{
>> +	return platform_driver_probe(&rcar_pci_driver, rcar_pci_probe);
>> +}
>
> driver should exist under ${LINUX}/driver, not ${LINUX}/arch/arm/

Thanks, I'll move it to drivers/pci/host.

(was mislead by some PCI drivers still residing in arch/arm
for other platforms.)

>
> Best regards
> ---
> Kuninori Morimoto
>

Thanks,
Val.

      parent reply	other threads:[~2013-10-02 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01 18:30 [PATCH 3/6] arm: shmobile: Add internal PCI support to RCAR Gen2 Valentine Barshak
2013-10-02  0:13 ` Kuninori Morimoto
2013-10-02 12:16 ` Valentine [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=524C0E95.9020001@cogentembedded.com \
    --to=valentine.barshak@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).