[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bd7d005b-c715-4fd9-9b0d-52956d28d272@lunn.ch>
Date: Thu, 10 Apr 2025 19:36:38 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Prathosh.Satish@...rochip.com
Cc: ivecera@...hat.com, conor@...nel.org, krzk@...nel.org,
netdev@...r.kernel.org, vadim.fedorenko@...ux.dev,
arkadiusz.kubalewski@...el.com, jiri@...nulli.us, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, lee@...nel.org,
kees@...nel.org, andy@...nel.org, akpm@...ux-foundation.org,
mschmidt@...hat.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH v2 02/14] dt-bindings: dpll: Add support for Microchip
Azurite chip family
> Prathosh, could you please bring more light on this?
>
> > Just to clarify, the original driver was written specifically with 2-channel
> > chips in mind (ZL30732) with 10 input and 20 outputs, which led to some confusion of using zl3073x as compatible.
> > However, the final version of the driver will support the entire ZL3073x family
> > ZL30731 to ZL30735 and some subset of ZL30732 like ZL80732 etc
> > ensuring compatibility across all variants.
Hi Prathosh
Your email quoting is very odd, i nearly missed this reply.
Does the device itself have an ID register? If you know you have
something in the range ZL30731 to ZL30735, you can ask the hardware
what it is, and the driver then does not need any additional
information from DT, it can hard code it all based on the ID in the
register?
Andrew
Powered by blists - more mailing lists