From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>
Subject: [PATCH net-next v4 0/4] ieee802154: ca8210: Sparse fix and GPIOd conversion
Date: Wed, 5 Mar 2025 12:55:33 +0200 [thread overview]
Message-ID: <20250305105656.2133487-1-andriy.shevchenko@linux.intel.com> (raw)
The main part is the patch 3 that converts the driver to GPIO descriptor APIs,
the first one is just an ad-hoc fix WRT sparse complains on the bitwise
types misuse. The second one is a small cleanup that helps patch 3 to be nicer.
In v4:
- split DT patch (Krzysztof)
- collected tags (Miquel)
In v3:
- inverted polarity of the reset line in accordance with datasheet (Linus)
- added quirk for the out-of-tree admittedly wrong DTS implementations
- collected tags (Linus)
In v2:
- split and extended cleanup pieces into patch 2 (Miquel)
- updated kernel doc for changed members (Miquel)
- unfolded PTR_ERR_OR_ZERO() to the preferred pattern (Miquel)
- collected tags (Miquel)
Andy Shevchenko (4):
ieee802154: ca8210: Use proper setters and getters for bitwise types
ieee802154: ca8210: Get platform data via dev_get_platdata()
ieee802154: ca8210: Switch to using gpiod API
dt-bindings: ieee802154: ca8210: Update polarity of the reset pin
.../bindings/net/ieee802154/ca8210.txt | 2 +-
drivers/gpio/gpiolib-of.c | 9 +++
drivers/net/ieee802154/ca8210.c | 78 ++++++++-----------
3 files changed, 41 insertions(+), 48 deletions(-)
--
2.47.2
next reply other threads:[~2025-03-05 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 10:55 Andy Shevchenko [this message]
2025-03-05 10:55 ` [PATCH net-next v4 1/4] ieee802154: ca8210: Use proper setters and getters for bitwise types Andy Shevchenko
2025-03-05 10:55 ` [PATCH net-next v4 2/4] ieee802154: ca8210: Get platform data via dev_get_platdata() Andy Shevchenko
2025-03-05 10:55 ` [PATCH net-next v4 3/4] ieee802154: ca8210: Switch to using gpiod API Andy Shevchenko
2025-03-05 10:55 ` [PATCH net-next v4 4/4] dt-bindings: ieee802154: ca8210: Update polarity of the reset pin Andy Shevchenko
2025-03-05 16:27 ` Conor Dooley
2025-03-06 21:05 ` [PATCH net-next v4 0/4] ieee802154: ca8210: Sparse fix and GPIOd conversion 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=20250305105656.2133487-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alex.aring@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=stefan@datenfreihafen.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 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.