Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934087AbbLPJQ6 (ORCPT ); Wed, 16 Dec 2015 04:16:58 -0500 Received: from mga02.intel.com ([134.134.136.20]:47686 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932927AbbLPJQz (ORCPT ); Wed, 16 Dec 2015 04:16:55 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,436,1444719600"; d="scan'208";a="874727791" Date: Wed, 16 Dec 2015 11:16:52 +0200 From: Mika Westerberg To: Suravee Suthikulpanit Cc: wsa@the-dreams.de, linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] i2c: designware: Add support for AMD Seattle I2C Message-ID: <20151216091652.GN1762@lahna.fi.intel.com> References: <1450216553-5641-1-git-send-email-Suravee.Suthikulpanit@amd.com> <5670C90A.5020305@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5670C90A.5020305@amd.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1562 Lines: 39 On Tue, Dec 15, 2015 at 08:14:34PM -0600, Suravee Suthikulpanit wrote: > Hi Mika, > > On 12/15/15 15:55, Suravee Suthikulpanit wrote: > >Add device HID AMDI0510 to match the I2C controlers on AMD Seattle platform > > > >Signed-off-by: Suravee Suthikulpanit > >--- > > drivers/i2c/busses/i2c-designware-platdrv.c | 1 + > > 1 file changed, 1 insertion(+) > > > >diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c b/drivers/i2c/busses/i2c-designware-platdrv.c > >index 57f623b..a027154 100644 > >--- a/drivers/i2c/busses/i2c-designware-platdrv.c > >+++ b/drivers/i2c/busses/i2c-designware-platdrv.c > >@@ -117,6 +117,7 @@ static const struct acpi_device_id dw_i2c_acpi_match[] = { > > { "80860F41", 0 }, > > { "808622C1", 0 }, > > { "AMD0010", 0 }, > >+ { "AMDI0510", 0 }, > > { } > > Since this driver seems to be used by several SOCs, and we have been adding > the HID from various SOC vendors. Do you think it would be better to assign > a CID so that each SOC vendor can specify in their ACPI DSDT and we can > match them here? Sure _CID would work here. > Then, we can also associate the FMCN and SSCN along with the CID, and > guarantee compatibility. Well, the driver checks those everytime it finds that the device has ACPI companion regardless of _HID/_CID. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/