Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751508AbaKZTbV (ORCPT ); Wed, 26 Nov 2014 14:31:21 -0500 Received: from mail-vc0-f176.google.com ([209.85.220.176]:32931 "EHLO mail-vc0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750736AbaKZTbS (ORCPT ); Wed, 26 Nov 2014 14:31:18 -0500 MIME-Version: 1.0 In-Reply-To: References: <1416874644-12070-1-git-send-email-abrestic@chromium.org> Date: Wed, 26 Nov 2014 11:31:17 -0800 X-Google-Sender-Auth: j-QZ_EZEqln5tfeDgRaSGAF1N9Y Message-ID: Subject: Re: [PATCH V6 00/12] Tegra xHCI support From: Andrew Bresticker To: Jassi Brar Cc: Stephen Warren , Thierry Reding , Alexandre Courbot , "linux-tegra@vger.kernel.org" , Mark Rutland , Devicetree List , Linux USB list , Mathias Nyman , Pawel Moll , Ian Campbell , Greg Kroah-Hartman , Linus Walleij , Jassi Brar , lkml , Felipe Balbi , Kishon Vijay Abraham I , Olof Johansson , Rob Herring , Alan Stern , "linux-arm-kernel@lists.infradead.org" , Kumar Gala , Grant Likely , Arnd Bergmann Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 25, 2014 at 5:32 AM, Jassi Brar wrote: > On 25 November 2014 at 05:47, Andrew Bresticker wrote: >> This series adds support for xHCI on NVIDIA Tegra SoCs. This includes: >> - patches 1, 2, and 3: minor cleanups for mailbox framework and xHCI, >> - patches 4 and 5: adding a driver for the mailbox used to communicate >> with the xHCI controller's firmware, >> - patches 6 and 7: extending the XUSB pad controller driver to support >> the USB PHY types (UTMI, HSIC, and USB3), >> - patches 8 and 9: adding a xHCI host-controller driver, and >> - patches 10, 11, and 12: updating the relevant DT files. >> >> The mailbox driver (patch 5) has a compile-time dependency on patch 2 and >> a run-time dependency on patch 3. Both the PHY (patch 7) and host (patch 9) >> drivers have compile-time dependencies on the mailbox driver. The host >> driver also has a run-time dependency on patch 1. Because of this, this >> entire series should probably go through the Tegra tree. >> > Why shouldn't I pick 2 & 3 at least? I don't see why not. Because of the PHY API change I'm going to have to re-spin the series and at this point 3.19 is looking pretty unlikely. Maybe we could get a Tegra maintainer's ACK for patches 4 and 5 so that you could take them through your tree as well for 3.19? (Stephen, Thierry, Alex?) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/