From: Rob Herring <robherring2@gmail.com>
To: Olof Johansson <olof@lixom.net>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
devicetree-discuss@lists.ozlabs.org, linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: mpu3050: add of_match table for device-tree probing
Date: Tue, 27 Dec 2011 10:07:42 -0600 [thread overview]
Message-ID: <4EF9ED4E.6000408@gmail.com> (raw)
In-Reply-To: <CAOesGMiGJmc6FhsDcsmROUgoLD4eDFKK=LE7yYjkJn1O7oiL8Q@mail.gmail.com>
On 12/23/2011 09:58 AM, Olof Johansson wrote:
> Hi,
>
> On Fri, Dec 23, 2011 at 1:22 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
>> Hi Olof,
>>
>> On Thu, Dec 22, 2011 at 06:39:52PM -0800, Olof Johansson wrote:
>>> Adding invn,mpu3050 as the initial id.
>>>
>>
>> I believe you also need to add this to
>> Documentation/devicetree/bindings/input/
>
> For simple i2c devices that only have a name, address and possibly an
> interrupt, there's no need to document a binding (it hasn't been done
> in the past for the vast majority of those devices).
But then how do you find out if there is a existing binding for a device
without searching in the kernel source tree? The binding docs are
planned to be moved out as they are not Linux specific. There needs to
be 1 location to find binding information.
I do wonder if we should have a more structured registry or database of
bindings than free form text files...
Rob
next prev parent reply other threads:[~2011-12-27 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 2:39 [PATCH] Input: mpu3050: add of_match table for device-tree probing Olof Johansson
[not found] ` <1324607992-2919-1-git-send-email-olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
2011-12-23 9:22 ` Dmitry Torokhov
2011-12-23 15:58 ` Olof Johansson
2011-12-27 16:07 ` Rob Herring [this message]
2011-12-27 17:14 ` Olof Johansson
2012-01-02 8:42 ` Grant Likely
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=4EF9ED4E.6000408@gmail.com \
--to=robherring2@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=olof@lixom.net \
/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;
as well as URLs for NNTP newsgroup(s).