linux-kernel - [PATCH v2 0/2] ARM: berlin: add SDHCI 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-next>] [day] [month] [year] [list]

Date:	Tue, 22 Apr 2014 10:27:26 +0200
From:	Antoine Ténart 
	<antoine.tenart@...e-electrons.com>
To:	sebastian.hesselbarth@...il.com
Cc:	Antoine Ténart 
	<antoine.tenart@...e-electrons.com>,
	alexandre.belloni@...e-electrons.com, zmxu@...vell.com,
	jszhang@...vell.com, linux-arm-kernel@...ts.infradead.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/2] ARM: berlin: add SDHCI support

This series adds the Berlin BG2Q SDHCI nodes to support the 3 controllers
available. The Berlin BG2Q SDHCI controllers are compatible with the pxav3
driver. This patches also enable the SD Card reader and the eMMC of the
BG2Q DMP.

This series applies on top of Alexandre's patches for the Berlin's pll:
https://patchwork.kernel.org/patch/3890341/
https://patchwork.kernel.org/patch/3876271/

Changes since v1:
	The v2 introduced a custom Berlin SDHCI driver. It turns out the
	available pxav3 driver was compatible with the BG2Q SDHCI controllers.
	- removed the unneeded custom driver
	- switched to the pxav3 driver
	- removed the board specific properties from the SoC device tree

Antoine Ténart (2):
  ARM: dts: berlin: add the SDHCI nodes for the BG2Q
  ARM: dts: berlin: enable SD card reader and eMMC for the BG2Q DMP

 arch/arm/boot/dts/berlin2q-marvell-dmp.dts | 11 ++++++++++
 arch/arm/boot/dts/berlin2q.dtsi            | 32 ++++++++++++++++++++++++++++++
 2 files changed, 43 insertions(+)

-- 
1.8.3.2

--
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/