diff for duplicates of <20160905014636.GB25778@tiger> diff --git a/a/1.txt b/N1/1.txt index b8f1b99..6ebabf9 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -3,33 +3,33 @@ On Tue, Aug 30, 2016 at 02:07:17PM +0000, Stuart Yoder wrote: > > > On Mon, 2016-08-29 at 17:52 +0800, Shawn Guo wrote: > > > > On Fri, Aug 26, 2016 at 03:57:21PM +0530, Bhaskar Upadhaya wrote: > > > > > -> > > > > + clockgen: clocking at 1ee1000 { +> > > > > + clockgen: clocking@1ee1000 { > > > > > + compatible = "fsl,ls1012a-clockgen"; > > > > The compatible cannot be found in binding docs. > > > -> > > From?Documentation/devicetree/bindings/clock/qoriq-clock.txt: +> > > From Documentation/devicetree/bindings/clock/qoriq-clock.txt: > > > > > > - compatible: Should contain a chip-specific clock block compatible -> > > ????????string and (if applicable) may contain a chassis-version clock -> > > ????????compatible string. +> > > string and (if applicable) may contain a chassis-version clock +> > > compatible string. > > > -> > > ? ? ? ? Chip-specific strings are of the form "fsl,<chip>-clockgen", such as: -> > > ????????* "fsl,p2041-clockgen" -> > > ????????* "fsl,p3041-clockgen" -> > > ????????* "fsl,p4080-clockgen" -> > > ????????* "fsl,p5020-clockgen" -> > > ????????* "fsl,p5040-clockgen" -> > > ????????* "fsl,t4240-clockgen" -> > > ????????* "fsl,b4420-clockgen" -> > > ????????* "fsl,b4860-clockgen" -> > > ????????* "fsl,ls1021a-clockgen" -> > > ????????Chassis-version clock strings include: -> > > ????????* "fsl,qoriq-clockgen-1.0": for chassis 1.0 clocks -> > > ????????* "fsl,qoriq-clockgen-2.0": for chassis 2.0 clocks +> > > Chip-specific strings are of the form "fsl,<chip>-clockgen", such as: +> > > * "fsl,p2041-clockgen" +> > > * "fsl,p3041-clockgen" +> > > * "fsl,p4080-clockgen" +> > > * "fsl,p5020-clockgen" +> > > * "fsl,p5040-clockgen" +> > > * "fsl,t4240-clockgen" +> > > * "fsl,b4420-clockgen" +> > > * "fsl,b4860-clockgen" +> > > * "fsl,ls1021a-clockgen" +> > > Chassis-version clock strings include: +> > > * "fsl,qoriq-clockgen-1.0": for chassis 1.0 clocks +> > > * "fsl,qoriq-clockgen-2.0": for chassis 2.0 clocks > > > > > > I really hope we don't have to update every single fsl,<chip>-whatever binding -> > > every time a new chip comes out. ?There are already other chips not listed, -> > > FWIW (e.g. t1040, t2080, ls1043a, and ls2080a). ?That's why it says "such as". +> > > every time a new chip comes out. There are already other chips not listed, +> > > FWIW (e.g. t1040, t2080, ls1043a, and ls2080a). That's why it says "such as". > > > > If I remember correctly, DT maintainers want every supported compatible > > string explicitly listed in bindings doc. And they even added a check @@ -58,3 +58,7 @@ and checkpatch is basically asking for conflicting thing. Rob, Mark, can you guys please clarify? Shawn +-- +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 diff --git a/a/content_digest b/N1/content_digest index f6a1556..cdf3e83 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,10 +3,20 @@ "ref\01472493061.13245.39.camel@buserror.net\0" "ref\020160830120220.GC8363@tiger\0" "ref\0HE1PR0401MB2636B40376255680B6A58CFB8DE00@HE1PR0401MB2636.eurprd04.prod.outlook.com\0" - "From\0shawnguo@kernel.org (Shawn Guo)\0" - "Subject\0[PATCH v2 1/1] arm64: Add DTS support for FSL's LS1012A SoC\0" + "ref\0HE1PR0401MB2636B40376255680B6A58CFB8DE00-B0v07Ae2tarUYqUkpow3g43W/0Ik+aLCnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org\0" + "From\0Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>\0" + "Subject\0Re: [PATCH v2 1/1] arm64: Add DTS support for FSL's LS1012A SoC\0" "Date\0Mon, 5 Sep 2016 09:46:36 +0800\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Stuart Yoder <stuart.yoder-3arQi8VN3Tc@public.gmane.org>" + Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> + " Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>\0" + "Cc\0Scott Wood <oss-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>" + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + Bhaskar U <bhaskar.upadhaya-3arQi8VN3Tc@public.gmane.org> + Prabhakar Kushwaha <prabhakar.kushwaha-3arQi8VN3Tc@public.gmane.org> + linux-devel-XDVM779Km55Y1YpKYGMr2+TW4wlIGRCZ@public.gmane.org <linux-devel-XDVM779Km55Y1YpKYGMr2+TW4wlIGRCZ@public.gmane.org> + Pratiyush Srivastava <pratiyush.srivastava-3arQi8VN3Tc@public.gmane.org> + " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>\0" "\00:1\0" "b\0" "On Tue, Aug 30, 2016 at 02:07:17PM +0000, Stuart Yoder wrote:\n" @@ -14,33 +24,33 @@ "> > > On Mon, 2016-08-29 at 17:52 +0800, Shawn Guo wrote:\n" "> > > > On Fri, Aug 26, 2016 at 03:57:21PM +0530, Bhaskar Upadhaya wrote:\n" "> > > > >\n" - "> > > > > +\t\tclockgen: clocking at 1ee1000 {\n" + "> > > > > +\t\tclockgen: clocking@1ee1000 {\n" "> > > > > +\t\t\tcompatible = \"fsl,ls1012a-clockgen\";\n" "> > > > The compatible cannot be found in binding docs.\n" "> > >\n" - "> > > From?Documentation/devicetree/bindings/clock/qoriq-clock.txt:\n" + "> > > From\302\240Documentation/devicetree/bindings/clock/qoriq-clock.txt:\n" "> > >\n" "> > > - compatible: Should contain a chip-specific clock block compatible\n" - "> > > ????????string and (if applicable) may contain a chassis-version clock\n" - "> > > ????????compatible string.\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240string and (if applicable) may contain a chassis-version clock\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240compatible string.\n" "> > >\n" - "> > > ? ? ? ? Chip-specific strings are of the form \"fsl,<chip>-clockgen\", such as:\n" - "> > > ????????* \"fsl,p2041-clockgen\"\n" - "> > > ????????* \"fsl,p3041-clockgen\"\n" - "> > > ????????* \"fsl,p4080-clockgen\"\n" - "> > > ????????* \"fsl,p5020-clockgen\"\n" - "> > > ????????* \"fsl,p5040-clockgen\"\n" - "> > > ????????* \"fsl,t4240-clockgen\"\n" - "> > > ????????* \"fsl,b4420-clockgen\"\n" - "> > > ????????* \"fsl,b4860-clockgen\"\n" - "> > > ????????* \"fsl,ls1021a-clockgen\"\n" - "> > > ????????Chassis-version clock strings include:\n" - "> > > ????????* \"fsl,qoriq-clockgen-1.0\": for chassis 1.0 clocks\n" - "> > > ????????* \"fsl,qoriq-clockgen-2.0\": for chassis 2.0 clocks\n" + "> > > \302\240 \302\240 \302\240 \302\240 Chip-specific strings are of the form \"fsl,<chip>-clockgen\", such as:\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,p2041-clockgen\"\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,p3041-clockgen\"\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,p4080-clockgen\"\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,p5020-clockgen\"\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,p5040-clockgen\"\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,t4240-clockgen\"\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,b4420-clockgen\"\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,b4860-clockgen\"\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,ls1021a-clockgen\"\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240Chassis-version clock strings include:\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,qoriq-clockgen-1.0\": for chassis 1.0 clocks\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240* \"fsl,qoriq-clockgen-2.0\": for chassis 2.0 clocks\n" "> > >\n" "> > > I really hope we don't have to update every single fsl,<chip>-whatever binding\n" - "> > > every time a new chip comes out. ?There are already other chips not listed,\n" - "> > > FWIW (e.g. t1040, t2080, ls1043a, and ls2080a). ?That's why it says \"such as\".\n" + "> > > every time a new chip comes out. \302\240There are already other chips not listed,\n" + "> > > FWIW (e.g. t1040, t2080, ls1043a, and ls2080a). \302\240That's why it says \"such as\".\n" "> > \n" "> > If I remember correctly, DT maintainers want every supported compatible\n" "> > string explicitly listed in bindings doc. And they even added a check\n" @@ -68,6 +78,10 @@ "and checkpatch is basically asking for conflicting thing. Rob, Mark,\n" "can you guys please clarify?\n" "\n" - Shawn + "Shawn\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -67255810abf69bf5039967c6f2c7bff56a284b634283905e70fab94c1a74236f +9b12db06a7118bc23ef1bafa93442bf0f421dc5d488a2fadb16d336d771b7b3c
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.