Re: [PATCH] ARM: dts: qcom: Update msm8960 device trees

2014-05-28 Thread Kumar Gala

On May 28, 2014, at 3:09 PM, Josh Cartwright  wrote:

> On Wed, May 28, 2014 at 01:27:23PM -0500, Kumar Gala wrote:
>> * Move SoC peripherals into an SoC container node
>> * Move serial enabling into board file (qcom-msm8960-cdp.dts)
>> * Cleanup cpu node to match binding spec, enable-method and compatible
>>  should be per cpu, not part of the container
>> * Drop interrupts property from l2-cache node as its not part of the
>>  binding spec
>> 
>> Signed-off-by: Kumar Gala 
>> ---
>> arch/arm/boot/dts/qcom-msm8960-cdp.dts |   6 ++
>> arch/arm/boot/dts/qcom-msm8960.dtsi| 165 
>> +
>> 2 files changed, 93 insertions(+), 78 deletions(-)
>> 
>> diff --git a/arch/arm/boot/dts/qcom-msm8960-cdp.dts 
>> b/arch/arm/boot/dts/qcom-msm8960-cdp.dts
>> index a58fb88..8e77ed7 100644
>> --- a/arch/arm/boot/dts/qcom-msm8960-cdp.dts
>> +++ b/arch/arm/boot/dts/qcom-msm8960-cdp.dts
>> @@ -3,4 +3,10 @@
>> / {
>>  model = "Qualcomm MSM8960 CDP";
>>  compatible = "qcom,msm8960-cdp", "qcom,msm8960";
>> +
>> +soc {
>> +serial@1644 {
>> +status = "ok";
>> +};
>> +};
>> };
> 
> Is now the time put these serial nodes under a GSBI parent node?

Yeah, I’ll make the change to the 8960 & 8660 dts

- k

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by 
The Linux Foundation

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH] ARM: dts: qcom: Update msm8960 device trees

2014-05-28 Thread Josh Cartwright
On Wed, May 28, 2014 at 01:27:23PM -0500, Kumar Gala wrote:
> * Move SoC peripherals into an SoC container node
> * Move serial enabling into board file (qcom-msm8960-cdp.dts)
> * Cleanup cpu node to match binding spec, enable-method and compatible
>   should be per cpu, not part of the container
> * Drop interrupts property from l2-cache node as its not part of the
>   binding spec
> 
> Signed-off-by: Kumar Gala 
> ---
>  arch/arm/boot/dts/qcom-msm8960-cdp.dts |   6 ++
>  arch/arm/boot/dts/qcom-msm8960.dtsi| 165 
> +
>  2 files changed, 93 insertions(+), 78 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/qcom-msm8960-cdp.dts 
> b/arch/arm/boot/dts/qcom-msm8960-cdp.dts
> index a58fb88..8e77ed7 100644
> --- a/arch/arm/boot/dts/qcom-msm8960-cdp.dts
> +++ b/arch/arm/boot/dts/qcom-msm8960-cdp.dts
> @@ -3,4 +3,10 @@
>  / {
>   model = "Qualcomm MSM8960 CDP";
>   compatible = "qcom,msm8960-cdp", "qcom,msm8960";
> +
> + soc {
> + serial@1644 {
> + status = "ok";
> + };
> + };
>  };

Is now the time put these serial nodes under a GSBI parent node?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH] ARM: dts: qcom: Update msm8960 device trees

2014-05-28 Thread Josh Cartwright
On Wed, May 28, 2014 at 01:27:23PM -0500, Kumar Gala wrote:
 * Move SoC peripherals into an SoC container node
 * Move serial enabling into board file (qcom-msm8960-cdp.dts)
 * Cleanup cpu node to match binding spec, enable-method and compatible
   should be per cpu, not part of the container
 * Drop interrupts property from l2-cache node as its not part of the
   binding spec
 
 Signed-off-by: Kumar Gala ga...@codeaurora.org
 ---
  arch/arm/boot/dts/qcom-msm8960-cdp.dts |   6 ++
  arch/arm/boot/dts/qcom-msm8960.dtsi| 165 
 +
  2 files changed, 93 insertions(+), 78 deletions(-)
 
 diff --git a/arch/arm/boot/dts/qcom-msm8960-cdp.dts 
 b/arch/arm/boot/dts/qcom-msm8960-cdp.dts
 index a58fb88..8e77ed7 100644
 --- a/arch/arm/boot/dts/qcom-msm8960-cdp.dts
 +++ b/arch/arm/boot/dts/qcom-msm8960-cdp.dts
 @@ -3,4 +3,10 @@
  / {
   model = Qualcomm MSM8960 CDP;
   compatible = qcom,msm8960-cdp, qcom,msm8960;
 +
 + soc {
 + serial@1644 {
 + status = ok;
 + };
 + };
  };

Is now the time put these serial nodes under a GSBI parent node?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH] ARM: dts: qcom: Update msm8960 device trees

2014-05-28 Thread Kumar Gala

On May 28, 2014, at 3:09 PM, Josh Cartwright jo...@codeaurora.org wrote:

 On Wed, May 28, 2014 at 01:27:23PM -0500, Kumar Gala wrote:
 * Move SoC peripherals into an SoC container node
 * Move serial enabling into board file (qcom-msm8960-cdp.dts)
 * Cleanup cpu node to match binding spec, enable-method and compatible
  should be per cpu, not part of the container
 * Drop interrupts property from l2-cache node as its not part of the
  binding spec
 
 Signed-off-by: Kumar Gala ga...@codeaurora.org
 ---
 arch/arm/boot/dts/qcom-msm8960-cdp.dts |   6 ++
 arch/arm/boot/dts/qcom-msm8960.dtsi| 165 
 +
 2 files changed, 93 insertions(+), 78 deletions(-)
 
 diff --git a/arch/arm/boot/dts/qcom-msm8960-cdp.dts 
 b/arch/arm/boot/dts/qcom-msm8960-cdp.dts
 index a58fb88..8e77ed7 100644
 --- a/arch/arm/boot/dts/qcom-msm8960-cdp.dts
 +++ b/arch/arm/boot/dts/qcom-msm8960-cdp.dts
 @@ -3,4 +3,10 @@
 / {
  model = Qualcomm MSM8960 CDP;
  compatible = qcom,msm8960-cdp, qcom,msm8960;
 +
 +soc {
 +serial@1644 {
 +status = ok;
 +};
 +};
 };
 
 Is now the time put these serial nodes under a GSBI parent node?

Yeah, I’ll make the change to the 8960  8660 dts

- k

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by 
The Linux Foundation

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/