Add initial device tree support for Qualcomm APQ8016 SBC Evaluation board.
This board is also referred to as the DragonBoard 410c.
Signed-off-by: Kumar Gala
---
arch/arm64/boot/dts/qcom/Makefile | 2 +-
arch/arm64/boot/dts/qcom/apq8016-sbc.dts | 22 +
arch/arm64
Add initial device tree support for Qualcomm APQ8016 SBC Evaluation board.
This board is also referred to as the DragonBoard 410c.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
arch/arm64/boot/dts/qcom/Makefile | 2 +-
arch/arm64/boot/dts/qcom/apq8016-sbc.dts | 22
On Mar 17, 2015, at 1:58 PM, Madalin Bucur wrote:
> This introduces the Freescale Data Path Acceleration Architecture
> (DPAA) Ethernet driver (dpaa_eth) that builds upon the DPAA QMan,
> BMan, PAMU and FMan drivers to deliver Ethernet connectivity on
> the Freescale DPAA QorIQ platforms.
>
>
On Mar 17, 2015, at 1:58 PM, Madalin Bucur madalin.bu...@freescale.com wrote:
This introduces the Freescale Data Path Acceleration Architecture
(DPAA) Ethernet driver (dpaa_eth) that builds upon the DPAA QMan,
BMan, PAMU and FMan drivers to deliver Ethernet connectivity on
the Freescale DPAA
On Mar 17, 2015, at 4:24 AM, Stanimir Varbanov
wrote:
> On 03/13/2015 06:06 PM, Kumar Gala wrote:
>> Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
>> evaluation board. At the current time we only boot up a single processor.
>>
>> Signed-off-b
On Mar 17, 2015, at 4:24 AM, Stanimir Varbanov stanimir.varba...@linaro.org
wrote:
On 03/13/2015 06:06 PM, Kumar Gala wrote:
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/galak/linux-qcom.git
tags/qcom-defconfig-for-4.1
for you to fetch changes up to
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/galak/linux-qcom.git
tags/qcom-arm64-for-4.1
for you to fetch changes up to
support for ADM CRCI muxing
Kumar Gala (4):
ARM: qcom: Merge scm and scm boot code together
ARM: qcom: Cleanup scm interface to only export what is needed
ARM: qcom: Prep scm code for move to drivers/firmware
firmware: qcom: scm: Move the scm driver to drivers/firmware
Lina
On Mar 16, 2015, at 9:20 AM, Gabriel FERNANDEZ wrote:
> ST sti SoCs PCIe IPs are built around DesignWare IP Core.
> But in these SoCs PCIe IP doesn't support IO.
>
> This patch adds the possibility to disable it through
> a DT property, by creating an empty IO window and by
> removing
On Mar 16, 2015, at 9:20 AM, Gabriel FERNANDEZ gabriel.fernan...@st.com wrote:
ST sti SoCs PCIe IPs are built around DesignWare IP Core.
But in these SoCs PCIe IP doesn't support IO.
This patch adds the possibility to disable it through
a DT property, by creating an empty IO window and by
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/galak/linux-qcom.git
tags/qcom-arm64-for-4.1
for you to fetch changes up to
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/galak/linux-qcom.git
tags/qcom-defconfig-for-4.1
for you to fetch changes up to
support for ADM CRCI muxing
Kumar Gala (4):
ARM: qcom: Merge scm and scm boot code together
ARM: qcom: Cleanup scm interface to only export what is needed
ARM: qcom: Prep scm code for move to drivers/firmware
firmware: qcom: scm: Move the scm driver to drivers/firmware
Lina
On Mar 13, 2015, at 11:25 AM, Mark Rutland wrote:
> On Fri, Mar 13, 2015 at 03:50:42PM +0000, Kumar Gala wrote:
>>
>> On Mar 13, 2015, at 5:52 AM, Mark Rutland wrote:
>>
>>>> +/ {
>>>> + chosen {
>>>> + stdout-path
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala
---
v5:
* killed use of skeleton, moved to addr/size cells both being 2
* Added serial alias in prep of being able to spec
On Mar 13, 2015, at 5:52 AM, Mark Rutland wrote:
>> +/ {
>> +chosen {
>> +stdout-path = _uart2;
>> +};
>
> It would be good if we had the configuration too (see
> Documentation/devicetree/bindings/chosen.txt), as that avoids any
> reliance on kernel defaults.
>
> You can
On Mar 13, 2015, at 5:52 AM, Mark Rutland mark.rutl...@arm.com wrote:
+/ {
+chosen {
+stdout-path = blsp1_uart2;
+};
It would be good if we had the configuration too (see
Documentation/devicetree/bindings/chosen.txt), as that avoids any
reliance on kernel defaults.
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
v5:
* killed use of skeleton, moved to addr/size cells both being 2
* Added serial alias in prep
On Mar 13, 2015, at 11:25 AM, Mark Rutland mark.rutl...@arm.com wrote:
On Fri, Mar 13, 2015 at 03:50:42PM +, Kumar Gala wrote:
On Mar 13, 2015, at 5:52 AM, Mark Rutland mark.rutl...@arm.com wrote:
+/ {
+ chosen {
+ stdout-path = blsp1_uart2;
+ };
It would be good
On Mar 12, 2015, at 1:25 PM, Mark Rutland wrote:
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ CPU0: cpu@0 {
+ device_type = "cpu";
+ compatible = "arm,cortex-a53", "arm,armv8";
+
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala
---
v4:
* Added chosen node so we dont need to spec everything for earlycon
* fixed up timer node to armv8, dropped clock
On Mar 12, 2015, at 12:05 PM, Mark Rutland wrote:
> Hi Kumar,
>
>> +/ {
>> +model = "Qualcomm Technologies, Inc. MSM 8916 MTP";
>> +compatible = "qcom,msm8916-mtp", "qcom,msm8916-mtp-smb1360",
>> +"qcom,msm8916", "qcom,mtp";
>> +};
>
> No /chosen/stdout-path?
Nope
On Mar 11, 2015, at 12:04 AM, Igal.Liberman wrote:
> From: Igal Liberman
commit message?
>
> Signed-off-by: Igal Liberman
> ---
> drivers/soc/fsl/fman/Kconfig | 10 +
> drivers/soc/fsl/fman/Makefile |2 +
> drivers/soc/fsl/fman/port/Makefile|3 +
>
On Mar 11, 2015, at 12:03 AM, Igal.Liberman wrote:
> From: Igal Liberman
>
> The Freescale Data Path Acceleration Architecture (DPAA) is a set of
> hardware components on specific QorIQ multicore processors. This
> architecture provides the infrastructure to support simplified
> sharing of
On Mar 11, 2015, at 12:07 AM, Igal.Liberman wrote:
> From: Igal Liberman
>
> Add Frame Manager Multi-User RAM support.
>
> Signed-off-by: Igal Liberman
> ---
> drivers/soc/fsl/fman/Kconfig|1 +
> drivers/soc/fsl/fman/Makefile |5 +-
>
On Mar 11, 2015, at 12:07 AM, Igal.Liberman igal.liber...@freescale.com wrote:
From: Igal Liberman igal.liber...@freescale.com
Add Frame Manager Multi-User RAM support.
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/Kconfig|1 +
On Mar 11, 2015, at 12:03 AM, Igal.Liberman igal.liber...@freescale.com wrote:
From: Igal Liberman igal.liber...@freescale.com
The Freescale Data Path Acceleration Architecture (DPAA) is a set of
hardware components on specific QorIQ multicore processors. This
architecture provides the
On Mar 12, 2015, at 12:05 PM, Mark Rutland mark.rutl...@arm.com wrote:
Hi Kumar,
+/ {
+model = Qualcomm Technologies, Inc. MSM 8916 MTP;
+compatible = qcom,msm8916-mtp, qcom,msm8916-mtp-smb1360,
+qcom,msm8916, qcom,mtp;
+};
No /chosen/stdout-path?
Nope ;).
On Mar 11, 2015, at 12:04 AM, Igal.Liberman igal.liber...@freescale.com wrote:
From: Igal Liberman igal.liber...@freescale.com
commit message?
Signed-off-by: Igal Liberman igal.liber...@freescale.com
---
drivers/soc/fsl/fman/Kconfig | 10 +
drivers/soc/fsl/fman/Makefile
On Mar 12, 2015, at 1:25 PM, Mark Rutland mark.rutl...@arm.com wrote:
+ cpus {
+ #address-cells = 1;
+ #size-cells = 0;
+
+ CPU0: cpu@0 {
+ device_type = cpu;
+ compatible = arm,cortex-a53, arm,armv8;
+ reg =
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
v4:
* Added chosen node so we dont need to spec everything for earlycon
* fixed up timer node to armv8
Add qcom,msm-id and qcom,board-id to allow bootloader to identify which
device tree to boot on the MTP8916 boards.
Signed-off-by: Kumar Gala
---
arch/arm64/boot/dts/qcom/msm8916-mtp.dts | 3 +++
arch/arm64/boot/dts/qcom/msm8916.dtsi| 5 +
2 files changed, 8 insertions(+)
diff --git
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala
---
v3:
* Removed qcom,msm-id and qcom,board-id
* Added top level compat for "qcom,msm8916-mtp-smb1360"
v2:
The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.
Cc:
Signed-off-by: Kumar Gala
---
Documentation/devicetree/bindings/arm/msm/ids.txt | 65
From: Abhimanyu Kapur
Add support for Qualcomm MSM8916 SoC in arm64 Kconfig and defconfig.
Enable MSM8916 clock, pin control, and MSM serial driver utilized by
MSM8916 and Qualcomm SoCs in general.
Signed-off-by: Kumar Gala
Signed-off-by: Abhimanyu Kapur
---
v3:
* Dropped ARCH_REQUIRE_GPIOLIB
On Mar 11, 2015, at 3:20 PM, Arnd Bergmann wrote:
> On Wednesday 11 March 2015 08:33:04 Bjorn Andersson wrote:
>>
>> But are these values actually used by the boot loader?
>>
>> As far as I could see in 8974 the dtbTool provided by Qualcomm
>> extracts the values from the list of dtbs and use
On Mar 11, 2015, at 10:33 AM, Bjorn Andersson wrote:
> On Tue, Mar 10, 2015 at 12:57 PM, Kumar Gala wrote:
>>
>> On Mar 10, 2015, at 2:52 PM, Arnd Bergmann wrote:
>>
>>> On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
>>>>>>>
On Mar 11, 2015, at 10:33 AM, Bjorn Andersson bj...@kryo.se wrote:
On Tue, Mar 10, 2015 at 12:57 PM, Kumar Gala ga...@codeaurora.org wrote:
On Mar 10, 2015, at 2:52 PM, Arnd Bergmann a...@arndb.de wrote:
On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
The top level qcom,msm-id
The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.
Cc: devicet...@vger.kernel.org
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
Documentation/devicetree/bindings/arm
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
v3:
* Removed qcom,msm-id and qcom,board-id
* Added top level compat for qcom,msm8916-mtp-smb1360
v2
Add qcom,msm-id and qcom,board-id to allow bootloader to identify which
device tree to boot on the MTP8916 boards.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
arch/arm64/boot/dts/qcom/msm8916-mtp.dts | 3 +++
arch/arm64/boot/dts/qcom/msm8916.dtsi| 5 +
2 files changed, 8
From: Abhimanyu Kapur abhim...@codeaurora.org
Add support for Qualcomm MSM8916 SoC in arm64 Kconfig and defconfig.
Enable MSM8916 clock, pin control, and MSM serial driver utilized by
MSM8916 and Qualcomm SoCs in general.
Signed-off-by: Kumar Gala ga...@codeaurora.org
Signed-off-by: Abhimanyu
On Mar 11, 2015, at 3:20 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 11 March 2015 08:33:04 Bjorn Andersson wrote:
But are these values actually used by the boot loader?
As far as I could see in 8974 the dtbTool provided by Qualcomm
extracts the values from the list of dtbs and
On Mar 10, 2015, at 2:52 PM, Arnd Bergmann wrote:
> On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
>>>>>>>>>>> The top level qcom,msm-id and qcom,board-id are utilized by
>>>>>>>>>>> bootloaders
>>
>>>>>>>>> The top level qcom,msm-id and qcom,board-id are utilized by
>>>>>>>>> bootloaders
>>>>>>>>>> on Qualcomm MSM platforms to determine which device tree should be
>>>>>>&g
On Mar 9, 2015, at 7:11 AM, Arnd Bergmann wrote:
> On Friday 06 March 2015 14:37:52 Kumar Gala wrote:
>> On Mar 6, 2015, at 1:15 PM, Olof Johansson wrote:
>>
>>> On Fri, Mar 6, 2015 at 8:08 AM, Kumar Gala wrote:
>>>>
>>>> On Mar 5, 2015, at 7:
The top level qcom,msm-id and qcom,board-id are utilized by
bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.
Cc: devicet...@vger.kernel.org
Signed-off-by: Kumar Gala ga...@codeaurora.org
Is this the special magic
On Mar 9, 2015, at 7:11 AM, Arnd Bergmann a...@arndb.de wrote:
On Friday 06 March 2015 14:37:52 Kumar Gala wrote:
On Mar 6, 2015, at 1:15 PM, Olof Johansson o...@lixom.net wrote:
On Fri, Mar 6, 2015 at 8:08 AM, Kumar Gala ga...@codeaurora.org wrote:
On Mar 5, 2015, at 7:59 PM, Olof
On Mar 10, 2015, at 2:52 PM, Arnd Bergmann a...@arndb.de wrote:
On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
The top level qcom,msm-id and qcom,board-id are utilized by
bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel
On Mar 6, 2015, at 4:03 PM, Kenneth Westfield wrote:
> On Fri, Mar 06, 2015 at 10:07:01AM -0600, Kumar Gala wrote:
>> On Mar 5, 2015, at 7:51 PM, Kenneth Westfield
>> wrote:
>>> On Thu, Mar 05, 2015 at 12:52:30PM -0600, Kumar Gala wrote:
>>>> On Mar 3,
On Mar 6, 2015, at 1:15 PM, Olof Johansson wrote:
> On Fri, Mar 6, 2015 at 8:08 AM, Kumar Gala wrote:
>>
>> On Mar 5, 2015, at 7:59 PM, Olof Johansson wrote:
>>
>>> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala wrote:
>>>>
>>&g
On Mar 4, 2015, at 11:45 PM, Emil Medve wrote:
> From: Igal Liberman
>
> The Freescale Data Path Acceleration Architecture (DPAA) is a set of
> hardware components on specific QorIQ P and T series multicore processors.
> This architecture provides the infrastructure to support simplified
>
On Mar 5, 2015, at 7:51 PM, Kenneth Westfield wrote:
> On Thu, Mar 05, 2015 at 12:52:30PM -0600, Kumar Gala wrote:
>>
>> On Mar 3, 2015, at 6:21 PM, Kenneth Westfield
>> wrote:
>>
>>> +++ b/Documentation/devicetree/bindings/sound/qcom,lpass-cpu.txt
On Mar 5, 2015, at 7:59 PM, Olof Johansson wrote:
> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala wrote:
>>
>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman wrote:
>>
>>> Kumar Gala writes:
>>>
>>>> The top level qcom,msm-id and qcom,board-
On Mar 4, 2015, at 11:45 PM, Emil Medve emilian.me...@freescale.com wrote:
From: Igal Liberman igal.liber...@freescale.com
The Freescale Data Path Acceleration Architecture (DPAA) is a set of
hardware components on specific QorIQ P and T series multicore processors.
This architecture
On Mar 5, 2015, at 7:59 PM, Olof Johansson o...@lixom.net wrote:
On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala ga...@codeaurora.org wrote:
On Mar 5, 2015, at 1:42 PM, Kevin Hilman khil...@kernel.org wrote:
Kumar Gala ga...@codeaurora.org writes:
The top level qcom,msm-id and qcom,board
On Mar 5, 2015, at 7:51 PM, Kenneth Westfield kwest...@codeaurora.org wrote:
On Thu, Mar 05, 2015 at 12:52:30PM -0600, Kumar Gala wrote:
On Mar 3, 2015, at 6:21 PM, Kenneth Westfield kwest...@codeaurora.org
wrote:
+++ b/Documentation/devicetree/bindings/sound/qcom,lpass-cpu.txt
@@ -0,0
On Mar 6, 2015, at 1:15 PM, Olof Johansson o...@lixom.net wrote:
On Fri, Mar 6, 2015 at 8:08 AM, Kumar Gala ga...@codeaurora.org wrote:
On Mar 5, 2015, at 7:59 PM, Olof Johansson o...@lixom.net wrote:
On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala ga...@codeaurora.org wrote:
On Mar 5
On Mar 6, 2015, at 4:03 PM, Kenneth Westfield kwest...@codeaurora.org wrote:
On Fri, Mar 06, 2015 at 10:07:01AM -0600, Kumar Gala wrote:
On Mar 5, 2015, at 7:51 PM, Kenneth Westfield kwest...@codeaurora.org
wrote:
On Thu, Mar 05, 2015 at 12:52:30PM -0600, Kumar Gala wrote:
On Mar 3, 2015
On Mar 5, 2015, at 1:42 PM, Kevin Hilman wrote:
> Kumar Gala writes:
>
>> The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
>> on Qualcomm MSM platforms to determine which device tree should be
>> utilized and passed to the kernel.
>>
&
On Mar 3, 2015, at 6:21 PM, Kenneth Westfield wrote:
> From: Kenneth Westfield
>
> Add documentation to the sound directory of the
> device-tree bindings for the QTi LPASS CPU DAI
> device.
>
> Signed-off-by: Kenneth Westfield
> Acked-by: Banajit Goswami
> ---
>
On Mar 4, 2015, at 4:33 PM, Stephen Boyd wrote:
> On 03/04/15 13:13, Kumar Gala wrote:
>> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
>> index 1b8e973..4c8b119 100644
>> --- a/arch/arm64/Kconfig
>> +++ b/arch/arm64/Kconfig
>> @@ -177,6 +177,15 @@
On Mar 5, 2015, at 1:42 PM, Kevin Hilman khil...@kernel.org wrote:
Kumar Gala ga...@codeaurora.org writes:
The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.
Cc
On Mar 3, 2015, at 6:21 PM, Kenneth Westfield kwest...@codeaurora.org wrote:
From: Kenneth Westfield kwest...@codeaurora.org
Add documentation to the sound directory of the
device-tree bindings for the QTi LPASS CPU DAI
device.
Signed-off-by: Kenneth Westfield kwest...@codeaurora.org
On Mar 4, 2015, at 4:33 PM, Stephen Boyd sb...@codeaurora.org wrote:
On 03/04/15 13:13, Kumar Gala wrote:
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 1b8e973..4c8b119 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -177,6 +177,15 @@ config ARCH_MEDIATEK
On Mar 4, 2015, at 3:19 PM, Arnd Bergmann wrote:
> On Wednesday 04 March 2015 15:13:20 Kumar Gala wrote:
>> The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
>> on Qualcomm MSM platforms to determine which device tree should be
>> utilized and
The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.
Cc:
Signed-off-by: Kumar Gala
---
Documentation/devicetree/bindings/arm/msm/ids.txt | 65
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala
---
v2:
* Updated to dropping CONFIG_ARCH_QCOM_MSM8916
* Updated to use qcom-ids.h
arch/arm64/boot/dts/Makefile
From: Abhimanyu Kapur
Add support for Qualcomm MSM8916 SoC in arm64 Kconfig and defconfig.
Enable MSM8916 clock, pin control, and MSM serial driver utilized by
MSM8916 and Qualcomm SoCs in general.
Signed-off-by: Kumar Gala
Signed-off-by: Abhimanyu Kapur
---
v2:
* Dropped
Document the Qualcomm MSM GICs implementation as compatible with the
ARM GIC standard.
Signed-off-by: Kumar Gala
---
Documentation/devicetree/bindings/arm/gic.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/gic.txt
b/Documentation/devicetree
Document the Qualcomm MSM GICs implementation as compatible with the
ARM GIC standard.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
Documentation/devicetree/bindings/arm/gic.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/gic.txt
b
From: Abhimanyu Kapur abhim...@codeaurora.org
Add support for Qualcomm MSM8916 SoC in arm64 Kconfig and defconfig.
Enable MSM8916 clock, pin control, and MSM serial driver utilized by
MSM8916 and Qualcomm SoCs in general.
Signed-off-by: Kumar Gala ga...@codeaurora.org
Signed-off-by: Abhimanyu
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
v2:
* Updated to dropping CONFIG_ARCH_QCOM_MSM8916
* Updated to use qcom-ids.h
arch/arm64/boot/dts
The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.
Cc: devicet...@vger.kernel.org
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
Documentation/devicetree/bindings/arm
On Mar 4, 2015, at 3:19 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 04 March 2015 15:13:20 Kumar Gala wrote:
The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala
---
arch/arm64/boot/dts/Makefile | 1 +
arch/arm64/boot/dts/qcom/Makefile | 5 +
arch/arm64/boot/dts
From: Abhimanyu Kapur
Add support for Qualcomm MSM8916 SoC in arm64 Kconfig and defconfig.
Enable MSM serial driver utilized by MSM8916 and Qualcomm SoCs in
general.
Signed-off-by: Kumar Gala
Signed-off-by: Abhimanyu Kapur
---
arch/arm64/Kconfig | 18 ++
arch/arm64
On Feb 27, 2015, at 12:58 PM, Stephen Boyd wrote:
> On 02/26/15 13:59, Kumar Gala wrote:
>> Architectural changes in the ARM Linux kernel tree mandate the eventual
>> removal of the mach-* directories. Move the scm driver to
>> drivers/firmware and the scm header to inc
Architectural changes in the ARM Linux kernel tree mandate the eventual
removal of the mach-* directories. Move the scm driver to
drivers/firmware and the scm header to include/linux to support that
removal.
Signed-off-by: Kumar Gala
---
v2:
* Moved to -M style diff output
* Added in missing
Architectural changes in the ARM Linux kernel tree mandate the eventual
removal of the mach-* directories. Move the scm driver to
drivers/firmware and the scm header to include/linux to support that
removal.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
v2:
* Moved to -M style diff output
On Feb 27, 2015, at 12:58 PM, Stephen Boyd sb...@codeaurora.org wrote:
On 02/26/15 13:59, Kumar Gala wrote:
Architectural changes in the ARM Linux kernel tree mandate the eventual
removal of the mach-* directories. Move the scm driver to
drivers/firmware and the scm header to include/linux
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
arch/arm64/boot/dts/Makefile | 1 +
arch/arm64/boot/dts/qcom/Makefile | 5
From: Abhimanyu Kapur abhim...@codeaurora.org
Add support for Qualcomm MSM8916 SoC in arm64 Kconfig and defconfig.
Enable MSM serial driver utilized by MSM8916 and Qualcomm SoCs in
general.
Signed-off-by: Kumar Gala ga...@codeaurora.org
Signed-off-by: Abhimanyu Kapur abhim...@codeaurora.org
Now that scom boot interface is merged we don't need export scm_call
anymore. Some other minor cleanups related to boot interface to only
export what is needed by scm_set_boot_addr().
Signed-off-by: Kumar Gala
---
arch/arm/mach-qcom/scm.c | 7 ---
arch/arm/mach-qcom/scm.h | 7 ---
2
Architectural changes in the ARM Linux kernel tree mandate the eventual
removal of the mach-* directories. Move the scm driver to
drivers/firmware and the scm header to include/linux to support that
removal.
Signed-off-by: Kumar Gala
---
MAINTAINERS | 1 +
arch/arm/mach-qcom
Add qcom prefix to functions, etc to create a unique name space for the
scm code as it gets ready to move out of qcom specific mach dir.
Signed-off-by: Kumar Gala
---
arch/arm/mach-qcom/platsmp.c | 8 +--
arch/arm/mach-qcom/scm.c | 148 +--
arch/arm
Put all scm related code into a single file as a first step in cleaning
up the scm interface to just expose functional behavior insteam of making
direct scm calls.
Signed-off-by: Kumar Gala
---
arch/arm/mach-qcom/Makefile | 2 +-
arch/arm/mach-qcom/platsmp.c | 2 +-
arch/arm/mach-qcom/scm
On Feb 23, 2015, at 1:53 AM, Srinivas Kandagatla
wrote:
> Hi Kumar,
> Now that the rpm header file dependency is resolved, Could you
> queue these dt patches for rc2.
>
>
> Thanks,
> srini
>
> Nicolas Dechesne (3):
> ARM: DT: apq8064: add pci support in CM QS600
> ARM: DT: apq8064: Add
On Feb 23, 2015, at 1:55 AM, Srinivas Kandagatla
wrote:
> This patch adds device tree nodes to support two usb hosts on APQ8064
> SOC.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 40 +
>
On Feb 23, 2015, at 1:55 AM, Srinivas Kandagatla
wrote:
> This patch adds USB OTG support on USB1 of APQ8064 SOC.
> Tested on IFC6410 with ethernet gadget.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 22
>
On Feb 23, 2015, at 1:54 AM, Srinivas Kandagatla
wrote:
> This patch adds rpm node to apq8064 dt as rpm would be used by other
> devices for regulator support. Also adds all the regulators in the rpm.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> arch/arm/boot/dts/qcom-apq8064.dtsi | 241
On Feb 23, 2015, at 1:54 AM, Srinivas Kandagatla
srinivas.kandaga...@linaro.org wrote:
This patch adds rpm node to apq8064 dt as rpm would be used by other
devices for regulator support. Also adds all the regulators in the rpm.
Signed-off-by: Srinivas Kandagatla
On Feb 23, 2015, at 1:55 AM, Srinivas Kandagatla
srinivas.kandaga...@linaro.org wrote:
This patch adds device tree nodes to support two usb hosts on APQ8064
SOC.
Signed-off-by: Srinivas Kandagatla srinivas.kandaga...@linaro.org
---
arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 40
On Feb 23, 2015, at 1:53 AM, Srinivas Kandagatla
srinivas.kandaga...@linaro.org wrote:
Hi Kumar,
Now that the rpm header file dependency is resolved, Could you
queue these dt patches for rc2.
Thanks,
srini
Nicolas Dechesne (3):
ARM: DT: apq8064: add pci support in CM QS600
ARM:
On Feb 23, 2015, at 1:55 AM, Srinivas Kandagatla
srinivas.kandaga...@linaro.org wrote:
This patch adds USB OTG support on USB1 of APQ8064 SOC.
Tested on IFC6410 with ethernet gadget.
Signed-off-by: Srinivas Kandagatla srinivas.kandaga...@linaro.org
---
Architectural changes in the ARM Linux kernel tree mandate the eventual
removal of the mach-* directories. Move the scm driver to
drivers/firmware and the scm header to include/linux to support that
removal.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
MAINTAINERS | 1
Now that scom boot interface is merged we don't need export scm_call
anymore. Some other minor cleanups related to boot interface to only
export what is needed by scm_set_boot_addr().
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
arch/arm/mach-qcom/scm.c | 7 ---
arch/arm/mach-qcom
Add qcom prefix to functions, etc to create a unique name space for the
scm code as it gets ready to move out of qcom specific mach dir.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
arch/arm/mach-qcom/platsmp.c | 8 +--
arch/arm/mach-qcom/scm.c | 148
Put all scm related code into a single file as a first step in cleaning
up the scm interface to just expose functional behavior insteam of making
direct scm calls.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
arch/arm/mach-qcom/Makefile | 2 +-
arch/arm/mach-qcom/platsmp.c | 2
101 - 200 of 1752 matches
Mail list logo