From: David Mosberger-Tang <davidm@egauge.net>
To: Ajay Singh <ajay.kathat@microchip.com>
Cc: Adham Abozaeid <adham.abozaeid@microchip.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
devicetree@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Kalle Valo <kvalo@kernel.org>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
David Mosberger-Tang <davidm@egauge.net>
Subject: [PATCH v7 0/2] wilc1000: Add reset/enable GPIO support to SPI driver
Date: Tue, 21 Dec 2021 21:25:34 +0000 (UTC) [thread overview]
Message-ID: <20211221212531.4011609-1-davidm@egauge.net> (raw)
v7:
- Rebase to latest wireless-drivers-next.
v6:
- Convert line comments to block comments.
v5:
- Fix a dt_binding_check error by including
<dt-bindings/gpio/gpio.h> in microchip,wilc1000.yaml.
v4:
- Simplify wilc_wlan_power() by letting gpiod_set_value()
handle NULL gpios.
v3:
- Fix to include correct header file.
- Rename wilc_set_enable() to wilc_wlan_power().
- Use devm_gpiod_get{,_optional}() instead of of_get_named_gpio()
- Parse GPIO pins once at probe time.
v2:
- Split documentation update and driver changes into seprate
patches.
David Mosberger-Tang (2):
wilc1000: Add reset/enable GPIO support to SPI driver
wilc1000: Document enable-gpios and reset-gpios properties
.../net/wireless/microchip,wilc1000.yaml | 19 ++++++
drivers/net/wireless/microchip/wilc1000/spi.c | 62 ++++++++++++++++++-
.../net/wireless/microchip/wilc1000/wlan.c | 2 +-
3 files changed, 79 insertions(+), 4 deletions(-)
--
2.25.1
next reply other threads:[~2021-12-21 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 21:25 David Mosberger-Tang [this message]
2021-12-21 21:25 ` [PATCH v7 1/2] wilc1000: Add reset/enable GPIO support to SPI driver David Mosberger-Tang
2021-12-22 6:21 ` Claudiu.Beznea
2021-12-22 17:51 ` Kalle Valo
2021-12-21 21:25 ` [PATCH v7 2/2] wilc1000: Document enable-gpios and reset-gpios properties David Mosberger-Tang
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=20211221212531.4011609-1-davidm@egauge.net \
--to=davidm@egauge.net \
--cc=adham.abozaeid@microchip.com \
--cc=ajay.kathat@microchip.com \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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 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.