linux-kernel - RE: [PATCH v3 3/8] arm64: dts: ls1028a: add flextimer based pwm nodes

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: <DU2PR04MB89497E16D2E9A01BF763D92B8FEC9@DU2PR04MB8949.eurprd04.prod.outlook.com>
Date:   Wed, 13 Apr 2022 19:10:32 +0000
From:   Leo Li <leoyang.li@....com>
To:     Vladimir Oltean <olteanv@...il.com>
CC:     Shawn Guo <shawnguo@...nel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Biwen Li <biwen.li@....com>
Subject: RE: [PATCH v3 3/8] arm64: dts: ls1028a: add flextimer based pwm nodes



> -----Original Message-----
> From: Vladimir Oltean <olteanv@...il.com>
> Sent: Wednesday, April 13, 2022 1:23 PM
> To: Leo Li <leoyang.li@....com>
> Cc: Shawn Guo <shawnguo@...nel.org>; linux-arm-
> kernel@...ts.infradead.org; linux-kernel@...r.kernel.org; Biwen Li
> <biwen.li@....com>
> Subject: Re: [PATCH v3 3/8] arm64: dts: ls1028a: add flextimer based pwm
> nodes
> 
> On Wed, Apr 13, 2022 at 06:07:20PM +0000, Leo Li wrote:
> > > arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi:1210.21-1219.5:
> > > Warning
> > > (unique_unit_address): /soc/pwm@...0000: duplicate unit-address
> > > (also used in node /soc/timer@...0000)
> > > arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi:1221.21-1230.5:
> > > Warning
> > > (unique_unit_address): /soc/pwm@...0000: duplicate unit-address
> > > (also used in node /soc/timer@...0000)
> >
> > Well, this is similar situation as pcie.  The flextimer controller can
> > be used as timer, PWM or alarm.  We have separate drivers and bindings
> > for these modes which resulted in different nodes for the same
> > controller.
> 
> I think the mfd framework can address the situation where multiple drivers,
> with multiple functionalities, want access to the same memory region?

I know mfd is used for device providing multiple functions at the same time.  I'm not sure if it can help dealing with the one function at a time scenario.

Regards,
Leo