From: Arnd Bergmann <arnd@arndb.de>
To: Roger Quadros <rogerq@ti.com>
Cc: tj@kernel.org, sergei.shtylyov@cogentembedded.com, kishon@ti.com,
b.zolnierkie@samsung.com, hdegoede@redhat.com,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 0/3] ata: ahci_platform: Add PHY support and OMAP support
Date: Thu, 9 Jan 2014 12:05:24 +0100 [thread overview]
Message-ID: <201401091205.24818.arnd@arndb.de> (raw)
In-Reply-To: <1389264962-22858-1-git-send-email-rogerq@ti.com>
On Thursday 09 January 2014, Roger Quadros wrote:
> Hi,
>
> Some platforms have a PHY hooked up to the SATA controller.
> The PHY needs to be initialized and powered up for SATA to work.
> We do that using the Generic PHY framework in PATCH 2.
>
> In order to support SATA on the OMAP platforms we need to runtime
> resume the device before use. PATCH 3 takes care of that.
>
> PATCH 1 just updates the compatible list in the DT binding document.
>
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2014-01-09 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 10:55 [PATCH v4 0/3] ata: ahci_platform: Add PHY support and OMAP support Roger Quadros
2014-01-09 10:56 ` [PATCH v4 1/3] ata: ahci_platform: Update DT compatible list Roger Quadros
[not found] ` <1389264962-22858-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2014-01-09 10:56 ` [PATCH v4 2/3] ata: ahci_platform: Manage SATA PHY Roger Quadros
2014-01-09 11:20 ` Sergei Shtylyov
2014-01-09 11:37 ` Roger Quadros
2014-01-09 15:00 ` Tejun Heo
2014-01-20 8:20 ` Roger Quadros
2014-01-10 14:25 ` Kishon Vijay Abraham I
2014-01-09 10:56 ` [PATCH v4 3/3] ata: ahci_platform: runtime resume the device before use Roger Quadros
2014-01-09 11:05 ` Arnd Bergmann [this message]
2014-01-09 11:33 ` [PATCH v4 0/3] ata: ahci_platform: Add PHY support and OMAP support Bartlomiej Zolnierkiewicz
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=201401091205.24818.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=kishon@ti.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tj@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).