From: Kalle Valo <kvalo@codeaurora.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Matt Ranostay <matt@ranostay.consulting>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mmc\@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"devicetree\@vger.kernel.org" <devicetree@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: [PATCH v3 2/2] mmc: pwrseq: add support for Marvell SD8787 chip
Date: Thu, 19 Jan 2017 22:10:22 +0200 [thread overview]
Message-ID: <87efzyhkup.fsf@purkki.adurom.net> (raw)
In-Reply-To: <CAPDyKFpcKuybQmhqCkaAkOM5d+ubU8O8=adLm+PXwc=+N87vng@mail.gmail.com> (Ulf Hansson's message of "Thu, 19 Jan 2017 15:13:12 +0100")
Ulf Hansson <ulf.hansson@linaro.org> writes:
> Twisting my head around how this could be integrated smoothly into
> pwrseq simple. No, I just can find a good way forward without messing
> up pwrseq simple itself.
>
> So, for now I decided (once more :-), that let's keep this as separate driver!
>
> Perhaps, following device specific mmc pwrseq drivers will needs
> something similar, but in such case we can look into that then.
> Thinking about cw1200 for example.
>
> Let's get Rob's ack for the DT bindings, seems almost there, then I
> will queue this.
Just to confirm, you will take the whole set (including the bindings
patch)?
--
Kalle Valo
next prev parent reply other threads:[~2017-01-19 20:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 5:29 [PATCH v3 0/2] mmc: pwrseq: add support for Marvell SD8787 chip Matt Ranostay
2017-01-13 5:29 ` [PATCH v3 1/2] devicetree: document new marvell-8xxx and pwrseq-sd8787 options Matt Ranostay
2017-01-18 22:02 ` Rob Herring
2017-01-13 5:29 ` [PATCH v3 2/2] mmc: pwrseq: add support for Marvell SD8787 chip Matt Ranostay
2017-01-13 7:16 ` Shawn Lin
2017-01-15 21:41 ` Matt Ranostay
2017-01-16 2:35 ` Shawn Lin
2017-01-18 7:50 ` Matt Ranostay
2017-01-19 12:50 ` Ulf Hansson
2017-01-19 14:13 ` Ulf Hansson
2017-01-19 20:10 ` Kalle Valo [this message]
2017-01-19 20:30 ` Ulf Hansson
2017-01-20 2:42 ` Shawn Lin
2017-01-20 7:31 ` Ulf Hansson
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=87efzyhkup.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matt@ranostay.consulting \
--cc=shawn.lin@rock-chips.com \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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