From: Conor Dooley <conor@kernel.org>
To: Vincent Jardin <vjardin@free.fr>
Cc: Ivan Vecera <ivecera@redhat.com>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: dpll: zl3073x: ZL30643 is compatible
Date: Thu, 30 Jul 2026 19:11:05 +0100 [thread overview]
Message-ID: <20260730-fiftieth-unknown-adbe797ccf1e@spud> (raw)
In-Reply-To: <20260730-for-upstream-zl30643-v2-1-0ea0bbd03755@free.fr>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On Thu, Jul 30, 2026 at 07:35:35PM +0200, Vincent Jardin wrote:
> The Microchip ZL30643 (chip ID 0x0E3B) is a member of the ZL3064x
> line card timing family. It is register compatible with the 3-channel
> ZL30733 (chip ID 0x0E95) of the ZL3073x family: both datasheets
> describe the same register map and use the same chip-ID encoding.
>
> Describe it with a fallback to microchip,zl30733 rather than a new
> standalone compatible.
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-30 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 17:35 [PATCH v2 0/2] dpll: zl3073x: add Microchip ZL30643 support Vincent Jardin via B4 Relay
2026-07-30 17:35 ` [PATCH v2 1/2] dt-bindings: dpll: zl3073x: ZL30643 is compatible Vincent Jardin via B4 Relay
2026-07-30 18:11 ` Conor Dooley [this message]
2026-07-30 17:35 ` [PATCH v2 2/2] dpll: zl3073x: recognize the ZL30643 chip ID (0x0E3B) Vincent Jardin via B4 Relay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260730-fiftieth-unknown-adbe797ccf1e@spud \
--to=conor@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vadim.fedorenko@linux.dev \
--cc=vjardin@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox