Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-mips <linux-mips@linux-mips.org>,
	John Crispin <blogic@openwrt.org>
Subject: Re: [PATCH 3/4] MIPS: pci-ar724x: remove static PCI IO/MEM resources
Date: Sun, 03 Feb 2013 15:18:52 +0400	[thread overview]
Message-ID: <510E479C.4020305@mvista.com> (raw)
In-Reply-To: <1359889185-15779-1-git-send-email-juhosg@openwrt.org>

Hello.

On 03-02-2013 14:59, Gabor Juhos wrote:

> Static resources become impractical when multiple
> PCI controllers are present. Move the resources
> into the platform device registration code and
> change the probe routine to get those from there
> platform device's resources.

> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
> ---
>   arch/mips/ath79/pci.c      |   21 ++++++++++++++++++++-
>   arch/mips/pci/pci-ar724x.c |   40 ++++++++++++++++++++++++----------------
>   2 files changed, 44 insertions(+), 17 deletions(-)

> diff --git a/arch/mips/ath79/pci.c b/arch/mips/ath79/pci.c
> index d90e071..45d1112 100644
> --- a/arch/mips/ath79/pci.c
> +++ b/arch/mips/ath79/pci.c
> @@ -139,10 +139,13 @@ static struct platform_device *
>   ath79_register_pci_ar724x(int id,
>   			  unsigned long cfg_base,
>   			  unsigned long ctrl_base,
> +			  unsigned long mem_base,
> +			  unsigned long mem_size,
> +			  unsigned long io_base,
>   			  int irq)
>   {
>   	struct platform_device *pdev;
> -	struct resource res[3];
> +	struct resource res[5];
>
>   	memset(res, 0, sizeof(res));
>
> @@ -160,6 +163,16 @@ ath79_register_pci_ar724x(int id,
>   	res[2].start = irq;
>   	res[2].end = irq;
>
> +	res[3].name = "mem_base";
> +	res[3].flags = IORESOURCE_MEM;
> +	res[3].start = mem_base;
> +	res[3].end = mem_base + mem_size - 1;
> +
> +	res[4].name = "io_base";
> +	res[4].flags = IORESOURCE_IO;
> +	res[4].start = io_base;
> +	res[4].end = io_base;

    One I/O port, hm? What is it good for?

WBR, Sergei

  reply	other threads:[~2013-02-03 11:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-03 10:58 [PATCH 1/4] MIPS: ath79: allow to specify bus number in PCI IRQ maps Gabor Juhos
2013-02-03 10:58 ` [PATCH 2/4] MIPS: pci-ar724x: use dynamically allocated PCI controller structure Gabor Juhos
2013-02-03 10:59 ` [PATCH 3/4] MIPS: pci-ar724x: remove static PCI IO/MEM resources Gabor Juhos
2013-02-03 11:18   ` Sergei Shtylyov [this message]
2013-02-03 12:31     ` Gabor Juhos
2013-02-04 12:13       ` Sergei Shtylyov
2013-02-04 13:14         ` Gabor Juhos
2013-02-03 11:00 ` [PATCH 4/4] MIPS: pci-ar724x: use per-controller IRQ base Gabor Juhos
2013-02-03 15:52 ` [PATCH 5/4] MIPS: pci-ar724x: setup command register of the PCI controller Gabor Juhos

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=510E479C.4020305@mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=blogic@openwrt.org \
    --cc=juhosg@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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