Devicetree
 help / color / mirror / Atom feed
From: Vincent Jardin <vjardin@free.fr>
To: Ivan Vecera <ivecera@redhat.com>
Cc: Vincent Jardin via B4 Relay <devnull+vjardin.free.fr@kernel.org>,
	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 2/2] dpll: zl3073x: add ZL30643 chip support
Date: Wed, 12 Aug 2026 22:00:19 +0200	[thread overview]
Message-ID: <anzQ04ySyCbjQPD5@L30177.local> (raw)
In-Reply-To: <760d9664-14f6-4cf8-af55-699ea3021b47@redhat.com>

Hi Ivan,

> Yes, minimal reference frequency for zl3064x is 1000Hz and also
> supported bandwidth range is different (not relevant now).
> 
> So, we need to
> - add new field into zl3073x_chip_info that will describe minimal input
>   reference frequency
> - add a check into zl3073x_pin_check_freq()
> 
> Let me know if you want to do it yourself or if I should do it (I would
> send it along with your two patches).

I'd prefer that you add it, please, cc me so I'll be review it.

Thanks for your help,
  Vincent

      reply	other threads:[~2026-08-12 20:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 23:09 [PATCH 0/2] dpll: zl3073x: add Microchip ZL30643 support Vincent Jardin via B4 Relay
2026-07-23 23:09 ` [PATCH 1/2] dt-bindings: dpll: zl3073x: add ZL30643 compatible Vincent Jardin via B4 Relay
2026-07-24 16:46   ` Conor Dooley
2026-07-30 17:01     ` Vincent Jardin
2026-07-24 23:09   ` sashiko-bot
2026-07-23 23:09 ` [PATCH 2/2] dpll: zl3073x: add ZL30643 chip support Vincent Jardin via B4 Relay
2026-07-27  8:36   ` Ivan Vecera
2026-07-30 17:08     ` Vincent Jardin
2026-08-03 11:51       ` Ivan Vecera
2026-08-12 20:00         ` Vincent Jardin [this message]

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=anzQ04ySyCbjQPD5@L30177.local \
    --to=vjardin@free.fr \
    --cc=Prathosh.Satish@microchip.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+vjardin.free.fr@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 \
    /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