From: Sebastian Reichel <sre@kernel.org>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v4 2/2] power: supply: ltc2941-battery-gauge: Add OF device ID table
Date: Tue, 11 Apr 2017 16:29:17 +0200 [thread overview]
Message-ID: <20170411142917.udh4cl4qw27dqte5@earth> (raw)
In-Reply-To: <20170329160057.8298-2-javier@osg.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
Hi,
On Wed, Mar 29, 2017 at 12:00:57PM -0400, Javier Martinez Canillas wrote:
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees. This is working on the assumption that a
> I2C device registered via OF will always match a legacy I2C device ID and
> that the MODALIAS reported will always be of the form i2c:<device>.
>
> But this could change in the future so the correct approach is to have an
> OF device ID table if the devices are registered via OF.
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
Thanks, queued.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-11 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 16:00 [PATCH v4 1/2] power: supply: ltc2941-battery-gauge: Add vendor to compatibles in binding Javier Martinez Canillas
2017-03-29 16:00 ` [PATCH v4 2/2] power: supply: ltc2941-battery-gauge: Add OF device ID table Javier Martinez Canillas
2017-04-11 14:29 ` Sebastian Reichel [this message]
[not found] ` <20170329160057.8298-1-javier-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2017-04-03 15:15 ` [PATCH v4 1/2] power: supply: ltc2941-battery-gauge: Add vendor to compatibles in binding Rob Herring
2017-04-11 14:28 ` Sebastian Reichel
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=20170411142917.udh4cl4qw27dqte5@earth \
--to=sre@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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