linux-kernel - Re: [PATCH 08/19] clk: meson: add regmap to the clock controllers

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1517824279.3153.42.camel@baylibre.com>
Date:   Mon, 05 Feb 2018 10:51:19 +0100
From:   Jerome Brunet <jbrunet@...libre.com>
To:     Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc:     Neil Armstrong <narmstrong@...libre.com>,
        Kevin Hilman <khilman@...libre.com>,
        Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...eaurora.org>,
        linux-kernel@...r.kernel.org, Carlo Caione <carlo@...one.org>,
        linux-amlogic@...ts.infradead.org, linux-clk@...r.kernel.org
Subject: Re: [PATCH 08/19] clk: meson: add regmap to the clock controllers

On Sat, 2018-02-03 at 19:53 +0100, Martin Blumenstingl wrote:
> On Wed, Jan 31, 2018 at 7:09 PM, Jerome Brunet <jbrunet@...libre.com> wrote:
> > This change register a regmap in meson8b, gxbb and axg controllers.
> > The clock are still accessing their registers directly through iomem.
> > Once all clocks handled by these controllers have been move to regmap,
> > the regmap register will be removed and replaced with a syscon request.
> 
> maybe you can add a comment that some of the registers from this area
> need to be accessed outside the clock driver (by the HDMI driver for
> example - which is the case on GX and Meson8/8b IIRC) if you have to
> re-spin this series

I think it was mentioned in the cover letter, but you are right, I should
mention it here as well.

> 
> > Signed-off-by: Jerome Brunet <jbrunet@...libre.com>
> 
> Acked-by: Martin Blumenstingl <martin.blumenstingl@...glemail.com>