On Mon, 25 Mar 2024 16:51:34 +0000 Lee Jones <lee@xxxxxxxxxx> wrote: > On Mon, 25 Mar 2024, Lee Jones wrote: > > > On Mon, 25 Mar 2024, Matti Vaittinen wrote: > > > > > Hi Andreas, > > > > > > On 3/25/24 14:16, Andreas Kemnade wrote: > > > > On Mon, 25 Mar 2024 13:31:15 +0200 > > > > Matti Vaittinen <mazziesaccount@xxxxxxxxx> wrote: > > > > > > > > > On 3/24/24 22:12, Andreas Kemnade wrote: > > > > > > Since the chip can power off the system, add the corresponding > > > > > > functionality. > > > > > > Based on https://github.com/kobolabs/Kobo-Reader/raw/master/hw/imx6sll-clara2e/kernel.tar.bz2 > > > > > > No information source about the magic numbers found. > > > > > > > > > > Oh, interesting repository :) Thanks for linking to it! I didn't know > > > > > someone had reworked this driver... > > > > > > > > > which btw: contains this interesting snippet (output from fdtdump) > > > > bd71828-i2c@4b { > > > > reg = <0x0000004b>; > > > > compatible = "rohm,bd71828"; > > > > gpio_int = <0x00000008 0x00000013 0x00000001>; > > > > gpio_wdogb = <0x00000039 0x00000018 0x00000001>; > > > > #address-cells = <0x00000001>; > > > > #size-cells = <0x00000000>; > > > > pmic@4b { > > > > compatible = "rohm,bd71828"; > > > > regulators { > > > > BUCK1 { > > > > regulator-name = "buck1"; > > > > > > > > > > > > and to make it work since basically no regulators are registered > > > > instead just some regmap_write()s are done to configure something > > > > in probe(). It is a pitfall to think that the information below pmic@4b > > > > is used, especially since it is not that obvious in the source. > > > > Odd! Not only did I not receive the original patch, I also did not > > receive your response Andreas. Spam is empty too. > > > > LORE too: https://lore.kernel.org/all/?q=%22mfd:%20rohm-bd71828:%20Add%20power%20off%20functionality%22 > > Super weird! They just all came through. > > The LORE link above is now working too. > > I suspect an issue with kernel.org. > Well, no, emails from me to everyone sitting behind a mail server without IPv6 address were affected. TCP ACK (3rd part of the handshake) was eaten up by something. Whatever... So nothing to blame kernel.org besides not having IPv6. Regards, Andreas
