Hi Joachim,
On 05/20/2014 08:09 PM, Joachim Eastwood wrote:
> On 20 May 2014 16:25, Florian Vaussard wrote:
>> Add the necessary DTS nodes to enable the micro-HDMI output on Parlor
>> board.
>>
>> Signed-off-by: Florian Vaussard
>> ---
>> arch/arm/boot/dts/omap4-duovero-parlor.dts | 42
>>
On 05/20/2014 04:39 PM, Tony Lindgren wrote:
> * Florian Vaussard [140520 07:26]:
>> @@ -77,6 +94,15 @@
>> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /*
>> gpmc_a24.gpio_48: amdix enabled */
>> >;
>> };
>> +
>> +dss_hdmi_pins: pinmux_dss_hdmi_pins {
>> +
* Lee Jones [140520 08:18]:
>
> Ah, I forgot to Ack this last time, didn't I?
>
> Acked-by: Lee Jones
Yeah, here's this one updated with your ack.
Regards,
Tony
8< ---
From: Tony Lindgren
Date: Tue, 20 May 2014 11:17:54 -0700
Subject: [PATCH] mfd: twl4030-power: A
* Lee Jones [140520 08:15]:
>
> Assuming the magic numbers are replaced by transparent #defines:
>
> Acked-by: Lee Jones
Updated the defines to use a define for the default delay. Did
not touch the number for resource group init order but added some
comments for those. Updated patch below.
* Lee Jones [140520 08:13]:
> >
> > http://www.omappedia.com/wiki/TWL4030_power_scripts
>
> Do you really want this bumph in the commit log?
Removed the links from the commit log.
> > +#define TWL_RESOURCE_ON(res)
> > \
> > + { MSG_SINGULAR(DEV
* Lee Jones [140520 08:04]:
> > We have these bits partially defined in two different
> > places, so let's fix them up and add defines for the
> > missing bits. These bits are the same for P1_SW_EVENTS,
> > P2_SW_EVENTS and P3_SW_EVENTS.
> >
> > Cc: Peter Ujfalusi
> > Signed-off-by: Tony Lindgre
On Mon, May 19, 2014 at 01:24:41PM +0530, Pekon Gupta wrote:
> --- a/drivers/mtd/nand/omap2.c
> +++ b/drivers/mtd/nand/omap2.c
> @@ -1201,6 +1219,41 @@ static int __maybe_unused
> omap_calculate_ecc_bch(struct mtd_info *mtd,
> *ecc_code++ = ((bch_val1 >> 4) & 0xFF);
>
On Mon, May 19, 2014 at 01:24:38PM +0530, Pekon Gupta wrote:
> As this series touches both linux-mtd and linux-omap (GPMC) sub-systems but in
> independent patch-sets, so looping both maintainers. 'Ack' from maintainers
> would
> help in getting this series accepted for 3.16
>
> *changes v3 -> v4
On Mon, May 19, 2014 at 10:48:52PM -0700, Tony Lindgren wrote:
> * Sebastian Reichel [140519 22:13]:
> > On Mon, May 19, 2014 at 10:05:15PM +0300, Tomi Valkeinen wrote:
> > > On 19/05/14 19:04, Tony Lindgren wrote:
> > >
> > > > In many cases however we do have multiple compatible strings that
>
On 20 May 2014 16:25, Florian Vaussard wrote:
> Add the necessary DTS nodes to enable the micro-HDMI output on Parlor
> board.
>
> Signed-off-by: Florian Vaussard
> ---
> arch/arm/boot/dts/omap4-duovero-parlor.dts | 42
> ++
> 1 file changed, 42 insertions(+)
>
> dif
> > > > > Looks like we can still hit the issue of wrong load order of
> > > > > twl4030 configuration. If we have a sleep configuration loaded,
> > > > > and do a warm reset, the device can hang while initializing the
> > > > > wakeup12 sequence. We do have a warning message about wrong order
> >
* Lee Jones [140520 10:38]:
> > > > Looks like we can still hit the issue of wrong load order of
> > > > twl4030 configuration. If we have a sleep configuration loaded,
> > > > and do a warm reset, the device can hang while initializing the
> > > > wakeup12 sequence. We do have a warning message a
Quoting Peter Ujfalusi (2014-05-07 03:20:47)
> Audio Tracking Logic is designed to be used by HD Radio applications to
> synchronize the audio output clocks to the baseband clock. ATL can be also
> used to track errors between two reference clocks (BWS, AWS) and generate a
> modulated
> clock outp
Hi Nishanth,
On Tuesday 20 May 2014 07:45 PM, Nishanth Menon wrote:
On 05/20/2014 04:11 AM, Keerthy wrote:
[...]
+config MFD_TPS65917
+ bool "TI TPS65917 series chips"
+ select MFD_CORE
+ select REGMAP_I2C
+ select REGMAP_IRQ
+ depends on I2C=y
^^ why =y?
Palmas
> > > Looks like we can still hit the issue of wrong load order of
> > > twl4030 configuration. If we have a sleep configuration loaded,
> > > and do a warm reset, the device can hang while initializing the
> > > wakeup12 sequence. We do have a warning message about wrong order
> > > of twl4030 con
Hi Alexandre,
On Mon, May 19, 2014 at 10:42 PM, Alexandre Belloni
wrote:
> Hi,
>
> Originally sent on Apr 14th, note that this series is blocking another 16
> patches series, I would like it to be taken in 3.16 if we can agree on this
> implementation.
>
> A patch set as suggested by Thierry to m
Hi Lee Jones,
Thanks for the review.
On Tuesday 20 May 2014 07:28 PM, Lee Jones wrote:
The TPS65917 chip is a power management IC for Portable Navigation Systems
and Tablet Computing devices. It contains the following components:
- Regulators.
- Over Temperature warning and Shut down.
Thi
On 17 May 09:04 PM, Ezequiel Garcia wrote:
> At probe time, the musb_am335x driver register its childs by
> calling of_platform_populate(), which registers all childs in
> the devicetree hierarchy recursively.
>
> On the other side, the driver's remove() function uses of_device_unregister()
> to r
Quoting Sourav Poddar (2014-04-29 01:34:20)
> tbclk does not need to be a composite clock, we can simply
> use gate clock for this purpose.
>
> Signed-off-by: Sourav Poddar
Looks good.
Regards,
Mike
> ---
> v1->v2:
> change compatible string according to mainline.
> arch/arm/boot/dts/am33xx-c
On Tue, 13 May 2014, Tony Lindgren wrote:
> With the recommended twl4030 configuration added, we can now add
> board specific changes as modifications to the recommended
> configuration.
>
> Note that the data is private to this driver, and the data must
> always have a NULL resource in the senti
> These settings are based on the "Recommended Sleep Sequences for
> the Zoom Platform" pdf at:
>
> http://omappedia.com/wiki/File:Recommended_Sleep_Sequences_Zoom.pdf
>
> These settings assume most of the regulators are under control of
> Linux, and twl4030 only cuts off VDD1 and VDD2 during off
> The twl4030 PMIC needs to be configured properly for things like
> warm reset and deeper idle states so the PMIC manages the regulators
> properly based on the hardware triggers from the SoC.
>
> For example, when rebooting an OMAP3530 at 125 MHz, it hangs.
> With this patch, TWL4030 will be re
* Lee Jones [140520 08:02]:
> On Tue, 13 May 2014, Tony Lindgren wrote:
>
> > Looks like we can still hit the issue of wrong load order of
> > twl4030 configuration. If we have a sleep configuration loaded,
> > and do a warm reset, the device can hang while initializing the
> > wakeup12 sequence.
> We have these bits partially defined in two different
> places, so let's fix them up and add defines for the
> missing bits. These bits are the same for P1_SW_EVENTS,
> P2_SW_EVENTS and P3_SW_EVENTS.
>
> Cc: Peter Ujfalusi
> Signed-off-by: Tony Lindgren
> ---
> drivers/mfd/twl4030-power.c | 2
On Tue, 13 May 2014, Tony Lindgren wrote:
> Looks like we can still hit the issue of wrong load order of
> twl4030 configuration. If we have a sleep configuration loaded,
> and do a warm reset, the device can hang while initializing the
> wakeup12 sequence. We do have a warning message about wrong
* Tero Kristo [140520 02:01]:
> On 05/19/2014 07:27 PM, Tony Lindgren wrote:
> >* Joachim Eastwood [140519 09:24]:
> >>On 19 May 2014 18:13, Tony Lindgren wrote:
> >>>* Joachim Eastwood [140518 05:08]:
> On 22 April 2014 14:39, Tero Kristo wrote:
> >On 04/20/2014 07:22 PM, Gilles Chant
* Balaji T K [140520 06:29]:
> On Monday 19 May 2014 10:24 PM, Tony Lindgren wrote:
> >* Balaji T K [140519 04:54]:
> >>On Saturday 17 May 2014 03:11 AM, Tony Lindgren wrote:
> -
> -#if defined(CONFIG_DMA_OMAP) || defined(CONFIG_DMA_OMAP_MODULE)
> -bool omap_dma_filter_fn(struct dma_c
* Florian Vaussard [140520 07:26]:
> @@ -77,6 +94,15 @@
> 0x30 (PIN_INPUT_PULLUP | MUX_MODE3) /*
> gpmc_a24.gpio_48: amdix enabled */
> >;
> };
> +
> + dss_hdmi_pins: pinmux_dss_hdmi_pins {
> + pinctrl-single,pins = <
> +
Add the necessary DTS nodes to enable the micro-HDMI output on Parlor
board.
Signed-off-by: Florian Vaussard
---
arch/arm/boot/dts/omap4-duovero-parlor.dts | 42 ++
1 file changed, 42 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-duovero-parlor.dts
b/arch/arm/b
On 05/20/2014 04:11 AM, Keerthy wrote:
[...]
> +config MFD_TPS65917
> + bool "TI TPS65917 series chips"
> + select MFD_CORE
> + select REGMAP_I2C
> + select REGMAP_IRQ
> + depends on I2C=y
^^ why =y?
> + help
> + If you say yes here you get support for the TPS65917
>
Summit and Tobi expansion boards have a HDMI connector with a TFP410
encoder. Add a common include file for this configuration, and then
use it for Summit and Tobi.
Signed-off-by: Florian Vaussard
---
arch/arm/boot/dts/omap3-overo-common-dvi.dtsi| 111 +++
arch/arm/boot/d
Chestnut43, Gallop43 and Palo43 expansion boards have a ZIF connector
for a 4.3'' LCD. Add a common include file for this configuration, and
use it on relevant expansion boards.
Signed-off-by: Florian Vaussard
---
.../boot/dts/omap3-overo-chestnut43-common.dtsi| 1 +
arch/arm/boot/dts/omap
Hi,
This series enables the DVI and LCD panels present on some of
the Overo expansion boards.
DVI output:
- Tobi
- Summit
LCD (3.5''):
- Alto35
LCD (4.3''):
- Chestnut43
- Palo43
- Gallop43
I tested on Tobi, Alto35 and Gallop43.
This series depends on several patches from Tomi [1][2][3] targe
> The TPS65917 chip is a power management IC for Portable Navigation Systems
> and Tablet Computing devices. It contains the following components:
>
> - Regulators.
> - Over Temperature warning and Shut down.
>
> This patch adds support for tps65917 mfd device. At this time only
> the regulator
Alto35 expansion board has a ZIF connector for a 3.5'' LCD.
Add a common include file for this configuration, and use it
on Alto35.
Signed-off-by: Florian Vaussard
---
arch/arm/boot/dts/omap3-overo-alto35-common.dtsi | 1 +
arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi | 165 +++
On 05/20/2014 02:41 PM, Tomi Valkeinen wrote:
> On 20/05/14 15:31, Florian Vaussard wrote:
>
>> +lcd0: display@0 { + compatible = "samsung,lte430wq-f0c",
>> "panel-dpi"; + label = "lcd"; + + gpios = <&gpio5
>> 16
>> GPIO_ACTIVE_HIGH /* gpio
On Monday 19 May 2014 10:24 PM, Tony Lindgren wrote:
* Balaji T K [140519 04:54]:
On Saturday 17 May 2014 03:11 AM, Tony Lindgren wrote:
-
-#if defined(CONFIG_DMA_OMAP) || defined(CONFIG_DMA_OMAP_MODULE)
-bool omap_dma_filter_fn(struct dma_chan *, void *);
-#else
-static inline bool omap_dma_f
On 20/05/14 15:31, Florian Vaussard wrote:
> + lcd0: display@0 {
> + compatible = "samsung,lte430wq-f0c", "panel-dpi";
> + label = "lcd";
> +
> + gpios = <&gpio5 16 GPIO_ACTIVE_HIGH /* gpio_144:
> enable */
> + &gpio5 17 GPI
Hi,
This series enables the DVI and LCD panels present on some of
the Overo expansion boards.
DVI output:
- Tobi
- Summit
LCD (3.5''):
- Alto35
LCD (4.3''):
- Chestnut43
- Palo43
- Gallop43
I tested on Tobi, Alto35 and Gallop43.
This series depends on several patches from Tomi [1][2][3] targe
Chestnut43, Gallop43 and Palo43 expansion boards have a ZIF connector
for a 4.3'' LCD. Add a common include file for this configuration, and
use it on relevant expansion boards.
Signed-off-by: Florian Vaussard
---
.../boot/dts/omap3-overo-chestnut43-common.dtsi| 1 +
arch/arm/boot/dts/omap
Summit and Tobi expansion boards have a HDMI connector with a TFP410
encoder. Add a common include file for this configuration, and then
use it for Summit and Tobi.
Signed-off-by: Florian Vaussard
---
arch/arm/boot/dts/omap3-overo-common-dvi.dtsi| 111 +++
arch/arm/boot/d
Alto35 expansion board has a ZIF connector for a 3.5'' LCD.
Add a common include file for this configuration, and use it
on Alto35.
Signed-off-by: Florian Vaussard
---
arch/arm/boot/dts/omap3-overo-alto35-common.dtsi | 1 +
arch/arm/boot/dts/omap3-overo-common-lcd35.dtsi | 144 +++
On 20/05/14 13:58, Florian Vaussard wrote:
>> static struct spi_driver lb035q02_spi_driver = {
>> .probe = lb035q02_panel_spi_probe,
>> .remove = lb035q02_panel_spi_remove,
>> @@ -357,6 +398,7 @@ static struct spi_driver lb035q02_spi_driver = {
>>
>
> .
On Tue, May 20, 2014 at 1:04 AM, Rajendra Nayak wrote:
> So we are back to checking revisions based on idcode register then?
> This patch was posted almost a year back and was shot down by you
> included saying we need to use dt compatibles for it.
>
> https://www.mail-archive.com/linux-omap@vger.
Hi Tomi,
On 05/15/2014 12:10 PM, Tomi Valkeinen wrote:
> Add DT bindings documentation for LG.Philips LB035Q02 LCD panel.
>
> Signed-off-by: Tomi Valkeinen
> Cc: devicet...@vger.kernel.org
> ---
> .../bindings/video/lgphilips,lb035q02.txt | 33
> ++
> 1 file change
Hi Tomi,
On 05/15/2014 12:10 PM, Tomi Valkeinen wrote:
> Add DT support for panel-lgphilips-lb035q02.
>
> We disable the use of the backlight_gpio as it should be handled via
> backlight framework with DT boots.
>
> Signed-off-by: Tomi Valkeinen
> ---
> .../omap2/displays-new/panel-lgphilips-l
Hi Tomi,
On 05/15/2014 12:10 PM, Tomi Valkeinen wrote:
> Hi,
>
> This adds DT support to panel-lgphilips-lb035q02. Compile tested only.
>
> This panel is used on some Overo boards (alto35, if I'm not mistaken).
>
I tested with the Alto35. Using the small fix for patch 2, I was able to
use the
On Monday 19 May 2014 10:23 PM, Peter Ujfalusi wrote:
> On 05/19/2014 04:06 PM, Sekhar Nori wrote:
>> On Friday 16 May 2014 05:47 PM, Peter Ujfalusi wrote:
>>> Hi,
>>>
>>> Changes since v2:
>>> - Comments from Sekhar and Arnd has been addressed best as I could.
>>> - Use the CCCFG information in al
Hello Roger,
On Tue, May 20, 2014 at 11:51 AM, Roger Quadros wrote:
> On 05/20/2014 12:24 PM, Javier Martinez Canillas wrote:
>> Hello Pekon,
>>
>> On Tue, May 20, 2014 at 10:46 AM, Gupta, Pekon wrote:
>>> Hi Roger,
>>>
>>> From: Quadros, Roger
On 05/20/2014 09:24 AM, Pekon Gupta wrote:
>>>
On 05/20/2014 12:24 PM, Javier Martinez Canillas wrote:
> Hello Pekon,
>
> On Tue, May 20, 2014 at 10:46 AM, Gupta, Pekon wrote:
>> Hi Roger,
>>
>> From: Quadros, Roger
>>> On 05/20/2014 09:24 AM, Pekon Gupta wrote:
This patch enables 'wait-pin' monitoring in NAND driver if following
p
On Tuesday 20 May 2014 01:34 PM, Tomi Valkeinen wrote:
On 08/05/14 12:15, Archit Taneja wrote:
The init/uninit port functions are used to set up the DPI and SDI outputs under
the dss platform device. A 'reg' property is used to determine whether the node
is DPI or SDI for OMAP34xx DSS revision.
Hello Pekon,
On Tue, May 20, 2014 at 10:46 AM, Gupta, Pekon wrote:
> Hi Roger,
>
> From: Quadros, Roger
>>On 05/20/2014 09:24 AM, Pekon Gupta wrote:
>>> This patch enables 'wait-pin' monitoring in NAND driver if following
>>> properties
>>> are present under NAND DT node
>>> gpmc,wait-pin =
>
Add the various binding files for the TPS65917 family of chips. There is a
top level MFD binding then a seperate binding for regulators IP blocks on chips.
Signed-off-by: Keerthy
---
Documentation/devicetree/bindings/mfd/tps65917.txt | 35
1 file changed, 35 insertions(+)
This patch adds support for TPS65917 PMIC regulators.
The regulators set consists of 5 SMPSs and 5 LDOs. The output
voltages are configurable and are meant to supply power to the
main processor and other components.
Signed-off-by: Keerthy
---
Comments fixed in V2:
Used the standard functions
Add TPS65917 Regulator Bindings.
Signed-off-by: Keerthy
---
.../bindings/regulator/tps65917-pmic.txt | 67
1 file changed, 67 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regulator/tps65917-pmic.txt
diff --git a/Documentation/devicetree/b
The TPS65917 chip is a power management IC for Portable Navigation Systems
and Tablet Computing devices. It contains the following components:
- Regulators.
- GPADC.
- Over Temperature warning and Shut down.
This patch series adds support for TPS65917 mfd device. At this time only
the regulato
On 05/19/2014 07:27 PM, Tony Lindgren wrote:
* Joachim Eastwood [140519 09:24]:
On 19 May 2014 18:13, Tony Lindgren wrote:
* Joachim Eastwood [140518 05:08]:
On 22 April 2014 14:39, Tero Kristo wrote:
On 04/20/2014 07:22 PM, Gilles Chanteperdrix wrote:
Le 19/04/2014 00:39, Tony Lindgren
Hi Roger,
From: Quadros, Roger
>On 05/20/2014 09:24 AM, Pekon Gupta wrote:
>> This patch enables 'wait-pin' monitoring in NAND driver if following
>> properties
>> are present under NAND DT node
>> gpmc,wait-pin =
>> gpmc,wait-on-read
>> gpmc,wait-on-write
>> As NAND generic framework uses
On Tuesday 20 May 2014 11:01 AM, Archit Taneja wrote:
> Hi,
>
> On Friday 16 May 2014 01:44 PM, Tomi Valkeinen wrote:
>> On 12/05/14 18:48, Tony Lindgren wrote:
>>
> Also, I'm wondering why we still have .clk and .opt_clks entries in the
> hwmod data for am43xx and omap5 which are both dev
On Tue, May 20, 2014 at 9:45 AM, Roger Quadros wrote:
> Hi Pekon,
>
> On 05/20/2014 09:24 AM, Pekon Gupta wrote:
>> This patch enables 'wait-pin' monitoring in NAND driver if following
>> properties
>> are present under NAND DT node
>> gpmc,wait-pin =
>> gpmc,wait-on-read
>> gpmc,wait-on-w
Some modules need their optional clocks to be enabled in order to complete
the ocp softreset. This is what hwmod uses optional clock information
for. While these modules are limited (GPIO and DSS) there are others which have
this data in hwmod but it seems to be completely unused. Get rid of all op
On 08/05/14 12:15, Archit Taneja wrote:
> The init/uninit port functions are used to set up the DPI and SDI outputs
> under
> the dss platform device. A 'reg' property is used to determine whether the
> node
> is DPI or SDI for OMAP34xx DSS revision. For other DSS revisions, only DPI
> output exi
Hi Pekon,
On 05/20/2014 09:24 AM, Pekon Gupta wrote:
> This patch enables 'wait-pin' monitoring in NAND driver if following
> properties
> are present under NAND DT node
> gpmc,wait-pin =
> gpmc,wait-on-read
> gpmc,wait-on-write
> As NAND generic framework uses common path nand_chip->dev_r
On 05/19/2014 09:26 PM, Gupta, Pekon wrote:
> Hi Javier,
>
>> From: Javier Martinez Canillas [mailto:jav...@dowhile0.org]
>>
>> Hello Pekon,
>>
>> On Fri, May 16, 2014 at 9:07 PM, Pekon Gupta wrote:
>>> This patch enables 'wait-pin' monitoring in NAND driver if following
>>> properties
>>> are p
64 matches
Mail list logo
