From: Bjorn Helgaas <bhelgaas@google.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] of/PCI: Add IORESOURCE_MEM_64 for 64-bit resource
Date: Wed, 8 Apr 2015 10:33:19 -0500 [thread overview]
Message-ID: <20150408153319.GM10892@google.com> (raw)
In-Reply-To: <CAL_JsqLx4dB9CG0t0pCV89VxECXVTZyyiGfq=awNJSgfD50Raw@mail.gmail.com>
On Tue, Apr 07, 2015 at 08:30:58PM -0500, Rob Herring wrote:
> On Tue, Apr 7, 2015 at 7:24 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> > For device resource PREF bit setting under bridge 64-bit pref resource,
> > we need to make sure only set PREF for 64bit resource, so set IORESOUCE_MEM_64
> > for 64bit resource during of device resource flags parsing.
> >
> > Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261
> > Link: https://bugzilla.kernel.org/show_bug.cgi?id=96241
> > Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> > Cc: Grant Likely <grant.likely@linaro.org>
> > Cc: Rob Herring <robh+dt@kernel.org>
> > Cc: devicetree@vger.kernel.org
>
> Acked-by: Rob Herring <robh@kernel.org>
>
> Bjorn, are you collecting these or should I apply?
I am not collecting them, at least not yet. These seem a little more on
the OF side of the fence than PCI. They are a little intertwingled with
the sparc PCI bridge window issue, and Ben has some concerns, so maybe
we'll have to figure out what makes the most sense when that gets sorted
out.
I'm still curious whether all these functions can be consolidated. If
that's possible, it would be much nicer than having to fix all the copies.
Bjorn
> > ---
> > drivers/of/address.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > Index: linux-2.6/drivers/of/address.c
> > ===================================================================
> > --- linux-2.6.orig/drivers/of/address.c
> > +++ linux-2.6/drivers/of/address.c
> > @@ -128,9 +128,11 @@ static unsigned int of_bus_pci_get_flags
> > flags |= IORESOURCE_IO;
> > break;
> > case 0x02: /* 32 bits */
> > - case 0x03: /* 64 bits */
> > flags |= IORESOURCE_MEM;
> > break;
> > + case 0x03: /* 64 bits */
> > + flags |= IORESOURCE_MEM | IORESOURCE_MEM_64;
> > + break;
> > }
> > if (w & 0x40000000)
> > flags |= IORESOURCE_PREFETCH;
prev parent reply other threads:[~2015-04-08 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 0:24 [PATCH] of/PCI: Add IORESOURCE_MEM_64 for 64-bit resource Yinghai Lu
[not found] ` <1428452680-24861-1-git-send-email-yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-04-08 1:30 ` Rob Herring
2015-04-08 15:33 ` Bjorn Helgaas [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=20150408153319.GM10892@google.com \
--to=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
--cc=yinghai@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