public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 6/9] usb: chipidea: add vbus regulator control
Date: Fri, 8 Mar 2013 16:32:46 +0800	[thread overview]
Message-ID: <20130308083245.GB22550@nchen-desktop> (raw)
In-Reply-To: <20130308072624.GF21589@arwen.pp.htv.fi>

On Fri, Mar 08, 2013 at 09:26:24AM +0200, Felipe Balbi wrote:
> 
> > Differ with dwc3, chipidea created its platform data at glue layer,
> > and chipidea core owing this data when platform device is created.
> 
> yeah yeah, but that's just because chipidea core doesn't understand DT.
> 
> It should take you no more than a day to teach it about DT, though. Not
> sure what you're complaining about.

I have not complained about it, it is out of scope of this patchset.
This patchset is just adds ID/vbus support for chipidea.
For other enhancements, it needs another patchset. 

> 
> > If we also want get things from DT node, we need to get node from
> > glue layer as this node is NOT belonged to chipidea core's pdev.
> 
> which DT node are you talking about ? you want chipidea core to have
> access to glue's DT node ? Are you insane ?

Please read chipidea code, the chipidea core (pdev & platform data)
is not created by DT, it is created by glue layer.
If we added dts entry like you showed me, we can't get node by
pdev->dev.of_node.

> 
> If you wanna add DT support for chipidea core, you need to come up with
> a compatible that makes sense. It won't be fsl,* because chipidea core
> doesn't belong to fsl.

I know it. 

> 
> > Convert platform data to DT for chipidea core is a big job,
> 
> no it's not.

I need to change all msm and pci board related files.

> 
> yeah, but this patch makes no sense. The right thing (TM) to do is, as I
> have said multiple times before, to teach chipidea core about DT. Please
> stop trying to find excuses for not doing the work you need to do; You
> would've already done it if you had spent so much of everybody's time
> trying to find excuses why not to do it and why Alex should accept your
> broken patches.

First let chipidea core know about DT is out of this patchset.

Second, why you think it is a broken patch, it just follows current
framework. Besides, if you have concerns about DT stuff for chipidea
core, why not mention it when sasche added dr_mode and phy_mode at that time?

> 
> Have you already forgotten how many issues were found in each and every
> version of your patchset ? There's a reason why we're revieweing v11,
> right ?

I just want to limit this patchset to id/vbus enable feature, 
I admit I am less upstream experience, but if new requirements
new features and new bugs always coming, things can't be ended up
easily.


-- 

Best Regards,
Peter Chen

  reply	other threads:[~2013-03-08  8:32 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06  9:56 [PATCH v11 0/9] Add tested id switch and vbus connect detect support for Chipidea Peter Chen
2013-03-06  9:56 ` [PATCH v11 1/9] Revert "USB: chipidea: add vbus detect for udc" Peter Chen
2013-03-06  9:56 ` [PATCH v11 2/9] usb: chipidea: add otg file Peter Chen
2013-03-06  9:56 ` [PATCH v11 3/9] usb: chipidea: add otg id switch and vbus connect/disconnect detect Peter Chen
2013-03-06 17:09   ` Alexander Shishkin
2013-03-07  5:50     ` Peter Chen
2013-03-08 12:42       ` Peter Chen
2013-03-06  9:56 ` [PATCH v11 4/9] usb: chipidea: udc: add pullup/pulldown dp at hw_device_state Peter Chen
2013-03-06 11:26   ` Felipe Balbi
2013-03-07  2:36     ` Peter Chen
2013-03-07  9:50       ` Felipe Balbi
2013-03-08  1:28         ` Peter Chen
2013-03-08  7:18           ` Felipe Balbi
2013-03-08  8:05             ` Peter Chen
2013-03-06  9:56 ` [PATCH v11 5/9] usb: chipidea: udc: retire the flag CI13_PULLUP_ON_VBUS Peter Chen
2013-03-06  9:56 ` [PATCH v11 6/9] usb: chipidea: add vbus regulator control Peter Chen
2013-03-06 11:29   ` Felipe Balbi
2013-03-07  2:41     ` Peter Chen
2013-03-07  9:52       ` Felipe Balbi
2013-03-08  6:27         ` Peter Chen
2013-03-08  7:26           ` Felipe Balbi
2013-03-08  8:32             ` Peter Chen [this message]
2013-03-08  8:42               ` Felipe Balbi
2013-03-08  8:52                 ` Peter Chen
2013-03-08  8:58                   ` Felipe Balbi
2013-03-06  9:56 ` [PATCH v11 7/9] usb: chipidea: delete the delayed work Peter Chen
2013-03-06  9:56 ` [PATCH v11 8/9] usb: chipidea: imx: add getting vbus regulator code Peter Chen
2013-03-06 10:11   ` Felipe Balbi
2013-03-07  2:18     ` Peter Chen
2013-03-06  9:56 ` [PATCH v11 9/9] usb: chipidea: udc: fix the oops when plugs in usb cable after rmmod gadget Peter Chen
2013-03-06 18:46   ` Russell King - ARM Linux
2013-03-07  2:48     ` 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=20130308083245.GB22550@nchen-desktop \
    --to=peter.chen@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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