From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1948057AbdEZPvT (ORCPT ); Fri, 26 May 2017 11:51:19 -0400 Received: from muru.com ([72.249.23.125]:49508 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S943798AbdEZPvN (ORCPT ); Fri, 26 May 2017 11:51:13 -0400 Date: Fri, 26 May 2017 08:51:09 -0700 From: Tony Lindgren To: Javier Martinez Canillas Cc: linux-kernel@vger.kernel.org, Wolfram Sang , Rob Herring , linux-arm-kernel@lists.infradead.org, =?utf-8?Q?Beno=C3=AEt?= Cousson , devicetree@vger.kernel.org, Rob Herring , Mark Rutland , linux-omap@vger.kernel.org, Russell King , Mark Jackson Subject: Re: [PATCH v5 03/20] ARM: dts: omap: Add generic compatible string for I2C EEPROM Message-ID: <20170526155108.GF3717@atomide.com> References: <20170523133448.4794-1-javier@dowhile0.org> <20170523133448.4794-4-javier@dowhile0.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170523133448.4794-4-javier@dowhile0.org> User-Agent: Mutt/1.8.2 (2017-04-18) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Javier Martinez Canillas [170523 06:38]: > 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. Picking this patch into omap-for-v4.13/dt thanks. Tony