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]
Message-ID: <CAE-0n528QaTtZFp=WAaHShegFRpKVN_67jQfUJTtsRPr6s--zA@mail.gmail.com>
Date:   Tue, 26 Jul 2022 20:19:18 -0500
From:   Stephen Boyd <swboyd@...omium.org>
To:     Lee Jones <lee.jones@...aro.org>, Mark Brown <broonie@...nel.org>,
        Satya Priya Kakitapalli <quic_c_skakit@...cinc.com>
Cc:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, quic_collinsd@...cinc.com,
        quic_subbaram@...cinc.com, quic_jprakash@...cinc.com
Subject: Re: [PATCH V15 6/9] mfd: pm8008: Use i2c_new_dummy_device() API

Quoting Satya Priya Kakitapalli (Temp) (2022-07-21 23:31:16)
>
>              regulator-name = "pm8008_l6";
>          };
>
>          pm8008_l7: ldo7@...0 {
>              reg = <0x4600>;
>              regulator-name = "pm8008_l7";
>          };
>      };
> };
>
>
> Stephen/Mark, Please do let me know if you are OK with this design.
>

I was happy with the previous version of the DT node. That had one node
for the "pm8008 chip", which is important because it really is one
package. Why isn't that possible to implement and also register i2c
devices on the i2c bus for the second address?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ