From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752925AbdLUPHF (ORCPT ); Thu, 21 Dec 2017 10:07:05 -0500 Received: from mail-qk0-f195.google.com ([209.85.220.195]:34261 "EHLO mail-qk0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751643AbdLUPHA (ORCPT ); Thu, 21 Dec 2017 10:07:00 -0500 X-Google-Smtp-Source: ACJfBovuLHV3tTbpdVUlUa7FnHPDi37vRMEp/Y2zEPnB260/9ONyVaDGY0ip0WYB1limhbNyufhGWvhxAQJcgi/mJCQ= MIME-Version: 1.0 In-Reply-To: <20171124162750.18756-1-javierm@redhat.com> References: <20171124162750.18756-1-javierm@redhat.com> From: Arnd Bergmann Date: Thu, 21 Dec 2017 16:06:59 +0100 X-Google-Sender-Auth: XqDfnDPEq4qcEOcF6VdH45C5WL4 Message-ID: Subject: Re: [RESEND PATCH 1/4] ARM: dts: efm32: Add generic compatible string for I2C EEPROM To: Javier Martinez Canillas Cc: Linux Kernel Mailing List , Olof Johansson , arm-soc , DTML , Rob Herring , Mark Rutland , Russell King , Linux ARM Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 24, 2017 at 5:27 PM, 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 Applied to next/dt, thanks Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [RESEND PATCH 1/4] ARM: dts: efm32: Add generic compatible string for I2C EEPROM Date: Thu, 21 Dec 2017 16:06:59 +0100 Message-ID: References: <20171124162750.18756-1-javierm@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20171124162750.18756-1-javierm-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Javier Martinez Canillas Cc: Linux Kernel Mailing List , Olof Johansson , arm-soc , DTML , Rob Herring , Mark Rutland , Russell King , Linux ARM List-Id: devicetree@vger.kernel.org On Fri, Nov 24, 2017 at 5:27 PM, 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 Applied to next/dt, thanks Arnd -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Thu, 21 Dec 2017 16:06:59 +0100 Subject: [RESEND PATCH 1/4] ARM: dts: efm32: Add generic compatible string for I2C EEPROM In-Reply-To: <20171124162750.18756-1-javierm@redhat.com> References: <20171124162750.18756-1-javierm@redhat.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Nov 24, 2017 at 5:27 PM, 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 Applied to next/dt, thanks Arnd