From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Javier Martinez Canillas <javier@dowhile0.org>,
linux-kernel@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
Rob Herring <robh+dt@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Javier Martinez Canillas <javier@dowhile0.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [RESEND, v5, 12/16] powerpc/5200: Add generic compatible string for I2C EEPROM
Date: Thu, 29 Jun 2017 22:21:11 +1000 (AEST) [thread overview]
Message-ID: <3wyzKN0hY6z9s7v@ozlabs.org> (raw)
In-Reply-To: <20170615185418.13980-13-javier@dowhile0.org>
On Thu, 2017-06-15 at 18:54:14 UTC, 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 <javier@dowhile0.org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/fd393188064e3d01a91a21160751f6
cheers
next prev parent reply other threads:[~2017-06-29 12:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 18:54 [RESEND PATCH v5 00/16] eeprom: at24: Add OF device ID table Javier Martinez Canillas
2017-06-15 18:54 ` [RESEND PATCH v5 12/16] powerpc/5200: Add generic compatible string for I2C EEPROM Javier Martinez Canillas
2017-06-29 12:21 ` Michael Ellerman [this message]
2017-06-15 18:54 ` [RESEND PATCH v5 13/16] powerpc/fsl: " Javier Martinez Canillas
2017-06-29 12:21 ` [RESEND, v5, " Michael Ellerman
2017-06-15 18:54 ` [RESEND PATCH v5 14/16] powerpc/512x: " Javier Martinez Canillas
2017-06-29 12:21 ` [RESEND, v5, " Michael Ellerman
2017-06-15 18:54 ` [RESEND PATCH v5 15/16] powerpc/83xx: " Javier Martinez Canillas
2017-06-29 12:21 ` [RESEND, v5, " Michael Ellerman
2017-06-15 18:54 ` [RESEND PATCH v5 16/16] powerpc/44x: " Javier Martinez Canillas
2017-06-29 12:21 ` [RESEND, v5, " Michael Ellerman
2017-07-10 7:47 ` [RESEND PATCH v5 00/16] eeprom: at24: Add OF device ID table Javier Martinez Canillas
2017-07-31 15:30 ` Wolfram Sang
2017-07-31 16:17 ` Javier Martinez Canillas
2017-08-28 16:01 ` Wolfram Sang
2017-08-29 8:44 ` Javier Martinez Canillas
2017-08-29 8:48 ` Wolfram Sang
2017-08-30 16:19 ` Javier Martinez Canillas
2017-08-30 17:42 ` Wolfram Sang
2017-08-30 19:57 ` Javier Martinez Canillas
2017-08-30 20:15 ` Geert Uytterhoeven
2017-08-30 20:59 ` Javier Martinez Canillas
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=3wyzKN0hY6z9s7v@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=devicetree@vger.kernel.org \
--cc=javier@dowhile0.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=wsa@the-dreams.de \
/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).