Convert the twl4030_wdt watchdog driver to watchdog core.
While at there use devm_kzalloc and set the default timeout in order to be
able test this driver with a simple shell script.
Signed-off-by: Jarkko Nikula jarkko.nik...@jollamobile.com
Tested-by: Aaro Koskinen aaro.koski...@iki.fi
---
v2:
Hi,
On Mon, Sep 10, 2012 at 10:30:59PM -0700, Tony Lindgren wrote:
We can't build CONFIG_ARCH_OMAP1 set with ARCH_OMAP2PLUS because
of different compiler flags needed, so we can define omap_kp_24xx()
instead of using cpu_is_omap24xx(). This way we can remove
depency to plat and mach headers
On Mon, Sep 10, 2012 at 10:31:11PM -0700, Tony Lindgren wrote:
Remove hardcoded IRQs in irqs.h and related files as these
are no longer needed.
Signed-off-by: Tony Lindgren t...@atomide.com
Finally, great work Tony :-)
FWIW: Reviewed-by: Felipe Balbi ba...@ti.com
---
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp.
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Applies on
* Felipe Balbi ba...@ti.com [120910 23:02]:
+#ifdef CONFIG_ARCH_OMAP1
+#define omap_kp_24xx() 0
+#else
+#define omap_kp_24xx() 1
+#endif
I would rather use revision detection or different driver names (if
revision register is broken).
Hmm actually looks
On Tue, Sep 11, 2012 at 12:25 AM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120908 01:20]:
Will you able to pick up these couple of wakeupgen fixes from here or
do you want me to send you a pull request for 3.6-rc5/6
I can pick them into
Let probe return error value if gpmc terminal
count interrupt could not be obtained
Signed-off-by: Afzal Mohammed af...@ti.com
---
Hi,
My commit (now in l-o/devel-gpmc),
bd4156f mtd: nand: omap2: use gpmc provided irqs
did not propogate error code properly due to
which this fix was required.
+Tony
On Tue, Sep 11, 2012 at 11:58:54, Mohammed, Afzal wrote:
Let probe return error value if gpmc terminal
count interrupt could not be obtained
Signed-off-by: Afzal Mohammed af...@ti.com
---
Hi,
My commit (now in l-o/devel-gpmc),
bd4156f mtd: nand: omap2: use gpmc provided irqs
Hi Rajendra,
A CCF testing branch has been built here. The base is v3.6-rc5, plus the
most recent version of the Common Clock Framework preparation patches that
you posted to the list, [PATCH v4 0/3] Prepare for OMAP2+ movement to
Common Clk, but updated to take RMK's feedback into account.
On Tue, 11 Sep 2012, Shilimkar, Santosh wrote:
On Tue, Sep 11, 2012 at 12:25 AM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120908 01:20]:
Will you able to pick up these couple of wakeupgen fixes from here or
do you want me to send you a pull
On Tue, Sep 11, 2012 at 01:15:10, Porter, Matt wrote:
Changes since v1:
- Series now applies on top of Anil's AM33XX DTS series
This series applies on top of the for_3.7/dts/ branch and Anil's
[v7,2/3] arm/dts: AM33XX: Configure pinmuxs for user leds control on Bone
patch that is
Hi Tony,
On Tue, Sep 11, 2012 at 11:12:27, Tony Lindgren wrote:
* Mohammed, Afzal af...@ti.com [120910 22:36]:
I was not careful enough, sorry. Thanks for fixing it.
Another hunk as follows would also be required for error
path even though compiler didn't complain.
Not sure
On Tue, Sep 11, 2012 at 12:07 PM, Paul Walmsley p...@pwsan.com wrote:
On Tue, 11 Sep 2012, Shilimkar, Santosh wrote:
On Tue, Sep 11, 2012 at 12:25 AM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120908 01:20]:
Will you able to pick up these couple
Currently in omap2_mcspi_txrx_dma the tx and the rx support is
interleaved. Make the rx related code in omap2_mcspi_rx_dma
and the tx related code omap2_mcspi_tx_dma and call the functions.
While at it remove the braces in the if statements which has only
one line.
Also fix [foo * bar to foo
On Tue, 11 Sep 2012, Shilimkar, Santosh wrote:
On Tue, Sep 11, 2012 at 12:07 PM, Paul Walmsley p...@pwsan.com wrote:
On Tue, 11 Sep 2012, Shilimkar, Santosh wrote:
On Tue, Sep 11, 2012 at 12:25 AM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com
Jon,
On Mon, Sep 10, 2012 at 8:53 PM, Jon Hunter jon-hun...@ti.com wrote:
This series adds PMU support for OMAP4 devices. This is based upon Will
Deacons
series [1] and re-based upon the latest arm-soc next/cleanup branch (3.6-rc3)
that includes Will's series. It has been re-based upon this
Hello Wolfram,
When booting using a device tree, the adapter number is dynamically
assigned after the log message is sent.
This patch modifies the log message to get a correct adapter id.
Applies on 3.6-rc3. Tested on OMAP3 (Gumstix Overo).
Thanks for the fix. Tested successfully on OMAP4
On Tue, Sep 11, 2012 at 12:13 PM, Paul Walmsley p...@pwsan.com wrote:
On Tue, 11 Sep 2012, Shilimkar, Santosh wrote:
On Tue, Sep 11, 2012 at 12:07 PM, Paul Walmsley p...@pwsan.com wrote:
On Tue, 11 Sep 2012, Shilimkar, Santosh wrote:
On Tue, Sep 11, 2012 at 12:25 AM, Tony Lindgren
On Tue, Sep 11, 2012 at 12:09 AM, Tony Lindgren t...@atomide.com wrote:
* Ruslan Bilovol ruslan.bilo...@ti.com [120910 03:39]:
OMAP mux now parses active wakeup events from pad registers and calls
corresponding handler, if handler is not registered - corresponding
hwmod ISRs once a wakeup is
Hi Tero, Paul,
After discussion with Paul at LPC I produced a new version that we are
now internally reviewing.
Paul, what is your plan?
Regards,
Jean
On Mon, Sep 10, 2012 at 5:09 PM, Tero Kristo t-kri...@ti.com wrote:
On Thu, 2012-08-16 at 11:20 +0530, Shilimkar, Santosh wrote:
Paul,
On
Hi Kishon,
On 09/11/2012 08:12 AM, Kishon Vijay Abraham I wrote:
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp.
Could you add more details about the omap-usb2?
You must update the
Hi,
On Tue, Sep 11, 2012 at 1:53 PM, Benoit Cousson b-cous...@ti.com wrote:
Hi Kishon,
On 09/11/2012 08:12 AM, Kishon Vijay Abraham I wrote:
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp.
Hi,
On Mon, Sep 10, 2012 at 10:13 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Sep 10, 2012 at 06:17:03PM +0200, Benoit Cousson wrote:
On 9/6/2012 8:25 PM, Kishon Vijay Abraham I wrote:
The mailbox register for usb otg in omap is present in control module.
On detection of any events
With pinctrl-single,bits it is possible to update just part of the register
within the pinctrl-single,function-mask area.
This is useful when one register configures mmore than one pin's mux.
pinctrl-single,bits takes three parameters:
reg offset, value, sub-mask
Signed-off-by: Peter Ujfalusi
This patch series adds device tree support for MUSB.
The glue layer is now made to write to mailbox register (present in
control module) instead of calling phy layer to write to mailbox
register. Writing to mailbox register notifies the core of events like
device connect/disconnect.
Changes from
The glue layer should directly write to mailbox register (present in
control module) instead of calling phy layer to write to mailbox
register. Writing to mailbox register notifies the core of events like
device connect/disconnect.
Currently writing to control module register is taken care in
Added device tree support for omap musb driver and updated the
Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 33
drivers/usb/musb/omap2430.c|
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to control module,
omap2430 will handle the register writes
On 09/11/2012 11:09 AM, Kishon Vijay Abraham I wrote:
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to
Hi,
On Fri, Aug 31, 2012 at 04:39:46PM +0530, Ravi Babu wrote:
This series of patches adds,
a) Multi instances support in musb driver
b) DT support for musb_dsps glue layer
c) DT support for NOP transceiver
AM33xx and TI81xx has dual musb controller and has two usb PHY of same type.
This
On Friday 31 August 2012 04:32 PM, Florian Vaussard wrote:
When booting using a device tree, the adapter number is dynamically
assigned after the log message is sent.
This patch modifies the log message to get a correct adapter id.
Applies on 3.6-rc3. Tested on OMAP3 (Gumstix Overo).
Benoit,
On Mon, Sep 10, 2012 at 7:09 PM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Mon, Sep 10, 2012 at 6:44 PM, Benoit Cousson b-cous...@ti.com wrote:
[...]
Silly question: Don't we have one arch-timer per CPU?
It is per CPU just like A9 TWD
Shouldn't we have two nodes
Changes since v1:
- removed tabification on patch 6/17
- removed dev_err() which was introduced on patch 09/17
Changes since v2:
- do not set full fifo depth in the RDR interrupt.
- some changelog updates.
- rebase to the Wolfram's tree.
Changes since v3:
From: Felipe Balbi ba...@ti.com
stat BIT(1) is the same as BIT(1), so let's
simplify things a bit by removing stat from
all omap_i2c_ack_stat() calls.
Code snippet (extremely simplified):
if (stat NACK) {
...
omap_i2c_ack_stat(dev, stat NACK);
}
if (stat RDR) {
...
From: Felipe Balbi ba...@ti.com
While they do pretty much the same thing, there
are a few peculiarities. Specially WRT erratas,
it's best to split those out and re-factor the
read/write loop to another function which both
cases call.
This last part will be done on another patch.
While at that,
From: Felipe Balbi ba...@ti.com
trivial patch to aid readability. No functional
changes.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git
From: Felipe Balbi ba...@ti.com
The patch intends to decrease the indentation level on the
data handling
by using the fact that else of if (dev-buf_len) is same as
if (!dev-buf_len)
if (dev-buf_len) {
aaa;
} else {
bbb;
break;
}
to
if (!dev-buf_len) {
bbb;
From: Felipe Balbi ba...@ti.com
omap_i2c_dev is allocated with kzalloc(),
so we need not initialize b_hw to zero.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |4 +---
1 files changed, 1 insertions(+), 3
From: Felipe Balbi ba...@ti.com
Make it not depend on ISR's local variables
in order to make it easier to re-factor the
transmit data loop.
Also since we are waiting for XUDF(Transmitter underflow) just before
writing data lets not flag the underflow.
This is anyways going to go once we write
the
From: Felipe Balbi ba...@ti.com
According to flow diagrams on OMAP TRMs,
we should ACK the IRQ as they happen.
Signed-off-by: Felipe Balbi ba...@ti.com
[Ack the stat OMAP_I2C_STAT_AL in case of arbitration lost]
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c
From: Felipe Balbi ba...@ti.com
this will make sure that we execute at least once.
No functional changes otherwise.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 20 ++--
1 files changed, 14
From: Felipe Balbi ba...@ti.com
that's a nice helper from drivers core which
will give us the exact IRQ number, instead
of a pointer to an IRQ resource.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 12
From: Felipe Balbi ba...@ti.com
Always return IRQ_HANDLED otherwise we could get our IRQ line disabled due
to many spurious IRQs.
Signed-off-by: Felipe Balbi ba...@ti.com
[Trivial changes to commitlogs]
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |2
From: Felipe Balbi ba...@ti.com
re-factor the common parts to a separate function,
so that code is easier to read and understand.
No functional changes.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 204
From: Felipe Balbi ba...@ti.com
that helps deleting some boiler plate code
and lets driver-core manage our resources
for us.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 41
From: Felipe Balbi ba...@ti.com
This patch will try to avoid the usage of
draining feature by reconfiguring the FIFO
the start condition of each message based
on the message's size.
By doing that, we will be better utilizing
the FIFO when doing big transfers.
While at that also drop the now
From: Felipe Balbi ba...@ti.com
even if our clocks are disabled, we still
handled the IRQ, so we should return IRQ_HANDLED.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |2 +-
1 files changed, 1 insertions(+), 1
From: Felipe Balbi ba...@ti.com
for OMAP2, we can easily switch over to threaded
IRQs on the I2C driver. This will allow us to
spend less time in hardirq context.
Signed-off-by: Felipe Balbi ba...@ti.com
[Trivial formating changes]
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
From: Felipe Balbi ba...@ti.com
that way we can ignore TX IRQs while in receiver
mode and ignore RX IRQs while in transmitter mode.
Signed-off-by: Felipe Balbi ba...@ti.com
[Remove unnecessary braces]
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |8
Remove the redundant read of the status register.
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index 5d4bad4..498a462
From: Felipe Balbi ba...@ti.com
before starting any messages we call pm_runtime_get_sync()
which will make sure that by the time we program a transfer
and our IRQ handler gets called, we're not suspended
anymore.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D
From: Felipe Balbi ba...@ti.com
move the goto out label one line down, so that
it can be used when stat is read as zero. All
other exits, can be done with a break statement.
While at that, also break out as soon as we
complete draining IRQ, since at that time
we know we transferred everything
From: Felipe Balbi ba...@ti.com
this helps us reduce unnecessary pm transitions
in case we have another i2c message starting soon.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 12 ++--
1 files changed,
From: Felipe Balbi ba...@ti.com
instead of having multiple return points, use
a goto statement to make that clearer.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 20
1 files changed, 8
From: Felipe Balbi ba...@ti.com
we can ack stat and complete the command from
the errata handling itself.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 16 +---
1 files changed, 13 insertions(+), 3
From: Felipe Balbi ba...@ti.com
trivial patch, no functional changes
If the fifo is disabled or fifo_size is 0 the num_bytes
is set to 1. Else it is set to fifo_size or in case of a
draining interrupt the remaining bytes in the buff stat.
So the zero check is redundant and can be safely
On 9/11/2012 12:05 PM, Paul Walmsley wrote:
Hi Rajendra,
A CCF testing branch has been built here. The base is v3.6-rc5, plus the
most recent version of the Common Clock Framework preparation patches that
you posted to the list, [PATCH v4 0/3] Prepare for OMAP2+ movement to
Common
On 9/11/2012 2:39 PM, Kishon Vijay Abraham I wrote:
Added device tree support for omap musb driver and updated the
Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 33
Hi,
Basic gpmc driver conversion series. Driver that is now created out of
gpmc code is a simple one, it handles tasks that were earlier executed
by gpmc_init. Now instead of relying on cpu_is_* checks, it obtains
resources and clk handle in the standard Linux way. The existing gpmc
interface
Add gpmc hwmod and associated interconnect data
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 18 +++
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 18 +++
arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c | 44
Create API for platforms to adapt GPMC to HWMOD
Signed-off-by: Afzal Mohammed af...@ti.com
Reviewed-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 22 ++
1 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc.c
Create a minimal driver out of gpmc code.
Responsibilities handled by earlier gpmc
initialization is now achieved in probe.
Signed-off-by: Afzal Mohammed af...@ti.com
Reviewed-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 171 +++-
1
On Saturday 08 September 2012 11:34 PM, Aaro Koskinen wrote:
-static struct platform_device *omap_wdt_dev;
-
static unsigned timer_margin;
module_param(timer_margin, uint, 0);
MODULE_PARM_DESC(timer_margin, initial watchdog timeout (in seconds));
-static unsigned int wdt_trgr_pattern =
Hi Jon,
On Thu, Sep 06, 2012 at 01:25:23, Hunter, Jon wrote:
Nit-pick, I see some devices writing the above as ...
WARN(IS_ERR(pdev), could not build omap_device for %s\n, oh_name);
return IS_ERR(pdev) ? PTR_ERR(pdev) : 0;
Otherwise ...
Reviewed-by: Jon Hunter
On Tuesday 11 September 2012 03:11 PM, Shubhrajyoti D wrote:
Changes since v1:
- removed tabification on patch 6/17
- removed dev_err() which was introduced on patch 09/17
Changes since v2:
- do not set full fifo depth in the RDR interrupt.
- some changelog
Hi,
On Fri, Aug 31, 2012 at 04:39:46PM +0530, Ravi Babu wrote:
This series of patches adds,
a) Multi instances support in musb driver
b) DT support for musb_dsps glue layer
c) DT support for NOP transceiver
AM33xx and TI81xx has dual musb controller and has two usb
PHY of same
Hi Tony,
On Sat, Sep 08, 2012 at 03:40:34, Tony Lindgren wrote:
Great, this all looks good to me. I suggest that on top of this
we add minimal devicetree binding that does not even attempt to
deal with the timings yet.
Then once the minimal devicetree binding is in place, we can
call the
On Mon, Sep 10, 2012 at 07:05:15PM +0200, Sebastian Andrzej Siewior wrote:
On 09/10/2012 06:40 PM, Fengguang Wu wrote:
tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git master
head: d9c88901337158c9f253a7de58a10b5125d61d26
commit: 7a7322b0a5d984025dd4faea9098b8fef07f8d8f
Hi,
On Tue, Sep 11, 2012 at 3:23 PM, Vaibhav Hiremath hvaib...@ti.com wrote:
On 9/11/2012 2:39 PM, Kishon Vijay Abraham I wrote:
Added device tree support for omap musb driver and updated the
Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
On Tue, Sep 11, 2012 at 04:57:08AM +, Hiremath, Vaibhav wrote:
On Mon, Sep 10, 2012 at 21:50:20, Porter, Matt wrote:
On AM33xx, the datasheet and TRM refer to four GPIO instances that
are 0-based, GPIO0-3.
Thanks Matt,
I think Anil labeled it as gpio1-4 due to hwmod naming
Hi Jon,
On 09/11/2012 12:57 AM, Jon Hunter wrote:
Add a minimal dts for original OMAP3430/3530 version of the Beagle board. This
version of the Beagle board has 256MB of DDR and features the same TWL4030
power management IC (PMIC) as the Beagle board XM.
Thanks for the patch.
Given that the
On Tue, Sep 11, 2012 at 16:59:05, Porter, Matt wrote:
On Tue, Sep 11, 2012 at 04:57:08AM +, Hiremath, Vaibhav wrote:
On Mon, Sep 10, 2012 at 21:50:20, Porter, Matt wrote:
On AM33xx, the datasheet and TRM refer to four GPIO instances that
are 0-based, GPIO0-3.
Thanks Matt,
I
On Sunday 09 September 2012 12:34 AM, Felipe Balbi wrote:
In addition, IMO, if this was only tested on Panda (as suggested by
earlier cover letters), it really should not have been merged until it
got some broader testing.
Shubhro's got his Tested-by tag. I believe he tested on beagleboard
Hi Tony,
As the plat and mach includes need to disappear for single zImage work,
we need to remove plat/hardware.h.
Do this by splitting plat/hardware.h into omap1 and omap2+ specific files.
The old plat/hardware.h already has omap1 only defines, so it gets moved
to mach/hardware.h for
Hi Russell,
I am currently working on implementing DMA Engine for omap serial
driver.
Came to know from santosh that you had suggested that certain modification need
to be done in the tty core layer, which I am unaware of. Can you
please explain what sort of
changes need to be done?
--
To
On Tue, Sep 11, 2012 at 16:54:37, ABRAHAM, KISHON VIJAY wrote:
Hi,
On Tue, Sep 11, 2012 at 3:23 PM, Vaibhav Hiremath hvaib...@ti.com wrote:
On 9/11/2012 2:39 PM, Kishon Vijay Abraham I wrote:
Added device tree support for omap musb driver and updated the
Documentation with device
On Tue, Sep 11, 2012 at 10:45:44AM +, B, Ravi wrote:
Hi,
On Fri, Aug 31, 2012 at 04:39:46PM +0530, Ravi Babu wrote:
This series of patches adds,
a) Multi instances support in musb driver
b) DT support for musb_dsps glue layer
c) DT support for NOP transceiver
+ Andrew,
On Thu, Sep 06, 2012 at 20:12:07, Cousson, Benoit wrote:
On 09/05/2012 04:41 PM, Hiremath, Vaibhav wrote:
...
There are other patches which are pending,
arm/dts: AM33XX: Convert all hex numbers to lower-case
https://patchwork.kernel.org/patch/1377351/
arm/dts: AM33XX:
On Fri, Aug 31, 2012 at 04:39:46PM +0530, Ravi Babu wrote:
This series of patches adds,
a) Multi instances support in musb driver
b) DT support for musb_dsps glue layer
c) DT support for NOP transceiver
AM33xx and TI81xx has dual musb controller and has two usb
On 09/11/2012 01:29 PM, Benoit Cousson wrote:
Hi Jon,
On 09/11/2012 12:57 AM, Jon Hunter wrote:
Add a minimal dts for original OMAP3430/3530 version of the Beagle board.
This
version of the Beagle board has 256MB of DDR and features the same TWL4030
power management IC (PMIC) as the
On Tue, Sep 11, 2012 at 05:01:06PM +0530, Shubhrajyoti wrote:
On Sunday 09 September 2012 12:34 AM, Felipe Balbi wrote:
In addition, IMO, if this was only tested on Panda (as suggested by
earlier cover letters), it really should not have been merged until it
got some broader testing.
Hi,
On Tue, Sep 11, 2012 at 03:48:34PM +0530, Shubhrajyoti wrote:
On Tuesday 11 September 2012 03:11 PM, Shubhrajyoti D wrote:
Changes since v1:
- removed tabification on patch 6/17
- removed dev_err() which was introduced on patch 09/17
Changes since v2:
- do not
Hi Juan,
On Wed, Aug 15, 2012 at 6:25 PM, Juan Gutierrez jgutier...@ti.com wrote:
Some remote processors (like Omap4's DSP) need to explicitly
set a boot address from which they start executing code when
taken out of reset.
Support for this has been added to remoteproc code through
a
As we discussed at the ARM mini summit in San Diego, we are
going to move all platform specific header files that are used
in drivers out of the mach-* directories, at least for those
platforms that we want to have in a multiplatform kernel.
A big step in this direction is to move all the
On Tue, 11 Sep 2012, NeilBrown wrote:
On Mon, 10 Sep 2012 12:28:35 +0200 (CEST) Thomas Gleixner
t...@linutronix.de wrote:
You might be looking for a different functionality. Can you explain
what you need?
I want as particular GPIO interrupt to be masked before entering suspend.
I
Platform data for device drivers should be defined in
include/linux/platform_data/*.h, not in the architecture
and platform specific directories.
This moves such data out of the omap include directories
Signed-off-by: Arnd Bergmann a...@arndb.de
Cc: Tony Lindgren t...@atomide.com
Cc: Kevin
Platform data for device drivers should be defined in
include/linux/platform_data/*.h, not in the architecture
and platform specific directories.
This moves such data out of the omap include directories
Signed-off-by: Arnd Bergmann a...@arndb.de
Cc: Tony Lindgren t...@atomide.com
Cc: Kevin
Hi Arnd,
On 09/11/2012 03:59 PM, Arnd Bergmann wrote:
Platform data for device drivers should be defined in
include/linux/platform_data/*.h, not in the architecture
and platform specific directories.
This moves such data out of the omap include directories
Signed-off-by: Arnd Bergmann
Arnd,
On Tue, Sep 11, 2012 at 6:32 PM, Arnd Bergmann a...@arndb.de wrote:
Platform data for device drivers should be defined in
include/linux/platform_data/*.h, not in the architecture
and platform specific directories.
This moves such data out of the omap include directories
On Tuesday 11 September 2012, Shilimkar, Santosh wrote:
Just curious to know how you came with some of the above header names ?
plat/mcbsp --- dsp-mcbsp.h
There is no connection of DSP with McBSP. omap-mcbsp.h would been a
better name.
This one was a mistake on my side, as Tony and Peter
On Tue, Sep 11, 2012 at 7:47 PM, Arnd Bergmann a...@arndb.de wrote:
On Tuesday 11 September 2012, Shilimkar, Santosh wrote:
Just curious to know how you came with some of the above header names ?
plat/mcbsp --- dsp-mcbsp.h
There is no connection of DSP with McBSP. omap-mcbsp.h would been a
Add a minimal dts for original OMAP3430/3530 version of the Beagle board. This
version of the Beagle board has 256MB of DDR and features the same TWL4030
power management IC (PMIC) as the Beagle board XM.
Given that the Beagle and Beagle-XM boards use the same PMIC, move the
definition of the
On 9/11/2012 7:54 PM, Shilimkar, Santosh wrote:
On Tue, Sep 11, 2012 at 7:47 PM, Arnd Bergmann a...@arndb.de wrote:
On Tuesday 11 September 2012, Shilimkar, Santosh wrote:
Just curious to know how you came with some of the above header names ?
plat/mcbsp --- dsp-mcbsp.h
There is no
From: J Keerthy j-keer...@ti.com
Removes checkpatch warnings on omap-bandgap.c.
Signed-off-by: J Keerthy j-keer...@ti.com
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
drivers/staging/omap-thermal/omap-bandgap.c | 15 ---
1 files changed, 8 insertions(+), 7
While registering the thermal zone, it is required to have the cooling
devices already setup, so that the .bind callback can succeed.
Due to that, the driver code needs to be reorganized so that we first
setup the cooling devices then the zones. This way we cope with the
right thermal framework
While registering the omap thermal zones we need to
properly specify TC1 and TC2, as long as the proper
passive polling period and monitor period.
This patch fixes the parameters passed while registering
the thermal zone.
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
Hello Greg,
Here are some patches to clean the omap-thermal driver code a bit.
There are 2 fixes as well related to registration to thermal fw.
These patches are based on staging-next tree.
They are also available here:
g...@gitorious.org:thermal-framework/thermal-framework.git
Simple checkpatch.pl clean ups.
Signed-off-by: Eduardo Valentin eduardo.valen...@ti.com
---
drivers/staging/omap-thermal/omap4-thermal.c | 54 +-
drivers/staging/omap-thermal/omap5-thermal.c | 38 +-
2 files changed, 46 insertions(+), 46 deletions(-)
From: Ajay Kumar Gupta ajay.gu...@ti.com
Moved global variable musb_debugfs_root and static variable
old_state to 'struct musb' to help support multi instance of
musb controller as present on AM335x platform.
Also removed the global variable orig_dma_mask and filled the
dev-dma_mask with parent
From: Ajay Kumar Gupta ajay.gu...@ti.com
As NOP device node is now added in am33xx tree so remove the call
which creates the NOP platform_device.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Santhapuri, Damodar damodar.santhap...@ti.com
Signed-off-by: Ravi Babu
1 - 100 of 150 matches
Mail list logo
