Arnd Bergmann writes:
> I would like those drivers to be enabled in some defconfig, so we get
> compile-time coverage, but we generally stopped having one-config-per-board
> files.
>
> Maybe we can have a pxa_defconfig file that enables lots of boards
> and then we remove the individual configs?
Arnd Bergmann writes:
> On Tuesday 15 December 2015 21:50:13 Sergei Ianovich wrote:
>> On Tue, 2015-12-15 at 19:06 +0100, Robert Jarzmik wrote:
>> Updated plan:
>> 1. MACH_PXA27X_DT
>> 2. PXA_FB and 8250_PXA to enable console
What about gpio-pxa ? And maybe pinctrl-px
Sergei Ianovich writes:
> On Tue, 2015-12-15 at 18:02 +0100, Arnd Bergmann wrote:
>> On Tuesday 15 December 2015 19:42:07 Sergei Ianovich wrote:
>> > There are several board-specific devices on LP8x4x: custom FPGA,
>> > custom
>> > UART, custom IRQ on FPGA, custom parallel bus for industrial IO.
: arch/arm/mach-pxa/
> F: drivers/dma/pxa*
> F: drivers/pcmcia/pxa2xx*
Acked-by: Robert Jarzmik
Cheers.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Add documentation for the PXA LCD controller devicetree binding.
Signed-off-by: Robert Jarzmik
---
Since v1: Philipp's review on the whole binding
Since v2: moved to display/, Philipp's and Rob's review
dropped panel description, should be a simple panel with a
Rob Herring writes:
>> The pxafb driver acts today on the subset of registers which are the same
>> across
>> all pxaXXX variants. This is what made me think only one compatible property
>> was
>> required.
>>
>> If I'm wrong, I could add "marvell,pxa3xx-lcdc", is that what you think I
>> shou
Rob Herring writes:
> On Sun, Oct 4, 2015 at 5:31 AM, Robert Jarzmik wrote:
>> Add documentation for the PXA frambuffer devicetree binding.
>
> Strictly speaking this is a binding for PXA display controller, not a
> Linux FB driver. There are lots of "framebuffer" an
Philipp Zabel writes:
> On Sun, Oct 4, 2015 at 12:31 PM, Robert Jarzmik
> wrote:
>> + lcd-controller@4050 {
>> + compatible = "marvell,pxa2xx-lcdc";
>> + reg = <0x4400 0x1>;
>> + interru
Add documentation for the PXA frambuffer devicetree binding.
Signed-off-by: Robert Jarzmik
---
Since v1: Philipp's review on the whole binding
---
.../devicetree/bindings/video/marvell,pxafb.txt| 80 ++
1 file changed, 80 insertions(+)
create mode 100644 Document
Philipp Zabel writes:
> On Sat, Oct 3, 2015 at 6:11 PM, Robert Jarzmik wrote:
>> Add documentation for the PXA frambuffer devicetree binding.
>>
>> Signed-off-by: Robert Jarzmik
>> Cc: Jean-Christophe Plagniol-Villard
>> Cc: Tomi Valkeinen
&
Add documentation for the PXA frambuffer devicetree binding.
Signed-off-by: Robert Jarzmik
Cc: Jean-Christophe Plagniol-Villard
Cc: Tomi Valkeinen
Cc: linux-fb...@vger.kernel.org
---
.../devicetree/bindings/video/marvell,pxafb.txt| 75 ++
1 file changed, 75 insertions
The PXA architecture provides a DMA to pump data from the nand
controller to memory and the other way around. Add it to the binding
description.
Signed-off-by: Robert Jarzmik
---
Documentation/devicetree/bindings/mtd/pxa3xx-nand.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a
Vaibhav Hiremath writes:
> Robert,
>
> It would be helpful if you can test this patch-series and confirm that
> it now fixes the NULL pointer deference issue.
Tested, it works on pxa27x in master mode, in non-DT mode.
For all non-DT patches, you can add my :
Tested-by: Robert Jarz
Vaibhav Hiremath writes:
> Robert,
>
> It would be helpful if you can test this patch-series and confirm that
> it now fixes the NULL pointer deference issue.
>
> Thanks,
> Vaibhav
Hi Vaibhav,
My next slot is probably this comming Sunday. I'll do the test and report.
Cheers.
--
Robert
--
To u
Vaibhav Hiremath writes:
> On Monday 20 July 2015 12:39 PM, Vaibhav Hiremath wrote:
>>
>>
>> On Monday 20 July 2015 12:36 PM, Vaibhav Hiremath wrote:
>>>
>>>
>>> On Saturday 18 July 2015 01:19 AM, Robert Jarzmik wrote:
>>>> Vaibhav Hi
Vaibhav Hiremath writes:
>> So, I applied patches 1-6 to for-next to make some progress.
>>
>> The others need more thought because of the bindings which shall be
>> discussed replying to the patches in question.
>>
>> Thanks for the updated work with lots of proper references.
>>
>
> OK, Thanks
Robert Jarzmik writes:
Applied to pxa/dt, thanks.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Add the usb host controller to pxa27x and pxa3xx.
Signed-off-by: Robert Jarzmik
---
Since v2: change node name from ohci to usb (ePAPR)
---
arch/arm/boot/dts/pxa27x.dtsi | 8
arch/arm/boot/dts/pxa3xx.dtsi | 8
2 files changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts
Add the correct address and size to the device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 1402e23..fc79df9 100644
--- a/arch/arm/boot
The pxa27x SoCs have an embedded camera host controller. Add the
description to the family description.
Signed-off-by: Robert Jarzmik
---
Since v1: Sergey's comment on ePAR standard: "imaging"
---
arch/arm/boot/dts/pxa27x.dtsi | 17 +
1 file changed, 17 insertions
Add the 3 possible mmc controllers on pxa3xx SoCs to the devicetree
description. Add the dma and clocks to the device-tree description of
pxa27x and pxa3xx at the same time.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa2xx.dtsi | 4
arch/arm/boot/dts/pxa3xx.dtsi | 33
Add the dma client description for pxa3xx-nand to use its dma through
device-tree.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa3xx.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/pxa3xx.dtsi b/arch/arm/boot/dts/pxa3xx.dtsi
index 4eb1563..d90489b 100644
Add the SoC embedded DMA controller, shared with the mmp architecture.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 9 +
arch/arm/boot/dts/pxa3xx.dtsi | 9 +
2 files changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts
Sergei Shtylyov writes:
>Sigh. ePAPR standardizes the "usb" name for such nodes.
> [...]
Indeed.
I'll send the v3 tomorrow.
Cheers.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
Add the correct address and size to the device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 1402e23..fc79df9 100644
--- a/arch/arm/boot
The pxa27x SoCs have an embedded camera host controller. Add the
description to the family description.
Signed-off-by: Robert Jarzmik
---
Since v1: Sergey's comment on ePAR standard: "imaging"
---
arch/arm/boot/dts/pxa27x.dtsi | 17 +
1 file changed, 17 insertions
Add the 3 possible mmc controllers on pxa3xx SoCs to the devicetree
description. Add the dma and clocks to the device-tree description of
pxa27x and pxa3xx at the same time.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa2xx.dtsi | 4
arch/arm/boot/dts/pxa3xx.dtsi | 33
Add the SoC embedded DMA controller, shared with the mmp architecture.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 9 +
arch/arm/boot/dts/pxa3xx.dtsi | 9 +
2 files changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts
Add the usb host controller to pxa27x and pxa3xx.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 8
arch/arm/boot/dts/pxa3xx.dtsi | 8
2 files changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index fc79df9
Add the dma client description for pxa3xx-nand to use its dma through
device-tree.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa3xx.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/pxa3xx.dtsi b/arch/arm/boot/dts/pxa3xx.dtsi
index 4eb1563..d90489b 100644
Sergei Shtylyov writes:
>> +pxa_camera: pxa_camera@5000 {
>
>The ePAPR standard has something to say about the node naming:
> "The name of a node should be somewhat generic, reflecting the function of the
> device and not its precise programming model." So I'd suggest "video@5
Add the usb host controller to pxa27x and pxa3xx.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 8
arch/arm/boot/dts/pxa3xx.dtsi | 8
2 files changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 94cf80f
The pxa27x SoCs have an embedded camera host controller. Add the
description to the family description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts
Add the correct address and size to the device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 9ebfd7f..94cf80f 100644
--- a/arch/arm/boot
Add the SoC embedded DMA controller, shared with the mmp architecture.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 9 +
arch/arm/boot/dts/pxa3xx.dtsi | 9 +
2 files changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts
Add the 3 possible mmc controllers on pxa3xx SoCs to the devicetree
description. Add the dma and clocks to the device-tree description of
pxa27x and pxa3xx at the same time.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa2xx.dtsi | 4
arch/arm/boot/dts/pxa3xx.dtsi | 33
Add the dma client description for pxa3xx-nand to use its dma through
device-tree.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa3xx.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/pxa3xx.dtsi b/arch/arm/boot/dts/pxa3xx.dtsi
index 4eb1563..d90489b 100644
Arnd Bergmann writes:
> On Thursday 26 March 2015, Robert Jarzmik wrote:
>>
>> Greg Kroah-Hartman writes:
>>
>> > On Fri, Feb 20, 2015 at 05:02:57PM +0100, Robert Jarzmik wrote:
>> >> If there is no solution, I'll fallback through arch/arm/plat
Greg Kroah-Hartman writes:
> On Fri, Feb 20, 2015 at 05:02:57PM +0100, Robert Jarzmik wrote:
>> If there is no solution, I'll fallback through arch/arm/plat-pxa, not very
>> nice,
>> but it has to land somewhere, I don't want lubbock to remain broken.
>
>
Lee Jones writes:
> On Sat, 28 Feb 2015, Robert Jarzmik wrote:
>
>> Lee Jones writes:
>> it doesn't specify which usecase is not covered by CLK_IGNORE_UNUSED, it
>> says, up to my understanding, that is it another way to have to
>> CLK_IGNORE_UN
Greg Kroah-Hartman writes:
> On Sat, Feb 28, 2015 at 10:57:30AM +0100, Robert Jarzmik wrote:
>> Robert Jarzmik writes:
>>
>> > Hi Arnd and Greg,
>> It's been a week, backlog ping ?
>
> If only my backlog was just one week...
Ah, that's bad :)
&
Robert Jarzmik writes:
> Hi Arnd and Greg,
It's been a week, backlog ping ?
>
> I have this driver I'm upstreaming, which comes out of
> arch/arm/mach-pxa/lubbock.c. As for the reason it is extracted, see submitted
> commit [1] for reference.
>
> The main questi
Lee Jones writes:
>> I wonder why there is a need for a new clock when CLK_IGNORE_UNUSED does
>> exist. What is the usecase that is covered by this patchset which is not
>> used by
>> CLK_IGNORE_UNUSED clock flag ?
>>
>> And if that reason exists, I'd like to find it in the commit message.
>
>
Lee Jones writes:
> v2 => v3:
> - Ensure DT actually reflects h/w
> - i.e. Nodes should not contain a mishmash of different IP
> blocks, but should identify related h/w. In the current
> example we use interconnects
> - Change naming from clkdomain to clk-always-on
> - Plac
Robert Jarzmik writes:
> Robert Jarzmik writes:
>
>> pxa27x variant has 2 I2C busses on the SoC :
>> - the casual I2C
>> - the power I2C, normally driving power regulators, and capable of
>> receiving orders on core frequency modifications
>>
>> Ad
Lee Jones writes:
> What's all this? Please configure your mail client correctly.
>
> For advice, see:
>
> Documentation/email-clients.txt
While at day work, I have only access to web mail ...
>> 2) after v2, we _both_ agreed that the accurate name is "cplds"
>> which exactly what is in
- Mail original -
De: "Lee Jones"
À: "Robert Jarzmik"
Cc: "Rob Herring" , "Pawel Moll" ,
"Mark Rutland" , "Ian Campbell"
, "Kumar Gala" , "Daniel
Mack" , "Haojian Zhuang" , "Samuel
Orti
Robert Jarzmik writes:
> pxa27x variant has 2 I2C busses on the SoC :
> - the casual I2C
> - the power I2C, normally driving power regulators, and capable of
> receiving orders on core frequency modifications
>
> Add the missing pwri2c to pxa27x description.
>
> Signe
Each pxa has an embedded OS Timers IP. The kernel cannot work without a
valid clocksource, and this adds the OS Timers to the pxa device-tree
description.
Signed-off-by: Robert Jarzmik
---
Since v1: removed clocksource node, pxa-timer being directly under
pxabus (Rob's comment).
x27;t
disable them automatically (unused clocks shutdown)
Signed-off-by: Robert Jarzmik
---
Since v3: change pxa2xx-clks into clks to accomodate pxa3xx as well
---
arch/arm/boot/dts/pxa27x.dtsi | 18 ++
arch/arm/boot/dts/pxa2xx.dtsi | 7 ++-
arch/arm/boot/dts/pxa3xx.dtsi
Each pxa27x has an embedded keypad controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 7cc36ef
pxa27x variant has 2 I2C busses on the SoC :
- the casual I2C
- the power I2C, normally driving power regulators, and capable of
receiving orders on core frequency modifications
Add the missing pwri2c to pxa27x description.
Signed-off-by: Robert Jarzmik
---
Since v2: as Dmitry pointed out
Each pxa27x has an embedded usb udc controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik
---
Since v3: changed pxa2xx-clks into clks
---
arch/arm/boot/dts/pxa27x.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b
Robert Jarzmik writes:
> Add a binding for lubbock motherboard IO board.
>
> Signed-off-by: Robert Jarzmik
> ---
> Since v3: name change to lubbock-cplds,
> Lee's comments taken into account.
Hi Lee,
I hope I have handled all the comments. Is this v4 go
> + ffuart: uart@4010 {
> + clocks = <&pxa2xx_clks CLK_FFUART>;
> + };
> +
After another thought about your "one line" node, I think this can be even
improved, so that :
- uart clocks are put into pxa2xx.dtsi instead of pxa27x.dtsi
- replace all px
Tyler Hall writes:
>> The issue with multiple gpiochips per of-node could be worked around as
>> followed I believe, comments?
>>
>> diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c
>> index 08261f2..43984ab 100644
>> --- a/drivers/gpio/gpiolib-of.c
>> +++ b/drivers/gpio/gpioli
Alexandre Courbot writes:
> Adding Robert who reported the same thing.
>
> On Sat, Feb 7, 2015 at 6:28 AM, Tyler Hall wrote:
>> 1. Require child nodes in DT for each bank
>
> This would break DT compatibility.
Agreed.
>
>> 2. Refactor gpio-pxa to only register one gpiochip
>
> Sounds better, es
Sergei Shtylyov writes:
> Hello.
>
> On 2/7/2015 3:39 PM, Robert Jarzmik wrote:
>> +stuart: uart@4070 {
>> +clocks = <&pxa2xx_clks CLK_STUART>;
>> +};
>> +
>
>The ePAPR standard tells to call s
Each pxa27x has an embedded usb udc controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index e8d5097
Each pxa27x has an embedded keypad controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index ddb6982
x27;t
disable them automatically (unused clocks shutdown)
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 31 ---
1 file changed, 28 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 98
Each pxa has an embedded OS Timers IP. The kernel cannot work without a
valid clocksource, and this adds the OS Timers to the pxa device-tree
description.
Signed-off-by: Robert Jarzmik
---
Since v1: removed clocksource node, pxa-timer being directly under
pxabus (Rob's comment).
pxa27x variant has 2 I2C busses on the SoC :
- the casual I2C
- the power I2C, normally driving power regulators, and capable of
receiving orders on core frequency modifications
Add the missing pwri2c to pxa27x description.
Signed-off-by: Robert Jarzmik
---
Since v2: as Dmitry pointed out
Sergei Shtylyov writes:
>> +clocksources {
>> +#address-cells = <1>;
>> +#size-cells = <1>;
>> +ranges;
>> +
>> +pxa-timer@40a0 {
>
>Just "timer@40a0", please.
Hi Sergei,
I forgot that in the v2, sorry. I'll put it in v3.
Cheers.
Each pxa has an embedded OS Timers IP. The kernel cannot work without a
valid clocksource, and this adds the OS Timers to the pxa device-tree
description.
Signed-off-by: Robert Jarzmik
---
Since v1: removed clocksource node, pxa-timer being directly under
pxabus (Rob's co
Each pxa27x has an embedded keypad controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 979560c
Each pxa variant has 2 I2C busses on the SoC :
- the casual I2C
- the power I2C, normally driving power regulators, and capable of
receiving orders on core frequency modifications
Add the missing pwri2c to pxa description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa2xx.dtsi | 9
x27;t
disable them automatically (unused clocks shutdown)
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 36
1 file changed, 32 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 80
Each pxa27x has an embedded usb udc controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 7cbf36f
Mark Rutland writes:
> On Sat, Jan 31, 2015 at 10:48:30PM +0000, Robert Jarzmik wrote:
>> +clocksources {
>> +#address-cells = <1>;
>> +#size-cells = <1>;
>> +ranges;
>> +
>
> There is absolutely no nee
Each pxa27x has an embedded keypad controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 979560c
x27;t
disable them automatically (unused clocks shutdown)
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 36
1 file changed, 32 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 80
Each pxa27x has an embedded usb udc controller. Add it in the pxa27x
device-tree description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/pxa27x.dtsi b/arch/arm/boot/dts/pxa27x.dtsi
index 7cbf36f
Each pxa variant has 2 I2C busses on the SoC :
- the casual I2C
- the power I2C, normally driving power regulators, and capable of
receiving orders on core frequency modifications
Add the missing pwri2c to pxa description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa2xx.dtsi | 9
Each pxa has an embedded OS Timers IP. The kernel cannot work without a
valid clocksource, and this adds the OS Timers to the pxa device-tree
description.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa27x.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm
, demuxing the
lubbock IO board interrupts.
This patch moves all that handling to a mfd driver. It's only purpose
for the time being is the interrupt handling, but in the future it
should encompass all the motherboard CPLDs handling :
- leds
- switches
- hexleds
Signed-off-by: Robert Ja
As the interrupt handling was transferred to the lubbock_cplds driver,
make the switch in lubbock platform code.
Signed-off-by: Robert Jarzmik
---
Since v1: change the name from cottula to lubbock_io
Dmitry pointed out the Cottula was the pxa25x family name,
lubbock was
Add entry Lubbock cplds driver into the pxa platform scope.
Signed-off-by: Robert Jarzmik
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ddb9ac8..8c6a49d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7681,6 +7681,7 @@ T:git git
Add a binding for lubbock motherboard IO board.
Signed-off-by: Robert Jarzmik
---
Since v3: name change to lubbock-cplds,
Lee's comments taken into account.
---
.../devicetree/bindings/mfd/lubbock-cplds.txt | 26 ++
1 file changed, 26 insertions(+)
c
Lee Jones writes:
> Very well, Russell and yourself have convinced me. If you fixup the
> remainder of comments, I'm happy.
Cool.
Let me a couple of days to gather my wits, cross-check I have not forgotten a
comment, make some testing on the board and then post v4.
Cheers.
--
Robert
--
To uns
> - Mail original -
> De: "Lee Jones"
First of all, this is my web mail interface, so please be kind with
my mail formatting ...
> Looking at one of the other patches in the series it appears the flag
> you're trying to capture is IORESOURCE_IRQ_LOWEDGE. When I grep for
> where this is b
Lee Jones writes:
> On Wed, 21 Jan 2015, Robert Jarzmik wrote:
>> > > > platform_get_irq()?
>> > > No. I need the flags.
>> > Where are they used?
>> A couple of lines below, using local "irqflags" variable :
>>ret
Russell King - ARM Linux writes:
> What I'd suggest (and always have done) is:
>
> dev_err(&pdev->dev, "couldn't request main irq%d: %d\n",
> irq, ret);
I like it, it's even more compact, I'll use it for next patch version.
> but I guess printing the IRQ number no longer make
Lee Jones writes:
> On Fri, 16 Jan 2015, Robert Jarzmik wrote:
>
>> Add a binding for lubbock motherboard IO board.
>>
>> Signed-off-by: Robert Jarzmik
>> ---
>> .../devicetree/bindings/mfd/lubbock-io.txt | 26
>> ++
>&
Lee Jones writes:
> On Fri, 16 Jan 2015, Robert Jarzmik wrote:
>
>> As a fix, move the gpio0 chained handler setup to a place where we have
>> the guarantee that pxa_gpio_probe() was called before, so that lubbock
>> handler becomes the true IRQ chained handler of GPIO0,
, demuxing the
lubbock IO board interrupts.
This patch moves all that handling to a mfd driver. It's only purpose
for the time being is the interrupt handling, but in the future it
should encompass all the motherboard CPLDs handling :
- leds
- switches
- hexleds
Signed-off-by: Robert Ja
As the interrupt handling was transferred to the lubbock_io driver, make
the switch in lubbock platform code.
Signed-off-by: Robert Jarzmik
---
Since v1: change the name from cottula to lubbock_io
Dmitry pointed out the Cottula was the pxa25x family name,
lubbock was the
Add a binding for lubbock motherboard IO board.
Signed-off-by: Robert Jarzmik
---
.../devicetree/bindings/mfd/lubbock-io.txt | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/lubbock-io.txt
diff --git a/Documentation
Mark Rutland writes:
> Hi Robert,
>
> Given the addition of an of_device_id table and some (implicit) property
> parsing, this requires a device tree binding document.
Yes, you're right. I'll prepare that.
>> +ret = devm_request_irq(&pdev->dev, cot->irq, lubbock_irq_handler, 0,
>> +
, demuxing the
lubbock IO board interrupts.
This patch moves all that handling to a mfd driver. It's only purpose
for the time being is the interrupt handling, but in the future it
should encompass all the motherboard CPLDs handling :
- leds
- switches
- hexleds
Signed-off-by: Robert Ja
Laurent Pinchart writes:
> Hi Robert,
>
> What happened to this patch ? It looks like the rest of the series got
> merged,
> but this one seems to be missing.
It got reverted, because there were 3 boards with a defconfig which required
that both pxa27x and pxa25x were ported to common clock fr
Robert Jarzmik writes:
> Arnd Bergmann writes:
>
>> On Monday 15 December 2014 00:10:06 Robert Jarzmik wrote:
>>> +
>>> + platform_set_drvdata(pdev, cot);
>>> + cot->gpio0 = gpiod_get(&pdev->dev, "lubbock_irq", 0);
>&g
Arnd Bergmann writes:
>> Will that look correct ?
>
> I'd still prefer the platform data, but this seems good enough and I
> see no serious problems with it.
OK, so I'll try with the 2 resources. If I'm bitten afterwards and am forced to
have a platform data, you'll tell me "I had warned you" ;)
Arnd Bergmann writes:
> On Monday 15 December 2014 00:10:06 Robert Jarzmik wrote:
>> +
>> + platform_set_drvdata(pdev, cot);
>> + cot->gpio0 = gpiod_get(&pdev->dev, "lubbock_irq", 0);
>> + if (IS_ERR(cot->gpio0)) {
>> +
the
lubbock IO board interrupts.
This patch moves all that handling to a mfd driver. It's only purpose
for the time being is the interrupt handling, but in the future it
should encompass all the motherboard CPLDs handling :
- leds
- switches
- hexleds
Signed-off-by: Robert Ja
Felipe Balbi writes:
> On Fri, Nov 21, 2014 at 06:17:58PM +0100, Robert Jarzmik wrote:
>> Felipe Balbi writes:
>>
>> > On Sun, Nov 09, 2014 at 02:02:18PM +0100, Robert Jarzmik wrote:
>> >> hsusb1_phy {
>> >> @@ -26,8 +31,11 @@
Felipe Balbi writes:
> On Sun, Nov 09, 2014 at 02:02:18PM +0100, Robert Jarzmik wrote:
>> hsusb1_phy {
>> @@ -26,8 +31,11 @@ Example:
>> clock-names = "main_clk";
>> vcc-supply = <&hsusb1_vcc_regulator>;
>>
Kevin Cernekee writes:
> On Thu, Nov 13, 2014 at 1:42 AM, Arnd Bergmann wrote:
>> TTY naming is a mess today, and you seem to be caught in the middle
>> of it trying to work around the inherent problems. Extending the PXA
>> driver is an interesting approach since as you say it's a very nice
>>
Kevin Cernekee writes:
> V1->V2:
>
> Add a new UPIO_MEM32BE iotype instead of a separate big_endian flag.
>
> Change some of the of_*_is_* APIs to return bool, where appropriate.
>
> Fix a few minor comment issues.
Hi Kevin,
I'll review the pxa part tonight or tomorrow, just a simple preliminar
Enhance the phy documentation by adding 2 new optional bindings :
- the vbus gpio, which detects usb insertion
- the vbus regulator, which provides current drawn from the usb cable
Signed-off-by: Robert Jarzmik
---
Documentation/devicetree/bindings/usb/usb-nop-xceiv.txt | 8
1 file
1 - 100 of 207 matches
Mail list logo
