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: <68f6dc44a8202fd83792e58aea137632.sboyd@kernel.org>
Date: Wed, 10 Jul 2024 16:21:15 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Alexander Stein <alexander.stein@...tq-group.com>, Heiko Stübner <heiko@...ech.de>, mturquette@...libre.com
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, quentin.schulz@...rry.de, linux-clk@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org
Subject: Re:  Re: [PATCH 1/6] dt-bindings: clocks: add binding for generic clock-generators

Quoting Heiko Stübner (2024-07-10 00:45:17)
> Am Mittwoch, 10. Juli 2024, 09:02:34 CEST schrieb Alexander Stein:
> > 
> > So essentially only enable-gpios and vdd-supply is added in comparison to
> > fixed-clock. Does it make sense to add that to the fixed-clocks instead?
> > Similar to fixed-regulator.
> 
> I wasn't that sure which way to go in the first place.
> The deciding point was reading that line about the fixed clock not
> being gateable, so I opted to not touch the fixed-clock.
> 
> But you're definitly right, this _could_ live inside the fixed-clock
> as well, if we decide to get rid of the not-gateable thing above.

It's probably more complicated to combine it with the fixed-clock
binding after making properties required like vdd-supply. I'd just make
a new binding and look at combining later.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ