From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>,
davem@davemloft.net, arkadiusz.kubalewski@intel.com
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, ivecera@redhat.com,
jiri@resnulli.us, donald.hunter@gmail.com
Subject: Re: [PATCH net-next 2/4] netlink: specs: dpll: drop the pin-set attributes nothing implements
Date: Sun, 6 Sep 2026 12:44:24 +0100 [thread overview]
Message-ID: <43cbac2e-d0ec-4315-b5fe-5a51745fce0d@linux.dev> (raw)
In-Reply-To: <20260904191023.3869690-3-kuba@kernel.org>
On 04/09/2026 20:10, Jakub Kicinski wrote:
> pin-set advertises top level direction, prio and state, so the
> generated policy accepts them and the generated user space API grows
> setters for them. dpll_pin_set_from_nlattr() has cases only for
> FREQUENCY, PHASE_ADJUST, PARENT_DEVICE, PARENT_PIN, ESYNC_FREQUENCY and
> REFERENCE_SYNC - the request succeeds, does nothing and produces no
> extack. The three values are only actionable inside the parent-device
> nest, where dpll_pin_parent_device_set() handles them next to
> DPLL_A_PIN_PARENT_ID, which is what makes them meaningful: a pin can be
> registered with more than one device.
>
> Never implemented - "git log -S 'case DPLL_A_PIN_PRIO'" on
> dpll_netlink.c comes up empty - the spec has advertised them since
> commit 3badff3a25d8 ("dpll: spec: Add Netlink spec in YAML").
>
> Note that this does change what the kernel accepts: sending one of the
> three now fails validation instead of being ignored.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
@Arkadiusz was this a plan that never happened?
Anyways, LGMT
Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
next prev parent reply other threads:[~2026-09-06 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 19:10 [PATCH net-next 0/4] dpll: fix lies in the Netlink spec Jakub Kicinski
2026-09-04 19:10 ` [PATCH net-next 1/4] netlink: specs: dpll: add clock-quality-level to the device-get reply Jakub Kicinski
2026-09-05 11:19 ` Vadim Fedorenko
2026-09-04 19:10 ` [PATCH net-next 2/4] netlink: specs: dpll: drop the pin-set attributes nothing implements Jakub Kicinski
2026-09-06 11:44 ` Vadim Fedorenko [this message]
2026-09-04 19:10 ` [PATCH net-next 3/4] netlink: specs: dpll: pin-get has no dump filter Jakub Kicinski
2026-09-06 11:44 ` Vadim Fedorenko
2026-09-04 19:10 ` [PATCH net-next 4/4] MAINTAINERS: dpll: add the netlink spec Jakub Kicinski
2026-09-06 11:45 ` Vadim Fedorenko
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=43cbac2e-d0ec-4315-b5fe-5a51745fce0d@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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