From: Thomas Chou <thomas@wytron.com.tw>
To: Walter Goossens <waltergoossens@home.nl>
Cc: Grant Likely <grant.likely@secretlab.ca>,
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
Subject: Re: [PATCH] alter_ps2: Add devicetree support
Date: Tue, 18 Jan 2011 22:26:15 +0800 [thread overview]
Message-ID: <4D35A307.5070706@wytron.com.tw> (raw)
In-Reply-To: <4D34D046.20708@home.nl>
On 01/18/2011 07:27 AM, Walter Goossens wrote:
>> so, instead of trying to us a 'generic' value like "altera,altera_ps2"
>> which has a bunch of ambiguity about which hardware actually
>> implements the behaviour, the values "altera,altera_ps2-1" and
>> "altera,altera_ps2-3" become the de-facto 'generic' values without any
>> messiness or ambiguity about what they mean.
>>
>> Plus, each .dts file still specifies the exact version that is
>> implemented on the board so that the driver can still fixup
>> version-specific bugs if any are discovered in the future.
>>
> Ahh ok.
> That does look like a good solution. I'll try and cook something up for
> that.
Hi Walter,
Can we use "kind" and "version" attribute of a sopcinfo file to build
the match string? This way, your dts converter won't need update for
each new component.
eg,
kind="altera_avalon_spi" version="9.0" ==> "altera","avalon-spi-9.0"
kind="altera_up_avalon_ps2_classic" version="6.1" ==>
"altera","up-avalon-ps2-classic-6.1"
- Thomas
next prev parent reply other threads:[~2011-01-18 14:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D040D1C.2020705@home.nl>
2011-01-17 6:29 ` [PATCH] alter_ps2: Add devicetree support Thomas Chou
2011-01-17 6:59 ` Grant Likely
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 [this message]
2011-01-17 21:31 ` Dmitry Torokhov
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
2011-02-03 3:05 ` [PATCH v3] " 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
2011-02-02 4:45 ` [PATCH v2] " Dmitry Torokhov
2011-02-02 11:48 ` Thomas Chou
2011-02-02 12:11 ` [Nios2-dev] " Tobias Klauser
2011-02-02 15:38 ` Grant Likely
2011-02-02 23:32 ` Thomas Chou
2011-02-02 15:39 ` Grant Likely
2011-02-02 23:35 ` Thomas Chou
2011-02-03 22:27 ` Walter Goossens
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=4D35A307.5070706@wytron.com.tw \
--to=thomas@wytron.com.tw \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmitry.torokhov@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nios2-dev@sopc.et.ntust.edu.tw \
--cc=waltergoossens@home.nl \
/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