On Oct 27, 2013, at 4:24 PM, Sebastian Reichel wrote:
> This patch adds device tree support to the Nokia N900 audio driver.
> It also removes GPIO defines and gets them from platform data /
> device tree, since some GPIO numbers may be different with DT boot.
>
> The binding also changes a
On Oct 22, 2013, at 7:47 AM, Sebastian Reichel wrote:
> Add device tree support for twl4030 keypad driver and update the
> Documentation with twl4030 keypad device tree binding information.
>
> Tested on Nokia N900.
>
> Signed-off-by: Sebastian Reichel
> ---
>
On Oct 27, 2013, at 11:14 AM, Sebastian Reichel wrote:
> Add device tree support for the spi variant of wl1251
> and document the binding.
>
> Signed-off-by: Sebastian Reichel
> ---
> .../devicetree/bindings/net/wireless/ti,wl1251.txt | 36 ++
>
On Oct 26, 2013, at 6:31 AM, Sebastian Reichel wrote:
> On Sat, Oct 26, 2013 at 01:37:57AM -0500, Kumar Gala wrote:
>>
>> On Oct 25, 2013, at 5:18 PM, Sebastian Reichel wrote:
>>
>>> On Fri, Oct 25, 2013 at 04:41:20PM -0500, Kumar Gala wrote:
>>>> On O
On Oct 26, 2013, at 6:31 AM, Sebastian Reichel wrote:
On Sat, Oct 26, 2013 at 01:37:57AM -0500, Kumar Gala wrote:
On Oct 25, 2013, at 5:18 PM, Sebastian Reichel wrote:
On Fri, Oct 25, 2013 at 04:41:20PM -0500, Kumar Gala wrote:
On Oct 24, 2013, at 9:48 AM, Sebastian Reichel wrote
On Oct 27, 2013, at 11:14 AM, Sebastian Reichel wrote:
Add device tree support for the spi variant of wl1251
and document the binding.
Signed-off-by: Sebastian Reichel s...@debian.org
---
.../devicetree/bindings/net/wireless/ti,wl1251.txt | 36 ++
On Oct 22, 2013, at 7:47 AM, Sebastian Reichel wrote:
Add device tree support for twl4030 keypad driver and update the
Documentation with twl4030 keypad device tree binding information.
Tested on Nokia N900.
Signed-off-by: Sebastian Reichel s...@debian.org
---
On Oct 27, 2013, at 4:24 PM, Sebastian Reichel wrote:
This patch adds device tree support to the Nokia N900 audio driver.
It also removes GPIO defines and gets them from platform data /
device tree, since some GPIO numbers may be different with DT boot.
The binding also changes a helper
deletions(-)
Acked-by: Kumar Gala ga...@codeaurora.org
[ I think the patch should be split up so we aren't touching versatile dts as
part of it ]
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by
The Linux
On Oct 27, 2013, at 10:16 PM, Mark Rutland wrote:
On Sun, Oct 27, 2013 at 08:24:08PM +, Rob Herring wrote:
On Sun, Oct 27, 2013 at 8:46 AM, Grant Likely grant.lik...@linaro.org
wrote:
On Tue, 15 Oct 2013 21:39:23 +0100, Grant Likely grant.lik...@linaro.org
wrote:
The standard
On Oct 28, 2013, at 5:28 AM, Alexandre Courbot wrote:
Trusted Foundations is a TrustZone-based secure monitor for ARM that
can be invoked using the same SMC-based API on all supported
platforms. This patch adds initial basic support for Trusted
Foundations using the ARM firmware API. Current
On Oct 28, 2013, at 4:05 AM, Xiubo Li wrote:
The RFC patch only added See ../clock/clock-bindings.txt for details of
the property values.
This adds the Document for Freescale FTM PWM driver under
Documentation/devicetree/bindings/pwm/.
Signed-off-by: Xiubo Li li.xi...@freescale.com
On Oct 14, 2013, at 7:46 AM, Maxime COQUELIN wrote:
This patch adds support to SSC (Synchronous Serial Controller)
I2C driver. This IP also supports SPI protocol, but this is not
the aim of this driver.
This IP is embedded in all ST SoCs for Set-top box platorms, and
supports I2C Standard
On Oct 28, 2013, at 12:15 PM, Grazvydas Ignotas wrote:
On Mon, Oct 28, 2013 at 8:37 AM, Kumar Gala ga...@codeaurora.org wrote:
On Oct 27, 2013, at 11:14 AM, Sebastian Reichel wrote:
+++ b/Documentation/devicetree/bindings/net/wireless/ti,wl1251.txt
@@ -0,0 +1,36 @@
+* Texas Instruments
On Oct 26, 2013, at 7:45 AM, Matt Porter wrote:
> On Sat, Oct 26, 2013 at 01:47:40AM -0500, Kumar Gala wrote:
>>
>> On Oct 26, 2013, at 1:46 AM, Kumar Gala wrote:
>>
>>>
>>> On Oct 25, 2013, at 7:00 PM, Wendy Ng wrote:
>>>
>>>>
On Oct 26, 2013, at 7:45 AM, Matt Porter wrote:
On Sat, Oct 26, 2013 at 01:47:40AM -0500, Kumar Gala wrote:
On Oct 26, 2013, at 1:46 AM, Kumar Gala wrote:
On Oct 25, 2013, at 7:00 PM, Wendy Ng wrote:
This adds the support for Temperature Monitor (TMON) driver for
Broadcom bcm281xx
On Oct 25, 2013, at 7:00 PM, Wendy Ng wrote:
>
> + tmon: tmon@34008000 {
> + compatible = "brcm,bcm11351-tmon", "brcm,kona-tmon";
> + reg = <0x34008000 0x0024>;
> + clocks = <_1m_clk>;
> + interrupts = ;
> + #thermal-sensor-cells =
On Oct 26, 2013, at 1:46 AM, Kumar Gala wrote:
>
> On Oct 25, 2013, at 7:00 PM, Wendy Ng wrote:
>
>> This adds the support for Temperature Monitor (TMON) driver for
>> Broadcom bcm281xx SoCs. This driver plugs into the Thermal Framework.
>>
>> Note that thi
+
> +
> +Example:
> + tmon@34008000 {
> + compatible = "brcm,bcm11351-tmon", "brcm,kona-tmon";
> + reg = <0x34008000 0x0024>;
> + clocks = <_1m_clk>;
> + interrupts = ;
> + status = "
On Oct 25, 2013, at 5:18 PM, Sebastian Reichel wrote:
> On Fri, Oct 25, 2013 at 04:41:20PM -0500, Kumar Gala wrote:
>> On Oct 24, 2013, at 9:48 AM, Sebastian Reichel wrote:
>>> +- interrupt: should be one of the following
>>> + - <8>: For controllers co
On Oct 25, 2013, at 5:18 PM, Sebastian Reichel wrote:
On Fri, Oct 25, 2013 at 04:41:20PM -0500, Kumar Gala wrote:
On Oct 24, 2013, at 9:48 AM, Sebastian Reichel wrote:
+- interrupt: should be one of the following
+ - 8: For controllers compatible with twl4030
Just checking
-by: Kumar Gala ga...@codeaurora.org
- 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
On Oct 26, 2013, at 1:46 AM, Kumar Gala wrote:
On Oct 25, 2013, at 7:00 PM, Wendy Ng wrote:
This adds the support for Temperature Monitor (TMON) driver for
Broadcom bcm281xx SoCs. This driver plugs into the Thermal Framework.
Note that this version of the TMON driver does support
On Oct 25, 2013, at 7:00 PM, Wendy Ng wrote:
+ tmon: tmon@34008000 {
+ compatible = brcm,bcm11351-tmon, brcm,kona-tmon;
+ reg = 0x34008000 0x0024;
+ clocks = tmon_1m_clk;
+ interrupts = GIC_SPI 183 IRQ_TYPE_LEVEL_HIGH;
+
+ twl_pwrbutton: pwrbutton {
> + compatible = "ti,twl4030-pwrbutton";
> + interrupts = <8>;
> + };
> +};
Otherwise Ack on binding:
Acked-by: Kumar Gala
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center,
On Oct 25, 2013, at 9:15 AM, Kamil Debski wrote:
> Add a new driver for the Exynos USB PHY. The new driver uses the generic
> PHY framework. The driver includes support for the Exynos 4x10 and 4x12
> SoC families.
>
> Signed-off-by: Kamil Debski
> Signed-off-by: Kyungmin Park
> ---
>
On Oct 25, 2013, at 3:24 PM, Andy Gross wrote:
> Add device tree probe support for the MSM BAM DMA driver.
>
The description here isn't correct, its the binding not probe ;).
> Signed-off-by: Andy Gross
> ---
> .../devicetree/bindings/dma/msm_bam_dma.txt| 49
>
On Oct 25, 2013, at 3:23 AM, Sebastian Reichel wrote:
> On Thu, Oct 24, 2013 at 10:32:36PM -0500, Kumar Gala wrote:
>> On Oct 24, 2013, at 9:27 AM, Sebastian Reichel wrote:
>>> Add Device Tree support for the TSL2563 driver
>>> and document the binding.
>>>
On Oct 25, 2013, at 3:23 AM, Sebastian Reichel wrote:
On Thu, Oct 24, 2013 at 10:32:36PM -0500, Kumar Gala wrote:
On Oct 24, 2013, at 9:27 AM, Sebastian Reichel wrote:
Add Device Tree support for the TSL2563 driver
and document the binding.
Signed-off-by: Sebastian Reichel s...@debian.org
On Oct 25, 2013, at 3:24 PM, Andy Gross wrote:
Add device tree probe support for the MSM BAM DMA driver.
The description here isn't correct, its the binding not probe ;).
Signed-off-by: Andy Gross agr...@codeaurora.org
---
.../devicetree/bindings/dma/msm_bam_dma.txt| 49
On Oct 25, 2013, at 9:15 AM, Kamil Debski wrote:
Add a new driver for the Exynos USB PHY. The new driver uses the generic
PHY framework. The driver includes support for the Exynos 4x10 and 4x12
SoC families.
Signed-off-by: Kamil Debski k.deb...@samsung.com
Signed-off-by: Kyungmin Park
on binding:
Acked-by: Kumar Gala ga...@codeaurora.org
- 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
ault = 1)
> +
> +Example:
> +
> +tsl2563@29 {
> + compatible = "amstaos,tsl2563";
> + reg = <0x29>;
> + amstaos,cover-comp-gain = <16>;
> +};
For the Binding, assuming another patch to add amstoas to the vendor list
Acked-by: Kumar Gala
#interrupt-cells = <1>;
> + interrupt-parent = <_ictl>;
> + interrupts = <27 2>;
> + reg = <0xFF14 0x1000>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + abilis,ngpio = &l
On Oct 24, 2013, at 5:43 AM, Sricharan R wrote:
> Hi Kumar,
>
> On Thursday 24 October 2013 03:03 PM, Kumar Gala wrote:
>> On Sep 30, 2013, at 8:59 AM, Sricharan R wrote:
>>
>>> Some socs have a large number of interrupts requests to service
>>> the needs
On Sep 30, 2013, at 8:59 AM, Sricharan R wrote:
> In some socs the gic can be preceded by a crossbar IP which
> routes the peripheral interrupts to the gic inputs. The peripheral
> interrupts are associated with a fixed crossbar input line and the
> crossbar routes that to one of the free gic
On Sep 30, 2013, at 8:59 AM, Sricharan R wrote:
> Some socs have a large number of interrupts requests to service
> the needs of its many peripherals and subsystems. All of the
> interrupt lines from the subsystems are not needed at the same
> time, so they have to be muxed to the irq-controller
On Sep 30, 2013, at 8:59 AM, Sricharan R wrote:
Some socs have a large number of interrupts requests to service
the needs of its many peripherals and subsystems. All of the
interrupt lines from the subsystems are not needed at the same
time, so they have to be muxed to the irq-controller
On Sep 30, 2013, at 8:59 AM, Sricharan R wrote:
In some socs the gic can be preceded by a crossbar IP which
routes the peripheral interrupts to the gic inputs. The peripheral
interrupts are associated with a fixed crossbar input line and the
crossbar routes that to one of the free gic input
On Oct 24, 2013, at 5:43 AM, Sricharan R wrote:
Hi Kumar,
On Thursday 24 October 2013 03:03 PM, Kumar Gala wrote:
On Sep 30, 2013, at 8:59 AM, Sricharan R wrote:
Some socs have a large number of interrupts requests to service
the needs of its many peripherals and subsystems. All
;
+ #gpio-cells = 2;
+ abilis,ngpio = 3;
+ gpio-ranges = iomux 0 0 0;
+ gpio-ranges-group-names = gpioa_pins;
+ };
For the Binding part:
Acked-by: Kumar Gala ga...@codeaurora.org
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation
,cover-comp-gain = 16;
+};
For the Binding, assuming another patch to add amstoas to the vendor list
Acked-by: Kumar Gala ga...@codeaurora.org
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by
The Linux Foundation
On Oct 18, 2013, at 1:14 PM, Christopher Covington wrote:
> Put architecture-specific assembly code where it belongs,
> allowing for support of additional architectures such as arm64 in
> the future.
>
> Signed-off-by: Christopher Covington
> ---
> arch/arm/include/asm/dcc.h | 45
On Oct 18, 2013, at 1:14 PM, Christopher Covington wrote:
Put architecture-specific assembly code where it belongs,
allowing for support of additional architectures such as arm64 in
the future.
Signed-off-by: Christopher Covington c...@codeaurora.org
---
arch/arm/include/asm/dcc.h | 45
| 9 +++
> 5 files changed, 60 insertions(+), 2 deletions(-)
> create mode 100644 arch/arm/boot/dts/qcom-apq8074-dragonboard.dts
> create mode 100644 arch/arm/boot/dts/qcom-msm8974.dtsi
Acked-by: Kumar Gala
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovati
files changed, 60 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/boot/dts/qcom-apq8074-dragonboard.dts
create mode 100644 arch/arm/boot/dts/qcom-msm8974.dtsi
Acked-by: Kumar Gala ga...@codeaurora.org
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center
On Oct 16, 2013, at 5:56 PM, Rob Herring wrote:
> On 08/08/2013 10:51 AM, Kumar Gala wrote:
>> I'm tossing my hat into the ring of maintainers/reviewers for device tree
>> bindings based on history of dealing with DT on embedded PPC and starting
>> work on ARM SoCs.
>&g
On Oct 12, 2013, at 4:14 PM, Rohit Vaswani wrote:
> This patch adds basic board support for APQ8074 Dragonboard
> which belongs to the Snapdragon 800 family.
> For now, just support a basic machine with device tree.
>
> Signed-off-by: Rohit Vaswani
> ---
> arch/arm/boot/dts/Makefile
On Oct 15, 2013, at 8:16 AM, Gerhard Sittig wrote:
> On Mon, Oct 14, 2013 at 13:09 -0700, Greg Kroah-Hartman wrote:
>>
>> On Mon, Oct 14, 2013 at 02:40:44PM -0500, Kumar Gala wrote:
>>>
>>> Greg,
>>>
>>> Wondering your thoughts on
On Oct 15, 2013, at 8:16 AM, Gerhard Sittig wrote:
On Mon, Oct 14, 2013 at 13:09 -0700, Greg Kroah-Hartman wrote:
On Mon, Oct 14, 2013 at 02:40:44PM -0500, Kumar Gala wrote:
Greg,
Wondering your thoughts on drivers/qe vs something like
drivers/soc/fsl/qe. The QuiccEngine (qe
On Oct 12, 2013, at 4:14 PM, Rohit Vaswani wrote:
This patch adds basic board support for APQ8074 Dragonboard
which belongs to the Snapdragon 800 family.
For now, just support a basic machine with device tree.
Signed-off-by: Rohit Vaswani rvasw...@codeaurora.org
---
On Oct 16, 2013, at 5:56 PM, Rob Herring wrote:
On 08/08/2013 10:51 AM, Kumar Gala wrote:
I'm tossing my hat into the ring of maintainers/reviewers for device tree
bindings based on history of dealing with DT on embedded PPC and starting
work on ARM SoCs.
Signed-off-by: Kumar Gala ga
On Oct 14, 2013, at 2:26 PM, Kumar Gala wrote:
>
> On Oct 14, 2013, at 6:37 AM, Xie Xiaobo wrote:
>
>> The QUICC Engine (QE) is a communications coprocessors on Freescale
>> embedded processors. The QE had been applied in PowerPC architecture
>> previously, an
On Oct 14, 2013, at 2:26 PM, Kumar Gala wrote:
On Oct 14, 2013, at 6:37 AM, Xie Xiaobo wrote:
The QUICC Engine (QE) is a communications coprocessors on Freescale
embedded processors. The QE had been applied in PowerPC architecture
previously, and it will be applied in ARM architecture
On Oct 3, 2013, at 11:25 AM, Greg Kroah-Hartman wrote:
> On Thu, Oct 03, 2013 at 11:21:10AM -0500, Kumar Gala wrote:
>>
>> On Oct 3, 2013, at 10:27 AM, Greg Kroah-Hartman wrote:
>>
>>> On Thu, Oct 03, 2013 at 09:45:38AM -0500, Kumar Gala wrote:
>>>&
On Oct 3, 2013, at 10:27 AM, Greg Kroah-Hartman wrote:
> On Thu, Oct 03, 2013 at 09:45:38AM -0500, Kumar Gala wrote:
>> As we look at upstreaming more support for the Qualcomm MSM SoCs there
>> are a number of drivers or library like routines that are unique to
>>
> So where have we gotten on this?
>
> It seems we are in agreement that:
> 1. reserve memory should be probably be described in nodes
> 2. it should be pulled out of the memory node and put at root level
> 3. Use reg to describe the memory regions for a given node
>
> Now to figure out about
As we look at upstreaming more support for the Qualcomm MSM SoCs there are a
number of drivers or library like routines that are unique to the MSM platform,
we are thinking that putting them under:
drivers/platform/qcom/
would make sense. In addition there are headers that might need to get
As we look at upstreaming more support for the Qualcomm MSM SoCs there are a
number of drivers or library like routines that are unique to the MSM platform,
we are thinking that putting them under:
drivers/platform/qcom/
would make sense. In addition there are headers that might need to get
So where have we gotten on this?
It seems we are in agreement that:
1. reserve memory should be probably be described in nodes
2. it should be pulled out of the memory node and put at root level
3. Use reg to describe the memory regions for a given node
Now to figure out about how to
On Oct 3, 2013, at 10:27 AM, Greg Kroah-Hartman wrote:
On Thu, Oct 03, 2013 at 09:45:38AM -0500, Kumar Gala wrote:
As we look at upstreaming more support for the Qualcomm MSM SoCs there
are a number of drivers or library like routines that are unique to
the MSM platform, we are thinking
On Oct 3, 2013, at 11:25 AM, Greg Kroah-Hartman wrote:
On Thu, Oct 03, 2013 at 11:21:10AM -0500, Kumar Gala wrote:
On Oct 3, 2013, at 10:27 AM, Greg Kroah-Hartman wrote:
On Thu, Oct 03, 2013 at 09:45:38AM -0500, Kumar Gala wrote:
As we look at upstreaming more support for the Qualcomm
On Sep 27, 2013, at 11:21 AM, Suman Anna wrote:
> On 09/27/2013 11:06 AM, Kumar Gala wrote:
>>
>> On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
>>
>>> HwSpinlock IP is present only on OMAP4 and other newer SoCs,
>>> which are all device-tree boot onl
On Sep 27, 2013, at 11:48 AM, Suman Anna wrote:
> Kumar,
>
> On 09/27/2013 11:04 AM, Kumar Gala wrote:
>>
>> On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
>>
>>> All the platform-specific hwlock driver implementations need the
>>> number of loc
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
> HwSpinlock IP is present only on OMAP4 and other newer SoCs,
> which are all device-tree boot only. This patch adds the
> base support for parsing the DT nodes, and removes the code
> dealing with the traditional platform device instantiation.
>
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
> All the platform-specific hwlock driver implementations need the
> number of locks and the associated base id for registering the
> locks present within a hwspinlock device with the driver core.
> These two variables are represented by
On Sep 18, 2013, at 3:21 AM, Benjamin Herrenschmidt wrote:
> On Tue, 2013-09-17 at 21:57 -0500, Grant Likely wrote:
>
>>> - It provides no indication of what a given region is used for (or used
>>> by). In the example, "display_region" is a label (thus information that
>>> is lost) and unless
On Sep 26, 2013, at 8:30 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2013-09-26 at 17:12 -0600, Stephen Warren wrote:
>> Well, ePAPR seems pretty specific that unit address and reg are
>> related,
>> but says nothing about ranges in the section on node naming, nor about
>> node naming in the
On Sep 27, 2013, at 12:17 AM, David Gibson wrote:
> On Fri, Sep 27, 2013 at 11:30:38AM +1000, Benjamin Herrenschmidt wrote:
>> On Thu, 2013-09-26 at 17:12 -0600, Stephen Warren wrote:
>>> Well, ePAPR seems pretty specific that unit address and reg are
>>> related,
>>> but says nothing about
On Sep 27, 2013, at 12:17 AM, David Gibson wrote:
On Fri, Sep 27, 2013 at 11:30:38AM +1000, Benjamin Herrenschmidt wrote:
On Thu, 2013-09-26 at 17:12 -0600, Stephen Warren wrote:
Well, ePAPR seems pretty specific that unit address and reg are
related,
but says nothing about ranges in the
On Sep 26, 2013, at 8:30 PM, Benjamin Herrenschmidt wrote:
On Thu, 2013-09-26 at 17:12 -0600, Stephen Warren wrote:
Well, ePAPR seems pretty specific that unit address and reg are
related,
but says nothing about ranges in the section on node naming, nor about
node naming in the section
On Sep 18, 2013, at 3:21 AM, Benjamin Herrenschmidt wrote:
On Tue, 2013-09-17 at 21:57 -0500, Grant Likely wrote:
- It provides no indication of what a given region is used for (or used
by). In the example, display_region is a label (thus information that
is lost) and unless it's
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
All the platform-specific hwlock driver implementations need the
number of locks and the associated base id for registering the
locks present within a hwspinlock device with the driver core.
These two variables are represented by
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing with the traditional platform device instantiation.
On Sep 27, 2013, at 11:48 AM, Suman Anna wrote:
Kumar,
On 09/27/2013 11:04 AM, Kumar Gala wrote:
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
All the platform-specific hwlock driver implementations need the
number of locks and the associated base id for registering the
locks
On Sep 27, 2013, at 11:21 AM, Suman Anna wrote:
On 09/27/2013 11:06 AM, Kumar Gala wrote:
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT
On Sep 26, 2013, at 4:10 PM, Rob Herring wrote:
> On 09/26/2013 02:33 PM, Kumar Gala wrote:
>>
>> On Sep 26, 2013, at 2:17 PM, Rohit Vaswani wrote:
>>
>>> On 9/26/2013 11:05 AM, Rohit Vaswani wrote:
>>>> On 9/26/2013 9:37 AM, Kumar Gala wrote:
>&
On Sep 26, 2013, at 3:58 PM, David Brown wrote:
> On Thu, Sep 26, 2013 at 02:33:53PM -0500, Kumar Gala wrote:
>
>>> "ePAPR 1.1 section 2.2.1.1 "Node Name Requirements" specifies that any
>>> node that has a reg property must include a unit address in its
On Sep 26, 2013, at 2:17 PM, Rohit Vaswani wrote:
> On 9/26/2013 11:05 AM, Rohit Vaswani wrote:
>> On 9/26/2013 9:37 AM, Kumar Gala wrote:
>>>
>>
>>> +++ b/arch/arm/boot/dts/qcom-apq8074-dragonboard.dts
>>> @@ -0,0 +1,6 @@
>>> +/include
On Sep 19, 2013, at 12:54 PM, Stephen Warren wrote:
> From: Stephen Warren
>
> ePAPR 1.1 section 2.2.1.1 "Node Name Requirements" specifies that any
> node that has a reg property must include a unit address in its name
> with value matching the first entry in its reg property. Conversely, if
On Sep 25, 2013, at 5:35 PM, Rohit Vaswani wrote:
> On 9/25/2013 12:49 PM, Kumar Gala wrote:
>> On Sep 23, 2013, at 10:13 PM, Rohit Vaswani wrote:
>>
>>> This patch adds basic board support for APQ8074 Dragonboard
>>> which belongs to the Snapdragon 800 family.
On Sep 25, 2013, at 5:35 PM, Rohit Vaswani wrote:
On 9/25/2013 12:49 PM, Kumar Gala wrote:
On Sep 23, 2013, at 10:13 PM, Rohit Vaswani wrote:
This patch adds basic board support for APQ8074 Dragonboard
which belongs to the Snapdragon 800 family.
For now, just support a basic machine
On Sep 19, 2013, at 12:54 PM, Stephen Warren wrote:
From: Stephen Warren swar...@nvidia.com
ePAPR 1.1 section 2.2.1.1 Node Name Requirements specifies that any
node that has a reg property must include a unit address in its name
with value matching the first entry in its reg property.
On Sep 26, 2013, at 2:17 PM, Rohit Vaswani wrote:
On 9/26/2013 11:05 AM, Rohit Vaswani wrote:
On 9/26/2013 9:37 AM, Kumar Gala wrote:
snip
+++ b/arch/arm/boot/dts/qcom-apq8074-dragonboard.dts
@@ -0,0 +1,6 @@
+/include/ qcom-msm8974.dtsi
+
+/ {
+model = Qualcomm APQ8074 Dragonboard
On Sep 26, 2013, at 3:58 PM, David Brown wrote:
On Thu, Sep 26, 2013 at 02:33:53PM -0500, Kumar Gala wrote:
ePAPR 1.1 section 2.2.1.1 Node Name Requirements specifies that any
node that has a reg property must include a unit address in its name
with value matching the first entry in its
On Sep 26, 2013, at 4:10 PM, Rob Herring wrote:
On 09/26/2013 02:33 PM, Kumar Gala wrote:
On Sep 26, 2013, at 2:17 PM, Rohit Vaswani wrote:
On 9/26/2013 11:05 AM, Rohit Vaswani wrote:
On 9/26/2013 9:37 AM, Kumar Gala wrote:
snip
+++ b/arch/arm/boot/dts/qcom-apq8074-dragonboard.dts
On Sep 23, 2013, at 10:13 PM, Rohit Vaswani wrote:
> This patch adds basic board support for APQ8074 Dragonboard
> which belongs to the Snapdragon 800 family.
> For now, just support a basic machine with device tree.
>
> Signed-off-by: Rohit Vaswani
> ---
> arch/arm/Kconfig.debug
On Sep 23, 2013, at 10:13 PM, Rohit Vaswani wrote:
This patch adds basic board support for APQ8074 Dragonboard
which belongs to the Snapdragon 800 family.
For now, just support a basic machine with device tree.
Signed-off-by: Rohit Vaswani rvasw...@codeaurora.org
---
On Sep 16, 2013, at 5:42 PM, Benjamin Herrenschmidt wrote:
> On Mon, 2013-09-16 at 10:22 -0500, Kumar Gala wrote:
>> Where is Jermey's binding documented ?
>
> It looks like I actually came up with this binding :-) Jeremy reminded
> me yesterday. It was posted to the DT
Use a standard 'qcom' prefix to denotate device trees meant for Qualcomm
based processors.
Signed-off-by: Kumar Gala
---
arch/arm/boot/dts/Makefile| 4 ++--
arch/arm/boot/dts/{msm8660-surf.dts => qcom-msm8660-surf.dts} | 0
arch/arm/boot/dts/{msm8960-cdp.
On Sep 16, 2013, at 1:50 PM, Olof Johansson wrote:
> On Mon, Sep 16, 2013 at 11:46 AM, Kumar Gala wrote:
>
>> I think the two options are either:
>>
>> qcom-msm*, qcom-apq*, etc
>>
>> or
>>
>> qcom/msm-*, qcom/apq*, etc
>>
>> I'm
On Sep 16, 2013, at 1:50 PM, Olof Johansson wrote:
On Mon, Sep 16, 2013 at 11:46 AM, Kumar Gala ga...@codeaurora.org wrote:
I think the two options are either:
qcom-msm*, qcom-apq*, etc
or
qcom/msm-*, qcom/apq*, etc
I'm guessing we'll end up without the dir and in the future have
Use a standard 'qcom' prefix to denotate device trees meant for Qualcomm
based processors.
Signed-off-by: Kumar Gala ga...@codeaurora.org
---
arch/arm/boot/dts/Makefile| 4 ++--
arch/arm/boot/dts/{msm8660-surf.dts = qcom-msm8660-surf.dts} | 0
arch/arm/boot
On Sep 16, 2013, at 5:42 PM, Benjamin Herrenschmidt wrote:
On Mon, 2013-09-16 at 10:22 -0500, Kumar Gala wrote:
Where is Jermey's binding documented ?
It looks like I actually came up with this binding :-) Jeremy reminded
me yesterday. It was posted to the DT list a while back, arguably we
On Sep 16, 2013, at 1:28 PM, Rohit Vaswani wrote:
> On 9/12/2013 7:05 PM, Kumar Gala wrote:
>> On Sep 12, 2013, at 5:47 PM, David Brown wrote:
>>
>>> On Thu, Sep 12, 2013 at 12:55:36PM -0500, Kumar Gala wrote:
>>>> On Sep 12, 2013, at 12:06 PM, Olof Johans
On Sep 15, 2013, at 9:57 PM, Benjamin Herrenschmidt wrote:
> [resent to the right list this time around]
>
> Hi folks !
>
> So I don't have the bandwidth to follow closely what's going on, but I
> just today noticed the crackpot that went into 3.11 as part of commit:
>
>
On Sep 15, 2013, at 9:57 PM, Benjamin Herrenschmidt wrote:
[resent to the right list this time around]
Hi folks !
So I don't have the bandwidth to follow closely what's going on, but I
just today noticed the crackpot that went into 3.11 as part of commit:
On Sep 16, 2013, at 1:28 PM, Rohit Vaswani wrote:
On 9/12/2013 7:05 PM, Kumar Gala wrote:
On Sep 12, 2013, at 5:47 PM, David Brown wrote:
On Thu, Sep 12, 2013 at 12:55:36PM -0500, Kumar Gala wrote:
On Sep 12, 2013, at 12:06 PM, Olof Johansson wrote:
My original request to please use
On Sep 12, 2013, at 5:47 PM, David Brown wrote:
> On Thu, Sep 12, 2013 at 12:55:36PM -0500, Kumar Gala wrote:
>>
>> On Sep 12, 2013, at 12:06 PM, Olof Johansson wrote:
>
>>> My original request to please use a common prefix for your product
>>> fam
On Sep 12, 2013, at 1:46 PM, Olof Johansson wrote:
> On Thu, Sep 12, 2013 at 11:20 AM, Rob Herring wrote:
>
>> As Stephen W has pointed out previously, the dtb filename itself is or
>> may be an ABI and the bootloader may be hardcoded to a name. So we
>> should avoid future renames.
>
> We
801 - 900 of 1752 matches
Mail list logo
