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: <36a68a0b-0c18-deb5-609c-2128aa3fc21f@somainline.org>
Date:   Wed, 6 Jul 2022 15:31:55 +0200
From:   Konrad Dybcio <konrad.dybcio@...ainline.org>
To:     Christian Marangi <ansuelsmth@...il.com>
Cc:     Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Jonathan McDowell <noodles@...th.li>
Subject: Re: [PATCH 04/13] ARM: dts: qcom: disable smb208 regulators for
 ipq8064-rb3011



On 6.07.2022 14:56, Christian Marangi wrote:
> On Wed, Jul 06, 2022 at 03:03:32PM +0200, Konrad Dybcio wrote:
>>
>>
>> On 5.07.2022 15:39, Christian Marangi wrote:
>>> Mikrotik RB3011 have a special configuration where the regulators are
>>> not the common smb208 controlled by RPM but they use a TPS563900
>>> controlled via i2c. Disable the smb208 for this specific device.
>> Ok, so that answers my question from the previous email.
>> Please define the SMB208 regulators only in the DTs of
>> boards that actually use it, as it is not a SoC component as
>> far as I can tell.
>>
>> Konrad
> 
> This was already discuessed,
Yeah sorry, I didn't notice earlier and started reviewing patches
that were already reviewed by others.


rb3011 is the exception, qcom for ipq8064
> recommends to use smb208 but gives the option to implement it in their
> own way. So again we have 28 device with smb208 and 1 device that use
> its own special way...
> 
> Wonder if a separate dtsi can be used for this if we really can't put
> smb208 in ipq8064 dtsi?
There's msm8916-pm8916.dtsi. You can follow.

Konrad

[...]

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ