All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: "Ulf Hansson" <ulf.hansson@linaro.org>,
	"Michal Simek" <michal.simek@xilinx.com>,
	"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-mmc@vger.kernel.org
Subject: Re: [RESEND PATCH v5 0/2] Add phy support for arasan,sdhci-5.1
Date: Fri, 4 Mar 2016 11:18:10 +0200	[thread overview]
Message-ID: <56D952D2.9070800@intel.com> (raw)
In-Reply-To: <56D8E48B.1040604@rock-chips.com>

On 04/03/16 03:27, Shawn Lin wrote:
> 在 2016/2/20 6:23, Ulf Hansson 写道:
>>
>> Den 19 feb 2016 3:24 fm skrev "Shawn Lin" <shawn.lin@rock-chips.com
>> <mailto:shawn.lin@rock-chips.com>>:
>>  >
>>  >
>>  > Hello Ulf and Adrian,
>>  >
>>  > Sorry for delay the new version for this topic. Actually I have no
>>  > platform available to test phy stuff since v4. Now, I can rework it.:)
>>  > I remove rpm support from v5 because this patchset just need to focus
>>  > on phy stuff, which will make the changes more precise. Another reason
>>  > is that phy_power_on take too much time from rpm, however the power
>> profit
>>  > gained from phy_power_off is little due to the low power mechanism
>> with the
>>  > phy itself observed from experiments.
>>  >
>>  > v4 can be found here:
>>  > https://patchwork.kernel.org/patch/7463251/
>>  >
>>  > Note:
>>  > Phy is mandatory requirement for arasan,sdhci-5.1, so we introduce
>>  > generic phy support for sdhci-of-arasan.
>>  >
>>  >
>>  > Shawn Lin (2):
>>  >   Documentation: bindings: add description of phy for sdhci-of-arasan
>>  >   mmc: sdhci-of-arasan: add phy support for sdhci-of-arasan
>>  >
>>  >  .../devicetree/bindings/mmc/arasan,sdhci.txt       | 20 ++++++-
>>  >  drivers/mmc/host/sdhci-of-arasan.c                 | 66
>> ++++++++++++++++++++--
>>  >  2 files changed, 80 insertions(+), 6 deletions(-)
>>  >
>>  > --
>>  > 2.3.7
>>  >
>>  >
>>
>> This looks good to me! When acks has been received I am ready to queue
>> it for next.
>>
> 
> Hi Adrian,
> 
>     Any chance to look at this patch? I assume Ulf need your ack for
> sdhci* patch. :)

Just sent some comments.

      reply	other threads:[~2016-03-04  9:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19  2:18 [RESEND PATCH v5 0/2] Add phy support for arasan,sdhci-5.1 Shawn Lin
2016-02-19  2:18 ` Shawn Lin
2016-02-19  2:19 ` [RESEND PATCH v5 1/2] Documentation: bindings: add description of phy for sdhci-of-arasan Shawn Lin
2016-02-23 20:29   ` Rob Herring
2016-02-23 20:29     ` Rob Herring
2016-02-19  2:20 ` [RESEND PATCH v5 2/2] mmc: sdhci-of-arasan: add phy support " Shawn Lin
2016-03-04  9:14   ` Adrian Hunter
2016-03-04 10:24     ` Shawn Lin
2016-03-04 10:24       ` Shawn Lin
2016-03-04 12:12       ` Adrian Hunter
2016-03-05  1:55         ` Shawn Lin
2016-02-19 22:23 ` [RESEND PATCH v5 0/2] Add phy support for arasan,sdhci-5.1 Ulf Hansson
2016-03-04  1:27   ` Shawn Lin
2016-03-04  1:27     ` Shawn Lin
2016-03-04  9:18     ` Adrian Hunter [this message]

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=56D952D2.9070800@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=robh+dt@kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=soren.brinkmann@xilinx.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 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.