From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Tejun Heo <tj@kernel.org>, Hans de Goede <hdegoede@redhat.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Antoine Ténart" <antoine.tenart@free-electrons.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Ezequiel Garcia" <ezequiel.garcia@free-electrons.com>,
"Maxime Ripard" <maxime.ripard@free-electrons.com>,
"Boris BREZILLON" <boris.brezillon@free-electrons.com>,
"Jason Cooper" <jason@lakedaemon.net>,
"Andrew Lunn" <andrew@lunn.ch>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Gregory CLEMENT" <gregory.clement@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
"Lior Amsalem" <alior@marvell.com>,
"Tawfik Bayouk" <tawfik@marvell.com>,
"Nadav Haklai" <nadavh@marvell.com>,
"Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: [PATCH v3 0/4] ata: libahci: Allow using a regulator for each port
Date: Tue, 13 Jan 2015 15:22:29 +0100 [thread overview]
Message-ID: <1421158953-2957-1-git-send-email-gregory.clement@free-electrons.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 1985 bytes --]
Hi,
The current implementation of the libahci allows using one PHY per
port but we still have one single regulator for the whole
controller. This series adds the support of multiple regulators.
This is the third version of the series.
I use now the same binding introduced in the first version. This one
was acked in the first place by Hans and was discussed during the
review of the second version.
To be able to use it, I made the port the platform devices when the
device tree was used. An other change was to manage the deferred
case. The regulator were now attached to a different device that the
SATA host, so the devres_release_group don't manage them, and they
have to be released in a separate call.
Thanks,
Grégory
Changelog:
v2 -> v3:
- put back the regulator inside the sub-node ports
- made the ports platform devices when the device tree is used
- released the regulator in case of error in the probe function
v1 -> v2:
- Kept the case when no child node are present under the ahci node
- Fix the test done under the label disable_target_pwrs
- No more use an of_ version of the regulator framework and instead
associate each regulator of a port with an unique name.
- Added the acked-by on the clean-up patch
Gregory CLEMENT (4):
ata: libahci: Clean-up the ahci_platform_en/disable_phys functions
Documentation: bindings: Add the regulator property to the sub-nodes
AHCI bindings
ata: libahci: Allow using multiple regulators
ARM: mvebu: Armada 385 GP: Add regulators to the SATA port
.../devicetree/bindings/ata/ahci-platform.txt | 9 +-
arch/arm/boot/dts/armada-388-gp.dts | 126 +++++++++++
drivers/ata/ahci.h | 2 +-
drivers/ata/ahci_imx.c | 14 +-
drivers/ata/libahci_platform.c | 233 ++++++++++++++-------
include/linux/ahci_platform.h | 2 +
6 files changed, 302 insertions(+), 84 deletions(-)
--
1.9.1
next reply other threads:[~2015-01-13 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 14:22 Gregory CLEMENT [this message]
2015-01-13 14:22 ` [PATCH v3 1/4] ata: libahci: Clean-up the ahci_platform_en/disable_phys functions Gregory CLEMENT
2015-01-13 14:22 ` [PATCH v3 2/4] Documentation: bindings: Add the regulator property to the sub-nodes AHCI bindings Gregory CLEMENT
2015-01-13 14:22 ` [PATCH v3 3/4] ata: libahci: Allow using multiple regulators Gregory CLEMENT
2015-01-15 8:46 ` Hans de Goede
2015-01-15 10:50 ` Gregory CLEMENT
2015-01-13 14:22 ` [PATCH v3 4/4] ARM: mvebu: Armada 385 GP: Add regulators to the SATA port Gregory CLEMENT
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=1421158953-2957-1-git-send-email-gregory.clement@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=hdegoede@redhat.com \
--cc=jason@lakedaemon.net \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=nadavh@marvell.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.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
all inboxes | Powered by JetHome®