linux-kernel - Re: [PATCH v3 0/15] Changes to support 150 MHz eMMC on rk3399

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: <1805593.i4NJUkPJQz@diego>
Date:	Mon, 20 Jun 2016 20:17:02 +0200
From:	Heiko Stübner <heiko@...ech.de>
To:	Douglas Anderson <dianders@...omium.org>
Cc:	ulf.hansson@...aro.org, kishon@...com, robh+dt@...nel.org,
	shawn.lin@...k-chips.com, xzy.xu@...k-chips.com,
	briannorris@...omium.org, adrian.hunter@...el.com,
	linux-rockchip@...ts.infradead.org, linux-mmc@...r.kernel.org,
	devicetree@...r.kernel.org, groeck@...omium.org,
	mark.rutland@....com, catalin.marinas@....com,
	linus.walleij@...aro.org, will.deacon@....com,
	linux-kernel@...r.kernel.org, wsa+renesas@...g-engineering.com,
	stefan.wahren@...e.com, zhengxing@...k-chips.com,
	michal.simek@...inx.com, geert@...ux-m68k.org,
	linux-arm-kernel@...ts.infradead.org, jay.xu@...k-chips.com,
	wxt@...k-chips.com, pawel.moll@....com,
	ijc+devicetree@...lion.org.uk, horms+renesas@...ge.net.au,
	soren.brinkmann@...inx.com, andrei.pistirica@...rochip.com,
	ludovic.desroches@...el.com, galak@...eaurora.org,
	yangbo.lu@...escale.com
Subject: Re: [PATCH v3 0/15] Changes to support 150 MHz eMMC on rk3399

Am Montag, 20. Juni 2016, 10:56:39 schrieb Douglas Anderson:
> The theme of this series of patches is to try to allow running the eMMC
> at 150 MHz on the rk3399 SoC, though the changes should still be correct
> and have merit on their own.  The motivation for running at 150 MHz is
> that doing so improves signal integrity and (with some eMMC devices)
> doesn't affect throughput.
> 
> These patches have been structured to keep things as separate as
> possible, but nevertheless there are still some dependencies between
> patches.  It probably makes the most sense for all of the non-device
> tree patches to go through a single tree.  PHY patches now have Acks
> from Kishon so that means things should be clear for all non-DTS patches
> to go through the MMC tree if Ulf agrees.  Device tree patches should be
> able to be landed separately and the worst what would happen is a
> warning in the kernel log if you have the code without the device tree.
> 
> The code patches are based on Ulf's mmc-next.  In v3 of the series I've
> pulled in the latest version of a previous PHY series posted by Brian
> Norris.
> 
> The device tree patches are based on Heiko's v4.8-armsoc/dts64.

just so it doesn't get lost from v2->v3, I plan on picking up the dts patches 
9 and 15 after the rest landed in the mmc tree - as they will only apply on 
top of my general dts branch.


Heiko