Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763006Ab3JQWFx (ORCPT ); Thu, 17 Oct 2013 18:05:53 -0400 Received: from mo4.mail-out.ovh.net ([178.32.228.4]:41505 "EHLO mo4.mail-out.ovh.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762535Ab3JQWFw (ORCPT ); Thu, 17 Oct 2013 18:05:52 -0400 Date: Thu, 17 Oct 2013 18:09:46 +0200 From: Jean-Christophe PLAGNIOL-VILLARD To: Lee Jones Cc: srinivas kandagatla , Maxime COQUELIN , Wolfram Sang , Rob Herring , Pawel Moll , Mark Rutland , Stephen Warren , Ian Campbell , Rob Landley , Russell King , Grant Likely , "devicetree@vger.kernel.org" , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-i2c@vger.kernel.org" , Stuart MENEFY , Stephen GALLIMORE , Gabriel FERNANDEZ Subject: Re: [PATCH v5 1/4] i2c: busses: i2c-st: Add ST I2C controller Message-ID: <20131017160946.GF14104@ns203013.ovh.net> References: <1381754813-4679-1-git-send-email-maxime.coquelin@st.com> <1381754813-4679-2-git-send-email-maxime.coquelin@st.com> <20131016151419.GA14104@ns203013.ovh.net> <525F915D.9020501@st.com> <525FAEED.7030207@st.com> <20131017141957.GE14104@ns203013.ovh.net> <20131017155308.GQ19112@lee--X1> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20131017155308.GQ19112@lee--X1> X-PGP-Key: http://uboot.jcrosoft.org/plagnioj.asc X-PGP-key-fingerprint: 6309 2BBA 16C8 3A07 1772 CC24 DEFC FFA3 279C CE7C User-Agent: Mutt/1.5.21 (2010-09-15) X-Ovh-Tracer-Id: 816840383210499071 X-Ovh-Remote: 91.121.171.124 (ns203013.ovh.net) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-OVH-SPAMSTATE: OK X-OVH-SPAMSCORE: -100 X-OVH-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeeiledrfeefucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd X-Spam-Check: DONE|U 0.5/N X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeeiledrfeefucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2140 Lines: 54 On 16:53 Thu 17 Oct , Lee Jones wrote: > On Thu, 17 Oct 2013, Jean-Christophe PLAGNIOL-VILLARD wrote: > > > On 10:33 Thu 17 Oct , srinivas kandagatla wrote: > > > On 17/10/13 08:27, Maxime COQUELIN wrote: > > > > ... > > > >>> >> + > > > >>> >> +static struct of_device_id st_i2c_match[] = { > > > >>> >> + { .compatible = "st,comms-ssc-i2c", }, > > > >> > the rules is to put the first soc that use the ip in the compatible > > > >> > as st,sti7100-scc-i2c > > > > Ok. There are no plans to upstream the SH4 platforms, it will only > > > > remains in stlinux.com. > > > > Maybe I can set the first ARM platform (STiH415)? > > > > That would give st,stih415-ssc-i2c. > > > NAK, for st,stih415-ssc-i2c naming. > > > > > > IMO, this makes sense when the same IP integration done on different SOC > > > changes slightly/very differently. > > > > > > But in this case the "comms" IP remains unchanged across all the SOCs. > > > > > > I would still prefer "st,comms-ssc-i2c", allowing a single device driver > > > to match against several SoCs. ST "comms" IP it is integrated across all > > > the STi series of SoCs, so we don't want to add new entry in compatible > > > for every new SOC. > > > > you never need this you always the first SoC that's all > > > > see other bindings on at91 as example sorry NACK > > I'm guessing that using the first SoC is an I2C'isum. > > Guys, if you don't want to be too specific, just make it as generic as > possible whilest still using the SoC as a POR: st,stih41x-ssc-i2c will > do for now, as it covers all current bases. except this is wrong the IP is used on much older SoC than the recent ARM ones and the DT so please respect the rule first SoC used on Best Regards, J. > > -- > Lee Jones > Linaro STMicroelectronics Landing Team Lead > Linaro.org │ Open source software for ARM SoCs > Follow Linaro: Facebook | Twitter | Blog -- 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/