mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Tang <dt.tangr@gmail.com>
To: Peter Chen <Peter.Chen@freescale.com>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-doc@vger.kernel.org>
Subject: 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'
Date: Thu, 5 Dec 2013 21:10:37 +1100	[thread overview]
Message-ID: <FAB4D64E-5DAD-4252-8B24-F076071D0279@gmail.com> (raw)
In-Reply-To: <20131205084909.GA25943@shlinux1.ap.freescale.net>

Hi,

On 05/12/2013, at 7:49 PM, Peter Chen <Peter.Chen@freescale.com> 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 <Peter.Chen@freescale.com> 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 and what is device specific. The SoC is Zevio but the driver is written for the TI-Nspire.
>> 
> 
> Please wrap the line to 80 characters.
> 
> The driver is written for the TI-Nspire, and you port this driver for
> SoC Zevio platform?

The TI-Nspire runs on the Zevio SoC.

> Since you use chipidea ip, we don't care the usb
> module name at your platform, we only care the soc name which you are
> running, it can detect the SoC platform at runtime.
> 

Yep, that's why the latest patch I sent in renames the device tree 
binding to "lsi,zevio-usb" since zevio is the name of the SoC that the 
TI-Nspire uses.

> At your dts patch, it still uses nspire-usb.
> http://marc.info/?l=linux-usb&m=138614886720024&w=2

I'll send a new one in right now.

> 
> Peter

Cheers,
Daniel Tang

  reply	other threads:[~2013-12-05 10:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04  9:20 dt.tangr
2013-12-04  9:20 ` [PATCH 2/2] arm: nspire: modify device tree to use the nspire-usb driver dt.tangr
2013-12-04 12:18 ` [PATCH 1/2] usb: chipidea: fix mistake in device tree binding of nspire-usb to use vendor name 'lsi' instead of SoC name 'zevio' Mark Rutland
2013-12-05  5:45   ` Daniel Tang
2013-12-04 13:44 ` Peter Chen
2013-12-05  5:44   ` Daniel Tang
2013-12-05  8:49     ` Peter Chen
2013-12-05 10:10       ` Daniel Tang [this message]
2013-12-06  2:27         ` 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=FAB4D64E-5DAD-4252-8B24-F076071D0279@gmail.com \
    --to=dt.tangr@gmail.com \
    --cc=Peter.Chen@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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

all inboxes | Powered by JetHome®