From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BCE8BC64EAD for ; Tue, 9 Oct 2018 14:57:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 80F3D214D5 for ; Tue, 9 Oct 2018 14:57:40 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="FJiIPLxI" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 80F3D214D5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726976AbeJIWO5 (ORCPT ); Tue, 9 Oct 2018 18:14:57 -0400 Received: from mail.kernel.org ([198.145.29.99]:39968 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726393AbeJIWO4 (ORCPT ); Tue, 9 Oct 2018 18:14:56 -0400 Received: from localhost (ip-213-127-77-176.ip.prioritytelecom.net [213.127.77.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C3BF2214C4; Tue, 9 Oct 2018 14:57:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1539097057; bh=ngNe1sU2/kRtPQJLBNvMSGTVGyryhaDZkreW6d57F64=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=FJiIPLxI7EHg+zCzOcs+5rWGkI8se3GyAPbQYcW54R6K4AVyBWClXUoVIQ8UEmuoU vk6js+eJ5OQ7zAdeBfpg0AfnNWHSVU6TdXUGiR6wMC3Bi+LRWSWfwTv+K746RsDUPZ GV4ISI5aIZCYw+gYSLHYnilB8kAG/fpLq3yerxVg= Date: Tue, 9 Oct 2018 16:57:34 +0200 From: Greg Kroah-Hartman To: Lubomir Rintel Cc: Kishon Vijay Abraham I , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Rob Herring , Mark Rutland , Eric Miao , Haojian Zhuang , Alan Stern Subject: Re: [PATCH 01/14] phy: phy-pxa-usb: add a new driver Message-ID: <20181009145734.GA22668@kroah.com> References: <20180822204307.13251-1-lkundrak@v3.sk> <20180822204307.13251-2-lkundrak@v3.sk> <1981ce54ce960d21976ce71b08a8779bfeb13be4.camel@v3.sk> <20181008132148.GC20703@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 09, 2018 at 04:51:03PM +0200, Lubomir Rintel wrote: > On Mon, 2018-10-08 at 15:21 +0200, Greg Kroah-Hartman wrote: > > On Sun, Oct 07, 2018 at 08:47:28PM +0200, Lubomir Rintel wrote: > > > On Tue, 2018-09-25 at 10:53 +0530, Kishon Vijay Abraham I wrote: > > > > On Thursday 23 August 2018 02:12 AM, Lubomir Rintel wrote: > > > > > Turned from arch/arm/mach-mmp/devices.c into a proper PHY driver, > > > > > so > > > > > that in can be instantiated from a DT. > > > > > > > > > > Signed-off-by: Lubomir Rintel > > > > > > > > Acked-by: Kishon Vijay Abraham I > > > > > > > > If this has to be merged via linux-phy tree, please let me know. > > > > > > Yes, either linux-phy or the usb tree. > > > > > > The EHCI patches have already been pulled into the usb tree, presumably > > > because they got an Ack from Alan Stern. That includes "USB: EHCI: > > > ehci-mv: use phy-pxa-usb" that depends on this. Perhaps the rest of > > > the patches can go via the same tree? > > > > > > I haven't submitted a patchset that would have dependencies spanning > > > across different subsystems before. I don't know what's usually done in > > > such cases. Advice welcome. > > > > > > Greg? > > > > You can either send them through the same tree, or wait a release cycle > > and get the rest in through a different one. As I usually take the phy > > tree into the USB tree for issues like this, I can take them all if you > > get the phy maintainer to ack them. > > I believe that would be Kishton, who acked this one (see above). Please > add it ("PATCH 01/14] phy: phy-pxa-usb: add a new driver") to the usb > tree than. > > The rest is DT bindings and MMP2 platform changes (DT, board files and > removal of dead code) which are not strictly dependent on this and > don't need to go through phy or usb trees. I still need to get someone > to review them. When you get that done, please resend. thanks, greg k-h From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Subject: [01/14] phy: phy-pxa-usb: add a new driver From: Greg Kroah-Hartman Message-Id: <20181009145734.GA22668@kroah.com> Date: Tue, 9 Oct 2018 16:57:34 +0200 To: Lubomir Rintel Cc: Kishon Vijay Abraham I , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Rob Herring , Mark Rutland , Eric Miao , Haojian Zhuang , Alan Stern List-ID: T24gVHVlLCBPY3QgMDksIDIwMTggYXQgMDQ6NTE6MDNQTSArMDIwMCwgTHVib21pciBSaW50ZWwg d3JvdGU6Cj4gT24gTW9uLCAyMDE4LTEwLTA4IGF0IDE1OjIxICswMjAwLCBHcmVnIEtyb2FoLUhh cnRtYW4gd3JvdGU6Cj4gPiBPbiBTdW4sIE9jdCAwNywgMjAxOCBhdCAwODo0NzoyOFBNICswMjAw LCBMdWJvbWlyIFJpbnRlbCB3cm90ZToKPiA+ID4gT24gVHVlLCAyMDE4LTA5LTI1IGF0IDEwOjUz ICswNTMwLCBLaXNob24gVmlqYXkgQWJyYWhhbSBJIHdyb3RlOgo+ID4gPiA+IE9uIFRodXJzZGF5 IDIzIEF1Z3VzdCAyMDE4IDAyOjEyIEFNLCBMdWJvbWlyIFJpbnRlbCB3cm90ZToKPiA+ID4gPiA+ IFR1cm5lZCBmcm9tIGFyY2gvYXJtL21hY2gtbW1wL2RldmljZXMuYyBpbnRvIGEgcHJvcGVyIFBI WSBkcml2ZXIsCj4gPiA+ID4gPiBzbwo+ID4gPiA+ID4gdGhhdCBpbiBjYW4gYmUgaW5zdGFudGlh dGVkIGZyb20gYSBEVC4KPiA+ID4gPiA+IAo+ID4gPiA+ID4gU2lnbmVkLW9mZi1ieTogTHVib21p ciBSaW50ZWwgPGxrdW5kcmFrQHYzLnNrPgo+ID4gPiA+IAo+ID4gPiA+IEFja2VkLWJ5OiBLaXNo b24gVmlqYXkgQWJyYWhhbSBJIDxraXNob25AdGkuY29tPgo+ID4gPiA+IAo+ID4gPiA+IElmIHRo aXMgaGFzIHRvIGJlIG1lcmdlZCB2aWEgbGludXgtcGh5IHRyZWUsIHBsZWFzZSBsZXQgbWUga25v dy4KPiA+ID4gCj4gPiA+IFllcywgZWl0aGVyIGxpbnV4LXBoeSBvciB0aGUgdXNiIHRyZWUuCj4g PiA+IAo+ID4gPiBUaGUgRUhDSSBwYXRjaGVzIGhhdmUgYWxyZWFkeSBiZWVuIHB1bGxlZCBpbnRv IHRoZSB1c2IgdHJlZSwgcHJlc3VtYWJseQo+ID4gPiBiZWNhdXNlIHRoZXkgZ290IGFuIEFjayBm cm9tIEFsYW4gU3Rlcm4uIFRoYXQgaW5jbHVkZXMgIlVTQjogRUhDSToKPiA+ID4gZWhjaS1tdjog dXNlIHBoeS1weGEtdXNiIiB0aGF0IGRlcGVuZHMgb24gdGhpcy4gUGVyaGFwcyB0aGUgIHJlc3Qg b2YKPiA+ID4gdGhlIHBhdGNoZXMgY2FuIGdvIHZpYSB0aGUgc2FtZSB0cmVlPwo+ID4gPiAKPiA+ ID4gSSBoYXZlbid0IHN1Ym1pdHRlZCBhIHBhdGNoc2V0IHRoYXQgd291bGQgaGF2ZSBkZXBlbmRl bmNpZXMgc3Bhbm5pbmcKPiA+ID4gYWNyb3NzIGRpZmZlcmVudCBzdWJzeXN0ZW1zIGJlZm9yZS4g SSBkb24ndCBrbm93IHdoYXQncyB1c3VhbGx5IGRvbmUgaW4KPiA+ID4gc3VjaCBjYXNlcy4gQWR2 aWNlIHdlbGNvbWUuCj4gPiA+IAo+ID4gPiBHcmVnPwo+ID4gCj4gPiBZb3UgY2FuIGVpdGhlciBz ZW5kIHRoZW0gdGhyb3VnaCB0aGUgc2FtZSB0cmVlLCBvciB3YWl0IGEgcmVsZWFzZSBjeWNsZQo+ ID4gYW5kIGdldCB0aGUgcmVzdCBpbiB0aHJvdWdoIGEgZGlmZmVyZW50IG9uZS4gIEFzIEkgdXN1 YWxseSB0YWtlIHRoZSBwaHkKPiA+IHRyZWUgaW50byB0aGUgVVNCIHRyZWUgZm9yIGlzc3VlcyBs aWtlIHRoaXMsIEkgY2FuIHRha2UgdGhlbSBhbGwgaWYgeW91Cj4gPiBnZXQgdGhlIHBoeSBtYWlu dGFpbmVyIHRvIGFjayB0aGVtLgo+IAo+IEkgYmVsaWV2ZSB0aGF0IHdvdWxkIGJlIEtpc2h0b24s IHdobyBhY2tlZCB0aGlzIG9uZSAoc2VlIGFib3ZlKS4gUGxlYXNlCj4gYWRkIGl0ICgiUEFUQ0gg MDEvMTRdIHBoeTogcGh5LXB4YS11c2I6IGFkZCBhIG5ldyBkcml2ZXIiKSB0byB0aGUgdXNiCj4g dHJlZSB0aGFuLgo+IAo+IFRoZSByZXN0IGlzIERUIGJpbmRpbmdzIGFuZCBNTVAyIHBsYXRmb3Jt IGNoYW5nZXMgKERULCBib2FyZCBmaWxlcyBhbmQKPiByZW1vdmFsIG9mIGRlYWQgY29kZSkgd2hp Y2ggYXJlIG5vdCBzdHJpY3RseSBkZXBlbmRlbnQgb24gdGhpcyBhbmQKPiBkb24ndCBuZWVkIHRv IGdvIHRocm91Z2ggcGh5IG9yIHVzYiB0cmVlcy4gSSBzdGlsbCBuZWVkIHRvIGdldCBzb21lb25l Cj4gdG8gcmV2aWV3IHRoZW0uCgpXaGVuIHlvdSBnZXQgdGhhdCBkb25lLCBwbGVhc2UgcmVzZW5k LgoKdGhhbmtzLAoKZ3JlZyBrLWgK From mboxrd@z Thu Jan 1 00:00:00 1970 From: gregkh@linuxfoundation.org (Greg Kroah-Hartman) Date: Tue, 9 Oct 2018 16:57:34 +0200 Subject: [PATCH 01/14] phy: phy-pxa-usb: add a new driver In-Reply-To: References: <20180822204307.13251-1-lkundrak@v3.sk> <20180822204307.13251-2-lkundrak@v3.sk> <1981ce54ce960d21976ce71b08a8779bfeb13be4.camel@v3.sk> <20181008132148.GC20703@kroah.com> Message-ID: <20181009145734.GA22668@kroah.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Oct 09, 2018 at 04:51:03PM +0200, Lubomir Rintel wrote: > On Mon, 2018-10-08 at 15:21 +0200, Greg Kroah-Hartman wrote: > > On Sun, Oct 07, 2018 at 08:47:28PM +0200, Lubomir Rintel wrote: > > > On Tue, 2018-09-25 at 10:53 +0530, Kishon Vijay Abraham I wrote: > > > > On Thursday 23 August 2018 02:12 AM, Lubomir Rintel wrote: > > > > > Turned from arch/arm/mach-mmp/devices.c into a proper PHY driver, > > > > > so > > > > > that in can be instantiated from a DT. > > > > > > > > > > Signed-off-by: Lubomir Rintel > > > > > > > > Acked-by: Kishon Vijay Abraham I > > > > > > > > If this has to be merged via linux-phy tree, please let me know. > > > > > > Yes, either linux-phy or the usb tree. > > > > > > The EHCI patches have already been pulled into the usb tree, presumably > > > because they got an Ack from Alan Stern. That includes "USB: EHCI: > > > ehci-mv: use phy-pxa-usb" that depends on this. Perhaps the rest of > > > the patches can go via the same tree? > > > > > > I haven't submitted a patchset that would have dependencies spanning > > > across different subsystems before. I don't know what's usually done in > > > such cases. Advice welcome. > > > > > > Greg? > > > > You can either send them through the same tree, or wait a release cycle > > and get the rest in through a different one. As I usually take the phy > > tree into the USB tree for issues like this, I can take them all if you > > get the phy maintainer to ack them. > > I believe that would be Kishton, who acked this one (see above). Please > add it ("PATCH 01/14] phy: phy-pxa-usb: add a new driver") to the usb > tree than. > > The rest is DT bindings and MMP2 platform changes (DT, board files and > removal of dead code) which are not strictly dependent on this and > don't need to go through phy or usb trees. I still need to get someone > to review them. When you get that done, please resend. thanks, greg k-h