linux-kernel - Re: [PATCH v6 0/7] ARM: berlin: add AHCI support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <539ECAFE.3000508@gmail.com>
Date:	Mon, 16 Jun 2014 12:46:22 +0200
From:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To:	Antoine Ténart 
	<antoine.tenart@...e-electrons.com>, tj@...nel.org, kishon@...com
CC:	alexandre.belloni@...e-electrons.com,
	thomas.petazzoni@...e-electrons.com, zmxu@...vell.com,
	jszhang@...vell.com, linux-arm-kernel@...ts.infradead.org,
	linux-ide@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 0/7] ARM: berlin: add AHCI support

On 06/16/2014 12:26 PM, Antoine Ténart wrote:
> This series adds the support for Berlin SoC AHCI controller. The
> controller allows to use the SATA host interface and, for example, the
> eSATA port on the BG2Q.
>
> The series adds a PHY driver to control the two SATA ports available,
> and adds a generic compatible to use the existing ahci_platform driver.

Besides the comment about adding SATA clock to SATA PHY node and driver,

Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>

for patches 1-5.

> Also enable the eSATA interface on the BG2Q DMP.
>
> Changes sinve v5:
> 	- rebased on top of v3.16-rc1
> 	- added the clocks property in the sata node
>
> Changes since v4:
>          - updated PHY driver as tristate
>          - handled the case were no SATA port is enabled
>          - updated the compatible to a generic one
>          - cosmetic fixups
>
> Changes since v3:
>          - moved all PHY operations to the PHY driver
>          - removed PHY sub-nodes
>          - removed the custom Berlin AHCI driver and switched to
>            ahci_platform
>          - added multiple PHYs support to the libahci_platform
>
> Changes since v2:
>          - modeled each PHY as a sub-node
>          - cosmetic fixups
>
> Changes since v1:
>          - added a PHY driver, allowing to enable each port
>            individually and removed the 'force-port-map' property
>          - made the drivers a bit less magic :)
>          - wrote a function to select and configure registers in the
>            AHCI driver
>          - removed BG2 / BG2CD nodes
>
> Antoine Ténart (7):
>    phy: add a driver for the Berlin SATA PHY
>    Documentation: bindings: add the Berlin SATA PHY
>    ata: libahci: allow to use multiple PHYs
>    ata: ahci_platform: add a generic AHCI compatible
>    Documentation: bindings: document the sub-nodes AHCI bindings
>    ARM: berlin: add the AHCI node for the BG2Q
>    ARM: berlin: enable the eSATA interface on the BG2Q DMP
>
>   .../devicetree/bindings/ata/ahci-platform.txt      |  37 ++++
>   .../devicetree/bindings/phy/berlin-sata-phy.txt    |  14 ++
>   arch/arm/boot/dts/berlin2q-marvell-dmp.dts         |   8 +
>   arch/arm/boot/dts/berlin2q.dtsi                    |  28 +++
>   drivers/ata/ahci.h                                 |   3 +-
>   drivers/ata/ahci_platform.c                        |   2 +
>   drivers/ata/libahci.c                              |   7 +
>   drivers/ata/libahci_platform.c                     | 170 +++++++++++----
>   drivers/phy/Kconfig                                |   7 +
>   drivers/phy/Makefile                               |   1 +
>   drivers/phy/phy-berlin-sata.c                      | 232 +++++++++++++++++++++
>   11 files changed, 473 insertions(+), 36 deletions(-)
>   create mode 100644 Documentation/devicetree/bindings/phy/berlin-sata-phy.txt
>   create mode 100644 drivers/phy/phy-berlin-sata.c
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/