On 02/05/2013 07:40 PM, Tony Lindgren wrote:
For some reason the CONFIG_DEBUG_SECTION_MISMATCH got disabled in my rolling
kernel config...
At least gcc version 4.3.5 (Debian 4.3.5-4) shows them. What's
the compiler you have?
It show for me as well now that I have enabled the
On 01/30/2013 12:46 PM, Chen Gang wrote:
the fields must be null-terminated:
the caller may use it as null-terminted string, next.
Signed-off-by: Chen Gang gang.c...@asianux.com
Acked-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/twl-common.c |3 ++-
1 file
Hi Tony,
On 02/01/2013 11:45 PM, Tony Lindgren wrote:
* Chen Gang gang.c...@asianux.com [130130 03:50]:
the fields must be null-terminated:
the caller may use it as null-terminted string, next.
Added Peter to cc on this one too, it's best that he queues
all the twl changes.
I can
Hi Tony,
On 01/22/2013 11:07 AM, Peter Ujfalusi wrote:
Hi Tony,
The content of this pull:
update for audio support via omap-twl4030 and pwm updates in board level:
http://www.spinics.net/lists/linux-omap/msg85085.html
and zoom-peripherals update to not request the TWL GPIO7:
http
:11: note: each undeclared identifier
is reported only once for each function it appears in
make[1]: *** [arch/arm/mach-omap2/omap_hwmod_reset.o] Error 1
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Hi Paul,
I could not find the patches from Sebastien's series:
http://www.mail
On 01/24/2013 10:14 PM, Florian Vaussard wrote:
You are right. But then the pwm core must provide a way to know if the pwm
access function are callable
from atomic context or not (the gpio framework provides gpio_cansleep()).
This implies a good amount of changes to the pwm framework, and
On 01/25/2013 09:29 AM, Peter Ujfalusi wrote:
On 01/24/2013 10:14 PM, Florian Vaussard wrote:
You are right. But then the pwm core must provide a way to know if the pwm
access function are callable
from atomic context or not (the gpio framework provides gpio_cansleep()).
This implies a good
On 01/25/2013 01:21 PM, Florian Vaussard wrote:
We have two drivers at the moment: pwm-twl and pwm-twl-led. However new out
of
SoC PWM drivers might come (for example for palmas). So it worth take a look
at some generic implementation.
OK. So I have the series. I need to add few more
Hi,
On 01/23/2013 06:56 PM, Florian Vaussard wrote:
Convert the on-board LED connected to the TWL4030 (LEDB) to use
pwm-leds.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
Hi,
On 01/23/2013 06:56 PM, Florian Vaussard wrote:
Add the needed sections to enable audio support on Overo.
Looks fine for me.
Reviewed-by: Peter Ujfalusi peter.ujfal...@ti.com
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi | 14
On 01/24/2013 04:42 PM, Florian Vaussard wrote:
I did it at first, but the led API executes in atomic context, where the
pwm-twl-led driver uses i2c communication. Setting a trigger will result in a
kernel panic.
Now that you mentioned it, this might be true.
I am working on a patch for
it can go and later when we have the fix for the slow path you can add
the default trigger.
Reviewed-by: Peter Ujfalusi peter.ujfal...@ti.com
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
Hi Tony,
On 01/18/2013 06:49 PM, Tony Lindgren wrote:
Currently it seems that we need the following working with DT to have panda
and blaze usable:
1. MMC (done)
2. USB (patches pending for EHCI and MUSB)
3. Ethernet (done for blaze, needs USB for panda)
4. DSS (various drivers pending,
to e4f4e8bfa47431b91fbb21dd9b86d9bc2c15cbd7:
ARM: board-zoom: Do not request LCD panel enable GPIO from twl4030
(2013-01-22 10:35:16 +0100)
Peter Ujfalusi (9):
ARM: OMAP: 3430sdp: Enable extmute functionality for audio
://gitorious.org/omap-audio/linux-audio.git peter/for-benoit
for you to fetch changes up to b6230ae20bc018d042d703d0667ba9e7ac027ccb:
ARM: dts: omap4-sdp: Add support for pwm-backlight (2013-01-22 11:08:37 +0100)
Peter Ujfalusi (5
HI Benoit,
On 01/22/2013 11:39 AM, Benoit Cousson wrote:
+
+twl_pwm: pwm {
+/* provides two PWMs (id 0, 1 for PWM1 and PWM2) */
+compatible = ti,twl6030-pwm;
+#pwm-cells = 2;
+};
+
+twl_pwmled: pwmled {
+/* provides one PWM (id
On 01/22/2013 04:21 PM, kishon wrote:
But it's better to check if deferred probing
takes place whenever a new driver is bound to a device as you just mentioned.
Whenever you load (might be also when you unload) a driver the deferred
modules will try to probe again. This is to check back if the
Hi,
On 01/20/2013 04:04 AM, Pali Rohár wrote:
Signed-off-by: Pali Rohár pali.ro...@gmail.com
This is really welcome.
It would be even better if we would have commit message...
Also for ASoC patches please CC alsa-devel and the maintainers so they will
also have a chance to review.
There are
Hi,
On 01/20/2013 04:04 AM, Pali Rohár wrote:
This patch series updating rx51 sound driver, using snd_soc_register_card,
adding module alias for autoloading kernel driver and registring sound
driver in rx51 board code.
Pali Rohár (2):
ASoC: omap: rx51: Use snd_soc_register_card and add
-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Hi Tony,
This patch is generated on top of my previous series for audio/pwm support:
http://www.spinics.net/lists/linux-omap/msg85085.html
Regards,
Peter
arch/arm/mach-omap2/board-zoom-peripherals.c | 12 +---
1 file changed, 1 insertion(+), 11
Hi Tony,
On 01/18/2013 12:16 AM, Tony Lindgren wrote:
Well we are planning to drop the non-DT support for omap4 as soon as it's
usable with DT.
Exactly, but right now we do have legacy and legacy should work in order to
help for example Luca to make the final push which allows us to move to DT
Hi Paul,
On 01/17/2013 07:43 PM, Paul Walmsley wrote:
The following patch fixes these:
https://lkml.org/lkml/2012/12/24/3
Thanks, I've added that info in the v3.8-rc3 test summary, and moved the
paragraph to the 'resolved by posted patches' section.
FYI: the patch is now in mainline
Enable the use of extmute on the HS path.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-3430sdp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-omap2/board-3430sdp.c
b/arch/arm/mach-omap2/board-3430sdp.c
index bb73afc..40c22a7 100644
and
backlight on these boards.
As a note: 4430SDP never had working backlight and the charger led did not
worked for couple of releases already due to wrong pwm_id.
On BeagleBoard we will be able to adjust the brighness of pmu_stat LED instead
of full on/off.
Regards,
Peter
---
Peter Ujfalusi (8
Select the most commonly used audio configuration on boards with twl4030
audio:
Headset, Handsfree output and Line in input
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/twl-common.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/arm
Boards with special audio routing can pass a custom omap_tw4030_pdata to the
audio machine driver.
At the same time update the board files using the same audio driver.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-cm-t35.c | 2 +-
arch/arm/mach-omap2
Use the common omap-twl4030 ASoC machine driver for audio.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-zoom-peripherals.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c
b/arch/arm/mach
the pwm_id was incorrect.
With the other patches we will be able to control the followings:
LCD backlight via pwm-backlight driver
Keypad leds via leds_pwm driver as normal LED
Charging indicator via leds_pwm driver as normal LED
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach
Use the common omap-twl4030 ASoC machine driver for audio.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-3430sdp.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/mach-omap2/board-3430sdp.c
b/arch/arm/mach-omap2/board-3430sdp.c
With the PWM backed driver the PMU_STAT led's brighness can be controlled.
This needs the new drivers for the TWL PWM/LED to work.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 39 ++---
1 file changed, 31 insertions
The HS extmute is not used on Zoom2 boards. Furthermore the GPIO153 is used
as IRQ for the TSC2004 touchscreen controller - for which we do not have
driver upstream, yet.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-zoom-peripherals.c | 11 +++
1 file
Hi,
Add the needed DT sections for twl4030 and twl6030 for the PWM childs.
Update the omap4-sdp to have working backlight and keypad/charging LED support.
Use the pwm-leds driver on BeagleBoard for the pmu_stat LED instead of the hacky
twl403-gpio mapped PWM.
Regards,
Peter
---
Peter Ujfalusi (5
Enable support for the PWMs and LEDs as PWM drivers.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/twl4030.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index ed0bc95..d216853
Enable support for the PWMs and LED as PWM drivers.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/twl6030.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/twl6030.dtsi b/arch/arm/boot/dts/twl6030.dtsi
index 9996cfc..d9b8b21
We have proper driver stack to handle the pmu_stat LED which is connected
PWMB of twl4030.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap3-beagle-xm.dts | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/omap3
Sections to describe the pwm-leds in the system.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
index 43e5258..8101a94
Section to describe the backlight for the LCD panels.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
index 8101a94..c2dee41
Hi Luca,
On 01/16/2013 10:45 PM, Luciano Coelho wrote:
The code to enable and disable the WiLink shared transport has been
removed from the TI-ST driver, so it must be implemented in the board
files instead. Add the relevant operations to Panda's board file.
Additionally, add the UART2
On 01/17/2013 10:34 AM, Felipe Balbi wrote:
I just wonder how this is going to work with DT... You are not going to have
the ability to use callback in this form.
I think the GPIO handling should be done in the driver itself rather than in
the board file.
that can (should ?) be moved to
Hi Luca,
On 01/17/2013 10:35 AM, Luciano Coelho wrote:
I just wonder how this is going to work with DT... You are not going to have
the ability to use callback in this form.
I think the GPIO handling should be done in the driver itself rather than in
the board file.
I agree. The problem
-by: Peter Ujfalusi peter.ujfal...@ti.com
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Linus,
On 01/17/2013 11:43 AM, Linus Walleij wrote:
On Thu, Jan 10, 2013 at 2:09 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
On 01/10/2013 11:41 AM, Linus Walleij wrote:
Sorry Peter this must have been missed somehow.
This does not apply to the current v3.8-rc3, could you respin
Hi,
On 01/15/2013 06:43 PM, Paul Barker wrote:
I've written a quick driver which issues SPI reads in response to hrtimer
events
to see if this is possible. I'm getting a rough average latency of 100us
between
calling spi_async() and the clock signal changing. This is no use for reading
a
Fixes the following boot time warning:
[2.230865] WARNING: at drivers/video/backlight/backlight.c:315
backlight_device_register+0x184/0x1f4()
[2.240386] nec-8048: invalid backlight type
We need to pass valid backlight type when the device is registered.
Signed-off-by: Peter Ujfalusi
Do not register a backlight device when the dssdev-set_backlight callback
is not set by the board.
In this case either we do not have means to control the backlight or the
board is using other means to control it, like bl-pwm.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
.../omap2
It has only a pointer to the backlight_device in it. We can just add the
pointer to the backlight_device as driver data.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
.../omap2/displays/panel-nec-nl8048hl11-01b.c | 32 +-
1 file changed, 7 insertions(+), 25
should not register another backlight device
in the NEC panel driver.
Regards,
Peter
---
Peter Ujfalusi (3):
OMAPDSS: Panel NEC: Set backlight type to remove boot time warning
OMAPDSS: Panel NEC: Get rid of nec_80848_data structure
OMAPDSS: Panel NEC: Only register backlight when we have valid
letter from v1:
Second part of the cleanup of twl-core which aims to make the code a bit more
readable.
It has been tested on: OMAP4 PandaBoard, OMAP4 Blaze, OMAP3 BeagleBoard, OMAP3
Zoom2.
Regards,
Peter
---
Peter Ujfalusi (11):
ARM: OMAP: zoom-display: Remove the use of TWL4030_MODULE_PWM1
At boot time we can allocate the twl_modules array dynamically based on the
twl class we are using with devm_kzalloc() instead of the static
twl_modules[] array.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 31 +--
1 file changed
Gather the global variables under a single structure and allocate it with
devm_kzalloc(). It is easier to see them and if in the future we try to add
support for multiple instance of twl in the system it is going to be much
simpler.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers
twl_i2c_read/write_u8 become as a simple wrapper over the twl_i2c_read/write.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 28
include/linux/i2c/twl.h | 17 +++--
2 files changed, 11 insertions(+), 34 deletions
Instead of using SUB_CHIP_ID* or magic numbers use the twl_mapping table to
look for the subchip ID.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 56 --
1 file changed, 27 insertions(+), 29 deletions(-)
diff
With the regmap conversion there is no longeer a need to allocate bigger
buffer for writes
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 3 ---
include/linux/i2c/twl.h | 3 ---
2 files changed, 6 deletions(-)
diff --git a/drivers/mfd/twl-core.c b/drivers/mfd
We can fail earlier in case multiple instance of the twl-core is tried to
be loaded.
The twl-core by design only supports one instance.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git
When booted with DT we can manage without the dummy pdata.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 31 +++
1 file changed, 7 insertions(+), 24 deletions(-)
diff --git a/drivers/mfd/twl-core.c b/drivers/mfd/twl-core.c
index
There is really no point to retry to add children devices in case the
of_platform_populate() fails.
We do not have any information provided via pdata in this case anyways.
Depending on the boot type (legacy or DT) only execute either one.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
The module id table no longer can have invalid/unused entries.
No need for checking the ID for validity.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/mfd/twl-core.c b
Use the future proof TWL_MODULE_PWM module id instead to aim the twl-core
cleanup planed for 3.9 kernel cycle.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/board-zoom-display.c | 14 +++---
1 file changed, 7
-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 105 +++-
include/linux/i2c/twl.h | 66 --
2 files changed, 86 insertions(+), 85 deletions(-)
diff --git a/drivers/mfd/twl-core.c b/drivers/mfd/twl-core.c
index
Hi Paul,
On 01/14/2013 06:59 PM, Paul Walmsley wrote:
Failing tests: needing investigation
Build tests:
* rmk_3430_ldp_allnoconfig, rmk_4430_sdp_allnoconfig: twl4030 build failures
- in drivers/mfd/twl-core.c
The following patch fixes these:
Hi Samuel,
On 12/31/2012 12:09 PM, Peter Ujfalusi wrote:
Hello,
Second part of the cleanup of twl-core which aims to make the code a bit more
readable.
It has been tested on: OMAP4 PandaBoard, OMAP4 Blaze, OMAP3 BeagleBoard, OMAP3
Zoom2.
I will resend the series since I need to add two
Hi,
On 01/11/2013 05:27 PM, Paul Barker wrote:
What functions you were using from the McBSP driver(s)?
I'm just using the request, free, start, stop and config functions, then
using DMA to copy data.
OK.
I have taken a brief look at ADS1672 datasheet. At first glance I would think
that
with Beagleboard patches and config from
https://github.com/beagleboard/kernel (branch beagleboard-3.2). I'd
like to keep up-to-date with the more recent kernels but my module
won't compile with them.
When the OMAP McBSP driver stack was merged into a single driver
(commit 45656b4 by Peter
Hi Linus,
On 01/10/2013 11:41 AM, Linus Walleij wrote:
On Thu, Dec 20, 2012 at 10:44 AM, Peter Ujfalusi peter.ujfal...@ti.com
wrote:
Use more coherent locking in the driver. Use bitfield to store the GPIO
direction and if the pin is configured as output store the status also in a
bitfiled
Use the future proof TWL_MODULE_PWM module id instead to aim the twl-core
cleanup planed for 3.9 kernel cycle.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Hi Tony,
can you queue this patch for 3.8 cycle?
With the second part of my twl-core cleanup series I have overlooked this file
On 01/04/2013 12:26 AM, Paul Walmsley wrote:
On Thu, 3 Jan 2013, Jon Hunter wrote:
I am not sure that this change to the comment is completely accurate. On
OMAP4430 I did not see any issues with the DPLL failing to turn on if
the DPLL was not locked. I only saw this particular problem on the
for all OMAP4 revisions not only for 446x and McPDM
need to be configured to no IDLE mode during activity.
Regards,
Peter
---
Peter Ujfalusi (2):
ARM: OMAP4: clock data: Lock ABE DPLL on all revisions
ARM: OMAP4: hwmod_data: Correct IDLEMODE for McPDM
arch/arm/mach-omap2/cclock44xx_data.c
To avoid issues with audio caused by non locked ABE DPLL we should
make sure it is locked in all OMAP4 revisions.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
asda d
---
arch/arm/mach-omap2/cclock44xx_data.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git
McPDM need to be configured to NO_IDLE mode when it is in used otherwise
vital clocks will be gated which results 'slow motion' audio playback.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
On 01/04/2013 04:10 PM, Jon Hunter wrote:
On 01/04/2013 04:09 AM, Peter Ujfalusi wrote:
To avoid issues with audio caused by non locked ABE DPLL we should
make sure it is locked in all OMAP4 revisions.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
asda d
Not sure what the above
the pwm_id was incorrect.
With the other patches we will be able to control the followings:
LCD backlight via pwm-backlight driver
Keypad leds via leds_pwm driver as normal LED
Charging indicator via leds_pwm driver as normal LED
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach
-zoom-display.c caused by the
changes in twl-core - which I missed :(
The DT support for these are going to be sent later.
Tony: can you apply this - if it looks OK - so it will hit linux-next before the
second batch of twl-core update?
Regards,
Peter
---
Peter Ujfalusi (3):
ARM: OMAP: board
With the PWM backed driver the PMU_STAT led's brighness can be controlled.
This needs the new drivers for the TWL PWM/LED to work.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 39 ++---
1 file changed, 31 insertions
Use pwm_leds driver for the keyboard light and pwm-backlight for the lcd
backlight control (instead of implementing the PWM driver part in the board
file).
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-zoom-display.c | 56
arch
Hi Tony,
On 01/03/2013 12:49 PM, Peter Ujfalusi wrote:
Hi,
The pwm-leds driver update is going for 3.9:
https://lkml.org/lkml/2012/12/21/99
This series will make sure that in 3.9 we are going to have working LEDs and
backlight on these boards.
As a note: 4430SDP never had working
during activity.
Regards,
Peter
---
Peter Ujfalusi (2):
ARM: OMAP4: clock data: ABE DPLL need to be locked on all revisions
ARM: OMAP4: hwmod_data: Correct IDLEMODE for McPDM
arch/arm/mach-omap2/cclock44xx_data.c | 14 ++
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 2 +-
2
We need to lock ABE DPPL on al OMAP4 revisions, not only for OMAP446x
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/cclock44xx_data.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/arch/arm/mach-omap2/cclock44xx_data.c
b/arch/arm
McPDM need to be configured to NO_IDLE mode when it is in used otherwise
vital clocks will be gated which results 'slow motion' audio playback.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
/ patches will go as a separate series to avoid cross
tree issues.
Regards,
Peter
---
Peter Ujfalusi (8):
ASoC: twl4030: Correct the support for Voice port
ASoC: zoom2: No need to configure the Voice port anymore
ASoC: sdp3430: No need to configure the Voice port anymore
ASoC: twl4030
(output from codec)
Use DAPM_SUPPLY for the VIF_EN bit and add DAPM_AIF_IO/OUT widget to handle
the playback/capture bit.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/codecs/twl4030.c | 17 -
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/sound
The codec driver takes care of these bits.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/omap/zoom2.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/sound/soc/omap/zoom2.c b/sound/soc/omap/zoom2.c
index 771bff2..5845d48 100644
--- a/sound/soc/omap/zoom2.c
The codec driver takes care of these bits.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/omap/sdp3430.c | 15 ---
1 file changed, 15 deletions(-)
diff --git a/sound/soc/omap/sdp3430.c b/sound/soc/omap/sdp3430.c
index b462a2c..86e77e9 100644
--- a/sound/soc/omap
In order to avoid breakage update the machine drivers at the same time using
twl4030: omap3pandora, sdp3430 and zoom2
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/codecs/twl4030.c| 10 +++---
sound/soc/omap/omap3pandora.c | 8
sound/soc/omap/sdp3430.c
The codec driver takes care of this.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/omap/sdp3430.c | 18 --
1 file changed, 18 deletions(-)
diff --git a/sound/soc/omap/sdp3430.c b/sound/soc/omap/sdp3430.c
index f2e2651..216cbdd 100644
--- a/sound/soc/omap
When HS extmute is enabled without custom GPIO we should configure the mux
to allow the pin to be used as extmute signal.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/codecs/twl4030.c | 44 +++-
1 file changed, 31 insertions(+), 13
Update the common machine driver to support more boards including Zoom2 and
SDP3430.
- Support for voice port of twl4030
- HS jack plug detection support
- The audio routing can be fine tuned via pdata or via provided routing
table from DT.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
These boards are using the common omap-twl4030 machine driver, no need for
separate machine drivers anymore.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/omap/Kconfig | 17
sound/soc/omap/Makefile | 4 -
sound/soc/omap/sdp3430.c | 245
support the zoom2 and sdp3430
boards as well.
Regards,
Peter
---
Peter Ujfalusi (6):
ARM: OMAP: 3430sdp: Enable extmute functionality for audio
ARM: OMAP: zoom: Zoom2 does not have extmute functionality
ARM: OMAP2+: twl-common: Add default twl4030 audio configuration
ARM: OMAP2+: twl-common
Enable the use of extmute on the HS path.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-3430sdp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-omap2/board-3430sdp.c
b/arch/arm/mach-omap2/board-3430sdp.c
index bb73afc..40c22a7 100644
The HS extmute is not used on Zoom2 boards. Furthermore the GPIO153 is used
as IRQ for the TSC2004 touchscreen controller - for which we do not have
driver upstream, yet.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-zoom-peripherals.c | 11 +++
1 file
Select the most commonly used audio configuration on boards with twl4030
audio:
Headset, Handsfree output and Line in input
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/twl-common.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/arm
Boards with special audio routing can pass a custom omap_tw4030_pdata to the
audio machine driver.
At the same time update the board files using the same audio driver.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-cm-t35.c | 2 +-
arch/arm/mach-omap2
Use the common omap-twl4030 ASoC machine driver for audio.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-zoom-peripherals.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c
b/arch/arm/mach
Use the common omap-twl4030 ASoC machine driver for audio.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-3430sdp.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/mach-omap2/board-3430sdp.c
b/arch/arm/mach-omap2/board-3430sdp.c
Hello,
Second part of the cleanup of twl-core which aims to make the code a bit more
readable.
It has been tested on: OMAP4 PandaBoard, OMAP4 Blaze, OMAP3 BeagleBoard, OMAP3
Zoom2.
Regards,
Peter
---
Peter Ujfalusi (10):
mfd: twl-core: Clean up module id lookup and definitions
mfd: twl-core
At boot time we can allocate the twl_modules array dynamically based on the
twl class we are using with devm_kzalloc() instead of the static
twl_modules[] array.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 31 +--
1 file changed
There is really no point to retry to add children devices in case the
of_platform_populate() fails.
We do not have any information provided via pdata in this case anyways.
Depending on the boot type (legacy or DT) only execute either one.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
twl_i2c_read/write_u8 become as a simple wrapper over the twl_i2c_read/write.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 28
include/linux/i2c/twl.h | 17 +++--
2 files changed, 11 insertions(+), 34 deletions
With the regmap conversion there is no longeer a need to allocate bigger
buffer for writes
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 3 ---
include/linux/i2c/twl.h | 3 ---
2 files changed, 6 deletions(-)
diff --git a/drivers/mfd/twl-core.c b/drivers/mfd
The module id table no longer can have invalid/unused entries.
No need for checking the ID for validity.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl-core.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/mfd/twl-core.c b
901 - 1000 of 1965 matches
Mail list logo
