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] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 04 Aug 2022 14:01:58 +0000
From:   Samuel Holland <samuel@...lland.org>
To:     Jernej Škrabec <jernej.skrabec@...il.com>,
        Rob Herring <robh@...nel.org>
CC:     Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>, Chen-Yu Tsai <wens@...e.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Maxime Ripard <mripard@...nel.org>, devicetree@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-sunxi@...ts.linux.dev
Subject: Re: [PATCH v2 3/4] regulator: dt-bindings: Add Allwinner D1 LDOs

On August 4, 2022 5:11:39 AM UTC, "Jernej Škrabec" <jernej.skrabec@...il.com> wrote:
>> > 'simple-mfd' also means the child nodes have zero dependence on the
>> > parent node and its resources.
>> 
>> That is correct. The regulators have zero dependencies on the audio codec
>> resources (clocks/resets/etc.). The _only_ relationship is the overlapping
>> address of the MMIO register.
>
>LDO registers are at the end of analogue codec MMIO space, right? We can 
>easily split that to separate device, like it's been done for A20 timer & 
>watchdog.

No, there are some audio-related registers after the LDO register ("POWER_REG" in the D1 and V853 manuals).
So it is not possible to cleanly split the MMIO region.

Regards,
Samuel

Powered by blists - more mailing lists