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:
 <DU0PR04MB9417A8F4230D2C7C76D1550988742@DU0PR04MB9417.eurprd04.prod.outlook.com>
Date: Tue, 23 Jan 2024 13:08:11 +0000
From: Peng Fan <peng.fan@....com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, "Peng Fan (OSS)"
	<peng.fan@....nxp.com>, "robh+dt@...nel.org" <robh+dt@...nel.org>,
	"krzysztof.kozlowski+dt@...aro.org" <krzysztof.kozlowski+dt@...aro.org>,
	"conor+dt@...nel.org" <conor+dt@...nel.org>, "abelvesa@...nel.org"
	<abelvesa@...nel.org>, "mturquette@...libre.com" <mturquette@...libre.com>,
	"sboyd@...nel.org" <sboyd@...nel.org>, "shawnguo@...nel.org"
	<shawnguo@...nel.org>, "s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
	"kernel@...gutronix.de" <kernel@...gutronix.de>, "festevam@...il.com"
	<festevam@...il.com>
CC: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, dl-linux-imx
	<linux-imx@....com>, "linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] dt-bindings: clock: support NXP i.MX95

Hi Conor, Krzysztof

I replied you both here.

> Subject: Re: [PATCH] dt-bindings: clock: support NXP i.MX95
> 
> On 21/01/2024 12:46, Peng Fan (OSS) wrote:
> > From: Peng Fan <peng.fan@....com>
> >
> > Add i.MX95 clock dt-binding header file
> >
> > Signed-off-by: Peng Fan <peng.fan@....com>
> 
> This should be squashed with respective binding patch.

i.MX95 use SCMI firmware, the SCP processor handles
clock/power/pinmux/reset/performance and etc.

I just add the index that SCMI exports, and Linux/UBoot
will use the index and go through SCMI to do real HW
configuration.

In such case, should I still add HW information in
a yaml binding doc? I am not sure what should be added
if yes.

Thanks,
Peng.

> 
> > +
> > +#define IMX95_CCM_NUM_CLK_SRC               41
> 
> Drop.
> 
> Best regards,
> Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ