From: Hans de Goede <hdegoede@redhat.com>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>,
Tejun Heo <tj@kernel.org>,
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>,
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: Re: [PATCH v4 0/4] ata: libahci: Allow using a regulator for each port
Date: Fri, 16 Jan 2015 08:58:18 +0100 [thread overview]
Message-ID: <54B8C49A.9070302@redhat.com> (raw)
In-Reply-To: <1421330978-9694-1-git-send-email-gregory.clement@free-electrons.com>
Hi,
On 15-01-15 15:09, Gregory CLEMENT wrote:
> 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 forth version of the series.
>
> The improvement of this version is the use of
> ahci_platform_put_resources to put the reference to the regulators.
>
> Thanks,
>
> Grégory
Thanks, patches 1 - 3 look good and are:
Acked-by: Hans de Goede <hdegoede@redhat.com>
Tejun, can you please queue up 1 - 3 ?
I still have some remarks wrt patch 4 (*), and it should probably go
upstream through another tree anyways.
Regards,
Hans
*) I didn't look closely at patch 4 as it seemed trivial, until now
that is ...
>
> Changelog:
>
> v3 -> v4
> - Moved putting the reference to the regulators into the
> ahci_platform_put_resources function.
> - Tested the port_dev pointer before dereferencing.
>
> 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 | 236 ++++++++++++++-------
> include/linux/ahci_platform.h | 2 +
> 6 files changed, 305 insertions(+), 84 deletions(-)
>
next prev parent reply other threads:[~2015-01-16 7:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 14:09 [PATCH v4 0/4] ata: libahci: Allow using a regulator for each port Gregory CLEMENT
2015-01-15 14:09 ` [PATCH v4 1/4] ata: libahci: Clean-up the ahci_platform_en/disable_phys functions Gregory CLEMENT
2015-01-15 14:09 ` [PATCH v4 2/4] Documentation: bindings: Add the regulator property to the sub-nodes AHCI bindings Gregory CLEMENT
2015-01-15 14:09 ` [PATCH v4 3/4] ata: libahci: Allow using multiple regulators Gregory CLEMENT
2015-01-15 14:09 ` [PATCH v4 4/4] ARM: mvebu: Armada 385 GP: Add regulators to the SATA port Gregory CLEMENT
2015-01-16 8:17 ` Hans de Goede
2015-01-16 9:27 ` Gregory CLEMENT
2015-01-16 10:10 ` Hans de Goede
2015-01-16 12:37 ` Mark Brown
2015-01-16 14:27 ` Gregory CLEMENT
2015-01-16 15:34 ` Mark Brown
2015-01-16 19:13 ` Hans de Goede
2015-01-16 19:44 ` Mark Brown
2015-01-16 19:12 ` Hans de Goede
2015-01-16 20:25 ` Mark Brown
2015-01-17 8:48 ` Hans de Goede
2015-01-17 13:14 ` Mark Brown
2015-01-17 14:28 ` Hans de Goede
2015-01-18 12:35 ` Mark Brown
2015-01-18 15:29 ` Hans de Goede
2015-01-18 19:28 ` Mark Brown
2015-01-16 7:58 ` Hans de Goede [this message]
2015-01-19 14:54 ` [PATCH v4 0/4] ata: libahci: Allow using a regulator for each port Tejun Heo
2015-01-19 15:05 ` Andrew Lunn
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=54B8C49A.9070302@redhat.com \
--to=hdegoede@redhat.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=gregory.clement@free-electrons.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;
as well as URLs for NNTP newsgroup(s).