From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: olof@lixom.net, arm@kernel.org, arnd@arndb.de,
devicetree@vger.kernel.org,
Santosh Shilimkar <ssantosh@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH 2/4] ARM: dts: keystone: Add generic compatible string for I2C EEPROM
Date: Sat, 2 Dec 2017 19:57:57 -0800 [thread overview]
Message-ID: <b98fb17b-289c-4756-cfca-85e633b55354@oracle.com> (raw)
In-Reply-To: <20171124162750.18756-2-javierm@redhat.com>
On 11/24/17 8:27 AM, Javier Martinez Canillas wrote:
> The at24 driver allows to register I2C EEPROM chips using different vendor
> and devices, but the I2C subsystem does not take the vendor into account
> when matching using the I2C table since it only has device entries.
>
> But when matching using an OF table, both the vendor and device has to be
> taken into account so the driver defines only a set of compatible strings
> using the "atmel" vendor as a generic fallback for compatible I2C devices.
>
> So add this generic fallback to the device node compatible string to make
> the device to match the driver using the OF device ID table.
>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> ---
>
Applied
next prev parent reply other threads:[~2017-12-03 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 16:27 [RESEND PATCH 1/4] ARM: dts: efm32: " Javier Martinez Canillas
2017-11-24 16:27 ` [RESEND PATCH 2/4] ARM: dts: keystone: " Javier Martinez Canillas
2017-12-03 3:57 ` santosh.shilimkar [this message]
2017-11-24 16:27 ` [RESEND PATCH 3/4] ARM: dts: lpc18xx: " Javier Martinez Canillas
2017-12-21 15:08 ` Arnd Bergmann
2017-11-24 16:27 ` [RESEND PATCH 4/4] ARM: dts: socfpga: " Javier Martinez Canillas
2017-12-21 15:08 ` Arnd Bergmann
2017-12-21 15:06 ` [RESEND PATCH 1/4] ARM: dts: efm32: " Arnd Bergmann
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=b98fb17b-289c-4756-cfca-85e633b55354@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=javierm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=ssantosh@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
all inboxes | Powered by JetHome®