From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
linux-wpan@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, David Girault <david.girault@qorvo.com>,
Romuald Despres <romuald.despres@qorvo.com>,
Frederic Blain <frederic.blain@qorvo.com>,
Nicolas Schodet <nico@ni.fr.eu.org>,
Guilhem Imberton <guilhem.imberton@qorvo.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH wpan-next 0/2] ieee802154: Handle imited devices
Date: Fri, 24 Mar 2023 12:05:56 +0100 [thread overview]
Message-ID: <20230324110558.90707-1-miquel.raynal@bootlin.com> (raw)
As rightly pointed out by Alexander a few months ago, ca8210 devices
will not support sending frames which are not pure datagrams (hardMAC
wired to the softMAC layer). In order to not confuse users and clarify
that scanning and beaconing is not supported on these devices, let's add
a flag to prevent them to be used with the new APIs.
Miquel Raynal (2):
net: ieee802154: Handle limited devices with only datagram support
ieee802154: ca8210: Flag the driver as being limited
drivers/net/ieee802154/ca8210.c | 3 ++-
include/net/cfg802154.h | 3 +++
net/ieee802154/nl802154.c | 10 ++++++++++
3 files changed, 15 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2023-03-24 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 11:05 Miquel Raynal [this message]
2023-03-24 11:05 ` [PATCH wpan-next 1/2] net: ieee802154: Handle limited devices with only datagram support Miquel Raynal
2023-03-24 11:05 ` [PATCH wpan-next 2/2] ieee802154: ca8210: Flag the driver as being limited Miquel Raynal
2023-03-24 13:56 ` [PATCH wpan-next 0/2] ieee802154: Handle imited devices Alexander Aring
2023-03-24 16:21 ` Stefan Schmidt
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=20230324110558.90707-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=david.girault@qorvo.com \
--cc=edumazet@google.com \
--cc=frederic.blain@qorvo.com \
--cc=guilhem.imberton@qorvo.com \
--cc=kuba@kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico@ni.fr.eu.org \
--cc=pabeni@redhat.com \
--cc=romuald.despres@qorvo.com \
--cc=stefan@datenfreihafen.org \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.