# Re: \[PATCH net-next v2 07/14\] dpll: dpllsim: Add support to get/set priority on input pins

- From: Ivan Vecera \<ivecera@redhat.com\>
- Date: 2026-11-06 10:49:48 
- List: netdev
- Page: https://ratatoskr.run/netdev/2026/11/17877443
- Thread: https://ratatoskr.run/netdev/2026/11/17871508/t.md

```text
On 11/5/26 16:18, Petr Oros wrote:
> Add support for getting and setting the priority of input pins.
> Implement the prio_get and prio_set callbacks and advertise the
> priority-can-change capability for input pins, which includes the MUX
> type pins since those are always inputs.
>
> The initial priority of a pin is configured through a new prio
> attribute of the pin directory, which takes a value between 0 and 255
> and defaults to 128, so that a test can lay out the reference order
> before the device goes live. Like the other pin attributes it is
> writable only while the device is not live. Priority changes made over
> netlink are stored and reported back, they will drive the automatic
> reference selection once the simulation loop exists. The setter
> rejects a value above 255 with EINVAL and an extack message. A priority
> is meaningful for input pins only, so live fails with EINVAL when an
> output pin was given a priority other than the default, next to the
> frequency validation.
>
> Signed-off-by: Petr Oros<redacted>

Reviewed-by: Ivan Vecera <ivecera@redhat.com>

```