2013/11/12 Balaji T K balaj...@ti.com:
On Tuesday 12 November 2013 01:36 AM, Andreas Fenkart wrote:
For now, only support SDIO interrupt if we are booted with
DT. This is because some platforms need special quirks. And
we don't want to add new legacy mux platform init code
callbacks any
Hi Tony,
On 11/14/2013 04:35 AM, Tony Lindgren wrote:
Commit c111feabe2e2 (gpio: twl4030: Cache the direction and output
states in private data) improved things in general, but caused a
regression for setting the GPIO output direction.
The change reorganized twl_direction_out() and
On Thu, Nov 14, 2013 at 02:35:30AM +, Tony Lindgren wrote:
Commit 89ce376c6bdc (drivers/net: Use of_match_ptr() macro in smc91x.c)
added minimal device tree support to smc91x, but it's not working on
many platforms because of the lack of some key configuration bits.
Fix the issue by
Vanilla 3.12 multi_v7_defconfig + cpu_idle result in a solid hang on my pandaes
board: has anyone experienced it before? is cpu_idle safe on omap4?
same kernel boots fine on omap3 and some other arm boards fwiw.
if you want to reproduce it:
config:
On Thu, Nov 14, 2013 at 02:35:32AM +, Tony Lindgren wrote:
Some features can be configured by the companion I2C chips,
which may not be available at the probe time. Fix the issue
by returning -EPROBE_DEFER when the MMC controller slots
are not configured.
While at it, let's also add
On Thu, Nov 14, 2013 at 02:35:33AM +, Tony Lindgren wrote:
As we claim to support device tree for mach-omap2, we
should have the necessary flags in the driver to make it
usable.
Cc: Wolfram Sang w...@the-dreams.de
Cc: linux-...@vger.kernel.org
Signed-off-by: Tony Lindgren
On Tue, Oct 22, 2013 at 01:02:53PM +0100, Felipe Balbi wrote:
Hi,
On Tue, Oct 22, 2013 at 10:42:00AM +0200, Sebastian Andrzej Siewior wrote:
On 10/21/2013 10:13 PM, Felipe Balbi wrote:
diff --git a/drivers/input/touchscreen/ti_am335x_tsc.c
b/drivers/input/touchscreen/ti_am335x_tsc.c
Enable the crossbar IP support for DRA7xx soc.
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Rajendra Nayak rna...@ti.com
Cc: Tony Lindgren t...@atomide.com
Signed-off-by: Sricharan R r.sricha...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
[V4] Removed the unnecessary soc
Some socs have a large number of interrupts requests to service
the needs of its many peripherals and subsystems. All of the
interrupt lines from the subsystems are not needed at the same
time, so they have to be muxed to the irq-controller appropriately.
In such places a interrupt controllers are
The wakeup gen mask/unmask callback uses the irq element of the
irq_data to setup. The irq is the linux virtual irq number and
is same as the hardware irq number only when the parent irqchip
is setup as a legacy domain. When it is used as a linear domain,
the virtual irqs are allocated dynamically
In some socs the gic can be preceded by a crossbar IP which
routes the peripheral interrupts to the gic inputs. The peripheral
interrupts are associated with a fixed crossbar input line and the
crossbar routes that to one of the free gic input line.
The DT entries for peripherals provides the
Some socs have a large number of interrupts requests to service
the needs of its many peripherals and subsystems. All of the interrupt
requests lines from the subsystems are not needed at the same
time, so they have to be muxed to the controllers appropriately.
In such places a interrupt
There is a IRQ crossbar device in the soc, which maps the
irq requests from the peripherals to the mpu interrupt
controller's inputs. The gic provides the support for such
IPs in the form of routable-irqs. So adding the property
here to gic node.
Cc: Benoit Cousson bcous...@baylibre.com
Cc:
Some socs have a large number of interrupts requests to service
the needs of its many peripherals and subsystems. All of the interrupt
requests lines from the subsystems are not needed at the same
time, so they have to be muxed to the controllers appropriately.
In such places a interrupt
Now with the crossbar IP in picture, the peripherals do not have the
fixed interrupt lines. Instead they rely on the crossbar irqchip to
allocate and map a free interrupt line to its crossbar input. So replacing
all the peripheral interrupt numbers with its fixed crossbar input lines.
Cc: Benoit
This adds the irq crossbar device node.
There is a IRQ crossbar device in the soc, which
maps the irq requests from the peripherals to the
mpu interrupt controller's inputs. The Peripheral irq
requests are connected to only one crossbar
input and the output of the crossbar is connected to only
On Thu, 14 Nov 2013, Sricharan R wrote:
[V3] Addressed unnecessary warn-on and updated default
xlate function as per Thomas Gleixner comments
Reviewed-by: Thomas Gleixner t...@linutronix.de
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
On Thursday 14 November 2013 06:03 PM, Thomas Gleixner wrote:
On Thu, 14 Nov 2013, Sricharan R wrote:
[V3] Addressed unnecessary warn-on and updated default
xlate function as per Thomas Gleixner comments
Reviewed-by: Thomas Gleixner t...@linutronix.de
Thanks Thomas..
Regards,
This patch introduces device tree support to the isp1704
charger driver. Adding support involved moving the handling
of the enable GPIO from board code into the driver.
Signed-off-by: Sebastian Reichel s...@debian.org
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 10 +
Add devicetree binding documentation for isp1704-charger.
Signed-off-by: Sebastian Reichel s...@debian.org
---
Documentation/devicetree/bindings/power/isp1704.txt | 17 +
1 file changed, 17 insertions(+)
create mode 100644 Documentation/devicetree/bindings/power/isp1704.txt
On Thu, Nov 14, 2013 at 12:18:47PM +, Sricharan R wrote:
In some socs the gic can be preceded by a crossbar IP which
routes the peripheral interrupts to the gic inputs. The peripheral
interrupts are associated with a fixed crossbar input line and the
crossbar routes that to one of the free
On Thu, Nov 14, 2013 at 12:18:48PM +, Sricharan R wrote:
Some socs have a large number of interrupts requests to service
the needs of its many peripherals and subsystems. All of the
interrupt lines from the subsystems are not needed at the same
time, so they have to be muxed to the
On Thursday 14 November 2013 07:25 AM, Sricharan R wrote:
Some socs have a large number of interrupts requests to service
the needs of its many peripherals and subsystems. All of the interrupt
requests lines from the subsystems are not needed at the same
time, so they have to be muxed to the
On Thursday 14 November 2013 07:18 AM, Sricharan R wrote:
Some socs have a large number of interrupts requests to service
the needs of its many peripherals and subsystems. All of the interrupt
requests lines from the subsystems are not needed at the same
time, so they have to be muxed to the
HI,
On Thu, Nov 14, 2013 at 11:19:59AM +, Mark Rutland wrote:
On Tue, Oct 22, 2013 at 10:42:00AM +0200, Sebastian Andrzej Siewior wrote:
On 10/21/2013 10:13 PM, Felipe Balbi wrote:
diff --git a/drivers/input/touchscreen/ti_am335x_tsc.c
b/drivers/input/touchscreen/ti_am335x_tsc.c
* Mark Rutland mark.rutl...@arm.com [131114 03:04]:
On Thu, Nov 14, 2013 at 02:35:30AM +, Tony Lindgren wrote:
Commit 89ce376c6bdc (drivers/net: Use of_match_ptr() macro in smc91x.c)
added minimal device tree support to smc91x, but it's not working on
many platforms because of the lack
Hi Mark,
On Thursday 14 November 2013 07:42 PM, Mark Rutland wrote:
On Thu, Nov 14, 2013 at 12:18:48PM +, Sricharan R wrote:
Some socs have a large number of interrupts requests to service
the needs of its many peripherals and subsystems. All of the
interrupt lines from the subsystems are
Hi Mark,
On Thursday 14 November 2013 07:31 PM, Mark Rutland wrote:
On Thu, Nov 14, 2013 at 12:18:47PM +, Sricharan R wrote:
In some socs the gic can be preceded by a crossbar IP which
routes the peripheral interrupts to the gic inputs. The peripheral
interrupts are associated with a
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of suspend activity.
For a device such as i2c who uses autosuspend, it is possible to enter
the suspend path with dev-power.runtime_status =
* Mark Rutland mark.rutl...@arm.com [131114 03:06]:
Missing binding document.
Here's this one updated with a minimal binding document. The
ti,hwmods is still needed until we have removed the dependencies
to hwmod code for omaps.
Regards,
Tony
From: Tony Lindgren t...@atomide.com
Date: Wed,
* Mark Rutland mark.rutl...@arm.com [131114 03:08]:
Please update Documentation/devicetree/bindings/i2c/i2c-omap.txt
Otherwise, this is fine.
Here's this one with updated documentation.
Regards,
Tony
From: Tony Lindgren t...@atomide.com
Date: Wed, 13 Nov 2013 16:36:37 -0800
Subject:
* Wolfram Sang w...@the-dreams.de [131113 22:59]:
On Wed, Nov 13, 2013 at 06:35:33PM -0800, Tony Lindgren wrote:
As we claim to support device tree for mach-omap2, we
should have the necessary flags in the driver to make it
usable.
Cc: Wolfram Sang w...@the-dreams.de
Cc:
It would have been helpful if the message PATCH [0/x] would have been
sent to the i2c-list also.
Thanks, next time I'll try check the cc list in the cover letter
manually after running git format patch. I guess there's no way
to deal with that in an automated way.
I use this hackish
* Sebastian Reichel s...@debian.org [131114 04:40]:
This patch introduces device tree support to the isp1704
charger driver. Adding support involved moving the handling
of the enable GPIO from board code into the driver.
Signed-off-by: Sebastian Reichel s...@debian.org
---
* Wolfram Sang w...@the-dreams.de [131114 09:49]:
It would have been helpful if the message PATCH [0/x] would have been
sent to the i2c-list also.
Thanks, next time I'll try check the cc list in the cover letter
manually after running git format patch. I guess there's no way
to
* Peter Ujfalusi peter.ujfal...@ti.com [131114 01:46]:
Hi Tony,
On 11/14/2013 04:35 AM, Tony Lindgren wrote:
Commit c111feabe2e2 (gpio: twl4030: Cache the direction and output
states in private data) improved things in general, but caused a
regression for setting the GPIO output
On Thursday 14 November 2013 13:38:53 Sebastian Reichel wrote:
diff --git a/drivers/power/isp1704_charger.c
b/drivers/power/isp1704_charger.c index fc04d19..db96778
100644
--- a/drivers/power/isp1704_charger.c
+++ b/drivers/power/isp1704_charger.c
@@ -28,6 +28,8 @@
#include
* Tony Lindgren t...@atomide.com [131112 11:57]:
* Linus Walleij linus.wall...@linaro.org [131112 10:45]:
On Fri, Oct 11, 2013 at 7:23 PM, Tony Lindgren t...@atomide.com wrote:
* Linus Walleij linus.wall...@linaro.org [131011 09:27]:
On Fri, Oct 11, 2013 at 6:13 PM, Roger Quadros
* Pekon Gupta pe...@ti.com [131015 11:29]:
Legacy OMAP SoC like OMAP2xxx, OMAP3xxx do not have in-build ELM h/w engine,
so they cannot support h/w based BCH ECC error-detection. Thus,
gpmc_hwecc_bch_capable() check was added in following commit to find-out
which SoC have in-built ELM h/w to
* Grygorii Strashko grygorii.stras...@ti.com [131022 12:09]:
The same workaround as ff999b8a0983ee15668394ed49e38d3568fc6859
ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC ...
need to be applied not only when system is booting, but when MPUSS hits
OSWR state through CPUIdle too.
* Eric Witcher ewitc...@mindspring.com [131022 21:14]:
Correct the SPI node compatible property items to match example code and
match current DTS usage.
Signed-off-by: Eric Witcher ewitc...@mindspring.com
---
Documentation/devicetree/bindings/spi/omap-spi.txt | 4 ++--
1 file changed, 2
* Paul Walmsley p...@pwsan.com [131024 09:01]:
Hi Tony,
The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
Linux 3.12-rc1 (2013-09-16 16:17:51 -0400)
are available in the git repository at:
* Igor Grinberg grinb...@compulab.co.il [131103 01:50]:
On 10/25/13 11:31, Wei Yongjun wrote:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
In case of error, the function platform_device_register_resndata()
returns ERR_PTR() and never returns NULL. The NULL test in the return
value
* Sebastian Reichel s...@debian.org [131027 09:15]:
From: Luciano Coelho coe...@ti.com
Move the wl1251 part of the wl12xx platform data structure into a new
structure specifically for wl1251. Change the platform data built-in
block and board files accordingly.
Cc: Tony Lindgren
Hi,
On Thu, Nov 14, 2013 at 11:05:16AM -0600, Nishanth Menon wrote:
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of suspend activity.
For a device such as i2c who uses autosuspend, it is
* Joel Fernandes jo...@ti.com [13 11:50]:
Add documentation for the generic OMAP DES crypto modul describing the device
tree bindings.
Reviewed-by: Mark Rutland mark.rutl...@arm.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Joel Fernandes jo...@ti.com
Thanks
On 11/14/2013 12:55 PM, Felipe Balbi wrote:
Hi,
On Thu, Nov 14, 2013 at 11:05:16AM -0600, Nishanth Menon wrote:
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of suspend activity.
For a
On Thu, Nov 14, 2013 at 07:05:06PM +0100, Pali Rohár wrote:
On Thursday 14 November 2013 13:38:53 Sebastian Reichel wrote:
diff --git a/drivers/power/isp1704_charger.c
b/drivers/power/isp1704_charger.c index fc04d19..db96778
100644
--- a/drivers/power/isp1704_charger.c
+++
On Thu, Nov 14, 2013 at 10:51:33AM -0800, Tony Lindgren wrote:
[...]
If this is not going into v3.13, these will cause conflicts
with the mach-omap2/board-*.c files for v3.14.
So it might be best to do a minimal header patch first that
can be merged in by both linux-omap and wireless
Looks like we're missing two lines needed to make it
work properly with device tree.
Cc: linux-...@vger.kernel.org
Cc: Aaro Koskinen aaro.koski...@iki.fi
Cc: Wolfram Sang w...@the-dreams.de
Signed-off-by: Tony Lindgren t...@atomide.com
---
Wolfram, I found one more bug booting omaps with device
* Sebastian Reichel s...@debian.org [131114 15:04]:
On Thu, Nov 14, 2013 at 10:51:33AM -0800, Tony Lindgren wrote:
[...]
If this is not going into v3.13, these will cause conflicts
with the mach-omap2/board-*.c files for v3.14.
So it might be best to do a minimal header patch first
Hi all,
Here are some early patches for the v3.14 merge window to make
omap2 booting device tree based before we make omap3 device
tree only. Otherwise we cannot remove the shared platform data
between omap2 and 3 for things like some hwmod entries.
I've added minimal support for 2430sdp to boot
I doubt that there are many people using 2430 sdp, but as
that's been historically an important acid test platform
for omap2+ related changes, let's add minimal device
tree support for it.
If anybody is using it beyond minimal boot testing, patches
for more complete device tree support are
This allows us to keep things working when booted with
device tree. Note that we still need to initialize most
things with platform data as the drivers are lacking
support for device tree.
Cc: Aaro Koskinen aaro.koski...@iki.fi
Signed-off-by: Tony Lindgren t...@atomide.com
---
Now we can boot n8x with the appended device tree with:
$ ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- make omap2420-n800.dtb
$ cat arch/arm/boot/zImage arch/arm/boot/dts/omap2420-n800.dtb /tmp/zImage
Note that you need at least the following enabled:
CONFIG_ARM_APPENDED_DTB=y
We can now boot with device tree and appended DTB
with basic devices working. If people are still using
this board, patches are welcome to add more complete
support.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/Kconfig | 6 -
arch/arm/mach-omap2/Makefile
The old 2420 based H4 is probably not used at all as 2420
was Nokia specific SoC. I have one, but I'm not using it because
of it's large size, and I doubt anybody else is using it either.
We do have minimal omap2420-h4.dts in place, so if anybody wants
more support on H4, patches are welcome.
So
These now come from device tree except for DSS and DMA that
still uses hwmod to initialize. That will get fixed when we
DSS gets device tree bindings and we move completely to the
dmaengine API.
Cc: Paul Walmsley p...@pwsan.com
Signed-off-by: Tony Lindgren t...@atomide.com
---
This allows us to initialize the legacy devices when booted
with device tree.
Cc: Aaro Koskinen aaro.koski...@iki.fi
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/board-n8x0.c | 51 +---
1 file changed, 42 insertions(+), 9 deletions(-)
Looks like some boards need to fill in the auxdata before
we call of_platform_populate(). Let's add support for
auxdata quirks like we already have for pdata quirks for
legacy drivers.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/pdata-quirks.c | 32
Add minimal device tree support for n8x0 boards so we
can make omap2 device tree only. Note that we still need
to initialize various platform data quirks to keep
things working until n8x0 drivers support device tree.
Here's a rough todo list for the people using n8x0:
1. Update menelaus for
Initialize some devices using a late_initcall and test for
the device tree based booting for some devices.
This way we can keep things working for legacy platform
devices when booted with device tree.
Cc: Aaro Koskinen aaro.koski...@iki.fi
Signed-off-by: Tony Lindgren t...@atomide.com
---
On Thursday 14 November 2013 23:34:19 Sebastian Reichel wrote:
On Thu, Nov 14, 2013 at 07:05:06PM +0100, Pali Rohár wrote:
On Thursday 14 November 2013 13:38:53 Sebastian Reichel
wrote:
diff --git a/drivers/power/isp1704_charger.c
b/drivers/power/isp1704_charger.c index fc04d19..db96778
63 matches
Mail list logo
