Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On 11/12, Rob Herring wrote: > On Thu, Nov 12, 2015 at 6:11 PM, Stephen Boyd wrote: > > On 11/12, Rob Herring wrote: > >> On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: > >> > On 11/12, Rob Herring wrote: > >> >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > >> > >> >> >

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On Thu, Nov 12, 2015 at 6:11 PM, Stephen Boyd wrote: > On 11/12, Rob Herring wrote: >> On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: >> > On 11/12, Rob Herring wrote: >> >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: >> >> >> > +Some qcom based bootloaders identify the

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On 11/12, Olof Johansson wrote: > On Mon, Oct 26, 2015 at 2:25 PM, Stephen Boyd wrote: > > +Examples: > > + > > + "qcom,msm8916-v1-cdp-pm8916-v2.1" > > This is just awkward, but this... > > > + > > +A CDP board with an msm8916 SoC, version 1 paired with a pm8916 PMIC of > > version > >

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On 11/12, Rob Herring wrote: > On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: > > On 11/12, Rob Herring wrote: > >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > > >> > +Some qcom based bootloaders identify the dtb blob based on a set of > >> > +device properties like

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

Hi, On Mon, Oct 26, 2015 at 2:25 PM, Stephen Boyd wrote: > Some qcom based bootloaders identify the dtb blob based on a set > of device properties like SoC, platform, PMIC, and revisions of > those components. In downstream kernels, these values are added > to the different component dtsi files

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: > On 11/12, Rob Herring wrote: >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: >> > Some qcom based bootloaders identify the dtb blob based on a set >> > of device properties like SoC, platform, PMIC, and revisions of >> >

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On 11/12, Rob Herring wrote: > On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > > Some qcom based bootloaders identify the dtb blob based on a set > > of device properties like SoC, platform, PMIC, and revisions of > > those components. In downstream kernels, these values are added

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > Some qcom based bootloaders identify the dtb blob based on a set > of device properties like SoC, platform, PMIC, and revisions of > those components. In downstream kernels, these values are added > to the different component dtsi

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On 11/12, Rob Herring wrote: > On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > > Some qcom based bootloaders identify the dtb blob based on a set > > of device properties like SoC, platform, PMIC, and revisions of > > those components. In downstream kernels, these values are added

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On Thu, Nov 12, 2015 at 6:11 PM, Stephen Boyd wrote: > On 11/12, Rob Herring wrote: >> On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: >> > On 11/12, Rob Herring wrote: >> >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: >> >> >> >

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On 11/12, Rob Herring wrote: > On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: > > On 11/12, Rob Herring wrote: > >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > > >> > +Some qcom based bootloaders identify the dtb blob based on a set of > >> >

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: > On 11/12, Rob Herring wrote: >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: >> > Some qcom based bootloaders identify the dtb blob based on a set >> > of device properties like SoC, platform, PMIC, and

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On 11/12, Olof Johansson wrote: > On Mon, Oct 26, 2015 at 2:25 PM, Stephen Boyd wrote: > > +Examples: > > + > > + "qcom,msm8916-v1-cdp-pm8916-v2.1" > > This is just awkward, but this... > > > + > > +A CDP board with an msm8916 SoC, version 1 paired with a pm8916 PMIC

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

Hi, On Mon, Oct 26, 2015 at 2:25 PM, Stephen Boyd wrote: > Some qcom based bootloaders identify the dtb blob based on a set > of device properties like SoC, platform, PMIC, and revisions of > those components. In downstream kernels, these values are added > to the different

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On 11/12, Rob Herring wrote: > On Thu, Nov 12, 2015 at 6:11 PM, Stephen Boyd wrote: > > On 11/12, Rob Herring wrote: > >> On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: > >> > On 11/12, Rob Herring wrote: > >> >> On Mon, Oct 26, 2015 at

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > Some qcom based bootloaders identify the dtb blob based on a set > of device properties like SoC, platform, PMIC, and revisions of > those components. In downstream kernels, these values are added > to the different component dtsi

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > Some qcom based bootloaders identify the dtb blob based on a set > of device properties like SoC, platform, PMIC, and revisions of > those components. In downstream kernels, these values are added > to the different component dtsi

Re: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > Some qcom based bootloaders identify the dtb blob based on a set > of device properties like SoC, platform, PMIC, and revisions of > those components. In downstream kernels, these values are added > to the different component dtsi

[PATCH 1/3] devicetree: bindings: Document qcom board compatible format

Some qcom based bootloaders identify the dtb blob based on a set of device properties like SoC, platform, PMIC, and revisions of those components. In downstream kernels, these values are added to the different component dtsi files (i.e. pmic dtsi file, SoC dtsi file, board dtsi file, etc.) via

[PATCH 1/3] devicetree: bindings: Document qcom board compatible format

Some qcom based bootloaders identify the dtb blob based on a set of device properties like SoC, platform, PMIC, and revisions of those components. In downstream kernels, these values are added to the different component dtsi files (i.e. pmic dtsi file, SoC dtsi file, board dtsi file, etc.) via