Devicetree
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Jayachandran C <jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
	Florian Fainelli
	<florian.fainelli-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH] arm64: dts: vulcan: Update PCI ranges
Date: Wed, 30 Mar 2016 00:30:03 +0200	[thread overview]
Message-ID: <163715315.6u7avlh5g3@wuerfel> (raw)
In-Reply-To: <56E3278F.5090200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Friday 11 March 2016 12:16:15 Florian Fainelli wrote:
> On 27/02/16 23:37, Jayachandran C wrote:
> > The PCI memory windows available in vulcan.dtsi are limited to 128MB
> > for 32-bit BARs, and 4GB for 64-bit BARs. Given the memory mapped IO
> > space available in arm64, these windows can be increased substantially
> > to support more use cases.
> > 
> > The change increases the 32-bit window to 256MB and the 64-bit window
> > to 128 GB. The firmware on vulcan boards will use these ranges as well.
> > 
> > PCI IO windows are not supported on Vulcan, so remove them instead of
> > keeping an unused value.
> > 
> > Signed-off-by: Jayachandran C <jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
> > ---
> > 
> > This is an update to the patch with subject
> > "arm64: Broadcom Vulcan support"
> > I had sent earlier, please fold it into that patch if possible
> 
> Arnd, I do not have any other Broadcom ARM64 DT changes for 4.6 to be
> sent at the moment, do you mind taking this patch directly?
> 
> Feel free to add my:
> 
> Signed-off-by: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> 
> 

Applied to the 4.6 fixes branch now, thanks!

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2016-03-29 22:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20 14:19 [PATCH v2 0/5] Support for Broadcom Vulcan ARM64 processor Jayachandran C
     [not found] ` <1455977964-8099-1-git-send-email-jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-02-20 14:19   ` [PATCH v2 1/5] arm64: Broadcom Vulcan support Jayachandran C
2016-02-20 14:19   ` [PATCH v2 2/5] dt-bindings: Add documentation for Broadcom Vulcan Jayachandran C
2016-02-20 14:19   ` [PATCH v2 3/5] arm64: defconfig: Add Broadcom Vulcan to defconfig Jayachandran C
2016-02-20 14:19   ` [PATCH v2 4/5] arm64: cputype info for Broadcom Vulcan Jayachandran C
2016-02-20 14:19   ` [PATCH v2 5/5] MAINTAINERS: Add entry for Broadcom Vulcan SoC Jayachandran C
2016-02-20 19:50   ` [PATCH v2 0/5] Support for Broadcom Vulcan ARM64 processor Florian Fainelli
     [not found]     ` <56C8C38E.50007-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-27  6:52       ` [PATCH v3 1/5] arm64: Broadcom Vulcan support Jayachandran C
     [not found]         ` <1456555925-11583-1-git-send-email-jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-02-27 20:03           ` Florian Fainelli
     [not found]             ` <56D200F5.7010505-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-02-28  7:37               ` [PATCH] arm64: dts: vulcan: Update PCI ranges Jayachandran C
     [not found]                 ` <1456645037-12978-1-git-send-email-jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-03-11 20:16                   ` Florian Fainelli
     [not found]                     ` <56E3278F.5090200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-29 22:30                       ` Arnd Bergmann [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=163715315.6u7avlh5g3@wuerfel \
    --to=arnd-r2ngtmty4d4@public.gmane.org \
    --cc=bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=florian.fainelli-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
    --cc=jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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