Add Runtime PM support to C_CAN/D_CAN controller. The runtime PM
APIs control clocks for C_CAN/D_CAN IP and prevent access to the
register of C_CAN/D_CAN IP when clock is turned off.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
This patch has been tested on AM335X EVM. Due to lack of hardware
Hi Matthias,
Can you comment on my latest patch? So that I can fix this issue
on the same.
https://patchwork.kernel.org/patch/1220151/
Thanks
AnilKumar
On Thu, Aug 09, 2012 at 02:30:51, Matthias Kaehlcke wrote:
tps65217_parse_dt() allocates a struct tps65217_board for each regulator
Hi,
El Fri, Jul 20, 2012 at 03:00:01PM +0530 AnilKumar Ch ha dit:
Regulator platform data handling was mistakenly added to MFD
driver. So we will see build errors if we compile MFD drivers
without CONFIG_REGULATOR. This patch moves regulator platform
data handling from TPS65217 MFD driver to
The following patch series add i2c support for omap5.
As well as enable I2C based devices like pressure and temperature
through device tree. Also add onchip keypad dts data.
Cc: Benoit Cousson b-cous...@ti.com
Cc: Felipe Balbi ba...@ti.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Sourav
Add I2C data node in omap5 device tree file.
Tested on omap5430 evm.
Cc: Benoit Cousson b-cous...@ti.com
Cc: Felipe Balbi ba...@ti.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Sourav Poddar sourav.pod...@ti.com
---
Add bmp085 pressure sensor data in omap5 evm dts file.
Tested on omap5430 evm with 3.5 custom kernel.
Cc: Benoit Cousson b-cous...@ti.com
Cc: Felipe Balbi ba...@ti.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Sourav Poddar
Add tmp102 temperature sensor data in omap5 evm dts file.
Tested on omap5430 evm with 3.5 custom kernel.
Cc: Benoit Cousson b-cous...@ti.com
Cc: Felipe Balbi ba...@ti.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Sourav Poddar
Add keypad data node in omap5 device tree file.
Also fill the device tree binding parameters
with the required value in omap5-evm dts file.
Tested on omap5430 evm with 3.5 custom kernel.
Cc: Benoit Cousson b-cous...@ti.com
Cc: Felipe Balbi ba...@ti.com
Cc: Santosh Shilimkar
Add keypad data node in omap5 device tree file.
Also fill the device tree binding parameters
with the required value in omap5-evm dts file.
Tested on omap5430 evm with 3.5 custom kernel.
Cc: Benoit Cousson b-cous...@ti.com
Cc: Felipe Balbi ba...@ti.com
Cc: Santosh Shilimkar
Add bmp085 pressure sensor data in omap5 evm dts file.
Tested on omap5430 evm with 3.5 custom kernel.
Cc: Benoit Cousson b-cous...@ti.com
Cc: Felipe Balbi ba...@ti.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Sourav Poddar
These are the few device tree related patches which has been posted and
reviewed on the list. They are intended for 3.7 merge window but I am
posting them early enough to get into linux-next and linux-omap for testing.
The following changes since commit 0d7614f09c1ebdbaa1599a5aba7593f147bf96ee:
From: Aneesh V ane...@ti.com
EMIF - External Memory Interface - is an SDRAM controller used in
TI SoCs. EMIF supports, based on the IP revision, one or more of
DDR2/DDR3/LPDDR2 protocols. This binding describes a given instance
of the EMIF IP and memory parts attached to it.
Reviewed-by: Benoit
From: Aneesh V ane...@ti.com
Device tree data for the EMIF sdram controllers in OMAP4
and LPDDR2 memory devices attached to OMAP4 boards.
Reviewed-by: Benoit Cousson b-cous...@ti.com
Reviewed-by: Grant Likely grant.lik...@secretlab.ca
Tested-by: Lokesh Vutla lokeshvu...@ti.com
Signed-off-by:
This provides PL310 Level 2 Cache Controller Device Tree
support for OMAP4 based devices.
Cc: Benoit Cousson b-cous...@ti.com
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |7 +++
arch/arm/mach-omap2/omap4-common.c |6 +-
2 files
Add cortex-a9 local timer support for all OMAP4 based
SOCs using DT.
Cc: Benoit Cousson b-cous...@ti.com
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |6 ++
arch/arm/mach-omap2/timer.c |6 ++
2 files changed, 12 insertions(+)
diff
From: Aneesh V ane...@ti.com
device tree bindings for LPDDR2 SDRAM memories compliant
to JESD209-2 standard.
The 'lpddr2' binding in-turn uses another binding 'lpddr2-timings'
for specifying the AC timing parameters of the memory device at
different speed-bins.
Reviewed-by: Benoit Cousson
Below are the couple of patches which enables the architected cpu local timer
support for OMAP5 devices.
Santosh Shilimkar (2):
ARM: OMAP: Add initialisation for the real-time counter.
ARM: OMAP5: Enable arch timer support
arch/arm/boot/dts/omap5.dtsi |6 +++
arch/arm/mach-omap2/Kconfig
Enable Cortex A15 generic timer support for OMAP5 based SOCs.
The CPU local timers run on the free running real time counter clock.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/boot/dts/omap5.dtsi |6 ++
arch/arm/mach-omap2/Kconfig |1 +
The real time counter also called master counter, is a free-running
counter. It produces the count used by the CPU local timer peripherals
in the MPU cluster. The timer counts at a rate of 6.144 MHz.
The ratio registers needs to be configured based on system clock
only onetime. After
Sourav,
On Mon, Aug 13, 2012 at 3:35 PM, Sourav Poddar sourav.pod...@ti.com wrote:
The following patch series add i2c support for omap5.
As well as enable I2C based devices like pressure and temperature
through device tree. Also add onchip keypad dts data.
Cc: Benoit Cousson
All the cpu_is checks have been moved to dispc_init_features function providing
a much more generic and cleaner interface. The OMAP version and revision
specific functions and data are initialized by dispc_features structure which is
local to dispc.c.
Signed-off-by: Chandrabhanu Mahapatra
All the cpu_is checks have been moved to dss_init_features function providing a
much more generic and cleaner interface. The OMAP version and revision specific
initializations in various functions are cleaned and the necessary data are
moved to dss_features structure which is local to dss.c.
On 08/13/2012 08:49 AM, AnilKumar Ch wrote:
Add Runtime PM support to C_CAN/D_CAN controller. The runtime PM
APIs control clocks for C_CAN/D_CAN IP and prevent access to the
register of C_CAN/D_CAN IP when clock is turned off.
Signed-off-by: AnilKumar Ch anilku...@ti.com
Looks good, minor
Hi,
I am planning to support BCH8 error correction using ELM module
in AM33xx.
Please let me know if any work or plan is there to support ELM
module in OMAP?
Thanks
Avinash Philip
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
On Fri, Jul 27, 2012 at 5:44 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Mon, Jul 23, 2012 at 8:04 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Mon, Jul 23, 2012 at 7:38 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Jul 23, 2012 at 07:31:10PM +0530, Munegowda, Keshava
* Timo Kokkonen timo.t.kokko...@iki.fi [120812 03:46]:
Calling omap_dm_timer_prepare while the spinlock is held is not
allowed as sleeping functions are called later on during the
preparation (namely within clk_get()).
dm_timer_lock is only required for protecting the
omap_timer_list. After
Hi Matthias,
On Mon, Aug 13, 2012 at 13:57:32, Matthias Kaehlcke wrote:
Hi,
El Fri, Jul 20, 2012 at 03:00:01PM +0530 AnilKumar Ch ha dit:
Regulator platform data handling was mistakenly added to MFD
driver. So we will see build errors if we compile MFD drivers
without
Hi Marc,
Thanks for the review.
On Mon, Aug 13, 2012 at 17:40:22, Marc Kleine-Budde wrote:
On 08/13/2012 08:49 AM, AnilKumar Ch wrote:
Add Runtime PM support to C_CAN/D_CAN controller. The runtime PM
APIs control clocks for C_CAN/D_CAN IP and prevent access to the
register of C_CAN/D_CAN
Add Runtime PM support to C_CAN/D_CAN controller. The runtime PM
APIs control clocks for C_CAN/D_CAN IP and prevent access to the
register of C_CAN/D_CAN IP when clock is turned off.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
This patch has been tested on AM335X EVM. Due to lack of hardware
On Mon, Aug 13, 2012 at 06:52:13PM +0530, Munegowda, Keshava wrote:
On Fri, Jul 27, 2012 at 5:44 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Mon, Jul 23, 2012 at 8:04 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Mon, Jul 23, 2012 at 7:38 PM, Felipe Balbi ba...@ti.com
Move the McBSP CLKS re-parenting code to ASoC driver from
arch/arm/mach-omap2.
The call fort the re-parenting has been already limited to OMAP2+ SoC in
the ASoC driver. There is no longer need to have callback function for it.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Jarkko
Hello,
Changes since v1:
- ICLK workaround for the sidetone module has been kept for legacy mode.
Intro mail ffrom v1 (updated):
in order to be able to add DT support for the McBSP driver which is used on all
OMAP platforms (OMAP1/2/3/4/5) I needed to make some cleanups to the stack:
- Removing
On OMAP2430 all McBSP ports have 128 word long buffer, enable the use of
the FIFO for the audio stack.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Jarkko Nikula jarkko.nik...@bitmer.com
---
arch/arm/mach-omap2/mcbsp.c |5 -
1 files changed, 4 insertions(+), 1
The muxing is done at board level, no need to do it in the ASoC machine
driver.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Jarkko Nikula jarkko.nik...@bitmer.com
---
sound/soc/omap/am3517evm.c | 20 ++--
1 files changed, 2 insertions(+), 18 deletions(-)
diff
NUM_LINKS is no longer in use by the code.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Jarkko Nikula jarkko.nik...@bitmer.com
---
sound/soc/omap/omap-mcbsp.h | 16
1 files changed, 0 insertions(+), 16 deletions(-)
diff --git a/sound/soc/omap/omap-mcbsp.h
We can use the has_ccr flag to replace the cpu_is_omap* checks.
This provides future proof implementation and we do not need to update the
code if new OMAP revision starts to use the McBSP driver.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Jarkko Nikula jarkko.nik...@bitmer.com
Only create the devices in a legacy way if we do not have the DT data.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/mcbsp.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/mcbsp.c b/arch/arm/mach-omap2/mcbsp.c
index
Device tree support for McBSP modules on OMAP2+ SoC.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
.../devicetree/bindings/sound/omap-mcbsp.txt | 45 +
sound/soc/omap/omap-mcbsp.c| 66 +++-
2 files changed, 110
am3517evm board uses McBSP1 for audio with 4pin configuration.
The CLKR/FSR signals need to be connected to CLKX/FSX pin of the SoC in
this case.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Jarkko Nikula jarkko.nik...@bitmer.com
---
arch/arm/mach-omap2/board-am3517evm.c | 13
Remove the feature to configure the CLKR/FSR mux on McBSP port with 6pin
configuration.
When moving to devicetree these callback can no longer be used in a clean
way anymore.
If a board require to change the 6pin port to work in 4pin setup it needs
to set up the mux in the board file.
For OMAP2/3:
Hi,
On Mon, Aug 13, 2012 at 12:34:53PM +1000, NeilBrown wrote:
On Thu, 9 Aug 2012 14:15:51 +0300 Felipe Balbi ba...@ti.com wrote:
hehe, that's nasty. Please send a patch converting to a try count and a
udelay_range(), or something.
how's this?
Thanks,
NeilBrown
From:
On Mon, Aug 13, 2012 at 7:39 PM, Felipe Balbi ba...@ti.com wrote:
On Mon, Aug 13, 2012 at 06:52:13PM +0530, Munegowda, Keshava wrote:
On Fri, Jul 27, 2012 at 5:44 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Mon, Jul 23, 2012 at 8:04 PM, Munegowda, Keshava
keshava_mgo...@ti.com
Regulator platform data handling was mistakenly added to MFD
driver. So we will see build errors if we compile MFD drivers
without CONFIG_REGULATOR. This patch moves regulator platform
data handling from TPS65217 MFD driver to regulator driver.
This makes MFD driver independent of REGULATOR
On Mon, Aug 13, 2012 at 08:36:05PM +0530, AnilKumar Ch wrote:
Regulator platform data handling was mistakenly added to MFD
driver. So we will see build errors if we compile MFD drivers
without CONFIG_REGULATOR. This patch moves regulator platform
data handling from TPS65217 MFD driver to
On Mon, Aug 13, 2012 at 05:22:40PM +0300, Peter Ujfalusi wrote:
+ fck_src = clk_get(mcbsp-dev, src);
+ if (IS_ERR_OR_NULL(fck_src)) {
I know the same error is in the original code, but let's stop propagating
it. IS_ERR() only here please.
--
To unsubscribe from this list: send the line
On 8/13/2012 4:37 PM, Santosh Shilimkar wrote:
The real time counter also called master counter, is a free-running
counter. It produces the count used by the CPU local timer peripherals
in the MPU cluster. The timer counts at a rate of 6.144 MHz.
The ratio registers needs to be configured
Hi,
On 08/10/12 13:16, Timo Kokkonen wrote:
These patches add the support for sending IR remote controller codes
on the Nokia N900 phone. The code is taken from the public N900 kernel
release and modified to work with today's kernel.
The code has been tested with a real Nokia N900 device
NeilBrown ne...@suse.de writes:
On Fri, 10 Aug 2012 11:49:27 -0700 Kevin Hilman khil...@ti.com wrote:
Hello,
In doing some automated testing of suspend/resume I noticed that
repeated attempts to suspend and resume via RTC wakeup fail on
3530/Beagle and 3730/Beagle-xM, but work fine on
On Fri, Aug 10, 2012 at 01:16:36PM +0300, Timo Kokkonen wrote:
This is the driver for the IR transmitter diode found on the Nokia
N900 (also known as RX51) device. The driver is mostly the same as
found in the original 2.6.28 based kernel that comes with the device.
The following
On 08/13/12 21:36, Sean Young wrote:
On Fri, Aug 10, 2012 at 01:16:36PM +0300, Timo Kokkonen wrote:
+static ssize_t lirc_rx51_write(struct file *file, const char *buf,
+ size_t n, loff_t *ppos)
+{
+int count, i;
+struct lirc_rx51 *lirc_rx51 = file-private_data;
Hi AnilKumar,
El Mon, Aug 13, 2012 at 01:35:55PM + AnilKumar, Chimata ha dit:
also the tps65217_board structure should be renamed to something like
tps65217_regulators, now that it is specific to the regulator
Not required because tps65217_board might contain platform data for WLED/
This is an automatic generated email to let you know that the following patch
were queued at the
http://git.linuxtv.org/media_tree.git tree:
Subject: [media] ARM: mach-omap2: board-rx51-peripherals: Add lirc-rx51 data
Author: Timo Kokkonen timo.t.kokko...@iki.fi
Date:Fri Aug 10 06:16:37
This is an automatic generated email to let you know that the following patch
were queued at the
http://git.linuxtv.org/media_tree.git tree:
Subject: [media] media: rc: Introduce RX51 IR transmitter driver
Author: Timo Kokkonen timo.t.kokko...@iki.fi
Date:Fri Aug 10 06:16:36 2012 -0300
On Mon, 13 Aug 2012 17:32:34 +0300 Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Aug 13, 2012 at 12:34:53PM +1000, NeilBrown wrote:
On Thu, 9 Aug 2012 14:15:51 +0300 Felipe Balbi ba...@ti.com wrote:
hehe, that's nasty. Please send a patch converting to a try count and a
Hi Greg,
On Mon, Aug 13, 2012 at 20:53:54, Greg KH wrote:
On Mon, Aug 13, 2012 at 08:36:05PM +0530, AnilKumar Ch wrote:
Regulator platform data handling was mistakenly added to MFD
driver. So we will see build errors if we compile MFD drivers
without CONFIG_REGULATOR. This patch moves
55 matches
Mail list logo
