From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Ivan Vecera <ivecera@redhat.com>, Jakub Kicinski <kuba@kernel.org>
Cc: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
netdev@vger.kernel.org, Jiri Pirko <jiri@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Donald Hunter <donald.hunter@gmail.com>,
Eric Dumazet <edumazet@google.com>, Jiri Pirko <jiri@resnulli.us>,
Michal Schmidt <mschmidt@redhat.com>,
Paolo Abeni <pabeni@redhat.com>,
Pasi Vaananen <pvaanane@redhat.com>, Petr Oros <poros@redhat.com>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org,
Grzegorz Nitka <grzegorz.nitka@intel.com>
Subject: Re: [PATCH net-next v5 1/4] dpll: add DPLL_PIN_TYPE_INT_NCO pin type
Date: Mon, 8 Jun 2026 12:33:56 +0100 [thread overview]
Message-ID: <d6b69d21-4542-498d-8253-7009a56634cc@linux.dev> (raw)
In-Reply-To: <3c5e01f5-8563-41a3-964f-13fcb80383b7@redhat.com>
On 04/06/2026 17:42, Ivan Vecera wrote:
> On 6/4/26 5:16 PM, Jakub Kicinski wrote:
>> On Thu, 4 Jun 2026 17:01:36 +0200 Ivan Vecera wrote:
>>>> Purely going on intuition here but feels like NCO should be a mode
>>>> (enum dpll_mode) rather than one of the input pins?
>>>>
>>>> More acks here would be great, Vadim, Arkadiusz, Grzegorz... ?
>>>
>>> I had a long discussion with Jiri about this and we agreed finally
>>> that dpll_mode represents a reference (input pin) selection strategy
>>> mode and not a DPLL device running mode.
>>
>> Long discussion? I see 2 emails ;) Let's hear from others.
>> (thanks for the link BTW, _if_ there's a v6 please put it in the cover
>> letter)
>
> I called him... he explained me 'why?' in detail.
> I also appreciate others' opinion.
Well, NCO mode means manual operation of frequency tuning. Does it mean
that different tunings may be applied to different out pins of DPLL
device? My assumption that it's not possible, and in this case NCO is
property/mode of DPLL device rather than single pin.
@Jiri could you please share your detailed explanation on "why"?
next prev parent reply other threads:[~2026-06-08 11:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 19:44 [PATCH net-next v5 0/4] dpll: add NCO pin type and zl3073x support Ivan Vecera
2026-05-31 19:44 ` [PATCH net-next v5 1/4] dpll: add DPLL_PIN_TYPE_INT_NCO pin type Ivan Vecera
2026-06-04 1:50 ` Jakub Kicinski
2026-06-04 15:01 ` Ivan Vecera
2026-06-04 15:16 ` Jakub Kicinski
2026-06-04 16:42 ` Ivan Vecera
2026-06-08 11:33 ` Vadim Fedorenko [this message]
2026-06-08 15:30 ` Ivan Vecera
2026-06-09 10:24 ` Vadim Fedorenko
2026-06-09 11:06 ` Jiri Pirko
2026-06-08 14:43 ` Kubalewski, Arkadiusz
2026-06-08 15:48 ` Ivan Vecera
2026-06-08 17:03 ` Kubalewski, Arkadiusz
2026-06-09 8:51 ` Jiri Pirko
2026-05-31 19:44 ` [PATCH net-next v5 2/4] dpll: zl3073x: use per-operation poll timeouts Ivan Vecera
2026-05-31 19:44 ` [PATCH net-next v5 3/4] dpll: zl3073x: add per-DPLL serialization lock Ivan Vecera
2026-06-04 1:40 ` Jakub Kicinski
2026-06-04 14:57 ` Ivan Vecera
2026-06-04 1:51 ` Jakub Kicinski
2026-06-04 15:12 ` Ivan Vecera
2026-05-31 19:44 ` [PATCH net-next v5 4/4] dpll: zl3073x: add NCO virtual input pin Ivan Vecera
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=d6b69d21-4542-498d-8253-7009a56634cc@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=grzegorz.nitka@intel.com \
--cc=horms@kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=pvaanane@redhat.com \
/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