From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Cc: Doug Berger <opendmb@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Brian Norris <computersforpeace@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>,
Vladimir Murzin <vladimir.murzin@arm.com>,
Philippe Ombredanne <pombredanne@nexb.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] ARM: brcmstb: Add support for the V7 memory map
Date: Mon, 16 Apr 2018 15:17:34 -0700 [thread overview]
Message-ID: <20180416221734.31965-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20180223210923.544-5-f.fainelli@gmail.com>
On Fri, 23 Feb 2018 13:09:23 -0800, Florian Fainelli <f.fainelli@gmail.com> wrote:
> From: Doug Berger <opendmb@gmail.com>
>
> The 7278 device is the first device that includes support for the V7
> memory map developed for use in 64-bit architecture brcmstb devices.
> This map relocates the register physical offset from 0xF0000000 to
> 0x0000000008000000.
>
> Since the ARM PERIPHBASE value is also relocated in the V7 memory map
> we can use its value to determine whether this device uses the new
> V7 memory map and therefore where to look for the SUN_TOP_CTRL
> register used to identify the chip family.
>
> Signed-off-by: Doug Berger <opendmb@gmail.com>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
Applied to soc/next, thanks!
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: brcmstb: Add support for the V7 memory map
Date: Mon, 16 Apr 2018 15:17:34 -0700 [thread overview]
Message-ID: <20180416221734.31965-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20180223210923.544-5-f.fainelli@gmail.com>
On Fri, 23 Feb 2018 13:09:23 -0800, Florian Fainelli <f.fainelli@gmail.com> wrote:
> From: Doug Berger <opendmb@gmail.com>
>
> The 7278 device is the first device that includes support for the V7
> memory map developed for use in 64-bit architecture brcmstb devices.
> This map relocates the register physical offset from 0xF0000000 to
> 0x0000000008000000.
>
> Since the ARM PERIPHBASE value is also relocated in the V7 memory map
> we can use its value to determine whether this device uses the new
> V7 memory map and therefore where to look for the SUN_TOP_CTRL
> register used to identify the chip family.
>
> Signed-off-by: Doug Berger <opendmb@gmail.com>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
Applied to soc/next, thanks!
--
Florian
next prev parent reply other threads:[~2018-04-16 22:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 21:09 [PATCH 0/4] ARM: brcmstb: Add support for the V7 memory map Florian Fainelli
2018-02-23 21:09 ` Florian Fainelli
2018-02-23 21:09 ` [PATCH 1/4] ARM: Allow this header to be included by assembly files Florian Fainelli
2018-02-23 21:09 ` Florian Fainelli
2018-04-10 20:19 ` Mylène Josserand
2018-04-10 20:19 ` Mylène Josserand
2018-04-16 22:17 ` Florian Fainelli
2018-04-16 22:17 ` Florian Fainelli
2018-02-23 21:09 ` [PATCH 2/4] ARM: add Broadcom Brahma-B53 main ID definition Florian Fainelli
2018-02-23 21:09 ` Florian Fainelli
2018-04-16 22:17 ` Florian Fainelli
2018-04-16 22:17 ` Florian Fainelli
2018-02-23 21:09 ` [PATCH 3/4] ARM: add Broadcom Brahma-B15 " Florian Fainelli
2018-02-23 21:09 ` Florian Fainelli
2018-04-16 22:17 ` Florian Fainelli
2018-04-16 22:17 ` Florian Fainelli
2018-02-23 21:09 ` [PATCH 4/4] ARM: brcmstb: Add support for the V7 memory map Florian Fainelli
2018-02-23 21:09 ` Florian Fainelli
2018-04-16 22:17 ` Florian Fainelli [this message]
2018-04-16 22:17 ` Florian Fainelli
2018-03-14 19:40 ` [PATCH 0/4] " Florian Fainelli
2018-03-14 19:40 ` Florian Fainelli
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=20180416221734.31965-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.0xf0@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=opendmb@gmail.com \
--cc=pombredanne@nexb.com \
--cc=vladimir.murzin@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.