From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: Make I2C ID tables non-mandatory for DT'ed and/or ACPI'ed devices
Date: Sat, 31 May 2014 15:48:06 +0200 [thread overview]
Message-ID: <20140531134805.GA3287@katana> (raw)
In-Reply-To: <20140530192516.GA4319@lee--X1>
> Right, I read the function which provides the functionality, but my
> point is; I don't think my patch changes the semantics in a way which
> would adversely affect this option. If you think that it does, can you
> specify how please?
Currently, if a driver would be DT only and does not provide a seperate
i2c_device_id table, then the driver is unusable with method 4. I don't
like to have some drivers being capable of it and some not.
> Does the sysfs method create a i2c_device_id table? If not, how does
> it probe successfully pre-patch?
The sysfs method creates a device. Its name is matched against
i2c_device_ids only since it does not have a node pointer for DT to be
matched against.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140531/ed161c08/attachment.sig>
next prev parent reply other threads:[~2014-05-31 13:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 12:26 [PATCH 0/{1,1}] i2c: Make I2C ID tables non-mandatory for DT/ACPI Lee Jones
2014-05-30 12:26 ` [PATCH] i2c: Make I2C ID tables non-mandatory for DT'ed and/or ACPI'ed devices Lee Jones
2014-05-30 12:36 ` Wolfram Sang
2014-05-30 12:55 ` Lee Jones
2014-05-30 13:34 ` Lee Jones
2014-05-30 17:48 ` Wolfram Sang
2014-05-30 19:25 ` Lee Jones
2014-05-31 13:48 ` Wolfram Sang [this message]
2014-06-02 12:16 ` Linus Walleij
2014-06-02 12:38 ` Wolfram Sang
2014-06-02 13:26 ` Linus Walleij
2014-06-02 13:26 ` Lee Jones
2014-06-02 14:29 ` Michael Lawnick
2014-06-03 11:18 ` Linus Walleij
2014-06-04 6:09 ` Michael Lawnick
2014-06-12 7:55 ` Linus Walleij
2014-06-12 9:28 ` Michael Lawnick
2014-05-30 12:26 ` Lee Jones
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=20140531134805.GA3287@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).