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: <DB8P190MB06340D1909D0B592D4D3B1F8D9B49@DB8P190MB0634.EURP190.PROD.OUTLOOK.COM>
Date:   Wed, 3 Feb 2021 16:26:26 +0000
From:   Sven Schuchmann <schuchmann@...leissheimer.de>
To:     Dan Murphy <dmurphy@...com>, Pavel Machek <pavel@....cz>
CC:     Rob Herring <robh+dt@...nel.org>,
        "linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: AW: [PATCH 2/2] leds: lp50xx: remove unused regulator

Hello Dan, hello Pavel,
> > Do you have set up where this is needed and you can test this? Will
> > you submit the fixes?
> 
> No I use an always on regulator in my setup. I have no managed supplies
> exposed.

I am also sorry I do not have a setup ready for testing this.
I think we should ignore this patch then?`

For now I am working on the enable pin in the driver.
The enablement seems it does not work. The order of I2C-Reset
and Enable is wrong and the pin is used before initialized.
But I do not have any patches ready.
Is the enable pin working on your side?

Best Regards,

   Sven

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ