.
Javier Martinez Canillas (3):
Documentation: dt: update TI GPMC ethernet binding properties
ARM: OMAP2+: only search for GPMC DT child nodes on probe
ARM: OMAP2+: only WARN if a GPMC child probe function fail
Jon Hunter (1):
Documentation: dt: update properties in TI
the property gpmc,device-nand as a required property and also
updated the example. However, this property is redundant and not needed
because the GPMC child device node for NAND is called nand. Therefore,
remove this property.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
Documentation/devicetree
On 04/26/2013 02:27 AM, Linus Walleij wrote:
On Wed, Apr 17, 2013 at 5:41 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 04/16/2013 05:14 PM, Jon Hunter wrote:
c) I have the feeling that hooking the of_xlate function for this is a
bit of an abuse of the function.
I was wondering about
On 04/26/2013 02:31 AM, Linus Walleij wrote:
On Wed, Apr 17, 2013 at 2:41 AM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
So:
+static int omap_gpio_irq_domain_xlate(struct irq_domain *d,
+ struct device_node *ctrlr,
+
On 04/18/2013 04:12 AM, Padma Venkat wrote:
Hi Stephen,
I am trying to add a header file for samsung audio subsystem clk
definitions, which can be used in kernel and dt files.
I applied following patches posted by you in my working tree.
[1/7] kbuild: create an include chroot for DT
On 04/18/2013 11:21 AM, Padma Venkat wrote:
Hi,
On Thu, Apr 18, 2013 at 8:19 PM, Jon Hunter jon-hun...@ti.com wrote:
On 04/18/2013 04:12 AM, Padma Venkat wrote:
Hi Stephen,
I am trying to add a header file for samsung audio subsystem clk
definitions, which can be used in kernel and dt
On 04/17/2013 02:55 AM, Javier Martinez Canillas wrote:
...
There are so many patches flying around in this thread that I missed it :-)
Sorry about that...
No problem.
I was trying to see if we could find a common solution that everyone
could use as it seems that ideally we should all
On 04/17/2013 07:05 AM, Javier Martinez Canillas wrote:
...
Yes, in fact I just realized that for_each_node_by_name() expand to:
#define for_each_node_by_name(dn, name) \
for (dn = of_find_node_by_name(NULL, name); dn; \
dn = of_find_node_by_name(dn, name))
which
On 04/17/2013 08:42 AM, Javier Martinez Canillas wrote:
On Wed, Apr 17, 2013 at 3:25 PM, Jon Hunter jon-hun...@ti.com wrote:
On 04/17/2013 02:55 AM, Javier Martinez Canillas wrote:
...
There are so many patches flying around in this thread that I missed it :-)
Sorry about
On 04/17/2013 09:07 AM, Javier Martinez Canillas wrote:
On 04/17/2013 03:48 PM, Jon Hunter wrote:
On 04/17/2013 07:05 AM, Javier Martinez Canillas wrote:
...
Yes, in fact I just realized that for_each_node_by_name() expand to:
#define for_each_node_by_name(dn, name) \
for (dn
On 04/17/2013 11:37 AM, Javier Martinez Canillas wrote:
The GPMC DT probe function use for_each_node_by_name() to search
child device nodes of the GPMC controller. But this function does
not use the GPMC device node as the root of the search and instead
search across the complete Device Tree.
will be restricted to its children.
Reported-by: Lars Poeschel poesc...@lemonage.de
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Changes since v1 (suggested by Jon Hunter):
- Split the search for GPMC child nodes and only warn if a
child probe fails
;
+ ti,timer-pwm;
};
timer11: timer@48088000 {
Make sure you copy the linux-arm and device-tree mailing lists.
Acked-by: Jon Hunter jon-hun...@ti.com
Thanks!
Jon
___
devicetree-discuss mailing list
devicetree
On 04/16/2013 01:40 PM, Stephen Warren wrote:
On 04/15/2013 05:04 PM, Jon Hunter wrote:
On 04/15/2013 05:16 PM, Stephen Warren wrote:
On 04/15/2013 03:40 PM, Jon Hunter wrote:
...
mmc {
label = pandaboard::status2;
gpios = gpio1 8 0;
...
};
But that's a gpio-leds instance
On 04/16/2013 02:27 PM, Jon Hunter wrote:
...
Right. In the DT case though, if someone does provide the IRQ and GPIO
IDs then at least they would use a different xlate function. Another
option to consider would be defining the #interrupt-cells = 3 where we
would have ...
cell-#1 -- IRQ
On 04/16/2013 05:11 PM, Stephen Warren wrote:
On 04/16/2013 01:27 PM, Jon Hunter wrote:
On 04/16/2013 01:40 PM, Stephen Warren wrote:
On 04/15/2013 05:04 PM, Jon Hunter wrote:
...
If some driver is calling gpio_request() directly, then they will most
likely just call gpio_to_irq() when
On 04/16/2013 07:41 PM, Javier Martinez Canillas wrote:
On Wed, Apr 17, 2013 at 1:14 AM, Jon Hunter jon-hun...@ti.com wrote:
On 04/16/2013 05:11 PM, Stephen Warren wrote:
On 04/16/2013 01:27 PM, Jon Hunter wrote:
On 04/16/2013 01:40 PM, Stephen Warren wrote:
On 04/15/2013 05:04 PM, Jon
On 04/15/2013 08:27 AM, Grant Likely wrote:
On Tue, 19 Mar 2013 11:35:48 -0500, Jon Hunter jon-hun...@ti.com wrote:
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
On 04/15/2013 11:53 AM, Stephen Warren wrote:
On 04/13/2013 07:35 PM, Javier Martinez Canillas wrote:
...
Is the following inlined patch [1] what you were thinking that would
be the right approach?
...
diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
...
+static int
On 04/15/2013 11:58 AM, Stephen Warren wrote:
On 04/14/2013 02:53 PM, Linus Walleij wrote:
On Sun, Apr 14, 2013 at 3:35 AM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
Is the following inlined patch [1] what you were thinking that would
be the right approach?
This looks sort
On 04/15/2013 04:40 PM, Jon Hunter wrote:
On 04/15/2013 11:58 AM, Stephen Warren wrote:
On 04/14/2013 02:53 PM, Linus Walleij wrote:
On Sun, Apr 14, 2013 at 3:35 AM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
Is the following inlined patch [1] what you were thinking
On 04/15/2013 05:16 PM, Stephen Warren wrote:
On 04/15/2013 03:40 PM, Jon Hunter wrote:
On 04/15/2013 11:58 AM, Stephen Warren wrote:
On 04/14/2013 02:53 PM, Linus Walleij wrote:
On Sun, Apr 14, 2013 at 3:35 AM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
Is the following
On 04/10/2013 02:39 PM, Linus Walleij wrote:
On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter jon-hun...@ti.com wrote:
When booting with device-tree the function pointer for detecting context
loss is not populated. Ideally, the pm_runtime framework should be
enhanced to allow a means
On 04/10/2013 02:33 PM, Linus Walleij wrote:
On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter jon-hun...@ti.com wrote:
Currently the IRQ domain is not freed once allocated, in the case where
omap_gpio_probe() fails. Therefore, ensure we free the domain if the
probe does fail. Furthermore
On 04/10/2013 02:44 PM, Linus Walleij wrote:
On Wed, Apr 10, 2013 at 9:41 PM, Jon Hunter jon-hun...@ti.com wrote:
On 04/10/2013 02:39 PM, Linus Walleij wrote:
On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter jon-hun...@ti.com wrote:
When booting with device-tree the function pointer for detecting
The GPMC timing properties for device-tree have been updated
by adding a -ns or -ps suffix to indicate the units of
time the property represents. Therefore, update the timing
property names for TI GPMC NAND example.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
.../devicetree/bindings/mtd/gpmc
Add device-tree node for the 128MB NOR on the OMAP3423-SDP board.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap3430-sdp.dts | 51 +++-
1 file changed, 50 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3430-sdp.dts
b
Add device-tree node for the 64MB NOR on the OMAP2420-H4 board.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2420-h4.dts | 46 +
1 file changed, 46 insertions(+)
diff --git a/arch/arm/boot/dts/omap2420-h4.dts
b/arch/arm/boot/dts
The GPMC timing properties for device-tree have been updated by adding
a -ns or -ps suffix to indicate the units of time the property
represents (as suggested by Rob Herring). Therefore, update the timing
property names for the OMAP3430 SDP NAND and ONENAND devices.
Signed-off-by: Jon Hunter jon
On 04/07/2013 08:17 PM, Jon Hunter wrote:
Add device-tree node for the 128MB NOR on the OMAP3423-SDP board.
Bugger ... it seems I have invented and new board. OMAP3423 SDP
does not exist. Fixed below.
Jon
From 4f486b5dddc5d960d786504b4e3e97a28b63c1c0 Mon Sep 17 00:00:00 2001
From: Jon Hunter
On 04/05/2013 01:35 AM, Santosh Shilimkar wrote:
On Friday 05 April 2013 01:46 AM, Jon Hunter wrote:
Main change is ensuring that the state of a gpio bank is restored when
booting with device-tree. The rest of the patches are clean-ups and one
optimisation.
The patch modifying the *.dtsi
correctly as these boards use a GPIO with the ethernet chips. Also
checked /proc/interrupts to ensure GPIO interrupt counts are
incrementing as expected.
[1] http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git
Jon Hunter (4):
gpio/omap: free irq domain in probe() failure paths
Currently the IRQ domain is not freed once allocated, in the case where
omap_gpio_probe() fails. Therefore, ensure we free the domain if the
probe does fail. Furthermore, the local variable ret is not needed
and so remove this.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
drivers/gpio/gpio
configured
as level-triggered since only edge-triggered gpios can generate
wakeup events. Therefore, the old context restores of the same
registers present later in the code is not needed any more.
Remove them.
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Signed-off-by: Jon Hunter jon-hun
state.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
.../devicetree/bindings/gpio/gpio-omap.txt |7 --
drivers/gpio/gpio-omap.c | 25 +---
2 files changed, 22 insertions(+), 10 deletions(-)
diff --git a/Documentation/devicetree/bindings
of the first set bit, to find all the set
bits.
This optimisation was suggested-by and developed in collaboration
with Felipe Balbi.
Cc: Felipe Balbi ba...@ti.com
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
drivers/gpio/gpio-omap.c | 14 +++---
1 file changed, 7 insertions(+), 7
Add the ti,gpio-always-on property to the appropriate GPIO banks to
indicate which banks are always powered and will never lose logic state.
Cc: Benoit Cousson b-cous...@ti.com
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/boot/dts/omap2420.dtsi |4
arch/arm/boot/dts/omap2430
On 04/02/2013 10:55 AM, Christoph Fritz wrote:
On Mon, 2013-04-01 at 22:05 +0200, Javier Martinez Canillas wrote:
As a quick-fix (hack) I wrote directly to the registers in gpio_probe()
to enable GPIO banks. I now geht this:
[0.214630] omap_gpio_probe, 1133, CM_CLKSEL_PER 0x48005040:
Vinod,
On 03/20/2013 11:36 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130319 09:08]:
Vinod, Tony, Benoit,
On 02/26/2013 12:27 PM, Jon Hunter wrote:
If the device-tree blob is present during boot, then register the SDMA
controller with the device-tree DMA driver so that we can
On 03/22/2013 10:33 AM, Stephen Warren wrote:
On 03/22/2013 02:10 AM, Linus Walleij wrote:
On Fri, Mar 15, 2013 at 12:21 PM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c
index 159f5c5..f5feb43 100644
---
Vinod, Tony, Benoit,
On 02/26/2013 12:27 PM, Jon Hunter wrote:
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
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
Tested-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc-onenand.c | 26
/93784
[3] https://github.com/jonhunter/linux/tree/omap-gpmc-for-v3.10
[4] https://github.com/jonhunter/linux/tree/omap-dt-for-v3.10
Javier Martinez Canillas (1):
ARM: OMAP2+: return -ENODEV if GPMC child device creation fails
Jon Hunter (17):
ARM: OMAP2+: Simplify code configuring ONENAND devices
not using
device-tree is fine.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Tested-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index
that support the
address-address-data multiplexing mode.
Signed-off-by: Jon Hunter jon-hun...@ti.com
Tested-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc.c | 100
arch/arm/mach-omap2/gpmc.h |6 +++
2 files changed, 106
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
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
Tested-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm
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
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
Tested-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach
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
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
Tested-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc.c | 22
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
Tested-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc.c | 24
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
Tested-by: Ezequiel Garcia ezequiel.gar
javier.marti...@collabora.co.uk
Signed-off-by: Jon Hunter jon-hun...@ti.com
Tested-by: Ezequiel Garcia ezequiel.gar...@free-electrons.com
---
arch/arm/mach-omap2/gpmc.c |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index 9208d8e..615da97
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
in the gpmc_timings structure. Therefore, simplify the
code by removing these checks.
The comment in the gpmc_read_timings_dt() 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
Tested-by: Ezequiel
includes ...
1. Booting kernel on above boards
2. Testing of various DMTIMER request APIs
3. Testing the timer overflow and match interrupts.
4. Using different clock sources to operate the timer with.
Jon Hunter (4):
ARM: OMAP: Force dmtimer restore if context loss is not detectable
ARM: OMAP
-device specific solution is in place, force a restore of
the dmtimer when enabling the timer.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/dmtimer.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/plat-omap/dmtimer.c b/arch/arm/plat-omap/dmtimer.c
index
-by: NeilBrown ne...@suse.de
[jon-hun...@ti.com: minor update to subject and changed variable name]
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/dmtimer.c | 32
1 file changed, 12 insertions(+), 20 deletions(-)
diff --git a/arch/arm/plat
Currently the DMTIMER errata flags are not being populated when using
device-tree. Add static platform data to populate errata flags when
using device-tree.
Please note that DMTIMER erratum i767 is applicable to OMAP3-5 devices
as well as AM335x devices.
Signed-off-by: Jon Hunter jon-hun
, by capability or by node) consolidate the code for all these
functions into a single helper function that can be used by these
request functions.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/plat-omap/dmtimer.c | 167 -
arch/arm/plat-omap/include/plat
. For example, errata flags can be populated
for the timer versions that are impacted.
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
.../devicetree/bindings/arm/omap/timer.txt | 17 --
arch/arm/boot/dts/am33xx.dtsi | 14 ++--
arch/arm/boot/dts/omap2
On 03/17/2013 12:24 AM, Ezequiel Garcia wrote:
Hi Jon,
I have some tiny nitpicks...
On Fri, Mar 15, 2013 at 10:21:08AM -0500, Jon Hunter wrote:
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
On 03/16/2013 03:59 PM, Ezequiel Garcia wrote:
Hi Jon,
On Fri, Mar 15, 2013 at 10:21:00AM -0500, Jon Hunter wrote:
The GPMC has wait-pin signals that can be assigned to a chip-select
to monitor the ready signal of an external device. Add a variable to
indicate the total number of wait
On 03/18/2013 09:07 AM, Rob Herring wrote:
On 03/15/2013 10:21 AM, Jon Hunter wrote:
Some of the GPMC timings parameters are currently missing from the GPMC
device-tree binding. Add these parameters to the binding documentation
as well as code to read them.
The existing code
On 03/18/2013 09:32 AM, Jon Hunter wrote:
On 03/18/2013 09:07 AM, Rob Herring wrote:
On 03/15/2013 10:21 AM, Jon Hunter wrote:
Some of the GPMC timings parameters are currently missing from the GPMC
device-tree binding. Add these parameters to the binding documentation
as well as code
-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
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
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
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
On 03/15/2013 09:21 AM, Nishanth Menon wrote:
On 10:48-20130315, Santosh Shilimkar wrote:
On Friday 15 March 2013 02:28 AM, 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
On 03/15/2013 09:38 AM, Nishanth Menon wrote:
On 09:26-20130315, Jon Hunter wrote:
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
/linux/tree/omap-gpmc-for-v3.10
[4] https://github.com/jonhunter/linux/tree/omap-dt-for-v3.10
Javier Martinez Canillas (1):
ARM: OMAP2+: return -ENODEV if GPMC child device creation fails
Jon Hunter (17):
ARM: OMAP2+: Simplify code configuring ONENAND devices
ARM: OMAP2+: Add variable to store
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 ef655d9..88a261c 100644
--- a/arch/arm/mach-omap2/gpmc.c
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
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
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
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
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
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
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
() 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
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
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
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
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
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
javier.marti...@collabora.co.uk
Signed-off-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index ee6601c..d4ec5bb 100644
--- a/arch/arm/mach-omap2/gpmc.c
+++ b/arch/arm/mach-omap2
.
This patch allows an ethernet chip to be defined as an GPMC
child device node.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
Changes since v2:
- remove optional #address-cells and #size-cells since are not relevant for
ethernet chips; suggested by Jon Hunter
Rob, Grant,
On 03/15/2013 10:24 AM, Jon Hunter wrote:
On 03/14/2013 04:54 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
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
1 - 100 of 371 matches
Mail list logo
