From: Tom Rini Date: Mon, 31 Jul 2017 09:11:18 -0400 Subject: [U-Boot] [PATCH 0/2] misc: i2c_eeprom: Add compatibles In-Reply-To: <20170731032531.22547-1-wenyou.yang@microchip.com> References: <20170731032531.22547-1-wenyou.yang@microchip.com> Message-ID: <20170731131118.GI16135@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Jul 31, 2017 at 11:25:29AM +0800, Wenyou Yang wrote: > Add the compatibles to support the I2C EEPROM 24AA02E48 and AT24MAC402 > respectively. > - microchip,24aa02e48 > - atmel,24mac402 > > > Wenyou Yang (2): > misc: i2c_eeprom: Add compatible for 24AA02E48 > misc: i2c_eeprom: Add compatible for AT24MAC402 > > drivers/misc/i2c_eeprom.c | 2 ++ > 1 file changed, 2 insertions(+) How does this work in the kernel? Grepping around on what we list currently even, I see that Documentation/devicetree/bindings/eeprom/eeprom.txt lists some of the ones we have in drivers/misc/i2c_eeprom.c as an example but nothing catching on the compatible string. Does the kernel have some smart logic to match these compatibles? If so, could we mirror that? Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: