Re: [PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks

Hi Paul, On Monday 28 September 2015 10:05 PM, Paul Walmsley wrote: > On Thu, 24 Sep 2015, Lokesh Vutla wrote: > >> On Thursday 27 August 2015 09:51 AM, Lokesh Vutla wrote: >>> On Thursday 23 July 2015 06:55 PM, Lokesh Vutla wrote: This series implements lock and unlock functions for RTC

Re: [PATCH v3 0/3] ARM: OMAP2+: hwmod: RTC: Add lock and unlock hooks

On Thu, 24 Sep 2015, Lokesh Vutla wrote: > On Thursday 27 August 2015 09:51 AM, Lokesh Vutla wrote: > > On Thursday 23 July 2015 06:55 PM, Lokesh Vutla wrote: > >> This series implements lock and unlock functions for RTC and hooks > >> the same to DRA7 and AMx3xx hwmod. > >> This is dependent on

[PATCH] arm: omap2: timer: always define omap4_local_timer_init

omap4_local_timer_init() can be used by other platforms as is. At least AM437x wants to use it. Instead of making omap4-only and providing a stub for builds without OMAP4, we can just always define that function. Reported-by: Nishanth Menon Signed-off-by: Felipe Balbi

Re: [PATCH RFC] ASoC: simple-card: Update clocks binding for simple-card DAI subnodes

On 09/19/15 21:42, Mark Brown wrote: On Fri, Sep 11, 2015 at 04:18:02PM +0300, Jyri Sarha wrote: The updated binding provides a way to set clock-ID and direction parameters for DAI drivers set_sysclk() call back. I proposed something similar about a year ago, but Mark rejected that at the

Re: [PATCH 1/3] iio:adc: add iio driver for Palmas (twl6035/7) gpadc

Hi, Am 27.09.2015 um 17:21 schrieb Jonathan Cameron : > On 23/09/15 13:48, H. Nikolaus Schaller wrote: >> This driver code was found as: >> >> https://android.googlesource.com/kernel/tegra/+/aaabb2e045f31e5a970109ffdaae900dd403d17e/drivers/staging/iio/adc >> >> Fixed various

Re: [PATCH] arm: omap2: timer: always define omap4_local_timer_init

On Mon, Sep 28, 2015 at 04:10:40PM -0500, Nishanth Menon wrote: > On 09/28/2015 01:25 PM, Felipe Balbi wrote: > > omap4_local_timer_init() can be used by other > > platforms as is. At least AM437x wants to use > > it. Instead of making omap4-only and providing > > a stub for builds without OMAP4,

[PATCHv2] arm: omap2: timer: always define omap4_local_timer_init

omap4_local_timer_init() can be used by other platforms as is. At least AM437x wants to use it. Instead of making omap4-only and providing a stub for builds without OMAP4, we can just always define that function. Reported-by: Nishanth Menon Signed-off-by: Felipe Balbi

Re: [PATCHv2] arm: omap2: timer: always define omap4_local_timer_init

bit of nitpick on capitalization of $subject.. aside.. On 09/28/2015 04:23 PM, Felipe Balbi wrote: > omap4_local_timer_init() can be used by other > platforms as is. At least AM437x wants to use > it. Instead of making omap4-only and providing > a stub for builds without OMAP4, we can just >

Re: [PATCH 07/17] ARM: dts: am4372: add reset data

On 09/25/2015 03:57 PM, Lokesh Vutla wrote: Hi Tero, On Thursday 24 September 2015 07:56 PM, Tero Kristo wrote: Add reset data for pruss, gfx, wkup-m3 and system reset. Signed-off-by: Tero Kristo --- arch/arm/boot/dts/am4372.dtsi | 24 1 file

OMAP baseline test results for v4.3-rc3

Here are some basic OMAP test results for Linux v4.3-rc3. Logs and other details at: http://www.pwsan.com/omap/testlogs/test_v4.3-rc3/20150927222545/ Test summary Build: uImage: Pass ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only,

Re: [PATCH RFC v4 3/8] ASoC: hdmi-codec: Add hdmi-codec for external HDMI-encoders

On Mon, Sep 28, 2015 at 11:01:34AM +0200, Arnaud Pouliquen wrote: > few questions/remarks > BR, > Arnaud > > >+static void hdmi_codec_abort(struct device *dev) > >+{ > >+struct hdmi_codec_priv *hcp = dev_get_drvdata(dev); > >+ > >+dev_dbg(dev, "%s()\n", __func__); > >+ > >+

Re: [PATCH RFC v4 3/8] ASoC: hdmi-codec: Add hdmi-codec for external HDMI-encoders

On 09/28/15 12:01, Arnaud Pouliquen wrote: few questions/remarks BR, Arnaud +static void hdmi_codec_abort(struct device *dev) +{ +struct hdmi_codec_priv *hcp = dev_get_drvdata(dev); + +dev_dbg(dev, "%s()\n", __func__); + +mutex_lock(>current_stream_lock); +if

Re: [PATCH RFC v4 3/8] ASoC: hdmi-codec: Add hdmi-codec for external HDMI-encoders

On Mon, Sep 28, 2015 at 12:26:28PM +0100, Russell King - ARM Linux wrote: > On Mon, Sep 28, 2015 at 11:01:34AM +0200, Arnaud Pouliquen wrote: > > few questions/remarks > > BR, > > Arnaud > > > > >+static void hdmi_codec_abort(struct device *dev) > > >+{ > > >+struct hdmi_codec_priv *hcp =

Re:[PATCH RFC v4 3/8] ASoC: hdmi-codec: Add hdmi-codec for external HDMI-encoders

few questions/remarks BR, Arnaud +static void hdmi_codec_abort(struct device *dev) +{ +struct hdmi_codec_priv *hcp = dev_get_drvdata(dev); + +dev_dbg(dev, "%s()\n", __func__); + +mutex_lock(>current_stream_lock); +if (hcp->current_stream && hcp->current_stream->runtime && +

[PATCH v2 2/2] arm: omap2+: PM: change trace_power_domain_target event format.

power_domain_target arg3 is now a string (event name) with generic power domains. In the case of Omap, it is a hint to the prev/next switch op. Compiled for Omap2+ but not tested. Signed-off-by: Marc Titinger --- arch/arm/mach-omap2/powerdomain.c | 27

[PATCH v2 1/2] Trace: PM: promote event 'power_domain_target' to generic power domains.

- change arg3 to a state name string: we got the current CPU rom the trace backend already. This also prepares for multiple/named states in the power domain, consistent with idle-states. states in the domain may match given CPU states in this case, we will trace them by their name, and potentially

[PATCH v3 1/2] Trace: PM: promote event 'power_domain_target' to generic power domains.

- change arg3 to a state name string: we got the current CPU rom the trace backend already. This also prepares for multiple/named states in the power domain, consistent with idle-states. states in the domain may match given CPU states in this case, we will trace them by their name, and potentially

[PATCH v3 2/2] arm: omap2+: PM: change trace_power_domain_target event format.

power_domain_target arg3 is now a string (event name) with generic power domains. In the case of Omap, it is a hint to the prev/next switch op. Compiled for Omap2+ but not tested. Signed-off-by: Marc Titinger --- arch/arm/mach-omap2/powerdomain.c | 27

[RFC PATCH 1/2] pci: host: pci-dra7xx: use "num-lanes" property to find phy count

use "num-lanes" property to find phy count instead of the number phy-names property. Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/host/pci-dra7xx.c | 23 +++ 1 file changed, 11 insertions(+), 12 deletions(-) diff --git

[RFC PATCH 2/2] pci: host: pci-dra7xx: Enable x2 mode support

Perform syscon configurations to get x2 mode to working in DRA74x and DRA72x. Also add a new compatible string to dfferentiate DRA72x and DRA74x, since b1c0 mask is different for both these platforms. Signed-off-by: Kishon Vijay Abraham I ---

[RFC PATCH 0/2] DRA72/DRA74: Add 2 lane support

Add driver modifications in pci-dra7xx to get x2 mode working in DRA72 and DRA74. Certain modifications is needed in PHY driver also which I'll send as a separate series. Kishon Vijay Abraham I (2): pci: host: pci-dra7xx: use "num-lanes" property to find phy count pci: host: pci-dra7xx:

Re: [PATCH] arm: omap2: timer: always define omap4_local_timer_init

On 09/28/2015 01:25 PM, Felipe Balbi wrote: > omap4_local_timer_init() can be used by other > platforms as is. At least AM437x wants to use > it. Instead of making omap4-only and providing > a stub for builds without OMAP4, we can just > always define that function. > > Reported-by: Nishanth

Re: [PATCH v3 1/2] Trace: PM: promote event 'power_domain_target' to generic power domains.

Hi Marc, [auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore] config: i386-allmodconfig (attached as .config) reproduce: git checkout cc6f7469844987395d46013269b2d2f4e1ad735c # save the attached .config to linux build tree make ARCH=i386 All error/warnings