All GPIO controller drivers have been migrated to use the struct
gpio_chip_ops virtual function table so the embeddeded function
pointers in struct gpio_chip can now be removed.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/gpio/gpiolib.c | 83
.
So this is an RFC patch-set to add a virtual table to be used by
GPIO chip controllers and consist of the following patches:
Javier Martinez Canillas (5):
gpio: add a vtable to abstract GPIO controller operations
gpiolib: set gpio_chip operations on add using a gpio_chip_ops
gpio: omap
-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/gpio/gpiolib.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index 761013f..f0cc93a 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -1188,6
pointers in
the object but there are some advantages on using the former approach.
This patch adds a struct gpio_chip_ops to be set by GPIO chip controllers.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
include/linux/gpio/driver.h | 47
The GPIO controller operations has been split to be stored
on a separate struct gpio_chip_ops virtual function table.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/gpio/gpio-twl4030.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff
The GPIO controller operations has been split to be stored
on a separate struct gpio_chip_ops virtual function table.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/gpio/gpio-omap.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions
. Having a zero
IRQ offset will be interpreted as a linear domain case while
a non-zero value will be interpreted as a legacy domain case.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/gpio/gpio-omap.c | 15 ---
1 file changed, 4 insertions(+), 11
to the list of maintainers for this
driver since that is what I've been doing lately anyways and that way tools
like get_maintainer.pl will hint people posting patches that I'm interested
in being cc'ed for this driver.
The patch-set is composed of the following patches:
Javier Martinez Canillas
The gpiochip_add() function can fail if the chip cannot
be registered so the return value has to be checked and
the error propagated in case it happens.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/gpio/gpio-omap.c | 16 +---
1 file changed, 13
config option.
So is better to add a boolean Kconfig option for this driver
that defaults to true if ARCH_OMAP is enabled.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/gpio/Kconfig | 7 +++
drivers/gpio/Makefile | 2 +-
2 files changed, 8 insertions(+), 1
in copy when sending patches for it.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f728ac2..fc0972e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6374,6 +6374,7 @@ F
Converts the GPIO OMAP driver to register its chained irq
handler and irqchip using the helpers in the gpiolib core.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/gpio/Kconfig | 1 +
drivers/gpio/gpio-omap.c | 107
The GPMC driver includes arch/arm/mach-omap2/common.h but
does not use anything on that header so it can be removed.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/gpmc.c | 1 -
1 file changed, 1
is made by the DT core so this code is not needed
anymore now that mach-omap2 related boards are DT-only.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/Makefile| 5 -
arch/arm/mach-omap2/gpmc
that OMAP2+ is DT-only.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/Makefile | 4 -
arch/arm/mach-omap2/board-flash.c | 245 --
arch/arm/mach-omap2/board-flash.h
Once OMAP2+ board files are removed, there is unused code that was only used
by legacy platform code and can be removed.
This patch-set depends on the series:
[PATCH 00/12] Drop omap3 board files and make mach-omap2 boot in DT only mode
[0]
and is composed of the following patches:
[RESEND
Hi Tony,
On Sat, Feb 22, 2014 at 10:59 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
This patch is based on commit:
016c12d2 (ARM: OMAP3: Fix hardware detection for omap3630 when booted with
device tree)
and fixes a boot hang due the IGEP board being wrongly
Hi Tony,
On Fri, Feb 28, 2014 at 3:57 PM, Tony Lindgren t...@atomide.com wrote:
* Javier Martinez Canillas jav...@dowhile0.org [140228 10:52]:
Hi Tony,
On Sat, Feb 22, 2014 at 10:59 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
This patch is based on commit
Hi Russell,
On Mon, Feb 24, 2014 at 3:03 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Mon, Feb 24, 2014 at 06:07:49PM +0100, Florian Vaussard wrote:
+ hdmi0: connector@0 {
+ compatible = hdmi-connector;
This looks way to generic a compatible string. Are you
This patch is based on commit:
016c12d2 (ARM: OMAP3: Fix hardware detection for omap3630 when booted with
device tree)
and fixes a boot hang due the IGEP board being wrongly initialized
as an OMAP3430 platform instead of an OMAP3630.
Signed-off-by: Javier Martinez Canillas javier.marti
/kernel/git/tomba/linux.git
work/dss-dt-review-3
I tested this branch on my DM3730 IGEPv2 and output display is working
correctly.
Tested-by: Javier Martinez Canillas jav...@dowhile0.org
Tomi
Javier Martinez Canillas (1):
ARM: omap3-igep0020.dts: add display information
Sebastian Reichel
Hello Christoph,
On 01/22/2014 04:04 PM, Christoph Fritz wrote:
DBB056 doesn't use DSI for its display, but omap3 forces this
erroneously for all its boards:
| OMAP DSS rev 2.0
| omapdss DPI error: can't get VDDS_DSI regulator
| omapfb omapfb: failed to connect default display
|
Hello Christoph,
On Tue, Jan 21, 2014 at 4:47 PM, Christoph Fritz
chf.fr...@googlemail.com wrote:
Full device tree support for omapdss is not yet accomplished. Until
then, init display by legacy platform code.
Signed-off-by: Christoph Fritz chf.fr...@googlemail.com
---
Hi Sebastian,
On Tue, Jan 21, 2014 at 9:24 PM, Sebastian Reichel s...@ring0.de wrote:
Hi,
On Tue, Jan 21, 2014 at 09:10:52PM -0300, Javier Martinez Canillas wrote:
On Tue, Jan 21, 2014 at 4:47 PM, Christoph Fritz wrote:
[PATCH]
I don't think that makes sense to add more legacy display
Hello Florian,
On Fri, Jan 17, 2014 at 10:22 AM, Florian Vaussard
florian.vauss...@epfl.ch wrote:
Hello Javier
On 01/09/2014 09:43 PM, Javier Martinez Canillas wrote:
[adding Enric Balletbo to cc]
Hello Florian,
On Thu, Jan 9, 2014 at 1:48 PM, Florian Vaussard
florian.vauss...@epfl.ch
[adding Enric Balletbo to cc]
Hello Florian,
On Thu, Jan 9, 2014 at 1:48 PM, Florian Vaussard
florian.vauss...@epfl.ch wrote:
MMC2 is used by the on-board WiFi module populated on some boards
(based on Marvell Libertas 8688 SDIO).
Note: currently WiFi only works on cold boot, as the module
Hi Kishon,
On Mon, Dec 9, 2013 at 7:07 AM, Kishon Vijay Abraham I kis...@ti.com wrote:
Hi,
On Saturday 07 December 2013 02:38 AM, Felipe Balbi wrote:
Hi,
On Fri, Dec 06, 2013 at 01:14:38PM +0100, Javier Martinez Canillas wrote:
On Fri, Dec 6, 2013 at 1:06 PM, Kishon Vijay Abraham I kis
Hi Tomi,
On Mon, Dec 9, 2013 at 1:06 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On 2013-12-06 10:41, Javier Martinez Canillas wrote:
Hi Tomi,
On Wed, Dec 4, 2013 at 1:28 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm
On Mon, Dec 9, 2013 at 1:01 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On 2013-12-07 06:28, Javier Martinez Canillas wrote:
Actually, I looked at drivers/video/omap2/connector-dvi.c and it does the
right
thing for legacy platform data probing but no for DT probing:
static int
Hi Tomi,
On Mon, Dec 9, 2013 at 1:56 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On 2013-12-06 10:57, Javier Martinez Canillas wrote:
+ tfp410: encoder@0 {
+ compatible = ti,tfp410;
+ gpios = gpio1 0 0; /* 0, power-down */
+
Please use the constants
Hi Tomi,
On Mon, Dec 9, 2013 at 4:30 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On 2013-12-09 17:09, Javier Martinez Canillas wrote:
Hi Tomi,
On Mon, Dec 9, 2013 at 1:56 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On 2013-12-06 10:57, Javier Martinez Canillas wrote:
+ tfp410
Hi Tomi,
On Wed, Dec 4, 2013 at 1:28 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts | 67
++
1 file changed, 67 insertions(+)
diff --git
Hi Tomi,
On Wed, Dec 4, 2013 at 1:28 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 102
++
1 file changed, 102 insertions(+)
diff --git
Hi Kishon,
On Fri, Dec 6, 2013 at 1:06 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
Previously MUSB wrapper (OMAP) device used PLATFORM_DEVID_AUTO while creating
MUSB core device. So in usb_bind_phy (binds the controller with the PHY), the
device name of the controller had *.auto* in it.
: Javier Martinez Canillas javier.marti...@collabora.co.uk
Date: Fri, 6 Dec 2013 02:53:38 +0100
Subject: [PATCH 1/1] ARM: dts: omap3-igep0020: add display information
The IGEPv2 has a TFP410 DPI-to-DVI encoder attached
to OMAP's Display SubSystem (DSS). Add DeviceTree
nodes for these devices
On 12/07/2013 04:48 AM, Javier Martinez Canillas wrote:
Hi Tomi,
On Wed, Dec 4, 2013 at 1:28 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Hi,
Here's a new version for DT support to OMAP Display Subsystem. See
http://article.gmane.org/gmane.linux.ports.arm.omap/102689 for the intro
[adding Pekon and Thomas as cc]
On Thu, Dec 5, 2013 at 6:13 PM, Tony Lindgren t...@atomide.com wrote:
* Peter Meerwald pme...@pmeerw.net [131205 08:13]:
I'd like to be able to update MLO and u-boot from within a booted Linux
system on the device (I have to resort to u-boot for that where I
Hi Ezequiel,
On Thu, Dec 5, 2013 at 7:26 PM, Ezequiel Garcia
ezequiel.gar...@free-electrons.com wrote:
Hi Javier,
(CCing Brian: What do you think about this?)
On Thu, Dec 05, 2013 at 06:39:10PM +0100, Javier Martinez Canillas wrote:
On Thu, Dec 5, 2013 at 6:13 PM, Tony Lindgren t
Hi Pekon,
On Mon, Dec 2, 2013 at 5:13 PM, Gupta, Pekon pe...@ti.com wrote:
From: Thomas Petazzoni [mailto:thomas.petazz...@free-electrons.com]
On Mon, 2 Dec 2013 11:00:35 -0500, Tom Rini wrote:
Although the new ECC schema breaks the compatibility between the board
files and new DT based
On Mon, Dec 2, 2013 at 5:24 PM, Tom Rini tr...@ti.com wrote:
On 12/02/2013 11:21 AM, Javier Martinez Canillas wrote:
Hi Pekon,
On Mon, Dec 2, 2013 at 5:13 PM, Gupta, Pekon pe...@ti.com wrote:
From: Thomas Petazzoni [mailto:thomas.petazz...@free-electrons.com]
On Mon, 2 Dec 2013 11:00:35
;
instead.
gpmc,sync-clk-ps = 0;
gpmc,cs-on-ns = 0;
--
1.8.1.2
--
Acked-by: Javier Martinez Canillas jav...@dowhile0.org
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo
Hi Grazvydas,
On Fri, Nov 29, 2013 at 12:57 AM, Grazvydas Ignotas nota...@gmail.com wrote:
On Tue, Nov 26, 2013 at 3:17 AM, Tony Lindgren t...@atomide.com wrote:
We can now boot all mach-omap2 related boards using appended device
tree by creating a related .dts file with pretty much the same
Hi Tony,
On Tue, Nov 26, 2013 at 1:14 AM, Tony Lindgren t...@atomide.com wrote:
Hi all,
We can finally make mach-omap2 to boot in device tree only mode for v3.14.
By doing that, we can get rid of about 2 lines of legacy code for v3.14
that's no longer needed with device tree :) And
that OMAP2+ is DT-only.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/mach-omap2/Makefile | 4 -
arch/arm/mach-omap2/board-flash.c | 245 --
arch/arm/mach-omap2/board-flash.h | 62 --
3 files changed, 311 deletions
Now that OMAP2+ board files are scheduled for removal for v3.14
there is unused code that was only used by legacy platform code
and can be removed.
This patch-set depends on the series:
[PATCH 00/12] Drop omap3 board files and make mach-omap2 boot in DT only mode
and is composed of the
is made by the DT core so this code is not needed
anymore now that mach-omap2 related boards are DT-only.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/mach-omap2/Makefile| 5 -
arch/arm/mach-omap2/gpmc-smc91x.c | 186
The GPMC driver includes arch/arm/mach-omap2/common.h but
does not use anything on that header so it can be removed.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/mach-omap2/gpmc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-omap2
On Wed, Nov 20, 2013 at 2:06 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
In order to make mach-omap2 Device Tree only, the board file for
IGEP boards was removed even when support for wifi and display
was still not supported by its DTS.
This is a second version
of :)
Javier Martinez Canillas patch did what I was thinking of in [0].
I dropped that patch from my series and posted a v2 that just name the
VPLL2 regulator as vdds_dsi [1]. That way will be safer for Tony and
Benoit to take this series as a fix for the -rc cycle since the
changes are contained within
Martinez Canillas javier.marti...@collabora.co.uk
Yours,
Linus Walleij
Thanks a lot and best regards,
Javier
--
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 at http://vger.kernel.org/majordomo
to use the TI AM/DM37x processor.
ARM: dts: AM33XX BASE0033: add pinmux and hdmi node to enable display
ARM: dts: AM33XX BASE0033: add pinmux and user led support.
ARM: dts: AM33XX BASE0033: add 32KBit EEPROM support.
ARM: dts: AM33XX IGEP0033: add USB support.
Javier Martinez
From: Enric Balletbo i Serra eballe...@gmail.com
Both, IGEPv2 and IGEP COM MODULE have a bus-width of 4 not 8, so fix this and
do not mux data pins from mmc1_data4 to mmc1_data7.
Signed-off-by: Enric Balletbo i Serra eballe...@gmail.com
---
arch/arm/boot/dts/omap3-igep.dtsi | 6 +-
1 file
From: Enric Balletbo i Serra eballe...@iseebcn.com
Add node to support the USB Host and the USB OTG on the IGEP AQUILA
Processor Board.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/am335x-igep0033.dtsi | 29 +
1 file changed, 29
boards after commit
06ff74fd (ARM: OMAP2+: remove legacy support for IGEP boards), the
i2c bus number has to be changed.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/mach-omap2/dss-common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Enric Balletbo i Serra eballe...@gmail.com
The LBEE1USJYC is a WiFi/BT combo module used on OMAP3-based IGEP boards. In
both cases, IGEPv2 Rev. C and IGEP COM MODULE, the module is connected using
the same MMC interface and uses the same GPIOs.
Signed-off-by: Enric Balletbo i Serra
From: Enric Balletbo i Serra eballe...@gmail.com
Enable the hdmi output and the LCD Controller on IGEP AQUILA. Also
configure the correct pinmux for output of video data from the SoC
to the HDMI encoder.
Signed-off-by: Enric Balletbo i Serra eballe...@gmail.com
---
From: Enric Balletbo i Serra eballe...@iseebcn.com
Enable the user leds on the IGEP AQUILA EXPANSION. The has two leds,
one green and one red, that are controllable by software.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/am335x-base0033.dts | 26
based on AM/DM37x
*
* Copyright (C) 2012 Javier Martinez Canillas jav...@collabora.co.uk
* Copyright (C) 2012 Enric Balletbo i Serra eballe...@gmail.com
@@ -10,7 +10,7 @@
*/
/dts-v1/;
-#include omap34xx.dtsi
+#include omap36xx.dtsi
/ {
memory {
diff --git a/arch/arm/boot/dts
From: Enric Balletbo i Serra eballe...@iseebcn.com
The IGEP AQUILA EXPANSION has a 32KBit EEPROM for user data storage.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/am335x-base0033.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git
The IGEPv2 has a TFP410 DPI-to-DVI encoder attached to OMAP's
Display SubSystem (DSS).
Add mux setup for DSS pins and also for the GPIO 170 pin that
is used to ensure that the DVI-D is powered down on power up.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm
on dpi_init_regulator().
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/omap3-igep0020.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-igep0020.dts
b/arch/arm/boot/dts/omap3-igep0020.dts
index b9a9e17..1c7e74d 100644
--- a/arch
Add pin muxing support for IGEP boards i2c controllers.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/omap3-igep.dtsi | 30 ++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-igep.dtsi
b/arch/arm
From: Enric Balletbo i Serra eballe...@iseebcn.com
Enable the user leds on the IGEP AQUILA EXPANSION. The has two leds,
one green and one red, that are controllable by software.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/am335x-base0033.dts | 26
.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/video/omap2/dss/dpi.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/video/omap2/dss/dpi.c b/drivers/video/omap2/dss/dpi.c
index bd48cde..e328f0b 100644
--- a/drivers/video/omap2/dss/dpi.c
+++ b
From: Enric Balletbo i Serra eballe...@gmail.com
The LBEE1USJYC is a WiFi/BT combo module used on OMAP3-based IGEP boards. In
both cases, IGEPv2 Rev. C and IGEP COM MODULE, the module is connected using
the same MMC interface and uses the same GPIOs.
Signed-off-by: Enric Balletbo i Serra
Add pin muxing support for IGEP boards i2c controllers.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/omap3-igep.dtsi | 30 ++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-igep.dtsi
b/arch/arm
From: Enric Balletbo i Serra eballe...@gmail.com
Enable the hdmi output and the LCD Controller on IGEP AQUILA. Also
configure the correct pinmux for output of video data from the SoC
to the HDMI encoder.
Signed-off-by: Enric Balletbo i Serra eballe...@gmail.com
---
The IGEPv2 has a TFP410 DPI-to-DVI encoder attached to OMAP's
Display SubSystem (DSS).
Add mux setup for DSS pins and also for the GPIO 170 pin that
is used to ensure that the DVI-D is powered down on power up.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm
based on AM/DM37x
*
* Copyright (C) 2012 Javier Martinez Canillas jav...@collabora.co.uk
* Copyright (C) 2012 Enric Balletbo i Serra eballe...@gmail.com
@@ -10,7 +10,7 @@
*/
/dts-v1/;
-#include omap34xx.dtsi
+#include omap36xx.dtsi
/ {
memory {
diff --git a/arch/arm/boot/dts
.
ARM: dts: AM33XX BASE0033: add pinmux and hdmi node to enable display
ARM: dts: AM33XX BASE0033: add pinmux and user led support.
ARM: dts: AM33XX BASE0033: add 32KBit EEPROM support.
ARM: dts: AM33XX IGEP0033: add USB support.
Javier Martinez Canillas (4):
ARM: dts
From: Enric Balletbo i Serra eballe...@iseebcn.com
Add node to support the USB Host and the USB OTG on the IGEP AQUILA
Processor Board.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/am335x-igep0033.dtsi | 29 +
1 file changed, 29
From: Enric Balletbo i Serra eballe...@gmail.com
Both, IGEPv2 and IGEP COM MODULE have a bus-width of 4 not 8, so fix this and
do not mux data pins from mmc1_data4 to mmc1_data7.
Signed-off-by: Enric Balletbo i Serra eballe...@gmail.com
---
arch/arm/boot/dts/omap3-igep.dtsi | 6 +-
1 file
boards after commit
06ff74fd (ARM: OMAP2+: remove legacy support for IGEP boards), the
i2c bus number has to be changed.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/mach-omap2/dss-common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Enric Balletbo i Serra eballe...@iseebcn.com
The IGEP AQUILA EXPANSION has a 32KBit EEPROM for user data storage.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/am335x-base0033.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git
On 11/16/2013 03:16 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [131116 05:25]:
In order to make mach-omap2 Device Tree only the board file for
IGEP boards was removed even when support for wifi and display
was still not supported by its DTS
On 11/16/2013 03:44 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [131116 05:25]:
From: Enric Balletbo i Serra eballe...@gmail.com
Most of the boards are using the TI AM/DM37x processor, there is only a small
quantity of IGEP Processor Boards based on TI
Hi Tony,
On 11/16/2013 03:18 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [131116 05:25]:
On Device Tree boot the VDDS_DSI regulator is not linked to
the DPI device so omapfb driver probing fails with:
[3.186035] OMAPFB: omapfb_probe
[3.190704
if multiple drivers need the same regulator under different
names.
-- Sebastian
So, what do you think about the following patch instead?
From 99f1c60f6db6cac07ea2c0398a9cbb3525dfdd72 Mon Sep 17 00:00:00 2001
From: Javier Martinez Canillas javier.marti...@collabora.co.uk
Date: Sat, 16 Nov 2013 17:59
Hi Sebastian,
On 11/17/2013 01:26 AM, Sebastian Reichel wrote:
Hi Javier,
On Sat, Nov 16, 2013 at 06:28:00PM +0100, Javier Martinez Canillas wrote:
The hack, as being sent by Javier, will result in the wrong
regulator being used on the Nokia N900, which is using vaux1.
It must depend
On 11/12/2013 09:51 PM, Ezequiel Garcia wrote:
Hey Javier,
Hi Ezequiel, thanks a lot for your feedback.
On Sat, Nov 09, 2013 at 05:34:02PM +0100, Javier Martinez Canillas wrote:
The OMAP2+ General-Purpose Memory Controller (GPMC) driver
should eventually be moved from arch/arm/mach-omap2
On 11/12/2013 11:12 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [131112 13:58]:
On 11/12/2013 09:51 PM, Ezequiel Garcia wrote:
I'm not too convinced about the above diffstat. Maybe you can try a
a better approach of making the move by: 1) renaming
The GPMC driver includes arch/arm/mach-omap2/common.h but
it does not use anything on that header so can be removed.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/mach-omap2/gpmc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-omap2
for taking the gpmc driver
outside arch/arm/mach-omap2 by moving its related headers
files to include/linux/platform_data.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Hi Tony,
I wonder what's your plan to move drivers outside of mach-omap2.
Currently this driver still
On Mon, Oct 28, 2013 at 2:32 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On 27/10/13 15:26, Javier Martinez Canillas wrote:
When booting with DT the omapfb's probe is deferred several times but
it always fails on dpi_connect() due not being able to get the
VDDS_DSI regulator
properly.
Those error prints should probably be tuned down a bit now that the
driver uses probe deferral.
Tomi
fwiw, my wip branch is [2]:
Javier Martinez Canillas (3):
ARM: dts: omap3-igep0020: Add pinmux setup for i2c devices
ARM: dts: omap3-igep0020: Add pinmuxig for DVI
Hi Ezequiel
On Wed, Oct 23, 2013 at 4:13 PM, Ezequiel Garcia
ezequiel.gar...@free-electrons.com wrote:
Pekon,
On Wed, Oct 23, 2013 at 01:55:58PM +, Gupta, Pekon wrote:
I'm wondering how are you testing this in your SOC_AM33XX board (which
is not ARCH_OMAP3). You probably have
On Sun, Oct 20, 2013 at 1:25 AM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
[cc'ing current Benoit's address instead of the old one]
On Sat, Oct 19, 2013 at 9:54 PM, Enric Balletbo i Serra
eballe...@gmail.com wrote:
Hi Benoit,
This series are some updates for IGEP boards
Hi Enric,
On Sat, Oct 19, 2013 at 9:54 PM, Enric Balletbo i Serra
eballe...@gmail.com wrote:
Both, IGEPv2 and IGEP COM MODULE have a bus-width of 4 not 8, so fix this and
do not mux data pins from mmc1_data5 to mmc1_data7.
I guess you meant pins from mmc1_data4 instead mmc1_data5? (i.e: only
Hi Enric,
On Sat, Oct 19, 2013 at 9:54 PM, Enric Balletbo i Serra
eballe...@gmail.com wrote:
The LBEE1USJYC is a WiFi/BT combo module used on OMAP3-based IGEP boards. In
both cases, IGEPv2 Rev. C and IGEP COM MODULE, the module is connected using
the same MMC interface and uses the same GPIOs.
so:
Reviewed-by: Javier Martinez Canillas jav...@collabora.co.uk
Enric Balletbo i Serra (3):
ARM: dts: omap3-igep: Fix bus-width for mmc1.
ARM: dts: omap3-igep: Add support for LBEE1USJYC WiFi connected to
SDIO.
ARM: dts: omap3-igep*: Update to use the TI AM/DM37x processor.
arch
On Fri, Oct 18, 2013 at 8:20 AM, NeilBrown ne...@suse.de wrote:
On Sat, 5 Oct 2013 13:17:09 +0200 Andreas Fenkart afenk...@gmail.com wrote:
The am335x can't detect pending cirq in PM runtime suspend.
This patch reconfigures dat1 as a GPIO before going to suspend.
SDIO interrupts are detected
for IGEP boards.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
MAINTAINERS | 2 +-
arch/arm/mach-omap2/board-igep0020.c | 683 ---
2 files changed, 1 insertion(+), 684 deletions(-)
delete mode 100644 arch/arm
for IGEP boards.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Changes since v1:
- Also remove the Kconfig and Makefile entries for IGEP boards.
MAINTAINERS | 2 +-
arch/arm/mach-omap2/Kconfig | 13 -
arch/arm/mach-omap2/Makefile
On Fri, Oct 18, 2013 at 5:24 PM, Tony Lindgren t...@atomide.com wrote:
* Kevin Hilman khil...@linaro.org [131018 07:49]:
Hi Tony,
Tony Lindgren t...@atomide.com writes:
The following changes since commit
f41509ad0d4c11d0911630440749d409ce2aa1aa:
Merge branches 'omap-for-v3.13/dt'
On Sat, Oct 19, 2013 at 1:14 AM, NeilBrown ne...@suse.de wrote:
On Fri, 18 Oct 2013 12:12:48 +0200 Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
On Fri, Oct 18, 2013 at 8:20 AM, NeilBrown ne...@suse.de wrote:
On Sat, 5 Oct 2013 13:17:09 +0200 Andreas Fenkart afenk...@gmail.com
On 10/16/2013 10:06 AM, Linus Walleij wrote:
On Wed, Oct 16, 2013 at 2:47 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
The OMAP GPIO driver keeps track about GPIO pins that are
used as IRQ lines for two reasons:
1) To prevent GPIO banks to be disabled while one
GPIO pins as used as IRQ lines
so the GPIO core only allows to set as output GPIO pins not
tied to an IRQ. So there is no need to have custom code for 2).
The IRQ usage still has to be maintained locally for 1) though.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
On 10/09/2013 08:02 AM, Tomi Valkeinen wrote:
Hi Tony,
On 09/10/13 00:11, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [131004 20:00]:
IGEPv2 board has both an DVI and TFP410 video interfaces but
DSS support for DeviceTree has not yet landed in mainline so
On 10/09/2013 08:00 AM, Tomi Valkeinen wrote:
Hi,
Hi Tomi, thanks a lot for your feedback.
On 05/10/13 05:51, Javier Martinez Canillas wrote:
IGEPv2 board has both an DVI and TFP410 video interfaces but
DSS support for DeviceTree has not yet landed in mainline so
is necessary to init
On 10/09/2013 09:47 AM, Tomi Valkeinen wrote:
On 09/10/13 10:44, Javier Martinez Canillas wrote:
I can't do it yet because the two are still needed for different boot paths.
Once the board DTS has all the hardware support that is currently available
on
the board file I'll delete the board
201 - 300 of 610 matches
Mail list logo
