From: Ivan Vecera <ivecera@redhat.com>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>, netdev@vger.kernel.org
Cc: Donald Hunter <donald.hunter@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
Petr Oros <poros@redhat.com>,
linux-kernel@vger.kernel.org,
Michal Schmidt <mschmidt@redhat.com>
Subject: Re: [PATCH net-next 3/3] dpll: zl3073x: Implement device mode setting support
Date: Mon, 12 Jan 2026 14:27:46 +0100 [thread overview]
Message-ID: <0db2bd26-07c4-4181-8f83-95d7d2cbd629@redhat.com> (raw)
In-Reply-To: <825dbb02-5e76-45d1-acf6-78bcc2e999c8@linux.dev>
On 1/12/26 12:37 PM, Vadim Fedorenko wrote:
>> + if (mode == DPLL_MODE_MANUAL) {
>> + /* We are switching from automatic to manual mode:
>> + * - if we have a valid reference selected during auto mode then
>> + * we will switch to forced reference lock mode and use this
>> + * reference for selection
>> + * - if NO valid reference is selected, we will switch to forced
>> + * holdover mode or freerun mode, depending on the current
>> + * lock status
>> + */
>> + if (ZL3073X_DPLL_REF_IS_VALID(ref))
>> + hw_mode = ZL_DPLL_MODE_REFSEL_MODE_REFLOCK;
>> + else if (zldpll->lock_status == DPLL_LOCK_STATUS_UNLOCKED)
>> + hw_mode = ZL_DPLL_MODE_REFSEL_MODE_FREERUN;
>> + else
>> + hw_mode = ZL_DPLL_MODE_REFSEL_MODE_HOLDOVER;
>> + } else {
>> + /* We are switching from manual to automatic mode:
>> + * - if there is a valid reference selected then ensure that
>> + * it is selectable after switch to automatic mode
>> + * - switch to automatic mode
>> + */
>> + struct zl3073x_dpll_pin *pin;
>> +
>> + pin = zl3073x_dpll_pin_get_by_ref(zldpll, ref);
>> + if (pin && !pin->selectable) {
>> + /* Restore pin priority in HW */
>> + rc = zl3073x_dpll_ref_prio_set(pin, pin->prio);
>> + if (rc)
>> + return rc;
>
> I think it's better to fill-up extack here to give at least some info of
> what's happened?
Will add, thanks for pointing this out.
Ivan
prev parent reply other threads:[~2026-01-12 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 10:14 [PATCH net-next 0/3] dpll: support mode switching Ivan Vecera
2026-01-12 10:14 ` [PATCH net-next 1/3] dpll: add dpll_device op to get supported modes Ivan Vecera
2026-01-12 11:44 ` Vadim Fedorenko
2026-01-12 10:14 ` [PATCH net-next 2/3] dpll: add dpll_device op to set working mode Ivan Vecera
2026-01-12 11:35 ` Vadim Fedorenko
2026-01-12 13:10 ` Ivan Vecera
2026-01-12 10:14 ` [PATCH net-next 3/3] dpll: zl3073x: Implement device mode setting support Ivan Vecera
2026-01-12 11:37 ` Vadim Fedorenko
2026-01-12 13:27 ` Ivan Vecera [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=0db2bd26-07c4-4181-8f83-95d7d2cbd629@redhat.com \
--to=ivecera@redhat.com \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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=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