Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754757AbbLaCfQ (ORCPT ); Wed, 30 Dec 2015 21:35:16 -0500 Received: from mail-am1on0099.outbound.protection.outlook.com ([157.56.112.99]:35579 "EHLO emea01-am1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752153AbbLaCfM (ORCPT ); Wed, 30 Dec 2015 21:35:12 -0500 X-Greylist: delayed 83838 seconds by postgrey-1.27 at vger.kernel.org; Wed, 30 Dec 2015 21:35:11 EST From: Yao Yuan To: Rob Herring CC: "mark.rutland@arm.com" , "pawel.moll@arm.com" , "galak@codeaurora.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" Subject: RE: [PATCH v2 1/4] Documentation: fsl-quadspi: Add fsl,ls2080a-dspi compatible string Thread-Topic: [PATCH v2 1/4] Documentation: fsl-quadspi: Add fsl,ls2080a-dspi compatible string Thread-Index: AQHRPjt1BXKDQbKDpketjcMY+9AOyp7iUsmAgACQtTCAAMsAAIAAuk6Q Date: Thu, 31 Dec 2015 02:35:07 +0000 Message-ID: References: <1450954863-7540-1-git-send-email-yao.yuan@freescale.com> <20151229183501.GH12450@rob-hp-laptop> In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=yao.yuan@nxp.com; x-originating-ip: [123.151.195.52] x-microsoft-exchange-diagnostics: 1;AM2PR04MB0722;5:g/qsmIicp2Jz4WvoZ+Al8Y2RNb1JcU6S5Cb+Ej3tFMfw2bt17RP/QYUhou0ikll19JVXgyvCpjYwi35IB2wMIemG0J1P+8ISnI3BNIStVY3YcidZWIEggHlU9o4EhMrgZr4rhkjB2qf0vx7VtsFbbg==;24:H24hCa2EbEzf8oQ1TeHvp2XGOAsA5TyQl6XWCRVjTF8kIb/febFYU52r4fXhJdN/puFbwZ/hA7UHttwoEghuO9/HTcAyhEZY2febxD1JSe8= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM2PR04MB0722; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(185117386973197); x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(2401047)(8121501046)(520078)(5005006)(3002001)(10201501046);SRVR:AM2PR04MB0722;BCL:0;PCL:0;RULEID:;SRVR:AM2PR04MB0722; x-forefront-prvs: 08076ABC99 x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(6009001)(377454003)(24454002)(189002)(199003)(1220700001)(40100003)(105586002)(5008740100001)(189998001)(81156007)(93886004)(3846002)(92566002)(11100500001)(5001960100002)(101416001)(74316001)(4326007)(586003)(33656002)(102836003)(1096002)(19580395003)(5003600100002)(19580405001)(97736004)(54356999)(66066001)(50986999)(76176999)(6116002)(87936001)(2950100001)(5004730100002)(2900100001)(122556002)(77096005)(86362001)(5002640100001)(106116001)(106356001)(76576001)(110136002)(10400500002)(142933001);DIR:OUT;SFP:1101;SCL:1;SRVR:AM2PR04MB0722;H:AM2PR04MB0722.eurprd04.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;MX:1;A:1;LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 X-OriginatorOrg: nxp.com X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Dec 2015 02:35:07.1642 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635 X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR04MB0722 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id tBV2ZLWQ006661 Content-Length: 2390 Lines: 63 On Wed, Dec 30, 2015 at 11:20 PM, Rob Herring wrote: > On Tue, Dec 29, 2015 at 9:17 PM, Yao Yuan wrote: > > Hi Rob, > > > > Thanks for your review. > > So you mean that I should add the commit message for why I add this new > compatible? > > Please don't top post on the lists. > > No, the binding doc should explain what are valid combinations of compatible > strings and the order when the dts can have multiple strings. For example, is > this valid: > > compatible = "fsl,vf610-dspi", "fsl,ls2080a-dspi"; > > In other words, I should be able to check a dts file against what the binding doc > says. > > Rob OK, I got it. The "fsl,vf610-dspi", "fsl,ls1021a-v1.0-dspi", "fsl,ls2085a-dspi" is valid and used in driver. But "fsl,ls2080a-dspi" is just used for platform flag. Could you help to give an example that how can I explain it in Documents? Or should I not write this compatible in Document. I find that many compatible strings like this (not valid just a platform flag) for other driver are not record in document. Thanks. Yuan Yao > > > On Wed, Dec 30, 2015 at 02:35AM, Rob Herring wrote: > >> On Thu, Dec 24, 2015 at 07:01:00PM +0800, Yuan Yao wrote: > >> > new compatible string: "fsl,ls2080a-qspi". > >> > > >> > Signed-off-by: Yuan Yao > >> > --- > >> > Changed in v2: > >> > Update my email to > >> > --- > >> > Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt | 3 ++- > >> > 1 file changed, 2 insertions(+), 1 deletion(-) > >> > > >> > diff --git a/Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt > >> b/Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt > >> > index fa77f87..2fe51d6 100644 > >> > --- a/Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt > >> > +++ b/Documentation/devicetree/bindings/spi/spi-fsl-dspi.txt > >> > @@ -1,7 +1,8 @@ > >> > ARM Freescale DSPI controller > >> > > >> > Required properties: > >> > -- compatible : "fsl,vf610-dspi", "fsl,ls1021a-v1.0-dspi", "fsl,ls2085a-dspi" > >> > +- compatible : "fsl,vf610-dspi", "fsl,ls1021a-v1.0-dspi", > >> > + "fsl,ls2085a-dspi", "fsl,ls2080a-dspi" > >> > >> You should explain what combinations of compatible strings are valid. > >> > >> Rob ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?