[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d081a505-487d-eb29-94fd-5e1f638bba29@gmail.com>
Date: Fri, 5 Feb 2021 08:56:55 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
f.fainelli@...il.com, bcm-kernel-feedback-list@...adcom.com,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>
Cc: phil@...pberrypi.com, wahrenst@....net,
linux-kernel@...r.kernel.org
Subject: Re: [RFC/PATCH 05/11] soc: bcm: bcm2835-power: Add support for
BCM2711's ARSAN ASB
On 2/5/21 5:52 AM, Nicolas Saenz Julienne wrote:
> In BCM2711 the new ARGON ASB took over V3D. The old ASB is still present
> with the ISP and H264 bits, and V3D is in the same place in the new ASB
> as the old one.
>
> Use the fact that 'pm->arsan_asb' is populated as a hint that we're on
> BCM2711. On top of that introduce the macro ASB_BASE() which will select
> the correct ASB register base, based on whether we're trying to access
> V3D and which platform we're on.
Your subject has a typo, you most likely intended to write "Argon ASB",
right?
I will review the series a little later today.
--
Florian
Powered by blists - more mailing lists