On 2013-03-11 08:10, Archit Taneja wrote:
> Hi,
>
> On Friday 08 March 2013 05:21 PM, Tomi Valkeinen wrote:
>> During the initialization of the DSI protocol registers, we always set
>> the sources of all DSI channels to L4. However, we don't update the
>> value in the dsi_data, so we may end up wi
This patch serie is converting OMAP Audio IPs in order to use OMAP sDMA DT
binding in case of DT boot on OMAP2+ platforms.
It is depending on the next patches:
[1] http://www.spinics.net/lists/arm-kernel/msg227836.html
[2] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg84668.html
It h
Update OMAP2+ driver in order to use OMAP DMA DT binding for OMAP2+.
In case of DT boot snd_dmaengine_generic_pcm_open function is used.
Signed-off-by: Sebastien Guiriec
---
sound/soc/omap/mcbsp.c | 26 --
sound/soc/omap/omap-dmic.c | 15 +--
sound/s
Populate DMA client information for McBSP DMIC and McPDM periperhal on
OMAP2+ devices.
Signed-off-by: Sebastien Guiriec
---
arch/arm/boot/dts/omap2420.dtsi |6 ++
arch/arm/boot/dts/omap2430.dtsi | 15 +++
arch/arm/boot/dts/omap3.dtsi| 15 +++
arch/arm/boot
On Monday 11 March 2013 12:32 PM, Tomi Valkeinen wrote:
On 2013-03-11 08:10, Archit Taneja wrote:
Hi,
On Friday 08 March 2013 05:21 PM, Tomi Valkeinen wrote:
During the initialization of the DSI protocol registers, we always set
the sources of all DSI channels to L4. However, we don't update t
On 2013-03-11 10:15, Archit Taneja wrote:
> On Monday 11 March 2013 12:32 PM, Tomi Valkeinen wrote:
>> On 2013-03-11 08:10, Archit Taneja wrote:
>>> Hi,
>>>
>>> On Friday 08 March 2013 05:21 PM, Tomi Valkeinen wrote:
During the initialization of the DSI protocol registers, we always set
t
On 03/08/2013 05:45 PM, Marc Kleine-Budde wrote:
> On 03/08/2013 11:46 AM, Marc Kleine-Budde wrote:
>> On 02/04/2013 04:58 PM, Roger Quadros wrote:
>>> The PHY clock, clock rate, VCC regulator and RESET regulator
>>> can now be provided via device tree.
>>>
>>> Signed-off-by: Roger Quadros
>>> ---
(+ Peter, Luca, Balaji)
else your e-mail might just go unnoticed ;)
On 03/07/2013 10:37 PM, Levi Pearson wrote:
> I recently upgraded from a 3.4 kernel to a 3.8 kernel and found that
> the drivers for the functionality provided by the TiWi module on the
> pandaboard (Bluetooth, WiFI, etc.) could
On 03/11/2013 09:58 AM, Roger Quadros wrote:
> (+ Peter, Luca, Balaji)
>
> else your e-mail might just go unnoticed ;)
>
> On 03/07/2013 10:37 PM, Levi Pearson wrote:
>> I recently upgraded from a 3.4 kernel to a 3.8 kernel and found that
>> the drivers for the functionality provided by the TiWi
Removed interrupt-parent property from dts file as it is already
with root node in dtsi file.
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
:100644 100644 f624dc8... 36e839a... M arch/arm/boot/dts/omap3-beagle.dts
:100644 100644 e8ba1c2... a5375fd... M arch/arm/boot/dts/omap3-evm.dts
:10064
On 2013-03-11 07:35, Archit Taneja wrote:
> Hi,
>
> On Friday 08 March 2013 05:21 PM, Tomi Valkeinen wrote:
>> The DISPC channel used for each output is currently passed in panel
>> platform data from the board files.
>>
>> To simplify this, and to make the panel drivers less dependent on OMAP,
>>
Kevin,
On Wednesday 13 February 2013 02:25 PM, Santosh Shilimkar wrote:
> Current CPU PM code code make use of common cpu_suspend() path for all the
> CPU power states which is not optimal. In fact cpu_suspend() path is needed
> only when we put CPU power domain to off state where the CPU context
Hi,
On Monday 11 March 2013 11:20 AM, Santosh Shilimkar wrote:
On Monday 11 March 2013 10:36 AM, Lokesh Vutla wrote:
From: Grygorii Strashko
ERRATA DESCRIPTION :
The EMIF supports power-down state for low power. The EMIF
automatically puts the SDRAM into power-down after the memory is
not acce
On 2013-03-11 07:53, Archit Taneja wrote:
> On Friday 08 March 2013 05:21 PM, Tomi Valkeinen wrote:
>> The DISPC channel used for each output is currently passed in panel
>> platform data from the board files.
>>
>> To simplify this, and to make the panel drivers less dependent on OMAP,
>> this pat
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
---
arch/arm/mach-omap2/board-zoom-display.c | 56
arch/arm/mach-omap2/board-
On 2013-03-11 07:53, Archit Taneja wrote:
> On Friday 08 March 2013 05:21 PM, Tomi Valkeinen wrote:
>> The DISPC channel used for each output is currently passed in panel
>> platform data from the board files.
>>
>> To simplify this, and to make the panel drivers less dependent on OMAP,
>> this pat
On 2013-03-11 07:35, Archit Taneja wrote:
> Hi,
>
> On Friday 08 March 2013 05:21 PM, Tomi Valkeinen wrote:
>> The DISPC channel used for each output is currently passed in panel
>> platform data from the board files.
>>
>> To simplify this, and to make the panel drivers less dependent on OMAP,
>>
On 2013-03-11 13:57, Peter Ujfalusi wrote:
> 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
> ---
> arch/arm/mach-omap2/board-zoom-display.c | 56
On Monday 11 March 2013 05:35 PM, Tomi Valkeinen wrote:
On 2013-03-11 07:35, Archit Taneja wrote:
Hi,
On Friday 08 March 2013 05:21 PM, Tomi Valkeinen wrote:
The DISPC channel used for each output is currently passed in panel
platform data from the board files.
To simplify this, and to make t
On 2013-03-05 00:39, Tony Lindgren wrote:
> Hi,
>
> * Aaro Koskinen [130304 13:08]:
>> Fix the following build regression in 3.9-rc1 by including
>> :
>>
>> drivers/video/omap/lcd_ams_delta.c: In function 'ams_delta_lcd_set_power':
>> drivers/video/omap/lcd_ams_delta.c:48:4: error: implicit decla
On 2013-03-05 16:17, Archit Taneja wrote:
> The support outputs struct for overlay managers is incorrect for OMAP4. Make
> these changes:
>
> - DPI isn't supported via the LCD1 overlay manager, remove DPI as a supported
> output.
> - the TV manager can suppport DPI, but the omapdss driver doesn'
Hi Tony/Benoit,
These patches had been sent couple of times before, but there were no comments
on it.
If there are no comments, Can these be picked ?
Cc: Andrew Morton
The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
Linux 3.9-rc2 (2013-03-10 16:54:19 -0700)
Booting 3.9-rc2 on omap 4430sdp results in the following error
omap_i2c 4807.i2c: did not get pins for i2c error: -19
[1.024261] omap_i2c 4807.i2c: bus 0 rev0.12 at 100 kHz
[1.030181] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
[1.037384] omap_i2c 48072000.i2c: b
Booting 3.9-rc2 on omap 5430evm results in the following error
omap_i2c 4807.i2c: did not get pins for i2c error: -19
[1.024261] omap_i2c 4807.i2c: bus 0 rev0.12 at 100 kHz
[1.030181] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
[1.037384] omap_i2c 48072000.i2c: b
Booting 3.9-rc2 on omap4 panda results in the following error
[0.27] omap_i2c 4807.i2c: did not get pins for i2c error: -19
[0.445770] omap_i2c 4807.i2c: bus 0 rev0.11 at 400 kHz
[0.473937] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
[0.474670] omap_i2c 4
From: Felipe Balbi
Add all 4 mcspi instances to omap5.dtsi file.
Cc: Andrew Morton
Signed-off-by: Felipe Balbi
Signed-off-by: Sourav Poddar
---
arch/arm/boot/dts/omap5.dtsi | 40
1 files changed, 40 insertions(+), 0 deletions(-)
diff --git a/arch/a
Add mcspi node and pinmux data for omap5 mcspi controller.
Tested on omap5430 evm with 3.9-rc2 custom kernel.
Cc: Andrew Morton
Signed-off-by: Sourav Poddar
---
arch/arm/boot/dts/omap5-evm.dts | 46 +++
1 files changed, 46 insertions(+), 0 deletions(-)
di
On 03/11/2013 08:50 AM, Sebastien Guiriec wrote:
> Update OMAP2+ driver in order to use OMAP DMA DT binding for OMAP2+.
> In case of DT boot snd_dmaengine_generic_pcm_open function is used.
Acked-by: Peter Ujfalusi
>
> Signed-off-by: Sebastien Guiriec
> ---
> sound/soc/omap/mcbsp.c | 2
On 03/11/2013 08:50 AM, Sebastien Guiriec wrote:
> Populate DMA client information for McBSP DMIC and McPDM periperhal on
> OMAP2+ devices.
Looks good to me:
Reviewed-by: Peter Ujfalusi
>
> Signed-off-by: Sebastien Guiriec
> ---
> arch/arm/boot/dts/omap2420.dtsi |6 ++
> arch/arm/boot
Hi Sourav,
On 03/11/2013 02:44 PM, Sourav Poddar wrote:
> Hi Tony/Benoit,
>
> These patches had been sent couple of times before, but there were no
> comments on it.
Sorry for that. I got a big flu in Jan and was in Linaro Connect last week.
Patches look good, I just have to check that they app
On Mon, Mar 11, 2013 at 08:50:22AM +0100, Sebastien Guiriec wrote:
> Update OMAP2+ driver in order to use OMAP DMA DT binding for OMAP2+.
> In case of DT boot snd_dmaengine_generic_pcm_open function is used.
Acked-by: Mark Brown
or I can apply to ASoC if people prefer, I don't think it makes muc
On Monday 11 March 2013 08:02 PM, Benoit Cousson wrote:
Hi Sourav,
On 03/11/2013 02:44 PM, Sourav Poddar wrote:
Hi Tony/Benoit,
These patches had been sent couple of times before, but there were no comments
on it.
Sorry for that. I got a big flu in Jan and was in Linaro Connect last week.
Pa
On 02/05/2013 08:26 AM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Feb 04, 2013 at 05:58:48PM +0200, Roger Quadros wrote:
>> The PHY clock, clock rate, VCC regulator and RESET regulator
>> can now be provided via device tree.
>>
>> Signed-off-by: Roger Quadros
>> ---
>> .../devicetree/bindings/usb/us
On 03/11/2013 09:40 AM, Roger Quadros wrote:
> On 03/08/2013 05:45 PM, Marc Kleine-Budde wrote:
>> On 03/08/2013 11:46 AM, Marc Kleine-Budde wrote:
>>> On 02/04/2013 04:58 PM, Roger Quadros wrote:
The PHY clock, clock rate, VCC regulator and RESET regulator
can now be provided via device
On 02/05/2013 10:43 AM, Roger Quadros wrote:
> On 02/05/2013 11:09 AM, Felipe Balbi wrote:
>> On Tue, Feb 05, 2013 at 10:44:05AM +0200, Roger Quadros wrote:
> diff --git a/include/linux/usb/nop-usb-xceiv.h
> b/include/linux/usb/nop-usb-xceiv.h
> index 3265b61..148d351 100644
> ---
Convert all uses of devm_request_and_ioremap() to the newly introduced
devm_ioremap_resource() which provides more consistent error handling.
devm_ioremap_resource() provides its own error messages so all explicit
error messages can be removed from the failure code paths.
Signed-off-by: Silviu-Mi
* Grazvydas Ignotas [130309 16:53]:
> VBUS_ERROR is a serious error that the driver often doesn't recover from
> in my tests, so we should at least inform the user about it.
Patch makes sens to me, just a related question..
Do you get this when trying to enable the host mode, right? Or have you
* Mark Brown [130311 07:37]:
> On Mon, Mar 11, 2013 at 08:50:22AM +0100, Sebastien Guiriec wrote:
> > Update OMAP2+ driver in order to use OMAP DMA DT binding for OMAP2+.
> > In case of DT boot snd_dmaengine_generic_pcm_open function is used.
>
> Acked-by: Mark Brown
>
> or I can apply to ASoC
On Mon, Mar 11, 2013 at 09:27:00AM -0700, Tony Lindgren wrote:
> I suggest you take the driver changes and Benoit takes the .dts
> changes as those should be queued separately to avoid unnecessary
> merge conflicts with the .dts files.
Won't that cause a bisect issue if the driver starts looking
* Paul Bolle [130309 11:52]:
> On Sat, 2013-03-09 at 00:01 +, Russell King - ARM Linux wrote:
>
> > However, going back to that MACH_NOKIA_RM696. If there exists only a
> > select of this symbol and no "config MACH_NOKIA_RM696" entry, then the
> > symbol will never be generated in the output
* Mark Brown [130311 09:32]:
> On Mon, Mar 11, 2013 at 09:27:00AM -0700, Tony Lindgren wrote:
>
> > I suggest you take the driver changes and Benoit takes the .dts
> > changes as those should be queued separately to avoid unnecessary
> > merge conflicts with the .dts files.
>
> Won't that cause
On Mon, Mar 11, 2013 at 1:15 AM, Paul Walmsley wrote:
> Hi Gražvydas,
>
> On Sun, 10 Mar 2013, Grazvydas Ignotas wrote:
>
>> For some unknown reason, allowing hwmod to control MIDLEMODE causes
>> core_pwrdm to not hit idle states for musb in DM3730 at least.
>> I've verified that setting any MIDLE
Hello Gražvydas,
On Mon, 11 Mar 2013, Grazvydas Ignotas wrote:
> Soft reset seems to recover from this so there is no problem, but you
> can't reset before every suspend so a workaround is still needed..
OK, that's good.
> Well as long as it works it's good for me, although it'll bloat the
> co
On Tue, Mar 5, 2013 at 7:44 PM, Andreas Müller
wrote:
> On Fri, Mar 1, 2013 at 10:07 PM, Andreas Müller
> wrote:
>> On Thu, Feb 28, 2013 at 5:27 PM, Andreas Müller
>> wrote:
>>> Hi,
>>>
>>> I am preparing 3.8 mainline for gumstix overo and have the following
>>> issue: waking Monitor connected b
On Mon, Mar 11, 2013 at 6:24 PM, Tony Lindgren wrote:
> * Grazvydas Ignotas [130309 16:53]:
>> VBUS_ERROR is a serious error that the driver often doesn't recover from
>> in my tests, so we should at least inform the user about it.
>
> Patch makes sens to me, just a related question..
>
> Do you
On 03/10/2013 12:18 PM, Javier Martinez Canillas wrote:
> Besides being used to interface with external memory devices,
> the General-Purpose Memory Controller can be used to connect
> Pseudo-SRAM devices such as ethernet controllers to OMAP2+
> processors using the GPMC as a data bus.
>
> The ac
* Grazvydas Ignotas [130311 10:12]:
> On Mon, Mar 11, 2013 at 6:24 PM, Tony Lindgren wrote:
> > * Grazvydas Ignotas [130309 16:53]:
> >> VBUS_ERROR is a serious error that the driver often doesn't recover from
> >> in my tests, so we should at least inform the user about it.
> >
> > Patch makes
On 03/08/2013 08:25 PM, Anil Kumar wrote:
> Hi Jon,
>
> On Fri, Mar 8, 2013 at 10:57 PM, Jon Hunter wrote:
>> Adds basic device-tree support for OMAP3430 SDP board which has 256MB
>> of RAM and uses the TWL4030 power management IC.
>
> I think this board support should be in separate patch seri
On 03/10/2013 09:45 PM, Anil Kumar wrote:
> Hi Jon,
>
> On Fri, Mar 8, 2013 at 10:57 PM, Jon Hunter wrote:
>> Adds basic device-tree support for OMAP3430 SDP board which has 256MB
>> of RAM and uses the TWL4030 power management IC.
>>
>> Signed-off-by: Jon Hunter
>> ---
>> arch/arm/boot/dts/Ma
On 03/09/2013 06:42 AM, Ezequiel Garcia wrote:
> On Fri, Mar 8, 2013 at 10:25 PM, Javier Martinez Canillas
> wrote:
>> On Fri, Mar 8, 2013 at 10:41 PM, Jon Hunter wrote:
>>>
>>> Yes you are correct. In general, I have been trying to stay some-what
>>> consistent with what hwmod was doing as this
On 03/11/2013 06:13 PM, Jon Hunter wrote:
>
Hi Jon, thanks a lot for your feedback.
> On 03/10/2013 12:18 PM, Javier Martinez Canillas wrote:
>> Besides being used to interface with external memory devices,
>> the General-Purpose Memory Controller can be used to connect
>> Pseudo-SRAM devices su
On 03/11/2013 12:57 PM, Javier Martinez Canillas wrote:
> On 03/11/2013 06:13 PM, Jon Hunter wrote:
>>
>
> Hi Jon, thanks a lot for your feedback.
>
>> On 03/10/2013 12:18 PM, Javier Martinez Canillas wrote:
>>> Besides being used to interface with external memory devices,
>>> the General-Purpos
On 03/11/2013 07:11 PM, Jon Hunter wrote:
>
> On 03/11/2013 12:57 PM, Javier Martinez Canillas wrote:
>> On 03/11/2013 06:13 PM, Jon Hunter wrote:
>>>
>>
>> Hi Jon, thanks a lot for your feedback.
>>
>>> On 03/10/2013 12:18 PM, Javier Martinez Canillas wrote:
Besides being used to interface
On 03/11/2013 04:19 PM, Peter Ujfalusi wrote:
> On 03/11/2013 08:50 AM, Sebastien Guiriec wrote:
>> Populate DMA client information for McBSP DMIC and McPDM periperhal on
>> OMAP2+ devices.
>
> Looks good to me:
> Reviewed-by: Peter Ujfalusi
>
Reviewed-by: Jarkko Nikula
--
To unsubscribe from
On 03/11/2013 04:18 PM, Peter Ujfalusi wrote:
> On 03/11/2013 08:50 AM, Sebastien Guiriec wrote:
>> Update OMAP2+ driver in order to use OMAP DMA DT binding for OMAP2+.
>> In case of DT boot snd_dmaengine_generic_pcm_open function is used.
>
> Acked-by: Peter Ujfalusi
>
Acked-by: Jarkko Nikula
Hi
On 03/11/2013 05:58 PM, Silviu-Mihai Popescu wrote:
> Convert all uses of devm_request_and_ioremap() to the newly introduced
> devm_ioremap_resource() which provides more consistent error handling.
>
> devm_ioremap_resource() provides its own error messages so all explicit
> error messages can
For some unknown reason, allowing hwmod to control MIDLEMODE causes
core_pwrdm to not hit idle states for musb in DM3730 at least.
I've verified that setting any MIDLEMODE value other than "force
standby" before enabling the device causes subsequent suspend
attempts to fail with core_pwrdm not ente
The following series arose from trying to use BeagleBoard-XM (OMAP3 variant)
for doing CPU DVFS using cpufreq-cpu0.
This is also an attempt to slowly remove the dependence on omap-cpufreq
driver and be entirely driven off cpufreq-cpu0 driver.
Somewhere in the future, when we have regulators drive
On certain SoCs like variants of OMAP, the clock conversion to DT
is not complete. In short, the ability to:
cpus {
cpu@0 {
clocks = <&cpuclk 0>;
};
};
is not possible. However, the clock node is registered.
Allow for clk names to be provided as string so as to be used when needed.
commit 5553f9e (cpufreq: instantiate cpufreq-cpu0 as a platform_driver)
now forces platform device to be registered for allowing cpufreq-cpu0
to be used by SoCs. example: drivers/cpufreq/highbank-cpufreq.c
However, for SoCs that wish to link up using device tree, instead
of platform device, provid
The pwm-backlight driver now takes a mandatory regulator that is gotten
during driver probe. Initialize a dummy regulator to satisfy this
requirement.
Signed-off-by: Andrew Chew
---
This patch, along with many more soon to follow, attempts to satisfy the new
mandatory regulator that pwm-backligh
On Mon, Mar 11, 2013 at 23:23:32, Hunter, Jon wrote:
>
> On 03/08/2013 08:25 PM, Anil Kumar wrote:
> > Hi Jon,
> >
> > On Fri, Mar 8, 2013 at 10:57 PM, Jon Hunter wrote:
> >> Adds basic device-tree support for OMAP3430 SDP board which has 256MB
> >> of RAM and uses the TWL4030 power management
On Tuesday 12 March 2013 04:35 AM, Nishanth Menon wrote:
> On certain SoCs like variants of OMAP, the clock conversion to DT
> is not complete. In short, the ability to:
> cpus {
> cpu@0 {
> clocks = <&cpuclk 0>;
> };
> };
> is not possible. However, the clock node is registered.
> A
On Tuesday 12 March 2013 04:35 AM, Nishanth Menon wrote:
> commit 5553f9e (cpufreq: instantiate cpufreq-cpu0 as a platform_driver)
> now forces platform device to be registered for allowing cpufreq-cpu0
> to be used by SoCs. example: drivers/cpufreq/highbank-cpufreq.c
>
> However, for SoCs that wi
On Monday 11 March 2013 05:58 PM, Tomi Valkeinen wrote:
On 2013-03-05 16:17, Archit Taneja wrote:
The support outputs struct for overlay managers is incorrect for OMAP4. Make
these changes:
- DPI isn't supported via the LCD1 overlay manager, remove DPI as a supported
output.
- the TV manager
On 3/6/2013 9:45 PM, Matt Porter wrote:
> Adds support for parsing the TI EDMA DT data into the
> required EDMA private API platform data. Enables runtime
> PM support to initialize the EDMA hwmod. Adds AM33XX EDMA
> crossbar event mux support. Enables build on OMAP.
>
> Signed-off-by: Matt Port
On 3/6/2013 9:45 PM, Matt Porter wrote:
> The binding definition is based on the generic DMA controller
> binding.
>
> Signed-off-by: Matt Porter
Okay the bindings the documented after they are used leading to some
confusion. This patch should be moved up the series. As I noted in my
other e-mai
67 matches
Mail list logo
