linux-kernel - Re: [PATCH v3 0/2] SoC driver for Broadcom STB DPFE

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Thu, 24 Aug 2017 17:54:42 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Markus Mayer <code@...yer.net>, Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Gregory Fong <gregory.0xf0@...il.com>
Cc:     Markus Mayer <mmayer@...adcom.com>,
        Broadcom Kernel List <bcm-kernel-feedback-list@...adcom.com>,
        Device Tree List <devicetree@...r.kernel.org>,
        ARM Kernel List <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/2] SoC driver for Broadcom STB DPFE

On 08/24/2017 04:36 PM, Markus Mayer wrote:
> From: Markus Mayer <mmayer@...adcom.com>
> 
> This series introduces a driver to interact with the Broadcom STB DDR
> PHY Front End (DPFE), specifically to communicate with the DCPU that is
> part of the DDR PHY and which is running its own firmware.
> 
> The DCPU provides information such as DRAM refresh rate, which can be
> used as indirect indicator for the DRAM temperature (the higher the
> refresh rate, the hotter the RAM).
> 
> The series was previously submitted as HWMON driver[1]. It has been
> removed from that subsystem, because it doesn't provide any standard
> HWMON data due to hardware design properties, and is now implemented as
> SoC driver.
> 
> Changes since v2:
>   - moved driver from drivers/soc/bcm/brcmstb to drivers/memory
>   - renamed the driver from dpfe.c to brcmstb_dpfe.c
>   - added le32_to_cpu() in a few places (where be32_to_cpu() calls
>     already existed)
>   - added a little blurb what the le32_to_cpu()/be32_to_cpu() business
>     is all about
> 
> Changes since v1:
>   - binding simplified to use one node with three memory regions
>     instead of three nodes with one region
>   - no longer part of the HWMON subsystem
>   - better error handling and error reporting to userland
>   - uses [readl|writel]_relaxed() directly, since there is no need for
>     wrappers doing endian conversion
>   - re-download firmware upon "resume"
>   - minor changes to improve clarity
> 
> [1] https://lkml.org/lkml/2017/4/18/640

Applied, thanks Markus! Will get that resubmitted in a short while:

https://github.com/Broadcom/stblinux/commits/drivers/next
-- 
Florian