From: Jiri Pirko <jiri@resnulli.us>
To: Vadim Fedorenko <vfedorenko@novek.ru>
Cc: Jakub Kicinski <kuba@kernel.org>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Vadim Fedorenko <vadfed@fb.com>, Aya Levin <ayal@nvidia.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org
Subject: Re: [RFC PATCH v2 2/3] dpll: add netlink events
Date: Thu, 29 Sep 2022 14:13:05 +0200 [thread overview]
Message-ID: <YzWL0QpCYDEwtj5P@nanopsycho> (raw)
In-Reply-To: <20220626192444.29321-3-vfedorenko@novek.ru>
Sun, Jun 26, 2022 at 09:24:43PM CEST, vfedorenko@novek.ru wrote:
>From: Vadim Fedorenko <vadfed@fb.com>
>
>Add netlink interface to enable notification of users about
>events in DPLL framework. Part of this interface should be
>used by drivers directly, i.e. lock status changes.
I don't get why this is a separate patch. I believe it should be
squashed to the previous one, making it easier to review as a whole
thing.
>
>Signed-off-by: Vadim Fedorenko <vadfed@fb.com>
>---
> drivers/dpll/dpll_core.c | 2 +
> drivers/dpll/dpll_netlink.c | 141 ++++++++++++++++++++++++++++++++++++
> drivers/dpll/dpll_netlink.h | 7 ++
> 3 files changed, 150 insertions(+)
>
>diff --git a/drivers/dpll/dpll_core.c b/drivers/dpll/dpll_core.c
>index dc0330e3687d..387644aa910e 100644
>--- a/drivers/dpll/dpll_core.c
>+++ b/drivers/dpll/dpll_core.c
>@@ -97,6 +97,8 @@ struct dpll_device *dpll_device_alloc(struct dpll_device_ops *ops, int sources_c
> mutex_unlock(&dpll_device_xa_lock);
> dpll->priv = priv;
>
>+ dpll_notify_device_create(dpll->id, dev_name(&dpll->dev));
>+
> return dpll;
>
> error:
>diff --git a/drivers/dpll/dpll_netlink.c b/drivers/dpll/dpll_netlink.c
>index e15106f30377..4b1684fcf41e 100644
>--- a/drivers/dpll/dpll_netlink.c
>+++ b/drivers/dpll/dpll_netlink.c
>@@ -48,6 +48,8 @@ struct param {
> int dpll_source_type;
> int dpll_output_id;
> int dpll_output_type;
>+ int dpll_status;
>+ const char *dpll_name;
> };
>
> struct dpll_dump_ctx {
>@@ -239,6 +241,8 @@ static int dpll_genl_cmd_set_source(struct param *p)
> ret = dpll->ops->set_source_type(dpll, src_id, type);
> mutex_unlock(&dpll->lock);
>
>+ dpll_notify_source_change(dpll->id, src_id, type);
>+
> return ret;
> }
>
>@@ -262,6 +266,8 @@ static int dpll_genl_cmd_set_output(struct param *p)
> ret = dpll->ops->set_source_type(dpll, out_id, type);
> mutex_unlock(&dpll->lock);
>
>+ dpll_notify_source_change(dpll->id, out_id, type);
>+
> return ret;
> }
>
>@@ -438,6 +444,141 @@ static struct genl_family dpll_gnl_family __ro_after_init = {
> .pre_doit = dpll_pre_doit,
> };
>
>+static int dpll_event_device_create(struct param *p)
>+{
>+ if (nla_put_u32(p->msg, DPLLA_DEVICE_ID, p->dpll_id) ||
>+ nla_put_string(p->msg, DPLLA_DEVICE_NAME, p->dpll_name))
>+ return -EMSGSIZE;
>+
>+ return 0;
>+}
>+
>+static int dpll_event_device_delete(struct param *p)
>+{
>+ if (nla_put_u32(p->msg, DPLLA_DEVICE_ID, p->dpll_id))
>+ return -EMSGSIZE;
>+
>+ return 0;
>+}
>+
>+static int dpll_event_status(struct param *p)
>+{
>+ if (nla_put_u32(p->msg, DPLLA_DEVICE_ID, p->dpll_id) ||
>+ nla_put_u32(p->msg, DPLLA_LOCK_STATUS, p->dpll_status))
>+ return -EMSGSIZE;
>+
>+ return 0;
>+}
>+
>+static int dpll_event_source_change(struct param *p)
>+{
>+ if (nla_put_u32(p->msg, DPLLA_DEVICE_ID, p->dpll_id) ||
>+ nla_put_u32(p->msg, DPLLA_SOURCE_ID, p->dpll_source_id) ||
>+ nla_put_u32(p->msg, DPLLA_SOURCE_TYPE, p->dpll_source_type))
>+ return -EMSGSIZE;
>+
>+ return 0;
>+}
>+
>+static int dpll_event_output_change(struct param *p)
>+{
>+ if (nla_put_u32(p->msg, DPLLA_DEVICE_ID, p->dpll_id) ||
>+ nla_put_u32(p->msg, DPLLA_OUTPUT_ID, p->dpll_output_id) ||
>+ nla_put_u32(p->msg, DPLLA_OUTPUT_TYPE, p->dpll_output_type))
>+ return -EMSGSIZE;
>+
>+ return 0;
>+}
>+
>+static cb_t event_cb[] = {
>+ [DPLL_EVENT_DEVICE_CREATE] = dpll_event_device_create,
>+ [DPLL_EVENT_DEVICE_DELETE] = dpll_event_device_delete,
>+ [DPLL_EVENT_STATUS_LOCKED] = dpll_event_status,
>+ [DPLL_EVENT_STATUS_UNLOCKED] = dpll_event_status,
>+ [DPLL_EVENT_SOURCE_CHANGE] = dpll_event_source_change,
>+ [DPLL_EVENT_OUTPUT_CHANGE] = dpll_event_output_change,
>+};
>+/*
>+ * Generic netlink DPLL event encoding
>+ */
>+static int dpll_send_event(enum dpll_genl_event event,
>+ struct param *p)
"struct param". Can't you please maintain some namespace for
function/struct names?
>+{
>+ struct sk_buff *msg;
>+ int ret = -EMSGSIZE;
>+ void *hdr;
>+
>+ msg = genlmsg_new(NLMSG_GOODSIZE, GFP_KERNEL);
>+ if (!msg)
>+ return -ENOMEM;
>+ p->msg = msg;
>+
>+ hdr = genlmsg_put(msg, 0, 0, &dpll_gnl_family, 0, event);
>+ if (!hdr)
>+ goto out_free_msg;
>+
>+ ret = event_cb[event](p);
>+ if (ret)
>+ goto out_cancel_msg;
>+
>+ genlmsg_end(msg, hdr);
>+
>+ genlmsg_multicast(&dpll_gnl_family, msg, 0, 1, GFP_KERNEL);
>+
>+ return 0;
>+
>+out_cancel_msg:
>+ genlmsg_cancel(msg, hdr);
>+out_free_msg:
>+ nlmsg_free(msg);
>+
>+ return ret;
>+}
>+
>+int dpll_notify_device_create(int dpll_id, const char *name)
>+{
>+ struct param p = { .dpll_id = dpll_id, .dpll_name = name };
>+
>+ return dpll_send_event(DPLL_EVENT_DEVICE_CREATE, &p);
Just do that automatically in register() and avoid the need to rely on
drivers to be so good to do it themselves. They won't.
>+}
>+
>+int dpll_notify_device_delete(int dpll_id)
>+{
>+ struct param p = { .dpll_id = dpll_id };
>+
>+ return dpll_send_event(DPLL_EVENT_DEVICE_DELETE, &p);
>+}
>+
>+int dpll_notify_status_locked(int dpll_id)
For all notification functions called from the driver, please use struct
dpll as an arg.
>+{
>+ struct param p = { .dpll_id = dpll_id, .dpll_status = 1 };
>+
>+ return dpll_send_event(DPLL_EVENT_STATUS_LOCKED, &p);
>+}
>+
>+int dpll_notify_status_unlocked(int dpll_id)
>+{
>+ struct param p = { .dpll_id = dpll_id, .dpll_status = 0 };
>+
>+ return dpll_send_event(DPLL_EVENT_STATUS_UNLOCKED, &p);
>+}
>+
>+int dpll_notify_source_change(int dpll_id, int source_id, int source_type)
>+{
>+ struct param p = { .dpll_id = dpll_id, .dpll_source_id = source_id,
>+ .dpll_source_type = source_type };
>+
>+ return dpll_send_event(DPLL_EVENT_SOURCE_CHANGE, &p);
>+}
>+
>+int dpll_notify_output_change(int dpll_id, int output_id, int output_type)
>+{
>+ struct param p = { .dpll_id = dpll_id, .dpll_output_id = output_id,
>+ .dpll_output_type = output_type };
>+
>+ return dpll_send_event(DPLL_EVENT_OUTPUT_CHANGE, &p);
>+}
>+
> int __init dpll_netlink_init(void)
> {
> return genl_register_family(&dpll_gnl_family);
>diff --git a/drivers/dpll/dpll_netlink.h b/drivers/dpll/dpll_netlink.h
>index e2d100f59dd6..0dc81320f982 100644
>--- a/drivers/dpll/dpll_netlink.h
>+++ b/drivers/dpll/dpll_netlink.h
>@@ -3,5 +3,12 @@
> * Copyright (c) 2021 Meta Platforms, Inc. and affiliates
> */
>
>+int dpll_notify_device_create(int dpll_id, const char *name);
>+int dpll_notify_device_delete(int dpll_id);
>+int dpll_notify_status_locked(int dpll_id);
>+int dpll_notify_status_unlocked(int dpll_id);
>+int dpll_notify_source_change(int dpll_id, int source_id, int source_type);
>+int dpll_notify_output_change(int dpll_id, int output_id, int output_type);
Why these are not returning void? Does driver care about the return
value? Why?
>+
> int __init dpll_netlink_init(void);
> void dpll_netlink_finish(void);
>--
>2.27.0
>
next prev parent reply other threads:[~2022-09-29 12:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 19:24 [RFC PATCH v2 0/3] Create common DPLL/clock configuration API Vadim Fedorenko
2022-06-26 19:24 ` [RFC PATCH v2 1/3] dpll: Add DPLL framework base functions Vadim Fedorenko
2022-06-29 8:34 ` Stephen Boyd
2022-06-29 23:37 ` Vadim Fedorenko
2022-07-11 9:01 ` Kubalewski, Arkadiusz
2022-07-14 23:23 ` Vadim Fedorenko
2022-07-15 17:31 ` Kubalewski, Arkadiusz
2022-06-26 19:24 ` [RFC PATCH v2 2/3] dpll: add netlink events Vadim Fedorenko
2022-07-11 9:02 ` Kubalewski, Arkadiusz
2022-07-14 23:29 ` Vadim Fedorenko
2022-07-15 17:31 ` Kubalewski, Arkadiusz
2022-08-02 14:02 ` Kubalewski, Arkadiusz
2022-08-02 15:52 ` Jakub Kicinski
2022-08-03 0:05 ` Vadim Fedorenko
2022-08-03 15:21 ` Stephen Hemminger
2022-09-29 12:13 ` Jiri Pirko [this message]
2022-09-30 0:48 ` Vadim Fedorenko
2022-06-26 19:24 ` [RFC PATCH v2 3/3] ptp_ocp: implement DPLL ops Vadim Fedorenko
2022-06-27 19:34 ` Jonathan Lemon
2022-06-27 22:13 ` Vadim Fedorenko
2022-06-28 19:11 ` Jonathan Lemon
2022-06-29 3:24 ` Jakub Kicinski
2022-06-29 23:31 ` Vadim Fedorenko
2022-09-29 11:33 ` Jiri Pirko
2022-09-30 0:56 ` Vadim Fedorenko
2022-09-01 12:02 ` [RFC PATCH v2 0/3] Create common DPLL/clock configuration API Gal Pressman
2022-09-29 11:40 ` Jiri Pirko
2022-09-30 0:44 ` Vadim Fedorenko
2022-09-30 8:33 ` Jiri Pirko
2022-09-30 14:33 ` Jakub Kicinski
2022-10-01 5:47 ` Jiri Pirko
2022-10-01 14:18 ` Jakub Kicinski
2022-10-02 14:35 ` Jiri Pirko
2022-10-03 14:28 ` Jakub Kicinski
2022-10-03 17:20 ` Vadim Fedorenko
2022-10-04 6:33 ` Jiri Pirko
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=YzWL0QpCYDEwtj5P@nanopsycho \
--to=jiri@resnulli.us \
--cc=arkadiusz.kubalewski@intel.com \
--cc=ayal@nvidia.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vadfed@fb.com \
--cc=vfedorenko@novek.ru \
/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