All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Chou <thomas-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.org,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	Dmitry Torokhov
	<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] altera_ps2: Add devicetree support
Date: Thu, 03 Feb 2011 07:32:43 +0800	[thread overview]
Message-ID: <4D49E99B.8080400@wytron.com.tw> (raw)
In-Reply-To: <20110202153803.GC20275-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>

On 02/02/2011 11:38 PM, Grant Likely wrote:
> On Wed, Feb 02, 2011 at 07:48:58PM +0800, Thomas Chou wrote:
>> On 02/02/2011 12:31 PM, Grant Likely wrote:
>>>> +static const struct of_device_id altera_ps2_match[] = {
>>>> +	{ .compatible = "altr,ps2-1.0", },
>>>
>>> I thought I had seen 'altera' instead of an abbreviation being used in
>>> a previous patch.  I don't care much whether 'altr' or 'altera' is
>>> used, but I'd like to know that there is consensus from the Altera
>>> users so that all the drivers use the same prefix.
>>>
>>
>> We had discussed on nios2-dev mailing list, and decided to use
>> 'altr' as Walter suggested that it saves space.
>>
>> About the documentation on dts binding, shall we have a single
>> altera.txt to describe all Altera related binding, and opencores.txt
>> to describe all OpenCores binding? Or separate file for each core in
>> its driver class?
>
> Since I'm reorganizing the binding documentation to reflect subsystems
> (bindings/spi, bindings/i2c, bindings/powerpc, etc) I'd prefer to see
> a separate file for each type of core.

OK. We will use separate files. I will send an updated patch to include 
the dts binding.

As for nios2 cpu related binding, we shall use binding/nios2 dir. Right?

- Thomas

>
> Eventually, I'd like to define a record format for documenting
> bindings that can generate searchable and crosslinked output, but I've
> not spent any time looking at that seriously yet.
>
> g.
>
>>
>> - Thomas
>

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Chou <thomas@wytron.com.tw>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-kernel@vger.kernel.org, nios2-dev@sopc.et.ntust.edu.tw,
	linux-input@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	Walter Goossens <waltergoossens@home.nl>
Subject: Re: [PATCH v2] altera_ps2: Add devicetree support
Date: Thu, 03 Feb 2011 07:32:43 +0800	[thread overview]
Message-ID: <4D49E99B.8080400@wytron.com.tw> (raw)
In-Reply-To: <20110202153803.GC20275@angua.secretlab.ca>

On 02/02/2011 11:38 PM, Grant Likely wrote:
> On Wed, Feb 02, 2011 at 07:48:58PM +0800, Thomas Chou wrote:
>> On 02/02/2011 12:31 PM, Grant Likely wrote:
>>>> +static const struct of_device_id altera_ps2_match[] = {
>>>> +	{ .compatible = "altr,ps2-1.0", },
>>>
>>> I thought I had seen 'altera' instead of an abbreviation being used in
>>> a previous patch.  I don't care much whether 'altr' or 'altera' is
>>> used, but I'd like to know that there is consensus from the Altera
>>> users so that all the drivers use the same prefix.
>>>
>>
>> We had discussed on nios2-dev mailing list, and decided to use
>> 'altr' as Walter suggested that it saves space.
>>
>> About the documentation on dts binding, shall we have a single
>> altera.txt to describe all Altera related binding, and opencores.txt
>> to describe all OpenCores binding? Or separate file for each core in
>> its driver class?
>
> Since I'm reorganizing the binding documentation to reflect subsystems
> (bindings/spi, bindings/i2c, bindings/powerpc, etc) I'd prefer to see
> a separate file for each type of core.

OK. We will use separate files. I will send an updated patch to include 
the dts binding.

As for nios2 cpu related binding, we shall use binding/nios2 dir. Right?

- Thomas

>
> Eventually, I'd like to define a record format for documenting
> bindings that can generate searchable and crosslinked output, but I've
> not spent any time looking at that seriously yet.
>
> g.
>
>>
>> - Thomas
>


  parent reply	other threads:[~2011-02-02 23:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D040D1C.2020705@home.nl>
     [not found] ` <4D040D1C.2020705-CmkmPbn3yAE@public.gmane.org>
2011-01-17  6:29   ` [PATCH] alter_ps2: Add devicetree support Thomas Chou
2011-01-17  6:29     ` Thomas Chou
2011-01-17  6:59     ` Grant Likely
     [not found]       ` <AANLkTi=8+Q5dm+5Pa-cYkmaBWQ4S7jgjZOL0ovtmrdxB-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-01-17 21:04         ` Walter Goossens
2011-01-17 21:04           ` Walter Goossens
2011-01-17 22:02           ` Grant Likely
2011-01-17 23:27             ` Walter Goossens
2011-01-18 14:26               ` Thomas Chou
2011-01-17 21:31     ` Dmitry Torokhov
     [not found]       ` <20110117213100.GC27245-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2011-01-17 22:04         ` Grant Likely
2011-01-17 22:04           ` Grant Likely
2011-01-24  5:58           ` [PATCH v2] altera_ps2: " Thomas Chou
2011-02-02  4:31             ` Grant Likely
2011-02-02  4:36               ` Grant Likely
     [not found]                 ` <AANLkTikxSrwOfU=m_h+6G5hQMk6drOpqOPSfbBdzg53g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-03  3:05                   ` [PATCH v3] " Thomas Chou
2011-02-03  3:05                     ` Thomas Chou
2011-02-12  9:26                     ` Grant Likely
2011-02-12 13:23                       ` Thomas Chou
2011-02-14  2:06                       ` [PATCH v4] " Thomas Chou
2011-02-14  2:20                         ` Dmitry Torokhov
2011-02-16  4:40                         ` Grant Likely
     [not found]               ` <20110202043121.GF29148-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2011-02-02  4:45                 ` [PATCH v2] " Dmitry Torokhov
2011-02-02  4:45                   ` Dmitry Torokhov
2011-02-02 11:48               ` Thomas Chou
2011-02-02 12:11                 ` [Nios2-dev] " Tobias Klauser
2011-02-02 12:11                   ` Tobias Klauser
2011-02-02 15:38                 ` Grant Likely
     [not found]                   ` <20110202153803.GC20275-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2011-02-02 23:32                     ` Thomas Chou [this message]
2011-02-02 23:32                       ` Thomas Chou
2011-02-02 15:39                 ` Grant Likely
2011-02-02 23:35                   ` Thomas Chou
     [not found]                   ` <20110202153959.GD20275-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2011-02-03 22:27                     ` Walter Goossens
2011-02-03 22:27                       ` Walter Goossens
     [not found]                       ` <4D4B2BC9.1030000-CmkmPbn3yAE@public.gmane.org>
2011-02-03 22:53                         ` Mitch Bradley
2011-02-03 22:53                           ` Mitch Bradley
2011-02-03 23:02                           ` Walter Goossens

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=4D49E99B.8080400@wytron.com.tw \
    --to=thomas-sdxuxyehebicupeqfhbrbg@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
    --cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.