linux-kernel - Re: [PATCH v2 4/4] usb: Add APIs to access host registers from Tegra PHY

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: <50F878C3.9030002@wwwdotorg.org>
Date:	Thu, 17 Jan 2013 15:18:43 -0700
From:	Stephen Warren <swarren@...dotorg.org>
To:	balbi@...com
CC:	Venu Byravarasu <vbyravarasu@...dia.com>,
	gregkh@...uxfoundation.org, stern@...land.harvard.edu,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-tegra@...r.kernel.org
Subject: Re: [PATCH v2 4/4] usb: Add APIs to access host registers from Tegra
 PHY

On 01/17/2013 02:02 AM, Felipe Balbi wrote:
> Hi,
> 
> On Thu, Jan 17, 2013 at 01:58:12PM +0530, Venu Byravarasu wrote:
>> As Tegra PHY driver need to access one of the Host registers, 
>> added few APIs to ehci tegra driver.
>> 
>> Signed-off-by: Venu Byravarasu <vbyravarasu@...dia.com>
> 
> Stephen is this another of those patches you're gonna take care of 
> yourself ?

Yes; in kernel 3.9, I believe I need to take any significant Tegra
EHCI or PHY patches through the Tegra tree due to the need to change
the Tegra device trees in lock-step with some of the code changes, and
other Tegra-related changes also changing the USB-related nodes in
device tree e.g. to add clocks properties.

Hopefully we get enough USB patches into 3.9 that the dependencies are
then removed, and we can revert back to the usual merging path in 3.10...
--
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/