From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Russell King <linux@armlinux.org.uk>
Cc: Brian Norris <computersforpeace@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>,
"maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
Doug Berger <opendmb@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 0/4] ARM: brcmstb: Add support for the V7 memory map
Date: Wed, 14 Mar 2018 12:40:10 -0700 [thread overview]
Message-ID: <d1c70d19-2d37-1fcd-5945-721557ab6962@gmail.com> (raw)
In-Reply-To: <20180223210923.544-1-f.fainelli@gmail.com>
On 02/23/2018 01:09 PM, Florian Fainelli wrote:
> Hi all,
>
> This patch series updates the brcmstb.S DEBUG_LL routines to dynamically detect
> one of the latest STB chip: BCM7278. This chip has a different memory map which
> requires use to lookup the main ID register to know whether which register
> physical offset we must use.
>
> As a consequence of doing that, we do a number of things:
>
> - allow the inclusion of cputype.h in assembly files to reduce the duplication
> of constants
> - define the Brahma-B53 and Brahma-B15 main ID register values, which was long
> overdue
> - finaly update brcmstb.S to detect 7278 and offset the base register address
> accordingly
>
> Note that Doug had a slightly different approach in our downstream tree where he
> actually added the same MIDR_* constants similar to what ARM64 has, I took that
> part away in order to minimize the delta, but I can easily submit that patch
> if this is the desired direction moving forward.
Russell, I would be more comfortable taking those changes through our
Broadcom ARM SoC pull requests, since the majority of the changes are in
brcmstb.S, can I get your acknowledgment for the first 3 patches?
Thank you!
>
> Thank you!
>
> Doug Berger (3):
> ARM: Allow this header to be included by assembly files
> ARM: add Broadcom Brahma-B53 main ID definition
> ARM: brcmstb: Add support for the V7 memory map
>
> Florian Fainelli (1):
> ARM: add Broadcom Brahma-B15 main ID definition
>
> arch/arm/include/asm/cputype.h | 15 ++++++++++++---
> arch/arm/include/debug/brcmstb.S | 21 ++++++++++++++++++++-
> 2 files changed, 32 insertions(+), 4 deletions(-)
>
--
Florian
prev parent reply other threads:[~2018-03-14 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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-04-10 20:19 ` Mylène Josserand
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-04-16 22:17 ` Florian Fainelli
2018-02-23 21:09 ` [PATCH 3/4] ARM: add Broadcom Brahma-B15 " 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-04-16 22:17 ` Florian Fainelli
2018-03-14 19:40 ` Florian Fainelli [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=d1c70d19-2d37-1fcd-5945-721557ab6962@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®