linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@freescale.com>
To: Antoine Tenart <antoine.tenart@free-electrons.com>
Cc: <alexandre.belloni@free-electrons.com>,
	<thomas.petazzoni@free-electrons.com>, <zmxu@marvell.com>,
	<jszhang@marvell.com>, <linux-usb@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6] usb: chipidea: add a core function to setup ci_hdrc_platform_data
Date: Mon, 17 Nov 2014 13:30:47 +0800	[thread overview]
Message-ID: <20141117053044.GA30017@shlinux2> (raw)
In-Reply-To: <20141114153455.GC2991@kwain>

On Fri, Nov 14, 2014 at 04:34:55PM +0100, Antoine Tenart wrote:
> Peter,
> 
> On Fri, Nov 14, 2014 at 09:16:55AM +0800, Peter Chen wrote:
> > 
> > Ok, Antoine, I find this patch set may not have many benefits due to
> > below reasons:
> > - There is already function ci_get_platdata to do the similar things
> > - If the PHY can't get from the DT, it will use devm_phy_get or
> > devm_usb_get_phy to get, this code has already in core.
> > 
> > I am apologized that I wanted you to do a patch for moving get PHY
> > operation to core, it doesn't have many benefits currently
> > - For non-dt user, the phy get function has already in core like I said
> > above.
> > - For dt generic phy user, it uses of_phy_get, the second parameter
> > con_id may be different for platforms.
> > - For dt usb phy, it uses devm_usb_get_phy_by_phandle, the second
> > parameters phandle may be different for platforms.
> 
> Ok.
> 
> > So, please rebase my next tree which your generic phy patch set has
> > already in, and send your generic usb2 chipidea patch base on it.
> 
> I just rebased my usb2 ci generic driver series and sent it to you and
> to the mailing lists. Since there is not reason from now to delay it, I
> expect it to be merged soon. I wouldn't want to miss yet another release.
> 
> Thanks,
> 

I hope soon, just your generic phy patch set changed lots of things, and
spent too much time on reviewing.

-- 

Best Regards,
Peter Chen

  reply	other threads:[~2014-11-17  6:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 11:36 [PATCH 1/6] usb: chipidea: setup ci_hdrc_platform_data in core driver Antoine Tenart
2014-10-30 11:36 ` [PATCH 1/6] usb: chipidea: add a core function to setup ci_hdrc_platform_data Antoine Tenart
2014-11-14  1:16   ` Peter Chen
2014-11-14 15:34     ` Antoine Tenart
2014-11-17  5:30       ` Peter Chen [this message]
2014-10-30 11:36 ` [PATCH 2/6] usb: chipidea: use ci_hdrc_get_platdata in ci_hdrc_imx Antoine Tenart
2014-10-30 11:36 ` [PATCH 3/6] usb: chipidea: use ci_hdrc_get_platdata in ci_hdrc_msm Antoine Tenart
2014-10-30 11:36 ` [PATCH 4/6] usb: chipidea: use ci_hdrc_get_platdata in ci_hdrc_pci Antoine Tenart
2014-10-30 11:36 ` [PATCH 5/6] usb: chipidea: use ci_hdrc_get_platdata in ci_hdrc_zevio Antoine Tenart
2014-10-30 11:36 ` [PATCH 6/6] usb: chipidea: remove obsolete ci_get_platdata function Antoine Tenart
2014-10-30 11:43 ` [PATCH 1/6] usb: chipidea: setup ci_hdrc_platform_data in core driver Antoine Tenart
2014-11-06  8:37   ` Antoine Tenart
2014-11-06 10:02     ` Peter Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141117053044.GA30017@shlinux2 \
    --to=peter.chen@freescale.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=antoine.tenart@free-electrons.com \
    --cc=jszhang@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=zmxu@marvell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).