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: <CADvTj4op-CEmBrfZ6a2YkzPbZ42EbG7wCkwGbwgdS-FXKG2Qxg@mail.gmail.com>
Date:   Sat, 22 Jul 2023 11:07:01 -0600
From:   James Hilliard <james.hilliard1@...il.com>
To:     Francesco Dolcini <francesco@...cini.it>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        devicetree@...r.kernel.org,
        Gregory CLEMENT <gregory.clement@...tlin.com>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        NXP Linux Team <linux-imx@....com>,
        Marek Vasut <marex@...x.de>,
        Frieder Schrempf <frieder.schrempf@...tron.de>,
        Stefan Wahren <stefan.wahren@...rgebyte.com>,
        Philippe Schenker <philippe.schenker@...adex.com>,
        Andreas Kemnade <andreas@...nade.info>,
        Marcel Ziswiler <marcel.ziswiler@...adex.com>,
        Christoph Niedermaier <cniedermaier@...electronics.com>,
        Li Yang <leoyang.li@....com>, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v6 2/3] ARM: dts: imx6qdl: Add Variscite VAR-SOM-MX6 SoM support

On Fri, Jul 21, 2023 at 5:41 AM Francesco Dolcini <francesco@...cini.it> wrote:
>
> On Fri, Jul 21, 2023 at 05:05:51AM -0600, James Hilliard wrote:
> > On Fri, Jul 21, 2023 at 4:43 AM Krzysztof Kozlowski
> > <krzysztof.kozlowski@...aro.org> wrote:
> > > On 21/07/2023 12:33, James Hilliard wrote:
> > > > +             compatible = "regulator-fixed";
> > > > +             regulator-name = "touch_3v3_supply";
> > > > +             regulator-always-on;
> > >
> > > Also, missing constraints.
> >
> > Hmm, what's the correct way to determine the constraint values?
>
> You should know/understand the hardware design. Normally when writing a
> DT file you have the hardware schematics and the relevant datasheets
> available.

I did find some datasheets/schematics, but I'm having trouble finding something
which indicates it would be anything other than 3.3v there(although I don't read
a lot of schematics in general so I might be missing something obvious):
https://www.variscite.com/wp-content/uploads/2017/12/VAR-SOM-MX6_v1-Datasheet.pdf
https://www.variscite.com/wp-content/uploads/2017/12/VAR-SOM-MX6_datasheet.pdf
https://www.variscite.com/wp-content/uploads/2017/12/VAR-MX6CustomBoard-Schematics-for-VAR-SOM-MX6_V1.pdf
https://www.variscite.com/wp-content/uploads/2017/12/V2_VAR-MX6CustomBoard-Schematics.pdf
https://www.variscite.com/wp-content/uploads/2017/12/VAR-MX6CustomBoard-Datasheet.pdf

>
> > I'm guessing they should just be set to this based on the name?:
> > regulator-min-microvolt = <3300000>;
> > regulator-max-microvolt = <3300000>;
>
> This looks like a good guess, assuming that the regulator name is
> correct.

Tested with that but it didn't work, screen failed so I guess must be
something different?

>
> Francesco
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ