Hello,
Before doing the work twice, is someone working on the arm/dts for the overo
board? I found a first support in the linaro tree [1], but is there any
active
work to complete this support and push it upstream? I am preparing a
daughter
board with some specific hardware, thus I could give
.
The second patch add the necessary aliases for OMAP3, OMAP4 and AM33xx.
This patchset applies on 3.6-rc3 and has been tested on OMAP3 (Gumstix Overo).
Regards,
Florian
Florian Vaussard (2):
i2c-omap: Fix incorrect adapter id when booting from a device tree
arm/dts: Add i2c aliases
When booting from a device tree, the omap driver is using pdev-id,
which is incorrect. The proposed patch uses aliases, as done in
omap-serial.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
drivers/i2c/busses/i2c-omap.c | 19 +++
1 files changed, 15 insertions
I2C aliases need to be set, for the omap-i2c driver to get a correct adapter id.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/am33xx.dtsi |3 +++
arch/arm/boot/dts/omap3.dtsi |3 +++
arch/arm/boot/dts/omap4.dtsi |4
3 files changed, 10
Hi Benoit,
[0.658843] omap_i2c i2c.15: bus -1 rev2.4.0 at 400 kHz
[0.760192] omap_i2c i2c.16: bus -1 rev2.4.0 at 400 kHz
[0.775817] omap_i2c i2c.17: bus -1 rev2.4.0 at 400 kHz
[0.791442] omap_i2c i2c.18: bus -1 rev2.4.0 at 400 kHz
OK, it is true that the current log is not that
When booting using a device tree, the adapter number is dynamically
assigned after the log message is sent.
This patch modifies the log message to get a correct adapter id.
Applies on 3.6-rc3. Tested on OMAP3 (Gumstix Overo).
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
drivers
=linux/kernel/git/tmlind/linux-omap.git;a=summary
Florian Vaussard (2):
ARM: omap/dts: Add support for Gumstix Overo with Tobi expansion
board
ARM: omap/dts: update the documentation
.../devicetree/bindings/arm/omap/omap.txt |3 +
arch/arm/boot/dts/omap3-overo.dtsi
updates the omap3 dtb build target.
Currently working:
- mmc0 (on board microSD)
- i2c0 and i2c2 (i2c1 not used)
- led on GPIO
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi | 42
arch/arm/boot/dts/omap3
Add the Tobi/Overo board to the list of supported platforms.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
.../devicetree/bindings/arm/omap/omap.txt |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/omap
Add device tree properties for twl4030/gpio, according to the
platform data of corresponding boards. This enables the led
connected to LEDB output for both boards, as well as
pullups/pulldowns on GPIO for the BeagleBoard.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot
Add the new properties to the documentation of bindings.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
.../devicetree/bindings/gpio/gpio-twl4030.txt |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/gpio/gpio
Hi Benoit,
Nit #2: the DTS file does not belong to the gpio subsystem. So you
should prefix them using the *convention* for ARM DTS patches:
arm/dts: omap3: Add gpio-twl4030 properties for BeagleBoard and omap3-EVM
Or maybe ARM: dts: because it looks like most people are using that
nowadays.
On 9/3/2012 7:24 PM, Florian Vaussard wrote:
Adds a number of missing properties to the device tree of
twl4030/gpio:
- ti,use-leds - .use_leds
- ti,debounce - .debounce
- ti,mmc-cd- .mmc_cd
- ti,pullups - .pullups
- ti,pulldowns - .pulldowns
Signed-off-by: Florian Vaussard
of_property_read_bool()
- Prefix the patches with the correct convention
Tested on Gumstix Overo. V1 was tested on omap3-evm by Vaibhav Hiremath.
BTW: who will merge this?
Regards,
Florian
Florian Vaussard (2):
gpio/twl4030: get platform data from device tree
ARM: dts: omap3: Add gpio
Adds a number of missing device tree properties for
twl4030/gpio, and update bindings:
- ti,use-leds - .use_leds
- ti,debounce - .debounce
- ti,mmc-cd- .mmc_cd
- ti,pullups - .pullups
- ti,pulldowns - .pulldowns
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Linus
Add device tree properties for twl4030/gpio, according to the
platform data of corresponding boards. This enables the led
connected to LEDB output for both boards, as well as
pullups/pulldowns on GPIO for the BeagleBoard.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Linus
Hello Benoit,
Le 07/09/2012 19:33, Benoit Cousson a écrit :
Hi Florian,
I've just noticed that this patch is reporting some CHECK issues.
d1f5052 - gpio/twl4030: get platform data from device tree
CHECK: Alignment should match open parenthesis
#66: FILE: drivers/gpio/gpio-twl4030.c:412:
+
Hello,
Le 08/09/2012 00:10, Tony Lindgren a écrit :
* Afzal Mohammed af...@ti.com [120905 05:37]:
Hi,
Basic gpmc driver conversion series. Driver that is now created out of
gpmc code is a simple one, it handles tasks that were earlier executed
by gpmc_init. Now instead of relying on cpu_is_*
Hello Benoit,
I fixed them since it was trivial, but next time you should ensure
that the patch pass checkpatch before posting.
Sorry for these errors. I however checked my patches before submitting,
and had no such warnings. I redone, and remarked that these warnings
appear only with the
Le 06/09/2012 22:52, Tony Lindgren a écrit :
* Florian Vaussard florian.vauss...@epfl.ch [120831 09:07]:
The Gumstix Overo is a computer on module using an OMAP3 processor.
This module must be plugged into an expansion board.
This patchset adds a first device tree support for the Overo, using
What is the status Benoit?
Patches looks good to me. I just adding them right now in my for_3.7/dts tree.
I've just slightly changed the subjects:
Documentation: dt: Update the OMAP documentation with Overo/Toby
ARM: dts: OMAP3: Add support for Gumstix Overo with Tobi expansion board
If you
Patches looks good to me. I just adding them right now in my for_3.7/dts tree.
I've just slightly changed the subjects:
Documentation: dt: Update the OMAP documentation with Overo/Toby
ARM: dts: OMAP3: Add support for Gumstix Overo with Tobi expansion board
If you want to give it a try, here
Hello,
This patch adds the support for the blue LED connected to the LEDB
pin of the TWL4030 on the Gumstix Overo when booting from the device
tree.
Build on top of Benoit's for_3.7/dts tree.
Regards,
Florian
Florian Vaussard (1):
ARM: dts: OMAP3: Add gpio-twl4030 properties for Overo
Support the blue LED connected to the LEDB pin of the TWL4030
on the Gumstix Overo.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3
Support the blue LED connected to the LEDB pin of the TWL4030
on the Gumstix Overo.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3
BTW, I'm just wondering. Cannot we use overo without tobi?
In that case, the model and compatible should probably be used as well:
model = TI OMAP3 Gumstix Overo;
compatible = ti,omap3-overo, ti,omap3;
No, it cannot. The Overo needs to be plugged into an expansion board, at
least
: bus 2 rev2.4.0 at 400 kHz
[0.799530] omap_i2c i2c.18: bus 3 rev2.4.0 at 400 kHz
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Tested-by: Benoit Cousson b-cous...@ti.com
and
Acked-by: Benoit Cousson b-cous...@ti.com
Regards,
Benoit
Was this patch picked-up by the i2c-embedded
Hello Benoit,
This patchset adds some new DT supports to the Overo products.
The first patch converts the PMIC LEDB output to use the pwm-leds,
newly merged in your branch for_3.9/dts. The second patch
adds the audio support.
Best regards,
Florian
Florian Vaussard (2):
ARM: dts: omap3-overo
Convert the on-board LED connected to the TWL4030 (LEDB) to use
pwm-leds.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-overo.dtsi
b/arch
Add the needed sections to enable audio support on Overo.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-overo.dtsi
b/arch/arm/boot/dts
Hi Peter,
diff --git a/arch/arm/boot/dts/omap3-overo.dtsi
b/arch/arm/boot/dts/omap3-overo.dtsi
index 89808ce..800be29 100644
--- a/arch/arm/boot/dts/omap3-overo.dtsi
+++ b/arch/arm/boot/dts/omap3-overo.dtsi
@@ -14,12 +14,13 @@
/include/ omap3.dtsi
/ {
- leds {
-
I did it at first, but the led API executes in atomic context, where the
pwm-twl-led driver uses i2c communication. Setting a trigger will result in a
kernel panic.
Now that you mentioned it, this might be true.
[c0013204] (unwind_backtrace+0x0/0xec) from [c00348ac]
Hi
I am working on a patch for pwm-twl-led to defer using a workqueue right now.
Great!
The only thing I worry about is the latency we are going to get with the
workqueue.
If the latency becomes critical, we can create our own workqueue.
Hrm, when we handled the led via gpio-leds it
We have two drivers at the moment: pwm-twl and pwm-twl-led. However new out of
SoC PWM drivers might come (for example for palmas). So it worth take a look
at some generic implementation.
OK. So I have the series. I need to add few more things but pwm-leds on
BeagleBoard works fine when I put
-conditional include inside the expansion boards' dts.
Or would it make sense to extend the DT binding for partitions?
This serie was tested on an Overo with 512MB of NAND.
Best regards,
Florian
[1] git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
omap-for-v3.9/gpmc
Florian
Add device-tree support for the GPMC controller on the OMAP3.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3.dtsi | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
Add device-tree support for the on-board NAND memory,
with corresponding partitions.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi | 49
1 files changed, 49 insertions(+), 0 deletions(-)
diff --git a/arch
So how should we handle such case? Having several dtsi depending
on the Overo's revision would be a mess to my sense, considering
the non-conditional include inside the expansion boards' dts.
Or would it make sense to extend the DT binding for partitions?
Yes makes sense to extend the binding
Hello Benoit,
On 01/24/2013 01:21 PM, Benoit Cousson wrote:
+ Peter who did the original PWM
Hi Florian,
On 01/23/2013 06:56 PM, Florian Vaussard wrote:
Hello Benoit,
This patchset adds some new DT supports to the Overo products. The
first patch converts the PMIC LEDB output to use the pwm
Hi Javier,
On 02/04/2013 10:27 AM, Javier Martinez Canillas wrote:
Hi Florian,
On Mon, Jan 28, 2013 at 6:54 PM, Florian Vaussard
florian.vauss...@epfl.ch wrote:
Add device-tree support for the GPMC controller on the OMAP3.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch
Hi Javier,
On 02/04/2013 12:57 PM, Javier Martinez Canillas wrote:
[...]
Yes, I saw on the list that Tony asked you too extend the GPMC DT
support. Flash support is on my TODO list too but I don't know if I'm
going to have time to work on this in the next few weeks.
Since you are thinking
Hi,
On 02/07/2013 08:58 AM, Peter Ujfalusi wrote:
Hi,
On 02/06/2013 02:30 PM, Benoit Cousson wrote:
So a patch is being merged to handle triggers in the case of pwm leds [1].
When done, we will be able to add back the default trigger. Do you want
to wait on it to merge this series?
What
On 05/17/2013 07:23 PM, Tony Lindgren wrote:
* Kishon Vijay Abraham I kis...@ti.com [130516 22:45]:
Hi,
On Thursday 16 May 2013 09:50 PM, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@iki.fi [130516 09:11]:
On 16/05/13 18:58, Tony Lindgren wrote:
* Tomi Valkeinen
The reset GPIO should be set for the SMSC911x, otherwise the controller
will not work and probing will fail. In the case of the tobi-duo
expansion board, the second controller shares the same GPIO, thus no
more changes are required (not tested).
Signed-off-by: Florian Vaussard florian.vauss
Replace /include/ by #include for OMAP2+ DT, in order to use the
C pre-processor, making use of #define features possible.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap2.dtsi |2 +-
arch/arm/boot/dts/omap2420-h4.dts |2 +-
arch
Define the OMAP_GPIO macro to conveniently use GPIO inside OMAP DT.
For example:
gpios = gpio6 3 0; /* GPIO 163 */
can be replaced by
gpios = OMAP_GPIO(163, 0);
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
include/dt-bindings/gpio/omap-gpio.h | 289
Use OMAP_GPIO(), in conjunction with standard GPIO flags, to enhance the
readability of DT GPIOs.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap2.dtsi |2 ++
arch/arm/boot/dts/omap3-beagle-xm.dts |4 ++--
arch/arm/boot/dts/omap3
On OMAP3, the INTC interrupt controller has only 1 cell.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3.dtsi |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index 15049b8
,
Florian
[1] https://patchwork.kernel.org/patch/2560091/
Florian Vaussard (5):
ARM: dts: OMAP2+: use #include for all device trees
ARM: dts: OMAP2+: create a DT header for GPIO
ARM: dts: OMAP2+: convert DT files to use the new OMAP_GPIO macro
ARM: dts: OMAP3: fix incorrect notation for musb
Use the constants defined in include/dt-bindings/interrupt-controller/
to enhance readability.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap4-panda-common.dtsi |8 +-
arch/arm/boot/dts/omap4-sdp.dts |6 +-
arch/arm/boot/dts/omap4-var
Hello Stephan, Tony,
Thank you for your reviews.
On 05/22/2013 05:34 PM, Tony Lindgren wrote:
* Stephen Warren swar...@wwwdotorg.org [130522 08:32]:
On 05/22/2013 08:27 AM, Florian Vaussard wrote:
Define the OMAP_GPIO macro to conveniently use GPIO inside OMAP DT.
For example:
gpios
Hi Stepen,
Thank you for your review,
On 05/22/2013 05:28 PM, Stephen Warren wrote:
On 05/22/2013 08:27 AM, Florian Vaussard wrote:
Use OMAP_GPIO(), in conjunction with standard GPIO flags, to enhance the
readability of DT GPIOs.
diff --git a/arch/arm/boot/dts/omap3-beagle-xm.dts
b/arch
Hi Tony,
On 05/22/2013 05:40 PM, Tony Lindgren wrote:
* Florian Vaussard florian.vauss...@epfl.ch [130522 07:33]:
Replace /include/ by #include for OMAP2+ DT, in order to use the
C pre-processor, making use of #define features possible.
This is good, but let's use it with case. Probably
Hello,
This series adds support to omap3-overo for the onboard NAND memory, and
restore the default trigger for the pwm-led provided by TWL4030.
Best regards,
Florian
Florian Vaussard (2):
ARM: dts: Add omap3-overo NAND flash memory binding
ARM: dts: omap3-overo: add default trigger
Add device-tree node for the on-board NAND memory.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi | 50
1 files changed, 50 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-overo.dtsi
b
Commit c971ff1 'leds: leds-pwm: Defer led_pwm_set() if PWM can sleep'
fixed a crash when using a trigger with a pwm-led provided by an
external chip. Now it is safe to add the default trigger according
to board-overo.c.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot
Commit d36b4cd 'ARM: OMAP2+: Add additional GPMC timing parameters'
updated GPMC binding, but omap3-devkit8000 was not updated accordingly,
resulting in a broken configuration.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-devkit8000.dts | 29
fix
- Remove OMAP_GPIO macro
- Add pinctrl constants
Florian Vaussard (5):
ARM: dts: OMAP2+: use #include for all device trees
ARM: dts: OMAP2+: use existing constants for GPIOs
ARM: dts: OMAP4/5: use existing constants for IRQs
ARM: dts: OMAP2+: header file for pinctrl constants
ARM: dts
Replace /include/ by #include for OMAP2+ DT, in order to use the
C pre-processor, making use of #define features possible.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap2.dtsi |2 +-
arch/arm/boot/dts/omap2420-h4.dts |2 +-
arch
Using constants for pinctrl allows a better readability, and remove
redundancy with comments.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap2.dtsi |1 +
arch/arm/boot/dts/omap3-beagle.dts| 24
arch/arm/boot/dts/omap3
Use standard GPIO constants to enhance the readability of DT GPIOs.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap2.dtsi |2 ++
arch/arm/boot/dts/omap3-beagle-xm.dts |4 ++--
arch/arm/boot/dts/omap3-beagle.dts|6
Use the constants defined in include/dt-bindings/interrupt-controller/
to enhance readability.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap4-panda-common.dtsi |8 +-
arch/arm/boot/dts/omap4-sdp.dts |6 +-
arch/arm/boot/dts/omap4-var
Most of the constants are taken from arch/arm/mach-omap2/mux.h.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
include/dt-bindings/pinctrl/omap.h | 54
1 files changed, 54 insertions(+), 0 deletions(-)
create mode 100644 include/dt-bindings
When making the dtbs target, omap4-sdp-es23plus.dtb is not built.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/Makefile |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index b9f7121
Hello Tony,
Thanks for your review.
On 05/23/2013 08:46 PM, Tony Lindgren wrote:
* Florian Vaussard florian.vauss...@epfl.ch [130523 08:42]:
index f39b237..b3cc896 100644
--- a/arch/arm/boot/dts/omap2.dtsi
+++ b/arch/arm/boot/dts/omap2.dtsi
@@ -9,6 +9,7 @@
*/
#include dt-bindings/gpio
Hello Santosh,
Thank you for your review.
On 05/23/2013 06:00 PM, Santosh Shilimkar wrote:
On Thursday 23 May 2013 11:36 AM, Florian Vaussard wrote:
Hello,
Following a similar proposal by Stephen Warren for tegra [1], this series
makes use of the C preprocessor when compiling OMAP DT files
Tony's comments (standardize comments, remove OMAP_ prefix)
From v1:
- Remove duplicated fix
- Remove OMAP_GPIO macro
- Add pinctrl constants
Florian Vaussard (5):
ARM: dts: OMAP2+: use #include for all device trees
ARM: dts: OMAP2+: use existing constants for GPIOs
ARM: dts: OMAP4/5: use
Replace /include/ by #include for OMAP2+ DT, in order to use the
C pre-processor, making use of #define features possible.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/boot/dts/omap2.dtsi |2 +-
arch
Use standard GPIO constants to enhance the readability of DT GPIOs.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/boot/dts/omap2.dtsi |2 ++
arch/arm/boot/dts/omap3-beagle-xm.dts |4 ++--
arch
Use the constants defined in include/dt-bindings/interrupt-controller/
to enhance readability.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi |8 +-
arch/arm/boot/dts/omap4-sdp.dts
Most of the constants are taken from arch/arm/mach-omap2/mux.h.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
include/dt-bindings/pinctrl/omap.h | 50
1 files changed, 50 insertions(+), 0
Using constants for pinctrl allows a better readability, and remove
redundancy with comments.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/boot/dts/omap2.dtsi |1 +
arch/arm/boot/dts/omap3-beagle.dts
On 05/27/2013 04:52 PM, Florian Vaussard wrote:
Hello,
Following a similar proposal by Stephen Warren for tegra [1], this series
makes use of the C preprocessor when compiling OMAP DT files, and
accomplishes some improvements to improve overall readability.
I realized that I should also
On 05/28/2013 05:07 PM, Stephen Warren wrote:
On 05/23/2013 09:36 AM, Florian Vaussard wrote:
Hello,
Following a similar proposal by Stephen Warren for tegra [1], this series
makes use of the C preprocessor when compiling OMAP DT files, and
accomplishes some improvements to improve overall
Hello Andreas,
On 03/05/2013 09:15 AM, Andreas Müller wrote:
On Mon, Mar 4, 2013 at 8:00 PM, Tony Lindgren t...@atomide.com wrote:
* Andreas Müller schnitzelt...@googlemail.com [130228 04:50]:
Can you please add a description here? Preferrably something
like With commit XYZ overo poweroff
Hello Benoit,
On 05/29/2013 10:46 AM, Benoit Cousson wrote:
Salut Florian,
On 05/28/2013 10:41 AM, Florian Vaussard wrote:
On 05/27/2013 04:52 PM, Florian Vaussard wrote:
Hello,
Following a similar proposal by Stephen Warren for tegra [1], this series
makes use of the C preprocessor when
Hello,
On 05/29/2013 10:53 AM, Benoit Cousson wrote:
+ Florian
Hi Afzal,
On 05/27/2013 04:37 PM, Afzal Mohammed wrote:
DT source (minimal) for AM4372 SoC to represent AM43x SoC's. Those
represented here are the minimal DT nodes necessary to get kernel
booting.
In DT nodes, ti,hwmod property
will follow shortly.
Best regards,
Florian
From v3:
- Rebased on Benoit's for_3.11/dts branch
From v2:
- Address Tony's comments (standardize comments, remove OMAP_ prefix)
From v1:
- Remove duplicated fix
- Remove OMAP_GPIO macro
- Add pinctrl constants
Florian Vaussard (5):
ARM: dts: OMAP2
Use the constants defined in include/dt-bindings/interrupt-controller/
to enhance readability.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
arch/arm/boot/dts/omap4-panda
Replace /include/ by #include for OMAP2+ DT, in order to use the
C pre-processor, making use of #define features possible.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
arch/arm
Most of the constants are taken from arch/arm/mach-omap2/mux.h.
Define some others for the PIN_OUTPUT_* flavours.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
include/dt-bindings
Using constants for pinctrl allows a better readability, and removes
redundancy with comments.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
arch/arm/boot/dts/omap2.dtsi
Use standard GPIO constants to enhance the readability of DT GPIOs.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
arch/arm/boot/dts/omap2.dtsi |2 ++
arch/arm/boot
Using constants for pinctrl allows a better readability, and removes
redundancy with comments.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/am335x-bone.dts | 18 +-
arch/arm/boot/dts/am335x-evm.dts | 28 ++--
arch
The pinctrl IP inside the AM33XX family differs slightly from
what is found on OMAP2+. Define a specific header to take account
of the differences.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
include/dt-bindings/pinctrl/am33xx.h | 19 +++
1 files changed, 19
Use standard GPIO constants to enhance the readability of DT GPIOs.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/am335x-bone.dts |8
arch/arm/boot/dts/am335x-evm.dts | 14 +++---
arch/arm/boot/dts/am335x-evmsk.dts | 16
Hello,
Gentle ping. Does someone has any comments on this fix? Can someone
tests on the real hardware?
Regards,
Florian
On 05/23/2013 10:11 AM, Florian Vaussard wrote:
Commit d36b4cd 'ARM: OMAP2+: Add additional GPMC timing parameters'
updated GPMC binding, but omap3-devkit8000
When making the dtbs target on OMAP/AM35xx, some trees are not
built.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/Makefile |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index
Hello,
When testing the OMAP/AM35xx DTS, I noticed that some platforms were missing
from the dtbs target, forcing the user to build them manually. This patch
corrects this.
Regards,
Florian
Since v1:
- Added AM35xx missing platforms
Florian Vaussard (1):
ARM: dts: OMAP4/AM35xx: Fix missing
Hello Dan,
On 05/31/2013 05:19 PM, Dan Murphy wrote:
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the LED definitions for the two boards into
the respective DTS
= v1v8;
v2v1-supply = v2v1;
I missed it during the conversion, thank you.
Reviewed-by: Florian Vaussard florian.vauss...@epfl.ch
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info
Hello Benoit,
On 05/31/2013 04:45 PM, Benoit Cousson wrote:
On 05/31/2013 04:05 PM, Florian Vaussard wrote:
When making the dtbs target on OMAP/AM35xx, some trees are not
built.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Thanks for the fix Florian.
I need to applied your AM
Hello Kevin,
On 06/01/2013 12:45 AM, Kevin Hilman wrote:
Ensure the console uart (UART3) on these boards is mux'd correctly, and
IO ring wakeup is enabled.
This is needed for serial console wakeups when using DT boot.
Signed-off-by: Kevin Hilman khil...@linaro.org
---
Hello Kevin,
On 06/01/2013 12:45 AM, Kevin Hilman wrote:
Using the gpio-keys bindings, configure the user button on Beagle
boards. Since the user button is enabled as a wakeup source, also
ensure the GPIO pin is mux'd correctly and has IO ring wakeups enabled,
so it can also wakeup from off
Hello Kevin,
On 06/01/2013 12:45 AM, Kevin Hilman wrote:
On most OMAP3 platforms, the twl4030 IRQ line is connected to the
SYS_NIRQ line on OMAP. Therefore, configure the defaults for the
SYS_NIRQ pin in the twl4030 DTS file.
Boards that hook up the twl4030 differently can easily override
Use standard GPIO constants to enhance the readability of DT GPIOs.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/am335x-bone.dts |8
arch/arm/boot/dts/am335x-evm.dts | 14 +++---
arch/arm/boot/dts/am335x-evmsk.dts | 16
The pinctrl IP inside the AM33XX family differs slightly from
what is found on OMAP2+. Define a specific header to take account
of the differences.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
include/dt-bindings/pinctrl/am33xx.h | 37 ++
1 files
Using constants for pinctrl allows a better readability, and removes
redundancy with comments.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/am335x-bone.dts | 18 +-
arch/arm/boot/dts/am335x-evm.dts | 58 ++--
arch
On 06/04/2013 12:19 AM, Kevin Hilman wrote:
Florian Vaussard florian.vauss...@epfl.ch writes:
Hello Kevin,
On 06/01/2013 12:45 AM, Kevin Hilman wrote:
On most OMAP3 platforms, the twl4030 IRQ line is connected to the
SYS_NIRQ line on OMAP. Therefore, configure the defaults
Hello,
Some very minor comments.
On 06/05/2013 08:46 AM, Sricharan R wrote:
From: Roger Quadros rog...@ti.com
Provide the RESET regulators for the USB PHYs, the USB Host
port modes and the PHY devices.
Also provide pin multiplexer information for the USB host
pins.
Cc: Roger Quadros
1 - 100 of 295 matches
Mail list logo
