From: <Ajay.Kathat@microchip.com>
To: <davidm@egauge.net>, <kvalo@codeaurora.org>
Cc: <davem@davemloft.net>, <kuba@kernel.org>, <robh+dt@kernel.org>,
<Claudiu.Beznea@microchip.com>, <adham.abozaeid@microchip.com>,
<linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wilc1000: Add reset/enable GPIO support to SPI driver
Date: Thu, 2 Dec 2021 15:58:27 +0000 [thread overview]
Message-ID: <3dc58b44-98c4-c733-1170-e587a9ad7efc@microchip.com> (raw)
In-Reply-To: <20211202034348.2901092-1-davidm@egauge.net>
On 02/12/21 09:25, David Mosberger-Tang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> This patch is based on similar code from the linux4sam/linux-at91 GIT
> repository.
>
> For the SDIO driver, the RESET/ENABLE pins of WILC1000 may be
> controlled through the SDIO power sequence driver. This commit adds
> analogous support for the SPI driver. Specifically, during bus
> probing, the chip will be reset-cycled and during unloading, the chip
> will be placed into reset and disabled (both to reduce power
> consumption and to ensure the WiFi radio is off).
>
> Both RESET and ENABLE GPIOs are optional. However, if the ENABLE GPIO
> is specified, then the RESET GPIO also must be specified as otherwise
> there is no way to ensure proper timing of the ENABLE/RESET sequence.
>
> Signed-off-by: David Mosberger-Tang <davidm@egauge.net>
Thanks!
Acked-by: Ajay Singh <ajay.kathat@microchip.com>
next prev parent reply other threads:[~2021-12-02 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 3:55 David Mosberger-Tang
2021-12-02 15:58 ` Ajay.Kathat [this message]
2021-12-07 10:11 ` Claudiu.Beznea
2021-12-07 12:57 ` Ajay.Kathat
2021-12-08 6:08 ` 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=3dc58b44-98c4-c733-1170-e587a9ad7efc@microchip.com \
--to=ajay.kathat@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=adham.abozaeid@microchip.com \
--cc=davem@davemloft.net \
--cc=davidm@egauge.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®