From: Loic Poulain <loic.poulain@linaro.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
Network Development <netdev@vger.kernel.org>,
M Chetan Kumar <m.chetan.kumar@intel.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [RFC 3/4] wwan: add interface creation support
Date: Tue, 1 Jun 2021 11:37:48 +0200 [thread overview]
Message-ID: <CAMZdPi-ZaH8WWKfhfKzy0OKpUtNAiCUfekh9R1de5awFP-ed=A@mail.gmail.com> (raw)
In-Reply-To: <20210601100320.7d39e9c33a18.I0474861dad426152ac7e7afddfd7fe3ce70870e4@changeid>
Hi Johannes,
On Tue, 1 Jun 2021 at 10:05, Johannes Berg <johannes@sipsolutions.net> wrote:
>
> From: Johannes Berg <johannes.berg@intel.com>
>
> Add support to create (and destroy) interfaces via a new
> rtnetlink kind "wwan". The responsible driver has to use
> the new wwan_register_ops() to make this possible.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> drivers/net/wwan/wwan_core.c | 219 ++++++++++++++++++++++++++++++++++-
> include/linux/wwan.h | 36 ++++++
> include/uapi/linux/wwan.h | 17 +++
> 3 files changed, 267 insertions(+), 5 deletions(-)
> create mode 100644 include/uapi/linux/wwan.h
>
> diff --git a/drivers/net/wwan/wwan_core.c b/drivers/net/wwan/wwan_core.c
> index cff04e532c1e..b1ad78f386bc 100644
> --- a/drivers/net/wwan/wwan_core.c
> +++ b/drivers/net/wwan/wwan_core.c
> @@ -13,6 +13,8 @@
> #include <linux/slab.h>
> #include <linux/types.h>
> #include <linux/wwan.h>
> +#include <net/rtnetlink.h>
> +#include <uapi/linux/wwan.h>
>
> #define WWAN_MAX_MINORS 256 /* 256 minors allowed with register_chrdev() */
>
> @@ -524,24 +526,231 @@ static const struct file_operations wwan_port_fops = {
> .llseek = noop_llseek,
> };
>
> +struct wwan_dev_reg {
> + struct list_head list;
> + struct device *dev;
> + const struct wwan_ops *ops;
> + void *ctxt;
> +};
> +
> +static DEFINE_MUTEX(wwan_mtx);
> +static LIST_HEAD(wwan_devs);
> +
> +int wwan_register_ops(struct device *parent, const struct wwan_ops *ops,
> + void *ctxt)
> +{
> + struct wwan_dev_reg *reg;
> + int ret;
> +
> + if (WARN_ON(!parent || !ops))
> + return -EINVAL;
> +
> + mutex_lock(&wwan_mtx);
> + list_for_each_entry(reg, &wwan_devs, list) {
> + if (WARN_ON(reg->dev == parent)) {
> + ret = -EBUSY;
> + goto out;
> + }
> + }
Thanks for this, overall it looks good to me, but just checking why
you're not using the wwan_dev internally to create-or-pick wwan_dev
(wwan_dev_create) and register ops to it, instead of having a global
new wwan_devs list.
> +
> + reg = kzalloc(sizeof(*reg), GFP_KERNEL);
> + if (!reg) {
> + ret = -ENOMEM;
> + goto out;
> + }
> +
> + reg->dev = parent;
> + reg->ops = ops;
> + reg->ctxt = ctxt;
> + list_add_tail(®->list, &wwan_devs);
> +
> + ret = 0;
> +
> +out:
> + mutex_unlock(&wwan_mtx);
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(wwan_register_ops);
Regards,
Loic
next prev parent reply other threads:[~2021-06-01 9:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 8:05 [RFC 0/4] wwan framework netdev creation Johannes Berg
2021-06-01 8:05 ` [RFC 1/4] iosm: fix stats and RCU bugs in RX Johannes Berg
2021-06-01 8:05 ` [RFC 2/4] rtnetlink: add alloc() method to rtnl_link_ops Johannes Berg
2021-06-01 8:05 ` [RFC 3/4] wwan: add interface creation support Johannes Berg
2021-06-01 9:37 ` Loic Poulain [this message]
2021-06-01 10:35 ` Johannes Berg
2021-06-02 6:52 ` Loic Poulain
2021-06-02 8:29 ` Johannes Berg
2021-06-03 7:00 ` Loic Poulain
2021-06-03 7:02 ` Kumar, M Chetan
2021-06-02 1:42 ` Sergey Ryazanov
2021-06-02 7:38 ` Johannes Berg
2021-06-02 12:45 ` Sergey Ryazanov
2021-06-02 12:56 ` Johannes Berg
2021-06-02 15:38 ` Sergey Ryazanov
2021-06-01 8:05 ` [RFC 4/4] iosm: convert to generic wwan ops Johannes Berg
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='CAMZdPi-ZaH8WWKfhfKzy0OKpUtNAiCUfekh9R1de5awFP-ed=A@mail.gmail.com' \
--to=loic.poulain@linaro.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=m.chetan.kumar@intel.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).