Re: PowerVR SGX540 drivers for PandaBoard(OMAP4460) on vanilla kernel

Tried hard but nothing available my hands except my experiences. I gave up trying custom kernel due to lots of error, and instead tried Ubuntu precise 3.2.0-1412-omap4 kernel which is one of the working kernel with SGX540 driver module. I built "omapdrm_pvr.ko" and load this module without error.

Re: [PATCH 03/13] twl4030_charger: correctly handle -EPROBE_DEFER from devm_usb_get_phy_by_node

Kevin Hilman writes: > ping... this boot failure has now landed in mainline sorry, I'm on leave at the moment and travelling so I'm unlikely to be able to look at this properly. I should be able to examine this issue before the end of the month but cannot promise sooner

Re: [net-next PATCH] drivers: net: cpsw: Add support to make gpio drive which slave connected to phy

On Tuesday 01 September 2015 09:06 PM, Tony Lindgren wrote: > * Mugunthan V N [150901 04:28]: >> --- a/Documentation/devicetree/bindings/net/cpsw.txt >> +++ b/Documentation/devicetree/bindings/net/cpsw.txt >> @@ -26,6 +26,9 @@ Optional properties: >> - dual_emac :

Re: [PATCH v4 9/9] usb: dwc3: core: don't break during suspend/resume while we're dual-role

Hello. On 09/02/2015 05:24 PM, Roger Quadros wrote: We can't rely just on dr_mode to decide if we're in host or gadget mode when we're configured as otg/dual-role. So while dr_mode is OTG, we find out from the otg state machine if we're in host or gadget mode and take the necessary actions

Re: [PATCH v2] security: device_cgroup: fix RCU lockdep splat

cc'ing Paul. On Wed, Sep 02, 2015 at 08:12:28AM -0500, Felipe Balbi wrote: > while booting AM437x device, the following splat > triggered: > > [ 12.005238] === > [ 12.009749] [ INFO: suspicious RCU usage. ] > [ 12.014116] 4.2.0-next-20150831 #1154 Not tainted >

Re: [PATCH 1/6] regulator: pbias: program pbias register offset in pbias driver

* Kishon Vijay Abraham I [150902 03:51]: > --- a/drivers/regulator/pbias-regulator.c > +++ b/drivers/regulator/pbias-regulator.c How about add a comment here: /* Offset from SCM general area (and syscon) base */ > +static const struct pbias_of_data pbias_of_data_omap2 = { > +

Re: [PATCH v2] security: device_cgroup: fix RCU lockdep splat

On Wed, Sep 2, 2015 at 9:12 AM, Felipe Balbi wrote: > while booting AM437x device, the following splat > triggered: > > [ 12.005238] === > [ 12.009749] [ INFO: suspicious RCU usage. ] > [ 12.014116] 4.2.0-next-20150831 #1154 Not tainted > [

[GIT PULL] omap fixes for v4.3 merge window

The following changes since commit 2faf962d90ca4c5ee7ba026b7351b1f74500bcdf: Merge tag 'armsoc-defconfig' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2015-09-01 13:17:43 -0700) are available in the git repository at:

Re: [PATCH v2] security: device_cgroup: fix RCU lockdep splat

On Wed, Sep 02, 2015 at 12:24:50PM -0400, Tejun Heo wrote: > cc'ing Paul. > > On Wed, Sep 02, 2015 at 08:12:28AM -0500, Felipe Balbi wrote: > > while booting AM437x device, the following splat > > triggered: > > > > [ 12.005238] === > > [ 12.009749] [ INFO:

[PATCH 2/3][v3] drivers: usb: dwc3: Add frame length adjustment quirk

Add adjust_frame_length_quirk for writing to fladj register which adjusts (micro)frame length to value provided by "snps,quirk-frame-length-adjustment" property thus avoiding USB 2.0 devices to time-out over a longer run Signed-off-by: Nikhil Badola --- Changes for

Re: [PATCH 1/6] regulator: pbias: program pbias register offset in pbias driver

On Wed, Sep 02, 2015 at 04:17:28PM +0530, Kishon Vijay Abraham I wrote: > Add separate compatible strings for every platform and populate the > pbias register offset in the driver data. > This helps avoid depending on the dt for pbias register offset. Can you respin with Tony's comment please and

Re: [PATCH] mtd: nand: omap2: Rename shippable module to omap2_nand

On Fri, Aug 21, 2015 at 01:45:35PM +0300, Roger Quadros wrote: > As both omap2 onenand and omap2 nand driver modules are > named the same i.e. "omap2.ko", only one of them gets shipped > during MODPOST if both are configured as loadable modules. > > To avoid this ambiguity let's ship the omap2

Re: [PATCH 1/2] regulator: pbias: use untranslated address to program pbias regulator

On Tue, Sep 01, 2015 at 11:56:06AM -0700, Tony Lindgren wrote: > * Mark Brown [150901 11:40]: > > That'd work. The other thing I was thinking we could do is to get > > syscon to treat any excessively large address that gets passed in that > > looks like an absolute address

[PATCH 5/6] ARM: dts: OMAP4: use "ti,pbias-omap4" compatible string for pbias

Use "ti,pbias-omap4" compatible string which is specifically added for OMAP4. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/omap4.dtsi |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi

[RFC PATCH 4/4] ARM: OMAP2: AM43XX: Modify optimize string comparisons in soc_is calls

Currently everytime soc_is calls are made, firstly device tree nodes are parsed and then string comparisons are made to determine the soc version. Optimizing it to be done one time and store the result. Use the stored value in all the subsequent checks for soc_is calls. Signed-off-by: Keerthy

[RFC PATCH 2/4] ARM: DRA7: Add omap revision detection under soc_is function

omap_type can be determined at the init time based on the device tree compatible string. This will avoid checking again for soc string. Signed-off-by: Keerthy --- arch/arm/mach-omap2/id.c | 38 +- 1 file changed, 21 insertions(+), 17

[RFC PATCH 3/4] ARM: dts: AM43x-epos-evm: Add AM438x compatible string for epos

Add AM438x compatible property to identify the SoCs on epos evms. Signed-off-by: Keerthy --- Documentation/devicetree/bindings/arm/omap/omap.txt | 5 - arch/arm/boot/dts/am43x-epos-evm.dts| 2 +- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git

[PATCH 4/6] ARM: dts: omap3: use "ti,pbias-omap3" compatible string for pbias

Use "ti,pbias-omap3" compatible string which is specifically added for OMAP3. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/omap3.dtsi |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi

[PATCH 0/6] Fix pbias regulator enable

vsel_reg and enable_reg of the pbias regulator descriptor should actually have the offset from syscon. However after "ARM: dts: : add minimal l4 bus layout with control module support" vsel_reg and enable_reg started to have the absolute address because of address translation that happens due to

[PATCH 1/6] regulator: pbias: program pbias register offset in pbias driver

Add separate compatible strings for every platform and populate the pbias register offset in the driver data. This helps avoid depending on the dt for pbias register offset. Also update the dt binding documentation with the new compatible strings. Suggested-by: Tony Lindgren

[PATCH 2/6] ARM: dts: dra7: use "ti,pbias-dra7" compatible string for pbias

Use "ti,pbias-dra7" compatible string which is specifically added for DRA7 SoCs. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/dra7.dtsi |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi

[RFC PATCH 0/4] ARM: OMAP2+: Optimize soc_is calls

The series implements optimizing soc_is calls for DRA7 and AM43XX family of SoCs. Originally the soc_is calls for DRA7 involved parsing device tree nodes and some repetitive string comparisons. Optimizing to store the result and use the result in the subsequent calls. The series is boot tested on

[RFC PATCH 1/4] ARM: OMAP2: DRA7: Modify optimize string comparisons in soc_is calls

Currently everytime soc_is calls are made, firstly device tree nodes are parsed and then string comparisons are made to determine the soc version. Optimizing it to be done one time and store the result. Use the stored value in all the subsequent checks for soc_is calls. Signed-off-by: Keerthy

[PATCH 6/6] ARM: dts: OMAP5: use "ti,pbias-omap5" compatible string for pbias

Use "ti,pbias-omap5" compatible string which is specifically added for OMAP5. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/omap5.dtsi |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi

[PATCH 3/6] ARM: dts: omap243x: use "ti,pbias-omap2" compatible string for pbias

Use "ti,pbias-omap2" compatible string which is specifically added for OMAP2. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/omap2430.dtsi |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/omap2430.dtsi

[PATCH v2] security: device_cgroup: fix RCU lockdep splat

while booting AM437x device, the following splat triggered: [ 12.005238] === [ 12.009749] [ INFO: suspicious RCU usage. ] [ 12.014116] 4.2.0-next-20150831 #1154 Not tainted [ 12.019050] --- [ 12.023408] security/device_cgroup.c:405

Re: [PATCH] security: device_cgroup: fix RCU lockdep splat

On Tue, Sep 1, 2015 at 9:08 AM, Felipe Balbi wrote: > On Tue, Sep 01, 2015 at 11:12:18AM +0200, Sebastian Ott wrote: >> On Mon, 31 Aug 2015, Felipe Balbi wrote: >> > while booting AM437x device, the following splat >> > triggered: >> > >> > [ 12.005238]

Re: [PATCH 03/13] twl4030_charger: correctly handle -EPROBE_DEFER from devm_usb_get_phy_by_node

* Neil Brown [150901 23:23]: > Kevin Hilman writes: > > > ping... this boot failure has now landed in mainline > > sorry, I'm on leave at the moment and travelling so I'm unlikely to be > able to look at this properly. I should be able to examine this

Re: [RFC PATCH 1/4] ARM: OMAP2: DRA7: Modify optimize string comparisons in soc_is calls

On Wed, Sep 02, 2015 at 03:50:10PM +0530, Keerthy wrote: > Currently everytime soc_is calls are made, firstly device tree nodes > are parsed and then string comparisons are made to determine the > soc version. Optimizing it to be done one time and store the result. but is that really a problem ?

Re: [PATCH] security: device_cgroup: fix RCU lockdep splat

On Wed, Sep 02, 2015 at 08:29:14AM -0400, Josh Boyer wrote: > On Tue, Sep 1, 2015 at 9:08 AM, Felipe Balbi wrote: > > On Tue, Sep 01, 2015 at 11:12:18AM +0200, Sebastian Ott wrote: > >> On Mon, 31 Aug 2015, Felipe Balbi wrote: > >> > while booting AM437x device, the following splat

Re: [PATCH v4 8/9] usb: dwc3: core: Prevent otg events from disabling themselves

On Wed, Sep 02, 2015 at 05:24:23PM +0300, Roger Quadros wrote: > There is a race happening during dwc3_drd_init() that causes > otg events to get disabled. This is what happens. > > dwc3_otg_irq() happens immediately when PRTCAP is set to OTG, > even though OEVTEN is 0. This is because BIT 31 IRQ

Re: [PATCH v4 9/9] usb: dwc3: core: don't break during suspend/resume while we're dual-role

On Wed, Sep 02, 2015 at 05:24:24PM +0300, Roger Quadros wrote: > We can't rely just on dr_mode to decide if we're in host or gadget > mode when we're configured as otg/dual-role. So while dr_mode is > OTG, we find out from the otg state machine if we're in host > or gadget mode and take the

Re: Antwort: Re: [PATCH 2/2] memory: omap-gpmc: Add Kconfig option for debug

On 01/09/15 16:31, Hannes Schmelzer wrote: >> Hi Hannes, > Hi Roger, > >> >> On 27/08/15 08:52, Hannes Schmelzer wrote: >>> Hi Tony, >>> >>> Did anyone test this changeset on some AM335x board? >>> >>> Today I ran into trouble with that because: >>> >>> The GPMC controller gets reseted on kernel

Re: [PATCH v4 5/9] usb: dwc3: core: make dual-role work with OTG irq

Hi, On Wed, Sep 02, 2015 at 05:24:20PM +0300, Roger Quadros wrote: > If the ID pin event is not available over extcon > then we rely on the OTG controller to provide us ID and VBUS > information. > > We still don't support any OTG features but just > dual-role operation. > > Signed-off-by:

[PATCH v4 8/9] usb: dwc3: core: Prevent otg events from disabling themselves

There is a race happening during dwc3_drd_init() that causes otg events to get disabled. This is what happens. dwc3_otg_irq() happens immediately when PRTCAP is set to OTG, even though OEVTEN is 0. This is because BIT 31 IRQ of OEVT can't be disabled by OEVTEN. We configure OEVTEN in

[PATCH v4 7/9] usb: dwc3: gadget: Fix suspend/resume during dual-role mode

Gdget controller might not be always active during suspend/ resume when we are operating in dual-role/otg mode. Check if we're active and only if we are then perform necessary actions during suspend/resume. Signed-off-by: Roger Quadros --- drivers/usb/dwc3/gadget.c | 6 ++ 1

[PATCH v4 9/9] usb: dwc3: core: don't break during suspend/resume while we're dual-role

We can't rely just on dr_mode to decide if we're in host or gadget mode when we're configured as otg/dual-role. So while dr_mode is OTG, we find out from the otg state machine if we're in host or gadget mode and take the necessary actions during suspend/resume. Also make sure that we disable OTG

[PATCH v4 2/9] usb: dwc3: core.h: add some register definitions

Add OTG and GHWPARAMS6 register definitions Signed-off-by: Roger Quadros --- drivers/usb/dwc3/core.h | 82 + 1 file changed, 82 insertions(+) diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h index 5ca2b25..4b85330

[PATCH v4 5/9] usb: dwc3: core: make dual-role work with OTG irq

If the ID pin event is not available over extcon then we rely on the OTG controller to provide us ID and VBUS information. We still don't support any OTG features but just dual-role operation. Signed-off-by: Roger Quadros --- drivers/usb/dwc3/core.c | 217

[PATCH v4 3/9] usb: dwc3: dwc3-omap: Make the wrapper interrupt shared

The wrapper interrupt is shared with OTG core so mark it IRQF_SHARED. Signed-off-by: Roger Quadros --- drivers/usb/dwc3/dwc3-omap.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/usb/dwc3/dwc3-omap.c b/drivers/usb/dwc3/dwc3-omap.c index

[PATCH v4 6/9] usb: dwc3: save/restore OTG registers during suspend/resume

Without this we loose OTG controller register context and malfunction after a system suspend-resume. Signed-off-by: Roger Quadros --- drivers/usb/dwc3/core.c | 17 + drivers/usb/dwc3/core.h | 6 +- 2 files changed, 22 insertions(+), 1 deletion(-) diff --git

Re: [PATCH v4 4/9] usb: dwc3: core: Adapt to named interrupts

On Wed, Sep 02, 2015 at 05:24:19PM +0300, Roger Quadros wrote: > From: Felipe Balbi > > Add support to use interrupt names, > > Following are the interrupt names > > Peripheral Interrupt - peripheral > HOST Interrupt - host > OTG Interrupt - otg > > [Roger Q] > - If any of these

[PATCH v4 0/9] usb: dwc3: add dual-role support

Hi, This series adds dual role support to dwc3 controller driver. Series depends on [1] for core OTG/dual-role support. Patches are based on greg/usb-next. Tested on am437x-gp-evm and dra7-evm after platform related patches are applied. Those are available at [2]. [1] core OTG/DRD support -

[PATCH v4 1/9] usb: dwc3: add dual-role support

Register with the USB OTG core. Since we don't support OTG yet we just work as a dual-role device even if device tree says "otg". Use extcon framework to get VBUS/ID cable events and kick the OTG state machine. Signed-off-by: Roger Quadros --- drivers/usb/dwc3/core.c |

[PATCH v4 4/9] usb: dwc3: core: Adapt to named interrupts

From: Felipe Balbi Add support to use interrupt names, Following are the interrupt names Peripheral Interrupt - peripheral HOST Interrupt - host OTG Interrupt - otg [Roger Q] - If any of these are missing we use the first available IRQ resource so that we don't break with older

Re: [PATCH v4 3/9] usb: dwc3: dwc3-omap: Make the wrapper interrupt shared

On Wed, Sep 02, 2015 at 05:24:18PM +0300, Roger Quadros wrote: > The wrapper interrupt is shared with OTG core so mark it IRQF_SHARED. > > Signed-off-by: Roger Quadros > --- > drivers/usb/dwc3/dwc3-omap.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git

Re: [PATCH v4 1/9] usb: dwc3: add dual-role support

Hi, On Wed, Sep 02, 2015 at 05:24:16PM +0300, Roger Quadros wrote: > Register with the USB OTG core. Since we don't support > OTG yet we just work as a dual-role device even > if device tree says "otg". > > Use extcon framework to get VBUS/ID cable events and > kick the OTG state machine. > >

Re: [PATCH v4 6/9] usb: dwc3: save/restore OTG registers during suspend/resume

On Wed, Sep 02, 2015 at 05:24:21PM +0300, Roger Quadros wrote: > Without this we loose OTG controller register context and malfunction > after a system suspend-resume. > > Signed-off-by: Roger Quadros > --- > drivers/usb/dwc3/core.c | 17 + >