linux-kernel - Re: [PATCH V2 0/2] Broadcom's PMB (Power Management Bus) support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b3836eff-ea33-1779-5e33-a569ae2d38e8@gmail.com>
Date:   Tue, 12 Jan 2021 20:46:28 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Rafał Miłecki <zajec5@...il.com>,
        Florian Fainelli <f.fainelli@...il.com>,
        Rob Herring <robh+dt@...nel.org>
Cc:     Philipp Zabel <p.zabel@...gutronix.de>,
        "Rafael J . Wysocki" <rjw@...ysocki.net>,
        Kevin Hilman <khilman@...nel.org>,
        Ulf Hansson <ulf.hansson@...aro.org>,
        devicetree@...r.kernel.org, bcm-kernel-feedback-list@...adcom.com,
        linux-kernel@...r.kernel.org,
        Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: [PATCH V2 0/2] Broadcom's PMB (Power Management Bus) support



On 12/14/2020 10:07 AM, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@...ecki.pl>
> 
> PMB is a hardware block used for powering SoC devices like PCIe, USB,
> SATA. Initially I planned to treat it as a reset controller and Philipp
> pointed out in review that PMB driver should use a power subsystem.
> 
> This is my refactored support.
> 
> ***
> 
> Please note one difference when compared to the initial reset attempt.
> 
> As I store info about SoC devices in the driver now, I had to put
> support for multiple buses there. That's required to avoid things like:
> 
> compatible = "brcm,bcm4908-pmb-no-1";
> compatible = "brcm,bcm4908-pmb-no-2";
> 
> So now a single "reg" covers bigger buses (e.g. 0x40) in size, see:
> 
> reg = <0x802800e0 0x40>;
> 
> Other SoCs my use something like:
> 
> reg = <0x802800e0 0x20>;
> reg = <0x802800e0 0x60>;
> 
> ***
> 
> AFAIU this should go through Florian's tree. I based in on top of the
> soc-arm64/next.
> 
> V2: Use drivers/soc/bcm/bcm63xx/ and add Kconfig help message

Series applied to drivers/next, thanks!
-- 
Florian