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 second version of the series.
The previous version depended of a patch set for the regulator
framework which was not accepted. Then I needed to do this in a
different way that it was done for the PHY. As result the regulator
need to be associated to each port as the host node level using the
property target-port<n>-supply, where <n> is the port number. But it
is however mandatory to have one port sub-node for each port
associated to a regulator.
Since the 1st version I also took into account the comments from Hans
and added a patch to use the new binding for the device tree of the
Armada 38x GP. This last patch should be merged through the mvebu
tree.
Thanks,
Gr??gory
Changelog:
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 | 224 ++++++++++++++-------
include/linux/ahci_platform.h | 2 +
6 files changed, 294 insertions(+), 83 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
