RE: [PATCH 1/2] usb: chipidea: fix mistake in device tree binding of nspire-usb to use vendor name 'lsi' instead of SoC name 'zevio'

2013-12-05 Thread Peter Chen
> > Hi, > > On 05/12/2013, at 7:49 PM, Peter Chen wrote: > > > On Thu, Dec 05, 2013 at 04:44:13PM +1100, Daniel Tang wrote: > >> Hi, > >> > >> On 05/12/2013, at 12:44 AM, Peter Chen > wrote: > >> > >>> > >>> lsi is vendor name, what are zevio and nspire? > >>> Usually, the compatible string

Re: [PATCH 1/2] usb: chipidea: fix mistake in device tree binding of nspire-usb to use vendor name 'lsi' instead of SoC name 'zevio'

2013-12-05 Thread Daniel Tang
Hi, On 05/12/2013, at 7:49 PM, Peter Chen wrote: > On Thu, Dec 05, 2013 at 04:44:13PM +1100, Daniel Tang wrote: >> Hi, >> >> On 05/12/2013, at 12:44 AM, Peter Chen wrote: >> >>> >>> lsi is vendor name, what are zevio and nspire? >>> Usually, the compatible string should be "vendor_name,soc_n

Re: [PATCH 1/2] usb: chipidea: fix mistake in device tree binding of nspire-usb to use vendor name 'lsi' instead of SoC name 'zevio'

2013-12-05 Thread Peter Chen
On Thu, Dec 05, 2013 at 04:44:13PM +1100, Daniel Tang wrote: > Hi, > > On 05/12/2013, at 12:44 AM, Peter Chen wrote: > > > > > lsi is vendor name, what are zevio and nspire? > > Usually, the compatible string should be "vendor_name,soc_name-module_name" > > > > Because this port uses document

Re: [PATCH 1/2] usb: chipidea: fix mistake in device tree binding of nspire-usb to use vendor name 'lsi' instead of SoC name 'zevio'

2013-12-04 Thread Daniel Tang
Hi, On 04/12/2013, at 11:18 PM, Mark Rutland wrote: >> >> >> Required properties: >> -- compatible: Should be "zevio,nspire-usb" >> +- compatible: Should be "lsi,nspire-usb" > > Surely this should be lsi,zevio-usb, matching the lsi,zevio-timer > binding? You're right. I'll fix up the patch a

Re: [PATCH 1/2] usb: chipidea: fix mistake in device tree binding of nspire-usb to use vendor name 'lsi' instead of SoC name 'zevio'

2013-12-04 Thread Daniel Tang
Hi, On 05/12/2013, at 12:44 AM, Peter Chen wrote: > > lsi is vendor name, what are zevio and nspire? > Usually, the compatible string should be "vendor_name,soc_name-module_name" > Because this port uses documentation from reverse engineering, it's difficult to work out what is SoC specific

Re: [PATCH 1/2] usb: chipidea: fix mistake in device tree binding of nspire-usb to use vendor name 'lsi' instead of SoC name 'zevio'

2013-12-04 Thread Peter Chen
On Wed, Dec 04, 2013 at 08:20:07PM +1100, dt.ta...@gmail.com wrote: > From: Daniel Tang > > The SoC name was mistakenly used instead of the vendor name in the > device tree binding for nspire-usb. > > This patch fixes this before the driver becomes widely adopted. > > Signed-off-by: Daniel Tang

Re: [PATCH 1/2] usb: chipidea: fix mistake in device tree binding of nspire-usb to use vendor name 'lsi' instead of SoC name 'zevio'

2013-12-04 Thread Mark Rutland
On Wed, Dec 04, 2013 at 09:20:07AM +, dt.ta...@gmail.com wrote: > From: Daniel Tang > > The SoC name was mistakenly used instead of the vendor name in the > device tree binding for nspire-usb. > > This patch fixes this before the driver becomes widely adopted. How widely adopted is it so fa

[PATCH 1/2] usb: chipidea: fix mistake in device tree binding of nspire-usb to use vendor name 'lsi' instead of SoC name 'zevio'

2013-12-04 Thread dt . tangr
From: Daniel Tang The SoC name was mistakenly used instead of the vendor name in the device tree binding for nspire-usb. This patch fixes this before the driver becomes widely adopted. Signed-off-by: Daniel Tang --- Documentation/devicetree/bindings/usb/ci-hdrc-nspire.txt |4 ++-- drivers