linux-kernel - Re: [PATCH v2 1/3] dt-bindings: mfd: sy7636a: Add missing gpio pins and supply

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: <20250910211804.5d88f12b@akair>
Date: Wed, 10 Sep 2025 21:18:04 +0200
From: Andreas Kemnade <andreas@...nade.info>
To: Frank Li <Frank.li@....com>
Cc: Andreas Kemnade <akemnade@...nel.org>, Lee Jones <lee@...nel.org>, Rob
 Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor
 Dooley <conor+dt@...nel.org>, Alistair Francis <alistair@...stair23.me>,
 Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>, Shawn
 Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>,
 Pengutronix Kernel Team <kernel@...gutronix.de>, Fabio Estevam
 <festevam@...il.com>, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, imx@...ts.linux.dev,
 linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 1/3] dt-bindings: mfd: sy7636a: Add missing gpio pins
 and supply

Am Wed, 10 Sep 2025 11:45:35 -0400
schrieb Frank Li <Frank.li@....com>:

> On Tue, Sep 09, 2025 at 10:33:02PM +0200, Andreas Kemnade wrote:
> > To be able to fully describe how the SY7636A is connected to the system,
> > add properties for the EN and VCOM_EN pins. To squeeze out every bit
> > of unused current, in many devices it is possible to power off the
> > complete chip. Add an input regulator to allow that.
> >
> > Signed-off-by: Andreas Kemnade <akemnade@...nel.org>
> > ---
> >  .../devicetree/bindings/mfd/silergy,sy7636a.yaml         | 16 ++++++++++++++++
> >  1 file changed, 16 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/mfd/silergy,sy7636a.yaml b/Documentation/devicetree/bindings/mfd/silergy,sy7636a.yaml
> > index ee0be32ac0204..054b97dd0c5c7 100644
> > --- a/Documentation/devicetree/bindings/mfd/silergy,sy7636a.yaml
> > +++ b/Documentation/devicetree/bindings/mfd/silergy,sy7636a.yaml
> > @@ -32,6 +32,22 @@ properties:
> >        Specifying the power good GPIOs.
> >      maxItems: 1
> >
> > +  enable-gpios:
> > +    description:
> > +      If EN pin is not hardwired, specify it here to have it set up.  
> 
> Need descript function of enabel-gpios, you can ref data sheet sy7636a.
> 
> "enable-gpios" is good self documented by property name, needn't
> description at all.
> 
What you are saying is contradictory. I would prefer to have a mapping
crystal clear visible between properties and pins. That is why I want
that description. I remember I have got the datasheet from the company
site with registration without acknowledging any terms. But I do not
find that site.

> > +    maxItems: 1
> > +
> > +  vcom-en-gpios:
> > +    description:
> > +      If VCOM_EN pin is not hardwired, specify it here to have it set up.
> > +    maxItems: 1
> > +
> > +  vin-supply:
> > +    description:
> > +      Supply for the chip. Some vendor kernels and devicetrees declare this
> > +      as a GPIO named "pwrall" which does not exist in the datasheet,
> > +      disabling it makes the chip disappear on the bus.
> > +  
> 
> The same here, descript function. such as power supply for whole chip.

I think it is useful what I am writing here. DT maintainers are
apparently fine with it, since it has earned a Reviewed-By.

Regards,
Andreas