legacy code that only enables read wait monitoring for
non-OMAP3 devices. There are no known OMAP3 device issues that prevent
this feature being enabled and so when booting with device-tree use the
wait-monitoring settings described in the device-tree blob.
Signed-off-by: Jon Hunter jon-hun...@ti.com
NOR flash is not currently supported when booting with device-tree
on OMAP2+ devices. Add support to detect and configure NOR devices
when booting with device-tree.
Add documentation for the TI GPMC NOR binding.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
Documentation/devicetree/bindings
If the device-tree blob is present during boot, then register the SDMA
controller with the device-tree DMA driver so that we can use device-tree
to look-up DMA client information.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
Acked-by: Santosh Shilimkar
]
http://git.infradead.org/users/vkoul/slave-dma.git/shortlog/refs/heads/topic/dmaengine_dt
[4] http://permalink.gmane.org/gmane.linux.kernel.spi.devel/12508
[5] http://permalink.gmane.org/gmane.linux.ports.arm.omap/93165
[6] http://permalink.gmane.org/gmane.linux.kernel/1435002
Jon Hunter (2):
ARM
Add SDMA controller binding for OMAP2+ devices and populate DMA client
information for SPI and MMC periperhal on OMAP3+ devices. Please note
that OMAP24xx devices do not have SPI and MMC bindings available yet and
so DMA client information is not populated.
Signed-off-by: Jon Hunter jon-hun
On 02/26/2013 04:01 AM, Javier Martinez Canillas wrote:
[snip]
I was wondering if the level/edge settings for gpios is working on OMAP.
I'm adding DT support for an SMSC911x ethernet chip connected to the
GPMC for an OMAP3 SoC based board.
In the smsc911x driver probe function
On 02/26/2013 04:44 PM, Stephen Warren wrote:
On 02/26/2013 03:40 PM, Jon Hunter wrote:
On 02/26/2013 04:01 AM, Javier Martinez Canillas wrote:
[snip]
I was wondering if the level/edge settings for gpios is working on OMAP.
I'm adding DT support for an SMSC911x ethernet chip connected
On 02/26/2013 04:01 AM, Javier Martinez Canillas wrote:
[snip]
I was wondering if the level/edge settings for gpios is working on OMAP.
I'm adding DT support for an SMSC911x ethernet chip connected to the
GPMC for an OMAP3 SoC based board.
In the smsc911x driver probe function
On 02/26/2013 05:06 PM, Stephen Warren wrote:
On 02/26/2013 04:01 PM, Jon Hunter wrote:
On 02/26/2013 04:44 PM, Stephen Warren wrote:
On 02/26/2013 03:40 PM, Jon Hunter wrote:
On 02/26/2013 04:01 AM, Javier Martinez Canillas wrote:
[snip]
I was wondering if the level/edge settings
On 02/26/2013 06:13 PM, Stephen Warren wrote:
On 02/26/2013 04:45 PM, Jon Hunter wrote:
On 02/26/2013 05:06 PM, Stephen Warren wrote:
On 02/26/2013 04:01 PM, Jon Hunter wrote:
On 02/26/2013 04:44 PM, Stephen Warren wrote:
On 02/26/2013 03:40 PM, Jon Hunter wrote:
On 02/26/2013 04:01 AM
On 02/26/2013 09:47 PM, Javier Martinez Canillas wrote:
On Wed, Feb 27, 2013 at 12:08 AM, Jon Hunter jon-hun...@ti.com wrote:
On 02/26/2013 04:01 AM, Javier Martinez Canillas wrote:
[snip]
I was wondering if the level/edge settings for gpios is working on OMAP.
I'm adding DT support
omap_irq_type is called.
commit 5e298de564e09f5ca4148a9bc0ed5d16b4742f14
Author: Jon Hunter jon-hun...@ti.com
Date: Wed Feb 27 17:14:11 2013 -0600
gpio/omap: warn if gpio bank is not enabled on setting irq type
diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
index f1fbedb2..cbdc796
will simplify code and ease the
migration to device-tree.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 65
arch/arm/mach-omap2/gpmc.h |6
2 files changed, 71 insertions(+)
diff --git a/arch/arm/mach-omap2
devices as no boards are currently
setting the dev_ready variable.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc-nand.c | 35 +++
1 file changed, 23 insertions(+), 12 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc-nand.c
b
On 02/28/2013 09:52 AM, Jon Hunter wrote:
On 02/28/2013 12:05 AM, Philip, Avinash wrote:
On Tue, Feb 26, 2013 at 23:00:31, Hunter, Jon wrote:
The GPMC has various different configuration options such as bus-width,
synchronous or asychronous mode selection, burst mode options etc.
Currently
On 02/28/2013 06:17 AM, Javier Martinez Canillas wrote:
On Thu, Feb 28, 2013 at 12:16 AM, Jon Hunter jon-hun...@ti.com wrote:
On 02/26/2013 09:57 PM, Javier Martinez Canillas wrote:
[snip]
Something like that would definitely solve the GPIO request issue but
we still have the issue
On 02/28/2013 06:09 PM, Linus Walleij wrote:
On Thu, Feb 28, 2013 at 2:04 PM, Benoit Cousson b-cous...@ti.com wrote:
On 02/28/2013 12:41 AM, Linus Walleij wrote:
On Wed, Feb 15, 2012 at 5:04 PM, Benoit Cousson b-cous...@ti.com wrote:
Gosh! That's pretty old stuff :-)
Hm yeah, haha :-)
On 02/28/2013 11:33 PM, Philip, Avinash wrote:
On Thu, Feb 28, 2013 at 22:42:37, Hunter, Jon wrote:
On 02/28/2013 09:52 AM, Jon Hunter wrote:
On 02/28/2013 12:05 AM, Philip, Avinash wrote:
On Tue, Feb 26, 2013 at 23:00:31, Hunter, Jon wrote:
The GPMC has various different configuration
.
The programming of where the wait-pin is also moved slightly, but this
will not have any impact to existing devices as no boards are currently
setting the dev_ready variable.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc-nand.c | 35
interrupts are working on OMAP5912 OSK, OMAP2420 H4,
OMAP3430 SDP and OMAP4430 SDP by making sure networking was working
correctly as these boards use a GPIO with the ethernet chips. Also
checked /proc/interrupts to ensure GPIO interrupt counts are
incrementing as expected.
Jon Hunter (2):
gpio
to simplify the logic in the OMAP
gpio_irq_handler() routine, by using irq_find_mapping() to obtain the
virtual irq number from the GPIO bank and bank index.
Reported-by: Linus Walleij linus.wall...@linaro.org
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
drivers/gpio/gpio-omap.c | 72
if this is detected.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
drivers/gpio/gpio-omap.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
index c3598d1..0d30c7a 100644
--- a/drivers/gpio/gpio-omap.c
+++ b/drivers/gpio/gpio-omap.c
On 03/01/2013 03:42 PM, Ezequiel Garcia wrote:
On Fri, Mar 1, 2013 at 6:08 PM, Ezequiel Garcia elezegar...@gmail.com wrote:
Hi Jon,
Yet more questions :-) See below...
On Wed, Feb 13, 2013 at 7:07 PM, Jon Hunter jon-hun...@ti.com wrote:
You don't need this extra entry if you add simple
On 03/01/2013 03:25 PM, Ezequiel Garcia wrote:
Hi Jon,
On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
[...]
+static int gpmc_probe_nor_child(struct platform_device *pdev,
+ struct device_node *child)
+{
+ struct gpmc_settings
On 03/01/2013 02:11 PM, Ezequiel Garcia wrote:
Hi Jon,
On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
[...]
+ if (!of_property_read_u32(np, gpmc,bus-turnaround, val))
+ gpmc_t-bus_turnaround = val;
+
AFAIK, you don't need to test
On 03/01/2013 02:12 PM, Ezequiel Garcia wrote:
On Fri, Mar 1, 2013 at 5:11 PM, Ezequiel Garcia elezegar...@gmail.com wrote:
Hi Jon,
On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
[...]
+ if (!of_property_read_u32(np, gpmc,bus-turnaround, val
On 03/01/2013 11:30 AM, Russell King - ARM Linux wrote:
On Fri, Mar 01, 2013 at 05:17:57PM +0100, Javier Martinez Canillas wrote:
unsigned long irq_flags = SMC_IRQ_FLAGS;
...
if (irq_flags == -1 || ires-flags IRQF_TRIGGER_MASK)
irq_flags = ires-flags
On 03/02/2013 05:48 AM, Felipe Balbi wrote:
On Fri, Mar 01, 2013 at 11:22:47AM -0600, Jon Hunter wrote:
Currently the OMAP GPIO driver uses a legacy mapping for the GPIO IRQ
domain. This is not necessary because we do not need to assign a
specific interrupt number to the GPIO IRQ domain
On 03/04/2013 05:57 AM, Ezequiel Garcia wrote:
Hi Jon,
On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
+
+Example:
+
+gpmc: gpmc@6e00 {
+ compatible = ti,omap3430-gpmc, simple-bus;
I'm concern about using simple-bus, and I'm not entirely sure
On 03/04/2013 11:11 AM, Felipe Balbi wrote:
On Mon, Mar 04, 2013 at 11:06:12AM -0600, Jon Hunter wrote:
On 03/02/2013 05:48 AM, Felipe Balbi wrote:
On Fri, Mar 01, 2013 at 11:22:47AM -0600, Jon Hunter wrote:
Currently the OMAP GPIO driver uses a legacy mapping for the GPIO IRQ
domain
On 03/04/2013 11:51 AM, Jon Hunter wrote:
On 03/04/2013 05:57 AM, Ezequiel Garcia wrote:
Hi Jon,
On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
+
+Example:
+
+gpmc: gpmc@6e00 {
+ compatible = ti,omap3430-gpmc, simple-bus;
I'm concern about using simple
specific properties:
- ti,hwmods: Name of the hwmod associated to the GPIO:
Thanks. Do you mind putting interrupt-controller before
#interrupt-cells as I see this is how they have it in
Documenation/devicetree/bindings/interrupt-controller/interrupts.txt?
Otherwise ...
Acked-by: Jon Hunter jon-hun
to the patchset cleaning redundant checks
It has been tested on a IGEP v2 board with OneNAND,
which means the gpmc-nand patch is tested by compilation only.
Altough this patchset is almost trivial,
any feedback or testing is more than welcome.
Thanks to Jon Hunter for his kind review!
Looks good
On 03/05/2013 08:34 AM, Mark Jackson wrote:
On 26/02/13 17:30, Jon Hunter wrote:
NOR flash is not currently supported when booting with device-tree
on OMAP2+ devices. Add support to detect and configure NOR devices
when booting with device-tree.
Add documentation for the TI GPMC NOR binding
On 03/05/2013 10:20 AM, Mark Jackson wrote:
On 05/03/13 14:46, Jon Hunter wrote:
On 03/05/2013 08:34 AM, Mark Jackson wrote:
On 26/02/13 17:30, Jon Hunter wrote:
NOR flash is not currently supported when booting with device-tree
on OMAP2+ devices. Add support to detect and configure NOR
On 03/05/2013 11:43 AM, Ezequiel Garcia wrote:
Hi Jon,
On Tue, Mar 5, 2013 at 2:30 PM, Jon Hunter jon-hun...@ti.com wrote:
This really highlights a weakness in the GPMC driver, particularly
for NOR, where the child device can only be probed once the parent
is probed. I don't see
On 03/05/2013 11:30 AM, Jon Hunter wrote:
On 03/05/2013 10:20 AM, Mark Jackson wrote:
[snip]
But I can see in physmap_of.c that the device gets registered without any
call to
devm_pinctrl_get_select_default() and hence no probe deferring takes place
is the
pinctrl device hasn't yet been
causes regression on omap3,4 platform
which are not yet dma dt adapted.
It is best to send this patch along with Jon Hunter dma dt series,
which adds dt dma support and mmc dma data. DMA dt series is needed
any way before hwmod cleanup can happen.
*sigh* ok, I should have never split this stuff
On 03/06/2013 07:30 AM, Mark Jackson wrote:
On 06/03/13 10:23, Mark Jackson wrote:
On 05/03/13 21:34, Jon Hunter wrote:
On 03/05/2013 11:30 AM, Jon Hunter wrote:
On 03/05/2013 10:20 AM, Mark Jackson wrote:
[snip]
But I can see in physmap_of.c that the device gets registered without any
On 03/06/2013 05:58 AM, Ezequiel Garcia wrote:
Jon,
On Tue, Mar 5, 2013 at 6:34 PM, Jon Hunter jon-hun...@ti.com wrote:
By the way, with this version you should remove simple-bus from your
gpmc node compatible strings. I now call of_platform_device_create() to
create the child device
On 03/06/2013 10:48 AM, Mark Jackson wrote:
On 06/03/13 16:44, Jon Hunter wrote:
On 03/06/2013 07:30 AM, Mark Jackson wrote:
On 06/03/13 10:23, Mark Jackson wrote:
snip
[1.541884] gpmc_probe_nor_child 1
[1.545483] GPMC_CS_CONFIG7_0 : 0f48
[1.549621] GPMC_CS_CONFIG7_1
On 03/06/2013 11:00 AM, Jon Hunter wrote:
On 03/06/2013 10:48 AM, Mark Jackson wrote:
On 06/03/13 16:44, Jon Hunter wrote:
On 03/06/2013 07:30 AM, Mark Jackson wrote:
On 06/03/13 10:23, Mark Jackson wrote:
snip
[1.541884] gpmc_probe_nor_child 1
[1.545483] GPMC_CS_CONFIG7_0
On 03/05/2013 04:13 AM, Mark Jackson wrote:
When setting the GPMC device type, make sure any previous
bits are cleared down, before applying the new setting.
Signed-off-by: Mark Jackson m...@newflow.co.uk
---
Changes in v2:
- Change mux type to 2 bits
- Add extra mux types in gpmc.h
On 03/06/2013 04:39 PM, Jon Hunter wrote:
On 03/05/2013 04:13 AM, Mark Jackson wrote:
When setting the GPMC device type, make sure any previous
bits are cleared down, before applying the new setting.
Signed-off-by: Mark Jackson m...@newflow.co.uk
---
Changes in v2:
- Change mux type
On 03/02/2013 02:05 PM, Grant Likely wrote:
On Tue, 26 Feb 2013 17:01:22 -0600, Jon Hunter jon-hun...@ti.com wrote:
On 02/26/2013 04:44 PM, Stephen Warren wrote:
On 02/26/2013 03:40 PM, Jon Hunter wrote:
On 02/26/2013 04:01 AM, Javier Martinez Canillas wrote:
Are you requesting the gpio
the flags member
of the structure is used. Simplify the code by only passing the flags
member and not the entire structure.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc-onenand.c | 26 ++
1 file changed, 10 insertions(+), 16 deletions(-)
diff
not using
device-tree is fine.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index 6ddecc8..452617b 100644
--- a/arch/arm/mach-omap2/gpmc.c
timing structure and some are directly programmed
into the GPMC configuration register. Add a new structure to store
these options and convert code to use this structure. Adding this
structure will allow us to create a common function for configuring
these options.
Signed-off-by: Jon Hunter jon
-gpmc-for-v3.10
[4] https://github.com/jonhunter/linux/tree/omap-dt-for-v3.10
Jon Hunter (17):
ARM: OMAP2+: Simplify code configuring ONENAND devices
ARM: OMAP2+: Add variable to store number of GPMC waitpins
ARM: OMAP2+: Add structure for storing GPMC settings
ARM: OMAP2+: Add function
Convert the OMAP2+ ONENAND code to use the gpmc_cs_program_settings()
function for configuring the various GPMC options instead of directly
programming the CONFIG1 register.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc-onenand.c | 61
dynamically
at runtime.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc-smc91x.c | 30 +-
1 file changed, 17 insertions(+), 13 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc-smc91x.c
b/arch/arm/mach-omap2/gpmc-smc91x.c
index 4b78338
Convert the OMAP2+ TUSB code to use the gpmc_cs_program_settings()
function for configuring the various GPMC options instead of directly
programming the CONFIG1 register.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/usb-tusb6010.c | 43
that support the
address-address-data multiplexing mode.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 100
arch/arm/mach-omap2/gpmc.h |6 +++
2 files changed, 106 insertions(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch
to be set once
regardless of whether the gpmc timing is changing dynamically at runtime.
The programming of where the wait-pin is also moved slightly, but this
will not have any impact to existing devices as no boards are currently
setting the dev_ready variable.
Signed-off-by: Jon Hunter jon-hun
Adds a function to read the various GPMC chip-select settings from
device-tree and store them in the gpmc_settings structure.
Update the GPMC device-tree binding documentation to describe these
options.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
Documentation/devicetree/bindings/bus/ti
When booting with device-tree, retrieve GPMC settings for NAND from
the device-tree blob. This will allow us to remove all static settings
stored in the gpmc-nand.c in the future once the migration to
device-tree is complete.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2
enabling a GPMC chip-select, ensure that the base address is aligned
to the appropriate boundary.
Reported-by: Mark Jackson mpfj-l...@mimc.co.uk
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 22 +++---
1 file changed, 19 insertions(+), 3 deletions
NOR flash is not currently supported when booting with device-tree
on OMAP2+ devices. Add support to detect and configure NOR devices
when booting with device-tree.
Add documentation for the TI GPMC NOR binding.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
Documentation/devicetree/bindings
With the addition of the gpmc_cs_program_settings(), we no longer need
or use gpmc_cs_configure() to configure some of the GPMC chip-select
options. So rename the function to gpmc_configure() and remove code that
modifies options in the CONFIG1 register.
Signed-off-by: Jon Hunter jon-hun
legacy code that only enables read wait monitoring for
non-OMAP3 devices. There are no known OMAP3 device issues that prevent
this feature being enabled and so when booting with device-tree use the
wait-monitoring settings described in the device-tree blob.
Signed-off-by: Jon Hunter jon-hun...@ti.com
before they can use the GPMC and on requesting a
chip-select, if memory has not already been reserved for the chip-select
then it will be.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 24 +++-
1 file changed, 7 insertions(+), 17 deletions
With commit 21cc2bd (ARM: OMAP2+: Remove apollon board support) the
variable boot_rom_space is now not needed and the code surrounding
this variable can be cleaned up and simplified. Remove unnecessary
definitions and clean-up the comment as well.
Signed-off-by: Jon Hunter jon-hun...@ti.com
() function, only for OMAP3430
is also incorrect as it is applicable to all OMAP3+ devices. So correct
this too.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
Documentation/devicetree/bindings/bus/ti-gpmc.txt | 25 +-
arch/arm/mach-omap2/gpmc.c| 93
SPI patch from Felipe Balbi [2].
[1] https://patchwork.kernel.org/patch/2057111/
[2] https://patchwork.kernel.org/patch/2134711/
Jon Hunter (9):
ARM: OMAP2+: Prepare for device-tree PMU support
ARM: dts: OMAP2+: Add PMU nodes
ARM: dts: OMAP2+: Add SDMA controller bindings and nodes
ARM: dts
driver) and so ensure that this
indicated on boot with or without device-tree.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/pmu.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2
Adds basic device-tree support for OMAP3430 SDP board which has 256MB
of RAM and uses the TWL4030 power management IC.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3430-sdp.dts | 46
2
to the absence of a cross-trigger
interface driver.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2.dtsi |5 +
arch/arm/boot/dts/omap3.dtsi |6 ++
arch/arm/boot/dts/omap4-panda-es.dts |2 ++
arch/arm/boot/dts/omap4460.dtsi | 18
Add the device-tree node for GPMC on OMAP2, OMAP4 and OMAP5 devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2420.dtsi | 11 +++
arch/arm/boot/dts/omap2430.dtsi | 11 +++
arch/arm/boot/dts/omap4.dtsi| 11 +++
arch/arm/boot/dts/omap5
Add gpios bindings for OMAP2420 and OMAP2430 devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2420.dtsi | 44 +++
arch/arm/boot/dts/omap2430.dtsi | 55 +++
2 files changed, 99 insertions(+)
diff
Add the device-tree nodes for the 128MB ONENAND flash and 256MB NAND
flash memories found on the OMAP3430 SDP board.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap3430-sdp.dts | 95
1 file changed, 95 insertions(+)
diff --git a/arch
Add SDMA controller binding for OMAP2+ devices and populate DMA client
information for SPI and MMC periperhal on OMAP3+ devices. Please note
that OMAP24xx devices do not have SPI and MMC bindings available yet and
so DMA client information is not populated.
Signed-off-by: Jon Hunter jon-hun
The OMAP3 gpio bindings are currently missing the reg and interrupt
properties and so add these properties.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap3.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm
) and polarity (high or low) of the interrupt. The OMAP gpio
controllers support these options and so update the #interrupt-cells
property for OMAP3+ devices to 2.
[1] Documentation/devicetree/bindings/gpio/gpio-omap.txt
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap3.dtsi
On 03/08/2013 02:25 PM, Javier Martinez Canillas wrote:
On Fri, Mar 8, 2013 at 6:27 PM, Jon Hunter jon-hun...@ti.com wrote:
Add the device-tree node for GPMC on OMAP2, OMAP4 and OMAP5 devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2420.dtsi | 11
On 03/10/2013 12:18 PM, Javier Martinez Canillas wrote:
Besides being used to interface with external memory devices,
the General-Purpose Memory Controller can be used to connect
Pseudo-SRAM devices such as ethernet controllers to OMAP2+
processors using the GPMC as a data bus.
The actual
On 03/08/2013 08:25 PM, Anil Kumar wrote:
Hi Jon,
On Fri, Mar 8, 2013 at 10:57 PM, Jon Hunter jon-hun...@ti.com wrote:
Adds basic device-tree support for OMAP3430 SDP board which has 256MB
of RAM and uses the TWL4030 power management IC.
I think this board support should be in separate
On 03/10/2013 09:45 PM, Anil Kumar wrote:
Hi Jon,
On Fri, Mar 8, 2013 at 10:57 PM, Jon Hunter jon-hun...@ti.com wrote:
Adds basic device-tree support for OMAP3430 SDP board which has 256MB
of RAM and uses the TWL4030 power management IC.
Signed-off-by: Jon Hunter jon-hun...@ti.com
On 03/09/2013 06:42 AM, Ezequiel Garcia wrote:
On Fri, Mar 8, 2013 at 10:25 PM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
On Fri, Mar 8, 2013 at 10:41 PM, Jon Hunter jon-hun...@ti.com wrote:
Yes you are correct. In general, I have been trying to stay some-what
consistent with what
On 03/11/2013 12:57 PM, Javier Martinez Canillas wrote:
On 03/11/2013 06:13 PM, Jon Hunter wrote:
Hi Jon, thanks a lot for your feedback.
On 03/10/2013 12:18 PM, Javier Martinez Canillas wrote:
Besides being used to interface with external memory devices,
the General-Purpose Memory
On 03/11/2013 09:42 PM, Kumar, Anil wrote:
On Mon, Mar 11, 2013 at 23:23:32, Hunter, Jon wrote:
On 03/08/2013 08:25 PM, Anil Kumar wrote:
Hi Jon,
On Fri, Mar 8, 2013 at 10:57 PM, Jon Hunter jon-hun...@ti.com wrote:
Adds basic device-tree support for OMAP3430 SDP board which has 256MB
be preferred. I don't see any downside in
taking this one and then having Vinod take the other later.
On 02/26/2013 07:27 PM, Jon Hunter wrote:
Add SDMA controller binding for OMAP2+ devices and populate DMA client
information for SPI and MMC periperhal on OMAP3+ devices. Please note
typo
Hi Javier,
On 03/14/2013 10:09 AM, Javier Martinez Canillas wrote:
Besides being used to interface with external memory devices,
the General-Purpose Memory Controller can be used to connect
Pseudo-SRAM devices such as ethernet controllers to OMAP2+
processors using the TI GPMC as a data bus.
On 03/14/2013 10:45 AM, Benoit Cousson wrote:
On 03/11/2013 06:56 PM, Jon Hunter wrote:
On 03/09/2013 06:42 AM, Ezequiel Garcia wrote:
On Fri, Mar 8, 2013 at 10:25 PM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
On Fri, Mar 8, 2013 at 10:41 PM, Jon Hunter jon-hun...@ti.com wrote
On 03/14/2013 10:45 AM, Florian Vaussard wrote:
Hi Benoit,
On 03/14/2013 03:57 PM, Benoit Cousson wrote:
Salut Jon,
On 03/08/2013 06:27 PM, Jon Hunter wrote:
Various OMAP device-tree updates for PMU, DMA, GPIO, GPMC and boards.
The DMA, PMU and OMAP3430 SDP board changes have been sent
On 03/14/2013 10:09 AM, Javier Martinez Canillas wrote:
gpmc_probe_nor_child() calls of_platform_device_create() to create a
platform device for the NOR child. If this function fails the value
of ret is returned to the caller but this value is zero since it was
assigned the return of a
On 03/14/2013 04:08 PM, Javier Martinez Canillas wrote:
Javier
Hi Jon,
On 14/03/2013, at 21:43, Jon Hunter jon-hun...@ti.com wrote:
On 03/14/2013 03:33 PM, Javier Martinez Canillas wrote:
Besides being used to interface with external memory devices,
the General-Purpose Memory
On 03/14/2013 03:58 PM, Nishanth Menon wrote:
The following series arose from trying to use BeagleBoard-XM (OMAP3 variant)
for doing CPU DVFS using cpufreq-cpu0. This series will eventually result in
migrating the cpufreq support only through device tree (part of the effort
to migrate away
On 03/14/2013 03:58 PM, Nishanth Menon wrote:
Add DT OPP table for OMAP34xx family of devices. This data is
decoded by OF with of_init_opp_table() helper function.
This is in preparation to use generic cpu0-cpufreq driver.
No mention here about what you are removing ;-)
Jon
--
To
On 03/14/2013 03:58 PM, Nishanth Menon wrote:
Add DT OPP table for OMAP36xx family of devices. This data is
decoded by OF with of_init_opp_table() helper function. This
overrides the default OMAP34xx CPU OPP table definition.
Not sure I following the last sentence. The tables are in a
On 03/14/2013 03:58 PM, Nishanth Menon wrote:
OMAP4430 and 4460 have different OPP definitions. So, create an SoC
variant dtsi file for 4460 and move the OPP definitions to it.
FYI, I had to create a similar file for PMU [1]. However, I called it
omap4460.dtsi and not omap446x.dtsi as there is
-for-v3.10
Jon Hunter (8):
ARM: OMAP2+: Prepare for device-tree PMU support
ARM: dts: OMAP2+: Add PMU nodes
ARM: dts: OMAP2+: Add SDMA controller bindings and nodes
ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5
ARM: dts: Add OMAP2 gpio bindings
ARM: dts: OMAP3+: Correct gpio
driver) and so ensure that this
indicated on boot with or without device-tree.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/pmu.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2
to the absence of a cross-trigger
interface driver.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2.dtsi |5 +
arch/arm/boot/dts/omap3.dtsi |6 ++
arch/arm/boot/dts/omap4-panda-es.dts |2 ++
arch/arm/boot/dts/omap4460.dtsi | 18
Add the device-tree node for GPMC on OMAP2, OMAP4 and OMAP5 devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2420.dtsi | 11 +++
arch/arm/boot/dts/omap2430.dtsi | 11 +++
arch/arm/boot/dts/omap4.dtsi| 11 +++
arch/arm/boot/dts/omap5
Add gpios bindings for OMAP2420 and OMAP2430 devices.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2420.dtsi | 44 +++
arch/arm/boot/dts/omap2430.dtsi | 55 +++
2 files changed, 99 insertions(+)
diff
The OMAP3 gpio bindings are currently missing the reg and interrupt
properties and so add these properties.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap3.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm
) and polarity (high or low) of the interrupt. The OMAP gpio
controllers support these options and so update the #interrupt-cells
property for OMAP3+ devices to 2.
[1] Documentation/devicetree/bindings/gpio/gpio-omap.txt
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap3.dtsi
Adds basic device-tree support for OMAP3430 SDP board which has 256MB
of RAM, 128MB ONENAND flash, 256MB NAND flash and uses the TWL4030
power management IC.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/omap3430-sdp.dts | 141
Add SDMA controller binding for OMAP2+ devices and populate DMA client
information for SPI and MMC peripheral on OMAP3+ devices. Please note
that OMAP24xx devices do not have SPI and MMC bindings available yet and
so DMA client information is not populated.
Signed-off-by: Jon Hunter jon-hun
On 03/15/2013 08:56 AM, Nishanth Menon wrote:
On 16:44-20130314, Jon Hunter wrote:
On 03/14/2013 03:58 PM, Nishanth Menon wrote:
Add DT OPP table for OMAP36xx family of devices. This data is
decoded by OF with of_init_opp_table() helper function. This
overrides the default OMAP34xx CPU OPP
901 - 1000 of 1153 matches
Mail list logo
