From: Ulf Hansson <ulf.hansson@linaro.org>
To: Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] mmc: pwrseq: sd8787: add support wilc1000 devices
Date: Tue, 24 Aug 2021 16:56:42 +0200 [thread overview]
Message-ID: <CAPDyKFrcBS2tf32H9+wsy7=TsHkaqtw0cZcSAgZc3XjnLzJ__w@mail.gmail.com> (raw)
In-Reply-To: <20210820092803.78523-1-claudiu.beznea@microchip.com>
On Fri, 20 Aug 2021 at 11:30, Claudiu Beznea
<claudiu.beznea@microchip.com> wrote:
>
> Hi,
>
> This series adds support for WILC1000 devices on pwrseq-sd8787 driver.
> WILC1000 devices needs a minimum delay of 5ms b/w reset and power lines.
> Adapt the sd8787 driver for this by adding a new compatible for WILC1000
> devices and specify the delay on .data field of struct of_device_id.
>
> Thank you,
> Claudiu Beznea
>
> Changes in v3:
> - fixed dt binding compilation
>
> Changes in v2:
> - changed cover letter title (it was: mmc: pwrseq: sd8787: add support
> for selectable)
> - use new compatible in pwrseq-sd8787 driver instead of adding a new
> binding for specifying the delay; with this, the patch 1/1 from v1 is
> not necessary
> - adapt patch 3/3 from this version with the new compatible
>
>
> Claudiu Beznea (3):
> dt-bindings: pwrseq-sd8787: add binding for wilc1000
> mmc: pwrseq: sd8787: add support for wilc1000
> mmc: pwrseq: add wilc1000_sdio dependency for pwrseq_sd8787
>
> Eugen Hristev (1):
> ARM: dts: at91: sama5d27_wlsom1: add wifi device
>
> .../bindings/mmc/mmc-pwrseq-sd8787.yaml | 4 +-
> arch/arm/boot/dts/at91-sama5d27_wlsom1.dtsi | 71 +++++++++++++++++++
> drivers/mmc/core/Kconfig | 2 +-
> drivers/mmc/core/pwrseq_sd8787.c | 11 ++-
> 4 files changed, 84 insertions(+), 4 deletions(-)
>
Applied patch1 -> patch3, thanks! I leave patch 4 for soc maintainers.
Kind regards
Uffe
next prev parent reply other threads:[~2021-08-24 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 9:27 [PATCH v3 0/4] mmc: pwrseq: sd8787: add support wilc1000 devices Claudiu Beznea
2021-08-20 9:28 ` [PATCH v3 1/4] dt-bindings: pwrseq-sd8787: add binding for wilc1000 Claudiu Beznea
2021-08-24 12:24 ` Rob Herring
2021-08-20 9:28 ` [PATCH v3 2/4] mmc: pwrseq: sd8787: add support " Claudiu Beznea
2021-08-20 9:28 ` [PATCH v3 3/4] mmc: pwrseq: add wilc1000_sdio dependency for pwrseq_sd8787 Claudiu Beznea
2021-08-20 9:28 ` [PATCH v3 4/4] ARM: dts: at91: sama5d27_wlsom1: add wifi device Claudiu Beznea
2021-08-24 12:23 ` Rob Herring
2021-08-24 15:26 ` Claudiu.Beznea
2021-08-24 14:56 ` Ulf Hansson [this message]
2021-09-01 8:08 ` [PATCH v3 0/4] mmc: pwrseq: sd8787: add support wilc1000 devices Nicolas Ferre
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='CAPDyKFrcBS2tf32H9+wsy7=TsHkaqtw0cZcSAgZc3XjnLzJ__w@mail.gmail.com' \
--to=ulf.hansson@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--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;
as well as URLs for NNTP newsgroup(s).