[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZBSbE+8p/u9hl0JI@nanopsycho>
Date: Fri, 17 Mar 2023 17:53:39 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Vadim Fedorenko <vadfed@...a.com>
Cc: Jakub Kicinski <kuba@...nel.org>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>,
Jonathan Lemon <jonathan.lemon@...il.com>,
Paolo Abeni <pabeni@...hat.com>,
Vadim Fedorenko <vadim.fedorenko@...ux.dev>, poros@...hat.com,
mschmidt@...hat.com, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
Michal Michalik <michal.michalik@...el.com>
Subject: Re: [PATCH RFC v6 1/6] dpll: spec: Add Netlink spec in YAML
Sun, Mar 12, 2023 at 03:28:02AM CET, vadfed@...a.com wrote:
>From: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>
>
[...]
>+ name: device-get
>+ doc: |
>+ Get list of DPLL devices (dump) or attributes of a single dpll device
>+ attribute-set: dpll
>+ flags: [ admin-perm ]
>+
[...]
>+ -
>+ name: pin-get
>+ doc: |
>+ Get list of pins and its attributes.
>+ - dump request without any attributes given - list all the pins in the system
>+ - dump request with target dpll - list all the pins registered with a given dpll device
>+ - do request with target dpll and target pin - single pin attributes
>+ attribute-set: dpll
>+ flags: [ admin-perm ]
Any particular reason to have admin cap required for get operations?
If not, please remove.
Powered by blists - more mailing lists