* Dr. H. Nikolaus Schaller h...@goldelico.com [150311 09:17]:
Hi,
Am 11.03.2015 um 16:24 schrieb Tony Lindgren t...@atomide.com:
Hi,
* Marek Belisko ma...@goldelico.com [150310 14:28]:
Signed-off-by: Marek Belisko ma...@goldelico.com
---
On Wed, Mar 11, 2015 at 03:47:53PM +0200, Grygorii Strashko wrote:
Hi Felipe,
On 03/11/2015 03:50 AM, Felipe Balbi wrote:
On Mon, Mar 09, 2015 at 11:39:17AM -0500, Felipe Balbi wrote:
On Thu, Feb 19, 2015 at 12:06:49PM -0600, Felipe Balbi wrote:
If either SCL or SDA are stuck low, we need
OMAP4/5 has been (ab)using the gic_arch_extn to provide
wakeup from suspend, and it makes a lot of sense to convert
this code to use stacked domains instead.
This patch does just this, updating the DT files to actually
reflect what the HW provides.
BIG FAT WARNING: because the DTs were so far
The only user of the so called routable domain functionality
now being fixed, let's clean up the GIC.
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Marc Zyngier marc.zyng...@arm.com
---
drivers/irqchip/irq-gic.c | 59 -
Make it look like a real interrupt controller.
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Marc Zyngier marc.zyng...@arm.com
---
.../devicetree/bindings/arm/omap/crossbar.txt | 18 +-
1 file changed, 5 insertions(+), 13 deletions(-)
diff --git
This proves to be useful with stacked domains, when the current
domain doesn't implement wake-up, but expect the parent to do so.
Acked-by: Tony Lindgren t...@atomide.com
Signed-off-by: Marc Zyngier marc.zyng...@arm.com
---
include/linux/irq.h | 1 +
kernel/irq/chip.c | 16
2
* Xunlei Pang xlp...@126.com [150310 20:18]:
From: Xunlei Pang pang.xun...@linaro.org
As part of addressing y2038 problem for in-kernel uses, this
patch adds the y2038-safe omap_read_persistent_clock64() using
timespec64.
Because we rely on some subsequent changes to convert arm multiarch
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at least partially.
This series addresses
Hi,
* Marek Belisko ma...@goldelico.com [150310 14:28]:
Signed-off-by: Marek Belisko ma...@goldelico.com
---
.../bindings/power_supply/twl4030_madc_battery.txt | 43
++
1 file changed, 43 insertions(+)
create mode 100644
Hi,
Am 11.03.2015 um 16:24 schrieb Tony Lindgren t...@atomide.com:
Hi,
* Marek Belisko ma...@goldelico.com [150310 14:28]:
Signed-off-by: Marek Belisko ma...@goldelico.com
---
.../bindings/power_supply/twl4030_madc_battery.txt | 43
++
1 file changed, 43
* Paul Bolle pebo...@tiscali.nl [150311 04:16]:
On Mon, 2015-03-09 at 13:51 -0700, Tony Lindgren wrote:
--- /dev/null
+++ b/drivers/phy/phy-dm816x-usb.c
@@ -0,0 +1,295 @@
+/*
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU
Am 11.03.2015 um 17:44 schrieb Tony Lindgren t...@atomide.com:
* Dr. H. Nikolaus Schaller h...@goldelico.com [150311 09:17]:
Hi,
Am 11.03.2015 um 16:24 schrieb Tony Lindgren t...@atomide.com:
Hi,
* Marek Belisko ma...@goldelico.com [150310 14:28]:
Signed-off-by: Marek Belisko
* Kishon Vijay Abraham I kis...@ti.com [150311 02:58]:
Hi Tony,
On Tuesday 10 March 2015 02:21 AM, Tony Lindgren wrote:
Add a minimal driver for dm816x USB. Otherwise we can just use
the existing musb_am335x and musb_dsps on dm816x.
If we can use an existing driver, I'd prefer that.
Hmm
On 03/11/2015 09:26 PM, Tony Lindgren wrote:
* Tero Kristo t-kri...@ti.com [150311 12:09]:
On 03/11/2015 07:17 PM, Tony Lindgren wrote:
Hi Tero,
* Tero Kristo t-kri...@ti.com [150225 11:09]:
Add node for system control module, and move all the existing system
control IO space users under
* Sebastian Reichel s...@kernel.org [150311 12:37]:
Hi,
On Wed, Mar 11, 2015 at 10:43:17AM -0700, Tony Lindgren wrote:
No no, capacity-uah is what we should use, but you need an ack from
the battery and device tree people that this is OK. Let's not add
ti,capacity-uah” as that can
* Tero Kristo t-kri...@ti.com [150311 12:09]:
On 03/11/2015 07:17 PM, Tony Lindgren wrote:
Hi Tero,
* Tero Kristo t-kri...@ti.com [150225 11:09]:
Add node for system control module, and move all the existing system
control IO space users under this new node as its children. A new node
for
Hi Tero,
* Tero Kristo t-kri...@ti.com [150225 11:09]:
Add node for system control module, and move all the existing system
control IO space users under this new node as its children. A new node
for scm_conf area is also added.
...
--- a/arch/arm/boot/dts/dra7.dtsi
+++
* Suman Anna s-a...@ti.com [150311 10:18]:
On 03/11/2015 11:26 AM, Tony Lindgren wrote:
* Dave Gerlach d-gerl...@ti.com [150310 12:55]:
Suman and I have been looking at this together, so I can comment here. An
implementation like this is what Suman is referring to:
+
On 03/11/2015 12:32 PM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [150311 10:18]:
On 03/11/2015 11:26 AM, Tony Lindgren wrote:
* Dave Gerlach d-gerl...@ti.com [150310 12:55]:
Suman and I have been looking at this together, so I can comment here. An
implementation like this is what Suman
* Dr. H. Nikolaus Schaller h...@goldelico.com [150311 10:13]:
Am 11.03.2015 um 17:44 schrieb Tony Lindgren t...@atomide.com:
* Dr. H. Nikolaus Schaller h...@goldelico.com [150311 09:17]:
Am 11.03.2015 um 16:24 schrieb Tony Lindgren t...@atomide.com:
Rather than just making platform_data
The family information in the soc-bus data is currently
not classified properly for AM33xx devices, and a read
of /sys/bus/soc/devices/soc0/family currently shows
Unknown. Fix the same.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/id.c | 2 ++
1 file changed, 2 insertions(+)
Hi,
I'm looking at sources for omap-twl4030.c driver which is used by many
boards. In DT bindings documentation is property ti,codec described as
mandatory but it's never parsed in driver code. I did small experiment
in gta04 board and remove ti,codec from devicetree and sound was
working. I
Tony Lindgren t...@atomide.com writes:
* Paul Bolle pebo...@tiscali.nl [150311 04:16]:
Oh, it should be just GPL v2 like most of the kernel. Probably copied
the header from some other phy driver, will update that instead.
Well, all my code is explicitly v2 or later.
I'll leave it someone else
On Wednesday 11 March 2015 01:34:19 Javier Martinez Canillas wrote:
+
+static struct wl12xx_platform_data *
+wlcore_get_platform_data(struct device *dev)
+{
+ struct wl12xx_platform_data *pdata;
+
+ /* first, look for DT data */
I thought it was the opposite, that
On Mon, 2015-03-09 at 13:51 -0700, Tony Lindgren wrote:
--- /dev/null
+++ b/drivers/phy/phy-dm816x-usb.c
@@ -0,0 +1,295 @@
+/*
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free
Hello Arnd,
On Wed, Mar 11, 2015 at 10:53 AM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 11 March 2015 02:00:59 Javier Martinez Canillas wrote:
What do you mean by parsing here? IIUC there isn't a clock driver for
these clocks and are setup directly in the
On Wed, Mar 11, 2015 at 11:24:34AM +0800, Xunlei Pang wrote:
From: Xunlei Pang pang.xun...@linaro.org
As part of addressing y2038 problem for in-kernel uses, this
patch adds the y2038-safe tegra_read_persistent_clock64() using
timespec64.
Because we rely on some subsequent changes to
I played with RGB LED a bit, and we have quite a gap in
documentation: what 50% brightness means is non-trivial and very
important in case we want to do smooth blinking and color
transitions.
Signed-off-by: Pavel Machek pa...@ucw.cz
diff --git a/Documentation/ABI/testing/sysfs-class-led
On Wed, Mar 11, 2015 at 11:24:35AM +0800, Xunlei Pang wrote:
From: Xunlei Pang pang.xun...@linaro.org
As part of addressing y2038 problem for in-kernel uses, this
patch converts read_boot_clock() to read_boot_clock64() and
read_persistent_clock() to read_persistent_clock64() using
Hi Tony,
On Tuesday 10 March 2015 02:21 AM, Tony Lindgren wrote:
Add a minimal driver for dm816x USB. Otherwise we can just use
the existing musb_am335x and musb_dsps on dm816x.
If we can use an existing driver, I'd prefer that.
Cc: Brian Hutchinson b.hutch...@gmail.com
Cc: Felipe Balbi
Hello Arnd,
On Wed, Mar 11, 2015 at 1:40 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 11 March 2015 12:34:03 Javier Martinez Canillas wrote:
Hello Arnd,
On Wed, Mar 11, 2015 at 10:53 AM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 11 March 2015 02:00:59 Javier Martinez Canillas
On Wed, Mar 11, 2015 at 2:17 PM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 11 March 2015 14:07:11 Javier Martinez Canillas wrote:
Right now it seems that all boards in mainline with a WiLink6 part are
using internal clocks. So as a first step I think that adding an
optional
Hi,
Changes since v1:
- Comments from Russell King and Paul Bolle addressed:
- Use the added defined in the omap-dma changes
- MODULE_* removed from the ti-dma-crossbar driver.
- DMA router documentation: do not limit the #dma-cells to be the same as the
dma controller's #dma-cells. It might
On Wednesday 11 March 2015 14:12:54 Eliad Peller wrote:
On Wed, Mar 11, 2015 at 1:34 PM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
I think that patch [0] should not be needed since for external clocks,
the IP providing the clocks should have its own clock driver and for
internal
Do not direct map the virtual channels to sDMA request number. When the
sDMA is behind of a crossbar this direct mapping can cause situations when
certain channel can not be requested since the crossbar request number
will no longer match with the sDMA request line.
The direct mapping for virtual
The DRA7x has more peripherals with DMA requests than the sDMA can handle:
205 vs 127. All DMA requests are routed through the DMA crossbar, which can
be configured to route selected incoming DMA requests to specific request
line of the DMA controller.
Signed-off-by: Peter Ujfalusi
Instead of magic numbers in the code, use define for number of logical DMA
channels and DMA requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/omap-dma.c
The sDMA requests are routed through the DMA crossbar and without the
crossbar only peripherals using DMA request 0-127 can be used.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 57 ++---
1 file changed, 33
The DRA7x has more peripherals with DMA requests than the sDMA can handle:
205 vs 127. All DMA requests are routed through the DMA crossbar, which can
be configured to route selected incoming DMA requests to specific sDMA
request.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Use the dma-requests property from DT to get the number of DMA requests.
In case of legacy boot or failure to find the property, use the default
127 as number of requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 12 +++-
1 file changed, 11
DMA routers are transparent devices used to mux DMA requests from
peripherals to DMA controllers. They are used when the SoC integrates more
devices with DMA requests then their controller can handle.
DRA7x is one example of such SoC, where the sDMA can hanlde 128 DMA request
lines, but in SoC
On Wednesday 11 March 2015 12:34:03 Javier Martinez Canillas wrote:
Hello Arnd,
On Wed, Mar 11, 2015 at 10:53 AM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 11 March 2015 02:00:59 Javier Martinez Canillas wrote:
What do you mean by parsing here? IIUC there isn't a clock driver for
hi Javier,
On Wed, Mar 11, 2015 at 2:28 AM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
Hello Eliad,
On Mon, Mar 9, 2015 at 4:36 PM, Eliad Peller el...@wizery.com wrote:
Add wl18xx (wilink8) bindings to omap3-igep0030-rev-g and
omap3-igep0020-rev-f dts files, instead of defining the
hi Javier,
On Wed, Mar 11, 2015 at 3:19 AM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
Hello Eliad,
On Wed, Mar 11, 2015 at 1:28 AM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
On Mon, Mar 9, 2015 at 4:36 PM, Eliad Peller el...@wizery.com wrote:
---
On Tue, Mar 10, 2015 at 6:03 AM, Linus Walleij linus.wall...@linaro.org wrote:
On Wed, Mar 4, 2015 at 1:00 AM, Nishanth Menon n...@ti.com wrote:
SoC family such as DRA7 family of processors have, in addition
to the regular muxing of pins (as done by pinctrl-single), an
additional hardware
On Wed, Mar 11, 2015 at 11:51 AM, Arnd Bergmann a...@arndb.de wrote:
+static void wlcore_del_platform_data(struct wl12xx_platform_data *pdata)
+{
+ kfree(pdata);
+}
+
This function seems to be an unnecessary, why not just call kfree() directly?
Or better, maybe the
Hello Eliad,
On Wed, Mar 11, 2015 at 12:59 PM, Eliad Peller el...@wizery.com wrote:
On Wed, Mar 11, 2015 at 3:19 AM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
But there wasn't a DT binding to describe that so most boards use the
same hack which is to define a fake fixed-regulator
On Wed, Mar 11, 2015 at 1:34 PM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
I think that patch [0] should not be needed since for external clocks,
the IP providing the clocks should have its own clock driver and for
internal clocks, a property should be used instead as you said.
If
On Friday 06 March 2015 16:27:05 Tony Lindgren wrote:
Fixes for various omap variants, mostly minor fixes for various SoCs
with the bigger changes being for the dra7 clocks and hwmod data:
Pulled into fixes, thanks!
Arnd
--
To unsubscribe from this list: send the line unsubscribe
Hi Felipe,
On 03/11/2015 03:50 AM, Felipe Balbi wrote:
On Mon, Mar 09, 2015 at 11:39:17AM -0500, Felipe Balbi wrote:
On Thu, Feb 19, 2015 at 12:06:49PM -0600, Felipe Balbi wrote:
If either SCL or SDA are stuck low, we need to
recover the bus using the procedure described
on section 3.1.16 of
50 matches
Mail list logo
