linux-kernel - Re: [PATCH v2 5/5] ARM: dts: sun50i: h6: Introduce Beelink GS1 board

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: <CAJiuCcdVsiKRxLFKnmAPnApi2EJANbuQf9WUESGE+LBP8zpD+A@mail.gmail.com>
Date:   Fri, 5 Apr 2019 18:40:23 +0200
From:   Clément Péron <peron.clem@...il.com>
To:     Maxime Ripard <maxime.ripard@...tlin.com>
Cc:     Rob Herring <robh+dt@...nel.org>, Chen-Yu Tsai <wens@...e.org>,
        Icenowy Zheng <icenowy@...c.io>,
        Jagan Teki <jagan@...rulasolutions.com>,
        devicetree <devicetree@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-sunxi@...glegroups.com
Subject: Re: [PATCH v2 5/5] ARM: dts: sun50i: h6: Introduce Beelink GS1 board

Hi,

On Fri, 5 Apr 2019 at 17:11, Maxime Ripard <maxime.ripard@...tlin.com> wrote:
>
> On Fri, Apr 05, 2019 at 02:53:35PM +0200, Clément Péron wrote:
> > Hi,
> >
> > Adding this r_pio regulators make a new error in the bootlog :
> >
> > [    0.346843] sun50i-h6-r-pinctrl 7022000.pinctrl: Couldn't get bank
> > PL regulator
> > [    0.346853] sun50i-h6-r-pinctrl 7022000.pinctrl: request() failed for pin 352
> > [    0.346862] sun50i-h6-r-pinctrl 7022000.pinctrl: pin-352
> > (7081400.i2c) status -517
> > [    0.346871] sun50i-h6-r-pinctrl 7022000.pinctrl: could not request
> > pin 352 (PL0) from group PL0  on device 7022000.pinctrl
> > [    0.346878] mv64xxx_i2c 7081400.i2c: Error applying setting,
> > reverse things back
> >
> > PL0 and PL1 are SCK/SDA for the PMIC :(
>
> How was this DT tested then?

There was a mistake when I tested the patch v2 and only saw this after
posting the patch.

Can I submit a V3 without pio / r_pio regulators ? (+ the yaml patch separated)

Thanks,

>
> Maxime
>
> --
> Maxime Ripard, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com