On Mon, Oct 22, 2012 at 01:21:37, Daniel Mack wrote:
On 19.10.2012 12:58, Mohammed, Afzal wrote:
Hi Daniel,
On Thu, Oct 18, 2012 at 22:03:13, Hiremath, Vaibhav wrote:
On Thu, Oct 18, 2012 at 21:49:44, Daniel Mack wrote:
On 18.10.2012 18:12, Vaibhav Hiremath wrote:
It would be
On Sunday 21 October 2012 06:24 PM, Wei Yongjun wrote:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Add the missing unlock on the error handling path in function
hdmi_dump_regs().
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
Looks good to me; feel free to add:
Reviewed-by:
On 2012-10-21 15:54, Wei Yongjun wrote:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Add the missing unlock on the error handling path in function
hdmi_dump_regs().
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
---
no test
---
drivers/video/omap2/dss/hdmi.c | 4 +++-
1
On 2012-10-22 08:48, Archit Taneja wrote:
On Wednesday 17 October 2012 04:50 PM, Tomi Valkeinen wrote:
Hi,
This series contains minor cleanups and fixes for omapdss.
This series looks fine to me. I have a related cleanup patch which you
may consider adding to the series.
Thanks,
Archit
On 2012-10-16 04:27, Ricardo Neri wrote:
Using devm_ioremap provides better memory handling and improves
readability.
Signed-off-by: Ricardo Neri ricardo.n...@ti.com
---
drivers/video/omap2/dss/hdmi.c | 11 +++
1 files changed, 7 insertions(+), 4 deletions(-)
diff --git
Adapt keypad to use pinctrl framework.
Tested on omap4430 sdp with 3.7-rc1 kernel.
Cc: Felipe Balbi ba...@ti.com
Cc: Dmitry Torokhov dmitry.torok...@gmail.com
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
---
drivers/input/keyboard/omap4-keypad.c |8
1 files changed, 8
Currently, omap4 keypad mux settings are done in the board file.
Populate the mux settings in the dts file for the keypad to
work via dt.
Cc: Felipe Balbi ba...@ti.com
Tested on omap4430 sdp with 3.7-rc1.
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts |
On 2012-10-16 04:27, Ricardo Neri wrote:
Creating the accessory devices, such as audio, from the HDMI driver
allows to regard HDMI as a single entity with audio an display
functionality. This intends to follow the design of drivers such
as MFD, in which a single entity handles the creation of
Hi Sourav,
On 10/22/2012 09:29 AM, Sourav Poddar wrote:
Currently, omap4 keypad mux settings are done in the board file.
Populate the mux settings in the dts file for the keypad to
work via dt.
Have you changed the driver to handle properly the dependency with the
pinctrl and thus return
Hi,
On Tue, Oct 16, 2012 at 05:23:20PM +0200, Sebastien Guiriec wrote:
Some GPIO expanders need some early pin control muxing. Due to
legacy boards sometimes the driver uses subsys_initcall instead of
module_init. This patch takes advantage of defer probe feature
and pin control in order to
Hi Benoit,
On Monday 22 October 2012 01:15 PM, Benoit Cousson wrote:
Hi Sourav,
On 10/22/2012 09:29 AM, Sourav Poddar wrote:
Currently, omap4 keypad mux settings are done in the board file.
Populate the mux settings in the dts file for the keypad to
work via dt.
Have you changed the driver to
On 10/22/2012 10:23 AM, Sourav wrote:
Hi Benoit,
On Monday 22 October 2012 01:15 PM, Benoit Cousson wrote:
Hi Sourav,
On 10/22/2012 09:29 AM, Sourav Poddar wrote:
Currently, omap4 keypad mux settings are done in the board file.
Populate the mux settings in the dts file for the keypad to
Hi,
On Thursday 18 October 2012 08:09 PM, Tero Kristo wrote:
On Thu, 2012-10-18 at 16:53 +0300, Felipe Balbi wrote:
hi,
On Thu, Oct 18, 2012 at 03:18:04PM +0300, Tero Kristo wrote:
+static int __init omap4430_phy_power_down(void)
+{
+ void __iomem *ctrl_base;
+
+ if
On Mon, Oct 22, 2012 at 02:24:30PM +0530, kishon wrote:
Hi,
On Thursday 18 October 2012 08:09 PM, Tero Kristo wrote:
On Thu, 2012-10-18 at 16:53 +0300, Felipe Balbi wrote:
hi,
On Thu, Oct 18, 2012 at 03:18:04PM +0300, Tero Kristo wrote:
+static int __init omap4430_phy_power_down(void)
Hi,
On Monday 22 October 2012 02:37 PM, Felipe Balbi wrote:
On Mon, Oct 22, 2012 at 02:24:30PM +0530, kishon wrote:
Hi,
On Thursday 18 October 2012 08:09 PM, Tero Kristo wrote:
On Thu, 2012-10-18 at 16:53 +0300, Felipe Balbi wrote:
hi,
On Thu, Oct 18, 2012 at 03:18:04PM +0300, Tero Kristo
Hi guys,
here's another series for OMAP I2C driver. There are a few cleanups
and one very nice new feature: we can now report how many bytes
we transferred until NACK.
Note that the implemementation for OMAP-I2C turned out to be a
little more complex then I expected, mainly because of the way
just a cleanup patch trying to make exit path
more straightforward. No changes otherwise.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 26 +-
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c
In case we loop on IRQ handler until stat is
finally zero, we would end up in a situation
where all I2C transfers would misteriously
timeout because we were not calling complete()
in that situation.
Fix the issue by moving omap_i2c_complete_cmd()
call inside the 'out' label.
Signed-off-by:
PM callbacks pass our device pointer as argument
and we don't need to access the platform_device
just to dereference that down to dev-drvdata.
instead, just use dev_get_drvdata() directly.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/i2c/busses/i2c-omap.c | 6 ++
1 file changed, 2
on OMAP4+ we want to read IRQSTATUS_RAW register,
instead of IRQSTATUS. The reason being that IRQSTATUS
will only contain the bits which were enabled on
IRQENABLE_SET and that will break when we need to
poll for a certain bit which wasn't enabled as an
IRQ source.
One such case is after we finish
this is important in cases where client driver
wants to know how many bytes were actually
transferred.
There is one trick here: if transfer is completed,
meaning I2C_CNT reaches zero, then ARDY will be
asserted to let SW know that it can program a
new transfer.
When ARDY is asserted, I2C_CNT is
From: Shubhrajyoti D shubhrajy...@ti.com
In case of a NACK, it's wise to tell our clients
drivers about how many bytes were actually transferred.
Support this by adding an extra field to the struct
i2c_msg which gets incremented the amount of bytes
actually transferred.
Signed-off-by:
Later patches will come adding support for
reporting amount of bytes transferred so that
client drivers can count how many bytes are
left to transfer.
This is useful mostly in case of NACKs when
client driver wants to know exactly which
byte got NACKed so it doesn't have to resend
all bytes
On Fri, 2012-10-19 at 16:54 -0700, Kevin Hilman wrote:
So I did the same thing for my ARM SoC, and it definitley stops the RT
throttling.
However, it has the undesriable (IMO) side effect of making timed printk
output rather unhelpful for debugging suspend/resume since printk time
stays
It's impossible to have Arbitration Lost,
Read Overflow, and Tranmist Underflow all
asserted at the same time.
Those error conditions are mutually exclusive
so what the code should be doing, instead, is
check each error flag separataly.
Signed-off-by: Felipe Balbi ba...@ti.com
---
I found it works only with
fdt addr 0x9000
and precompiled linaro u-boot
On Mon, Oct 22, 2012 at 7:29 AM, kishon kis...@ti.com wrote:
Hi,
On Monday 22 October 2012 03:58 AM, Constantine Shulyupin wrote:
Hi,
Tell me please, which u-boot and u-boot configuration to use to boot
latest
Add base address and interrupt line inside Device Tree data for
OMAP5
Signed-off-by: Sebastien Guiriec s-guir...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index
Since kernel 3.7 the DTS data are not overwriten by hwmod data we can add the
address space
and interrupt line description inside dtsi file for OMAP5. This serie is
updating the
current OMAP5 IP with missing entry.
It has been tested on OMAP5 with 3.7-audio-display feature tree.
- MMC is
Add base address and interrupt line inside Device Tree data for
Signed-off-by: Sebastien Guiriec s-guir...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
Add base address and interrupt line inside Device Tree data for
OMAP5.
Signed-off-by: Sebastien Guiriec s-guir...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index
Add base address and interrupt line inside Device Tree data for
OMAP5
Signed-off-by: Sebastien Guiriec s-guir...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi
On Mon, Oct 22, 2012 at 3:52 PM, Sebastien Guiriec s-guir...@ti.com wrote:
Add base address and interrupt line inside Device Tree data for
OMAP5
Looks good to me.
Thanks ,
Reviewed-by: Shubhrajyoti D shubhrajy...@ti.com
Signed-off-by: Sebastien Guiriec s-guir...@ti.com
---
Hi Sebastien,
On Monday 22 October 2012 03:52 PM, Sebastien Guiriec wrote:
Add base address and interrupt line inside Device Tree data for
Incomplete sentence!
Signed-off-by: Sebastien Guiriec s-guir...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 16 ++--
1 file changed, 14
Hi Tony,
On 10/18/2012 12:00 PM, Benoit Cousson wrote:
On 10/18/2012 11:25 AM, Peter Ujfalusi wrote:
Fixes the following errors:
[2.318084] omap-mcbsp 49022000.mcbsp: invalid rx DMA channel
[2.324432] omap-mcbsp 49024000.mcbsp: invalid rx DMA channel
Which is because we failed to
Hi Sourav,
On 10/22/2012 01:16 PM, Sourav wrote:
Hi Sebastien,
On Monday 22 October 2012 03:52 PM, Sebastien Guiriec wrote:
Add base address and interrupt line inside Device Tree data for
Incomplete sentence!
Signed-off-by: Sebastien Guiriec s-guir...@ti.com
---
The scheduler imposes a requirement to sched_clock()
which is to stop the clock during suspend, if we don't
do that IRQ threads will be rescheduled in the future
which might cause transfers to timeout depending on
how driver is written.
This became an issue on OMAP when we converted omap-i2c.c
to
On 10/22/2012 01:57 PM, Benoit Cousson wrote:
Hi Sourav,
On 10/22/2012 01:16 PM, Sourav wrote:
Hi Sebastien,
On Monday 22 October 2012 03:52 PM, Sebastien Guiriec wrote:
Add base address and interrupt line inside Device Tree data for
Incomplete sentence!
Signed-off-by: Sebastien Guiriec
Hi,
On Saturday 20 October 2012 03:54 AM, Kevin Hilman wrote:
From: Kevin Hilman khil...@ti.com
The runtime PM framework assumes that the hardware state of devices
when initialized is disabled. For all omap_devices, we idle/disable
device by default. However, the console uart uses a no idle
Hi Paul,
What is CGRM? Is it a typo?
Regards,
Benoit
On 10/16/2012 03:32 AM, Paul Walmsley wrote:
This series removes the omap_prcm_get_reset_sources() function. This
was exported from arch/arm/mach-omap2/prcm.c for use by the OMAP
watchdog driver to report the boot reason. This series
Hi,
On Mon, Oct 22, 2012 at 02:54:37PM +0300, Felipe Balbi wrote:
The scheduler imposes a requirement to sched_clock()
which is to stop the clock during suspend, if we don't
do that IRQ threads will be rescheduled in the future
which might cause transfers to timeout depending on
how driver
Hi Benoit,
On Monday 22 October 2012 05:37 PM, Benoit Cousson wrote:
On 10/22/2012 01:57 PM, Benoit Cousson wrote:
Hi Sourav,
On 10/22/2012 01:16 PM, Sourav wrote:
Hi Sebastien,
On Monday 22 October 2012 03:52 PM, Sebastien Guiriec wrote:
Add base address and interrupt line inside Device
Hi Felipe,
On 10/22/2012 11:46 AM, Felipe Balbi wrote:
on OMAP4+ we want to read IRQSTATUS_RAW register,
instead of IRQSTATUS. The reason being that IRQSTATUS
will only contain the bits which were enabled on
IRQENABLE_SET and that will break when we need to
poll for a certain bit which
Hi,
On Mon, Oct 22, 2012 at 02:27:20PM +0200, Benoit Cousson wrote:
Hi Felipe,
On 10/22/2012 11:46 AM, Felipe Balbi wrote:
on OMAP4+ we want to read IRQSTATUS_RAW register,
instead of IRQSTATUS. The reason being that IRQSTATUS
will only contain the bits which were enabled on
On Mon, Oct 22, 2012 at 05:57:00PM +0530, Sourav wrote:
Hi Benoit,
On Monday 22 October 2012 05:37 PM, Benoit Cousson wrote:
On 10/22/2012 01:57 PM, Benoit Cousson wrote:
Hi Sourav,
On 10/22/2012 01:16 PM, Sourav wrote:
Hi Sebastien,
On Monday 22 October 2012 03:52 PM, Sebastien Guiriec
On 10/22/2012 02:27 PM, Sourav wrote:
Hi Benoit,
On Monday 22 October 2012 05:37 PM, Benoit Cousson wrote:
On 10/22/2012 01:57 PM, Benoit Cousson wrote:
Hi Sourav,
On 10/22/2012 01:16 PM, Sourav wrote:
Hi Sebastien,
On Monday 22 October 2012 03:52 PM, Sebastien Guiriec wrote:
Add base
On Monday 22 October 2012 06:20 PM, Benoit Cousson wrote:
On 10/22/2012 02:27 PM, Sourav wrote:
Hi Benoit,
On Monday 22 October 2012 05:37 PM, Benoit Cousson wrote:
On 10/22/2012 01:57 PM, Benoit Cousson wrote:
Hi Sourav,
On 10/22/2012 01:16 PM, Sourav wrote:
Hi Sebastien,
On Monday 22
prepare() is supposed to prevent new children from
being registered. On the MMC subsystem, children
(new cards) registration starts with the card
detect IRQ.
Move card detect IRQ disabling to prepare() so that
no new cards will be registered while we're trying
to suspend.
Likewise, move card
On 10/22/2012 02:28 PM, Felipe Balbi wrote:
Hi,
On Mon, Oct 22, 2012 at 02:27:20PM +0200, Benoit Cousson wrote:
Hi Felipe,
On 10/22/2012 11:46 AM, Felipe Balbi wrote:
on OMAP4+ we want to read IRQSTATUS_RAW register,
instead of IRQSTATUS. The reason being that IRQSTATUS
will only contain
Adapt keypad to use pinctrl framework.
Tested on omap4430 sdp with 3.7-rc1 kernel.
Cc: Felipe Balbi ba...@ti.com
Cc: Dmitry Torokhov dmitry.torok...@gmail.com
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
---
v1-v2
- Added PROBE_DEFER check
drivers/input/keyboard/omap4-keypad.c | 11
Currently, omap4 keypad mux settings are done in the board file.
Populate the mux settings in the dts file for the keypad to
work via dt.
Tested on omap4430 sdp with 3.7-rc1.
Cc: Felipe Balbi ba...@ti.com
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
---
v1-v2
change the hex letter to lower
Hi,
On Mon, Oct 22, 2012 at 03:05:20PM +0200, Benoit Cousson wrote:
On 10/22/2012 02:28 PM, Felipe Balbi wrote:
Hi,
On Mon, Oct 22, 2012 at 02:27:20PM +0200, Benoit Cousson wrote:
Hi Felipe,
On 10/22/2012 11:46 AM, Felipe Balbi wrote:
on OMAP4+ we want to read IRQSTATUS_RAW
on OMAP4+ we want to read IRQSTATUS_RAW register,
instead of IRQSTATUS. The reason being that IRQSTATUS
will only contain the bits which were enabled on
IRQENABLE_SET and that will break when we need to
poll for a certain bit which wasn't enabled as an
IRQ source.
One such case is after we finish
On Mon, Oct 22, 2012 at 03:59:28PM +0300, Felipe Balbi wrote:
prepare() is supposed to prevent new children from
being registered. On the MMC subsystem, children
(new cards) registration starts with the card
detect IRQ.
Move card detect IRQ disabling to prepare() so that
no new cards will
Hi,
On Mon, Oct 22, 2012 at 12:46:50PM +0300, Felipe Balbi wrote:
Hi guys,
here's another series for OMAP I2C driver. There are a few cleanups
and one very nice new feature: we can now report how many bytes
we transferred until NACK.
Note that the implemementation for OMAP-I2C turned out
Hi Sebestien,
On Monday 22 October 2012 06:26 PM, Sourav wrote:
On Monday 22 October 2012 06:20 PM, Benoit Cousson wrote:
On 10/22/2012 02:27 PM, Sourav wrote:
Hi Benoit,
On Monday 22 October 2012 05:37 PM, Benoit Cousson wrote:
On 10/22/2012 01:57 PM, Benoit Cousson wrote:
Hi Sourav,
On
On Mon, Oct 22, 2012 at 7:00 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Oct 22, 2012 at 12:46:50PM +0300, Felipe Balbi wrote:
Hi guys,
here's another series for OMAP I2C driver. There are a few cleanups
and one very nice new feature: we can now report how many bytes
we transferred
Hi Seb,
Good work. Thanks for that series.
Just update it with all the acked-by you've got from the TI driver folks
+ the minor comment and I'll pull it in the for_3.8/dts branch.
That's a detail but you should update the subject with ARM: dts: OMAP5:
XXX prefix for consistency with the latest
Hi,
On Mon, Oct 22, 2012 at 07:36:31PM +0530, Shubhrajyoti Datta wrote:
On Mon, Oct 22, 2012 at 7:00 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Oct 22, 2012 at 12:46:50PM +0300, Felipe Balbi wrote:
Hi guys,
here's another series for OMAP I2C driver. There are a few cleanups
On Monday 22 October 2012 07:36 PM, Felipe Balbi wrote:
can you also check if echo mem /sys/power/state works ? Don't forget
to enable UART wakeups with:
echo enabled /sys/devices/platform/omap_uart.2/power/wakeup
echo enabled /sys/devices/platform/omap_uart.2/tty/ttyO2/power/wakeup
Hi Benoit,
On 10/22/2012 04:11 PM, Benoit Cousson wrote:
Hi Seb,
Good work. Thanks for that series.
Just update it with all the acked-by you've got from the TI driver folks
+ the minor comment and I'll pull it in the for_3.8/dts branch.
That's a detail but you should update the subject with
Hi Sourav,
On Mon, Oct 22, 2012 at 06:43:00PM +0530, Sourav Poddar wrote:
Adapt keypad to use pinctrl framework.
Tested on omap4430 sdp with 3.7-rc1 kernel.
I do not see anything in the driver that would directly use pinctrl. Is
there a better place to select default pin configuration; maybe
Hi Paul,
On 10/20/2012 04:26 PM, Paul Walmsley wrote:
...
Other:
* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
- Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
I am not seeing this on my omap4430 panda. I have an
Hi,
On Sat, Oct 20, 2012 at 8:14 AM, Paul Walmsley p...@pwsan.com wrote:
Hi Jean
On Fri, 19 Oct 2012, Paul Walmsley wrote:
On Thu, 18 Oct 2012, Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.7-rc1.
Logs and other details at
On Sat, 2012-10-20 at 17:20 +, Paul Walmsley wrote:
Hello Venkatraman,
On Thu, 18 Oct 2012, Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.7-rc1.
Logs and other details at http://www.pwsan.com/omap/testlogs/test_v3.7-rc1/
...
Failing tests: needing
When waking up from off-mode, some IP blocks are reset automatically by
hardware. For this reason, software must wait until the reset has
completed before attempting to access the IP block.
This patch fixes for example the bug introduced by commit
6c31b2150ff96755d24e0ab6d6fea08a7bf5c44c (mmc:
* Sourav Poddar sourav.pod...@ti.com [121022 00:30]:
--- a/arch/arm/boot/dts/omap4-sdp.dts
+++ b/arch/arm/boot/dts/omap4-sdp.dts
@@ -194,6 +194,27 @@
0xbc 0x100 /* abe_mcbsp2_fsx.abe_mcbsp2_fsx INPUT
| MODE0 */
;
};
+
+ keypad_pins:
Hi Paul,
On 10/20/2012 04:26 PM, Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.7-rc2.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.7-rc2/20121020134755/
Passing tests
-
Boot to userspace: 3517evm, 3530es3beagle,
* Jon Hunter jon-hun...@ti.com [121022 09:30]:
On 10/20/2012 04:26 PM, Paul Walmsley wrote:
* 2430sdp: vfp_reload_hw oops during MMC initialization
- Kernel attempts to save FP registers that don't exist; fix posted:
- http://www.spinics.net/lists/arm-kernel/msg200646.html
Has
Peter Zijlstra pet...@infradead.org writes:
On Fri, 2012-10-19 at 16:54 -0700, Kevin Hilman wrote:
So I did the same thing for my ARM SoC, and it definitley stops the RT
throttling.
However, it has the undesriable (IMO) side effect of making timed printk
output rather unhelpful for
+Colin Cross, Barry Song also
Felipe Balbi ba...@ti.com writes:
The scheduler imposes a requirement to sched_clock()
which is to stop the clock during suspend, if we don't
do that IRQ threads will be rescheduled in the future
which might cause transfers to timeout depending on
how driver is
On Mon, 22 Oct 2012, Benoit Cousson wrote:
What is CGRM? Is it a typo?
That's the OMAP1 Clock Generation and Reset Module that contains the
ARM_SYSST register:
http://www.ti.com/lit/ug/spru678a/spru678a.pdf
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the
Hi Jon
On Mon, 22 Oct 2012, Jon Hunter wrote:
On 10/20/2012 04:26 PM, Paul Walmsley wrote:
...
Other:
* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
- Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
I am not
On Mon, 22 Oct 2012, Paul Walmsley wrote:
On Mon, 22 Oct 2012, Jon Hunter wrote:
I am not seeing this on my omap4430 panda. I have an OMAP4430 ES2.3 and
I am using u-boot release 2012.10. What do you have?
It's documented in the bootlog:
Aaro Koskinen aaro.koski...@iki.fi writes:
Hi,
On Fri, Oct 19, 2012 at 10:01:36PM +0300, Felipe Balbi wrote:
On Fri, Oct 19, 2012 at 10:03:58PM +0300, Aaro Koskinen wrote:
FYI, I saw I2C hangs also on Nokia N900 with v3.7-rc1 (omap_i2c
omap_i2c.1: timeout waiting for bus ready). After
On Mon, Oct 22, 2012 at 6:12 PM, Jean Pihet jean.pi...@newoldbits.com wrote:
Hi,
On Sat, Oct 20, 2012 at 8:14 AM, Paul Walmsley p...@pwsan.com wrote:
Hi Jean
On Fri, 19 Oct 2012, Paul Walmsley wrote:
On Thu, 18 Oct 2012, Paul Walmsley wrote:
Here are some basic OMAP test results for
On 10/22/2012 07:06 PM, Paul Walmsley wrote:
On Mon, 22 Oct 2012, Benoit Cousson wrote:
What is CGRM? Is it a typo?
That's the OMAP1 Clock Generation and Reset Module that contains the
ARM_SYSST register:
Outch, that's pretty old stuff. Thanks for the clarification.
Regards,
Benoit
--
Paul Walmsley p...@pwsan.com writes:
Hi Kevin
On Fri, 19 Oct 2012, Paul Walmsley wrote:
On Thu, 18 Oct 2012, Paul Walmsley wrote:
Here are some basic OMAP test results for Linux v3.7-rc1.
Logs and other details at http://www.pwsan.com/omap/testlogs/test_v3.7-rc1/
...
Failing
(including the lists in my reply this time, oops; also adding some more
detail)
On Mon, 22 Oct 2012, Jon Hunter wrote:
On 10/20/2012 04:26 PM, Paul Walmsley wrote:
Failing tests: fixed by posted patches
--
Boot tests:
* AM335x Beaglebone:
On Mon, 22 Oct 2012, Paul Walmsley wrote:
On Mon, 22 Oct 2012, Jon Hunter wrote:
and toolchain used for any failures.
This would indeed be useful and will try to figure out a good way to add
that information.
Just realized that some of this appears in the beginning of the bootlogs:
[
On 10/22/2012 01:35 PM, Paul Walmsley wrote:
(including the lists in my reply this time, oops; also adding some more
detail)
On Mon, 22 Oct 2012, Jon Hunter wrote:
On 10/20/2012 04:26 PM, Paul Walmsley wrote:
Failing tests: fixed by posted patches
On 10/22/2012 01:36 PM, Paul Walmsley wrote:
On Mon, 22 Oct 2012, Paul Walmsley wrote:
On Mon, 22 Oct 2012, Jon Hunter wrote:
and toolchain used for any failures.
This would indeed be useful and will try to figure out a good way to add
that information.
Just realized that some of
On Sat, Oct 20, 2012 at 07:40:19PM +, Paul Walmsley wrote:
Hi
Hi Paul.
a few comments:
On Fri, 19 Oct 2012, Mark A. Greer wrote:
From: Mark A. Greer mgr...@animalcreek.com
Convert the device data for the OMAP2 SHAM crypto IP from
explicit platform_data to hwmod. When bit 1
On Sat, Oct 20, 2012 at 07:40:44PM +, Paul Walmsley wrote:
On Fri, 19 Oct 2012, Mark A. Greer wrote:
From: Mark A. Greer mgr...@animalcreek.com
Add the DMA information for the OMAP2 SHA module.
CC: Paul Walmsley p...@pwsan.com
Signed-off-by: Mark A. Greer
On Sat, Oct 20, 2012 at 07:34:51PM +, Paul Walmsley wrote:
On Fri, 19 Oct 2012, Mark A. Greer wrote:
From: Mark A. Greer mgr...@animalcreek.com
This series updates the crypto omap-sham driver and supporting
infrastructure.
Looks pretty good; this will make it easier for us to
On Sun, Oct 21, 2012 at 11:58:36AM +0530, Santosh Shilimkar wrote:
Mark,
Hi Santosh.
On Saturday 20 October 2012 03:23 AM, Mark A. Greer wrote:
From: Mark A. Greer mgr...@animalcreek.com
This series updates the crypto omap-sham driver and supporting
infrastructure.
Notes:
a) Based
On Mon, 22 Oct 2012, Mark A. Greer wrote:
On Sat, Oct 20, 2012 at 07:40:19PM +, Paul Walmsley wrote:
static void omap_init_sham(void)
{
- if (cpu_is_omap24xx()) {
- sham_device.resource = omap2_sham_resources;
- sham_device.num_resources =
On 19.10.2012 17:34, Afzal Mohammed wrote:
Hi Daniel,
On Thursday 11 October 2012 05:15 PM, Daniel Mack wrote:
Could you tell me which patches I need on top of soon-to-be-3.7-rc1? I
would like to augment this to make GPMC attached NAND probable in DT, in
case this is still an open topic.
On Mon, 22 Oct 2012, Mark A. Greer wrote:
On Sat, Oct 20, 2012 at 07:40:44PM +, Paul Walmsley wrote:
On Fri, 19 Oct 2012, Mark A. Greer wrote:
From: Mark A. Greer mgr...@animalcreek.com
Add the DMA information for the OMAP2 SHA module.
CC: Paul Walmsley p...@pwsan.com
Pass an optional device_node pointer in the platform data, which in turn
will be put into a mtd_part_parser_data. This way, code that sets up the
platform devices can pass along the node from DT so that the partitions
can be parsed.
For non-DT boards, this change has no effect.
Signed-off-by:
This is a series of patches to support GPMC peripherals on OMAP boards.
Depends on Linus' master +
omap-next (branch omap-for-v3.8/cleanup-headers-gpmc)
The only supported peripheral for now is NAND, but other types would be
easy to add.
In order to make the gpmc driver the 'hub' for all
Signed-off-by: Daniel Mack zon...@gmail.com
---
arch/arm/mach-omap2/gpmc-nand.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach-omap2/gpmc-nand.c
index 8607735..c3616c6 100644
--- a/arch/arm/mach-omap2/gpmc-nand.c
+++
On DT driven boards, the gpmc node will match the driver. Hence, there's
no need to do that unconditionally from the initcall.
Signed-off-by: Daniel Mack zon...@gmail.com
---
arch/arm/mach-omap2/gpmc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-omap2/gpmc.c
This patch adds basic DT bindings for OMAP GPMC.
The actual peripherals are instanciated from child nodes within the GPMC
node, and the only type of device that is currently supported is NAND.
Code was added to parse the generic GPMC timing parameters and some
documentation with examples on how
On Mon, Oct 22, 2012 at 07:53:06PM +, Paul Walmsley wrote:
On Mon, 22 Oct 2012, Mark A. Greer wrote:
On Sat, Oct 20, 2012 at 07:40:44PM +, Paul Walmsley wrote:
On Fri, 19 Oct 2012, Mark A. Greer wrote:
From: Mark A. Greer mgr...@animalcreek.com
Add the DMA
From: Kevin Hilman khil...@ti.com
After commit 24d7b40a60cf19008334bcbcbd98da374d4d9c64 (ARM: OMAP2+:
PM: MPU DVFS: use generic CPU device for MPU-SS), OPPs are registered
using an existing CPU device, not the omap_device for MPU-SS.
First, fix the board file to use get_cpu_device() as required
Hi all,
I noticed these two issues while testing some pinctrl
related changes.
Regards,
Tony
---
Tony Lindgren (2):
ARM: OMAP2+: Fix location of select PINCTRL
ARM: OMAP3: Fix 3430 legacy mux names for ssi1 signals.
0 files changed
--
Signature
--
To unsubscribe from this
Commit 8f31cefe (ARM: OMAP2+: select PINCTRL in Kconfig)
added select PINCTRL, but accdentally added it to a wrong
location.
We want to select if for ARCH_OMAP2PLUS, not for
ARCH_OMAP2PLUS_TYPICAL.
Signed-off-by: Tony Lindgren t...@atomide.com
---
0 files changed
diff --git
On n900 uart1 pins are not not used for uart, instead they are
used to connect to a cell modem over ssi. Looks like we're
currently missing these signal names for 3430 for some reason,
and only have some of them listed for 3630. Obviously the signals
are there for 3430 if n900 is using them and
* Péter Ujfalusi peter.ujfal...@ti.com [121022 04:42]:
Hi Tony,
On 10/18/2012 12:00 PM, Benoit Cousson wrote:
On 10/18/2012 11:25 AM, Peter Ujfalusi wrote:
Fixes the following errors:
[2.318084] omap-mcbsp 49022000.mcbsp: invalid rx DMA channel
[2.324432] omap-mcbsp
Kevin Hilman khil...@deeprootsystems.com writes:
Aaro Koskinen aaro.koski...@iki.fi writes:
Hi,
On Fri, Oct 19, 2012 at 10:01:36PM +0300, Felipe Balbi wrote:
On Fri, Oct 19, 2012 at 10:03:58PM +0300, Aaro Koskinen wrote:
FYI, I saw I2C hangs also on Nokia N900 with v3.7-rc1 (omap_i2c
1 - 100 of 115 matches
Mail list logo
