linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Andrew Murray <Andrew.Murray@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Thierry Reding <thierry.reding@avionic-design.de>,
	linux-pci@vger.kernel.org
Subject: Re: [RFC PATCH v2] of/pci: Provide support for parsing PCI DT ranges property
Date: Fri, 1 Mar 2013 02:24:00 +0100	[thread overview]
Message-ID: <CACRpkda9pVafqMRrZ-h6ry6X57754bb4pWRW8CWbF0n37pkVNA@mail.gmail.com> (raw)
In-Reply-To: <20130221154709.GA26660@arm.com>

On Thu, Feb 21, 2013 at 4:47 PM, Andrew Murray <Andrew.Murray@arm.com> wrote:

> DT bindings for PCI host bridges often use the ranges property to describe
> memory and IO ranges - this binding tends to be the same across architectures
> yet several parsing implementations exist, e.g. arch/mips/pci/pci.c,
> arch/powerpc/kernel/pci-common.c, arch/sparc/kernel/pci.c and
> arch/microblaze/pci/pci-common.c (clone of PPC). Some of these duplicate
> functionality provided by drivers/of/address.c.

Hm I wanted to test but was blocked by this:

Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

Making the raw patch look like this:

=09const u32 *ranges;
-=09int rlen;
-=09int pna =3D of_n_addr_cells(dev);
-=09int np =3D pna + 5;
 =09int memno =3D 0, isa_hole =3D -1;

I bet the other ARM guys can help you get the format right
somehow... can't you just use git send-email?

Yours,
Linus Walleij

  reply	other threads:[~2013-03-01  1:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21 15:47 [RFC PATCH v2] of/pci: Provide support for parsing PCI DT ranges property Andrew Murray
2013-03-01  1:24 ` Linus Walleij [this message]
2013-03-20 20:05 ` Thomas Petazzoni
2013-03-27 12:50   ` Linus Walleij
2013-03-27 12:55     ` Thomas Petazzoni

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=CACRpkda9pVafqMRrZ-h6ry6X57754bb4pWRW8CWbF0n37pkVNA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=Andrew.Murray@arm.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=thierry.reding@avionic-design.de \
    --cc=thomas.petazzoni@free-electrons.com \
    /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).