After the device names are created using PLATFORM_DEVID_AUTO, the old
device names given in usb_bind_phy are no longer valid causing the musb
controller not to get the phy reference. Updated the usb_bind_phy with
the new device names to get MUSB functional in omap4 panda.
Signed-off-by: Kishon Vij
Hi Kevin,
On Tuesday 23 April 2013 12:11 AM, Kevin Hilman wrote:
Grygorii Strashko writes:
On 04/22/2013 04:43 PM, Sourav Poddar wrote:
Remove the "OMAP_DEVICE_NO_IDLE_ON_SUSPEND" check, since
driver should be able to prevent idling of an omap device
whenever required.
Cc: Santosh Shilimkar
Hi Grygorii,
On Monday 22 April 2013 08:18 PM, Grygorii Strashko wrote:
On 04/22/2013 04:43 PM, Sourav Poddar wrote:
The driver manages "no_console_suspend" by preventing runtime PM
during the suspend path, which forces the console UART to stay awake.
Signed-off-by: Sourav Poddar
---
drivers
Hi Kevin,
On Tuesday 23 April 2013 12:06 AM, Kevin Hilman wrote:
Grygorii Strashko writes:
On 04/22/2013 04:43 PM, Sourav Poddar wrote:
The driver manages "no_console_suspend" by preventing runtime PM
during the suspend path, which forces the console UART to stay awake.
Signed-off-by: Sourav
On 22/04/13 18:01, Mugunthan V N wrote:
> On 4/22/2013 7:37 PM, Mark Jackson wrote:
>> Mugunthan
>>
>> Can you confirm that I'm actually trying to achieve the right thing ?
>>
>> I have all along assumed that Dual EMAC mode would simply provide the
>> kernel will a pair of independent Ethernet port
Hi Felipe,
On Monday 22 April 2013 08:05 PM, Felipe Balbi wrote:
Hi,
On Mon, Apr 22, 2013 at 07:13:56PM +0530, Sourav Poddar wrote:
The "ti,no_idle_on_suspend" property was required to keep ocmcram
clocks running during idle.
But the commit below[1], added in v3.6 should prevent the
any automa
Hi Felipe,
On Monday 22 April 2013 08:01 PM, Felipe Balbi wrote:
Hi,
On Mon, Apr 22, 2013 at 07:13:54PM +0530, Sourav Poddar wrote:
The driver manages "no_console_suspend" by preventing runtime PM
during the suspend path, which forces the console UART to stay awake.
Signed-off-by: Sourav Podda
Grygorii Strashko writes:
> On 04/22/2013 04:43 PM, Sourav Poddar wrote:
>> Remove the "OMAP_DEVICE_NO_IDLE_ON_SUSPEND" check, since
>> driver should be able to prevent idling of an omap device
>> whenever required.
>>
>> Cc: Santosh Shilimkar
>> Cc: Felipe Balbi
>> Cc: Rajendra nayak
>> Cc: G
Grygorii Strashko writes:
> On 04/22/2013 04:43 PM, Sourav Poddar wrote:
>> The driver manages "no_console_suspend" by preventing runtime PM
>> during the suspend path, which forces the console UART to stay awake.
>>
>> Signed-off-by: Sourav Poddar
>> ---
>> drivers/tty/serial/omap-serial.c |
As RGMII tx clock internal delay is not supported in AM335x, the same has
to be enabled in phy. This patch adds support for enabling tx clock internal
delay via phy debug registers
Signed-off-by: Mugunthan V N
---
arch/arm/boot/dts/am335x-evm.dts | 10 ++
arch/arm/boot/dts/am335x-evm
Add phy_id device tree data to am335x-evmsk device to bring up CPSW
ethernet present on am335x starter kit.
Signed-off-by: Mugunthan V N
---
arch/arm/boot/dts/am335x-evmsk.dts |8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-evmsk.dts
b/arch/arm/boot/dts/a
In earlier case phy fixup are added in board file as this is no more the case
so adding support for phy register fixup in Device Tree
Signed-off-by: Mugunthan V N
---
.../devicetree/bindings/net/phy-fixup.txt | 26 ++
drivers/of/of_net.c| 92 +
In earlier days phy fixup was added to phy frame work in board files.
As there won't be any board files here after the same has to be done in DT
This patch series adds the following features
* support for adding phy resigter fixup via DT
* adds phy id for EVMsk n DTS file
* adds phy fixup for AM335
* Grygorii Strashko [130422 05:27]:
> On 04/22/2013 01:24 PM, Tomi Valkeinen wrote:
> >On 2013-04-22 12:08, Tomi Valkeinen wrote:
> >>On 2013-04-19 20:13, Tony Lindgren wrote:
> >>
> >>>3. DSS fails with DT booting
> >>>
> >>>Works with legacy booting but fails with DT. I'm almost certain
> >>>the
* Kishon Vijay Abraham I [130422 01:46]:
> Hi,
>
> On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote:
> >Hi all,
> >
> >Here's a list of breakage I've noticed so far while trying to
> >use linux next on my pandaboard es. Probably similar issues exist
> >on other boards as well.
> >
> >Ideally
On 4/22/2013 7:37 PM, Mark Jackson wrote:
Mugunthan
Can you confirm that I'm actually trying to achieve the right thing ?
I have all along assumed that Dual EMAC mode would simply provide the
kernel will a pair of independent Ethernet ports.
Yes, it will provide two network interfaces for ex e
On 04/22/2013 09:11 AM, Bedia, Vaibhav wrote:
(removing Anil's email-id since it's no longer valid)
On Sat, Apr 20, 2013 at 05:54:10, Kondratiuk, Taras wrote:
On 04/19/2013 07:21 PM, Nishanth Menon wrote:
On 14:55-20130419, Taras Kondratiuk wrote:
Using a "voltage tolerance" for doing DVFS is
On 04/22/2013 04:43 PM, Sourav Poddar wrote:
The driver manages "no_console_suspend" by preventing runtime PM
during the suspend path, which forces the console UART to stay awake.
Signed-off-by: Sourav Poddar
---
drivers/tty/serial/omap-serial.c |5 -
1 files changed, 4 insertions(+)
On Mon, Apr 22, 2013 at 07:13:57PM +0530, Sourav Poddar wrote:
> Remove the "OMAP_DEVICE_NO_IDLE_ON_SUSPEND" check, since
> driver should be able to prevent idling of an omap device
> whenever required.
>
> Cc: Santosh Shilimkar
> Cc: Felipe Balbi
> Cc: Rajendra nayak
> Cc: Grygorii Strashko
Hi,
On Mon, Apr 22, 2013 at 07:13:57PM +0530, Sourav Poddar wrote:
> Remove the "OMAP_DEVICE_NO_IDLE_ON_SUSPEND" check, since
> driver should be able to prevent idling of an omap device
> whenever required.
>
> Cc: Santosh Shilimkar
> Cc: Felipe Balbi
> Cc: Rajendra nayak
> Cc: Grygorii Stras
Hi,
On Mon, Apr 22, 2013 at 07:13:56PM +0530, Sourav Poddar wrote:
> The "ti,no_idle_on_suspend" property was required to keep ocmcram
> clocks running during idle.
>
> But the commit below[1], added in v3.6 should prevent the
> any automaic clock gating for devices without drivers bound. Since
On Mon, Apr 22, 2013 at 07:13:55PM +0530, Sourav Poddar wrote:
> "no_console_suspend" is no longer handled in platform file,
> Since the omap serial driver is now adapted to prevent
> console UART idleing during suspend.
>
> Cc: Santosh Shilimkar
> Cc: Felipe Balbi
> Cc: Rajendra nayak
> Signe
Hi,
On Mon, Apr 22, 2013 at 07:13:54PM +0530, Sourav Poddar wrote:
> The driver manages "no_console_suspend" by preventing runtime PM
> during the suspend path, which forces the console UART to stay awake.
>
> Signed-off-by: Sourav Poddar
> ---
> drivers/tty/serial/omap-serial.c |5 -
>
On Mon, Apr 22, 2013 at 07:13:53PM +0530, Sourav Poddar wrote:
> Move "uart_console" definition to serial core header file, so that it can be
> used by serial drivers.
> Get rid of the uart_console defintion from mpc52xx_uart driver.
>
>
> Cc: Santosh Shilimkar
> Cc: Felipe Balbi
> Cc: Rajendra
On 04/22/2013 04:43 PM, Sourav Poddar wrote:
Remove the "OMAP_DEVICE_NO_IDLE_ON_SUSPEND" check, since
driver should be able to prevent idling of an omap device
whenever required.
Cc: Santosh Shilimkar
Cc: Felipe Balbi
Cc: Rajendra nayak
Cc: Grygorii Strashko
Signed-off-by: Sourav Poddar
---
On 18/04/13 17:01, Mark Jackson wrote:
> On 15/04/13 18:34, Mugunthan V N wrote:
>> On 4/15/2013 10:58 PM, Mark Jackson wrote:
>>> On 15/04/13 18:07, Mugunthan V N wrote:
On 4/15/2013 12:46 AM, Mark Jackson wrote:
>>>
>>>
>>>
>
> Notice that at the end, the nfs link appears to come ba
Remove the "OMAP_DEVICE_NO_IDLE_ON_SUSPEND" check, since
driver should be able to prevent idling of an omap device
whenever required.
Cc: Santosh Shilimkar
Cc: Felipe Balbi
Cc: Rajendra nayak
Cc: Grygorii Strashko
Signed-off-by: Sourav Poddar
---
Hi Kevin,
I have put this as an RFC, due to
Hi,
This patch series contains fixes and cleanups around the issue that
the console UART should not idled on suspend while using "no_console_suspend"
in bootargs.
The approach thought of is to modify the serial core/serial driver to bypass
runtime PM if the UART in contention is a console and we
The driver manages "no_console_suspend" by preventing runtime PM
during the suspend path, which forces the console UART to stay awake.
Signed-off-by: Sourav Poddar
---
drivers/tty/serial/omap-serial.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/drivers/tty/serial
"no_console_suspend" is no longer handled in platform file,
Since the omap serial driver is now adapted to prevent
console UART idleing during suspend.
Cc: Santosh Shilimkar
Cc: Felipe Balbi
Cc: Rajendra nayak
Signed-off-by: Sourav Poddar
---
arch/arm/mach-omap2/serial.c |7 ---
1 fi
Move "uart_console" definition to serial core header file, so that it can be
used by serial drivers.
Get rid of the uart_console defintion from mpc52xx_uart driver.
Cc: Santosh Shilimkar
Cc: Felipe Balbi
Cc: Rajendra nayak
Signed-off-by: Sourav Poddar
---
drivers/tty/serial/mpc52xx_uart.c |
The "ti,no_idle_on_suspend" property was required to keep ocmcram
clocks running during idle.
But the commit below[1], added in v3.6 should prevent the
any automaic clock gating for devices without drivers bound. Since
there is no driver for the OCM RAM block, we are not affected by
the automatic
On Mon, Apr 22, 2013 at 06:11:12AM +, Bedia, Vaibhav wrote:
> On Sat, Apr 20, 2013 at 05:54:10, Kondratiuk, Taras wrote:
> that the PMIC outputs can come is either 1.25V or 1.275V. Now i think there's
> been some confusion in the implementation phase due to things like board level
> IR drops a
On 04/22/2013 01:24 PM, Tomi Valkeinen wrote:
On 2013-04-22 12:08, Tomi Valkeinen wrote:
On 2013-04-19 20:13, Tony Lindgren wrote:
3. DSS fails with DT booting
Works with legacy booting but fails with DT. I'm almost certain
the DT booting was working last week or so?
This is what I now get w
Hi Dave,
On 2013-04-18 12:21, Tomi Valkeinen wrote:
> On 2013-04-18 12:09, Tomi Valkeinen wrote:
>> On 2013-04-18 11:37, Christoph Fritz wrote:
>
>>> With linux-next this patch breaks compiling here because DPI now depends
>>> on DSI - but my omap3 board here doesn't use DSI at all:
>>>
>>> drive
On 2013-04-22 12:08, Tomi Valkeinen wrote:
> On 2013-04-19 20:13, Tony Lindgren wrote:
>
>> 3. DSS fails with DT booting
>>
>> Works with legacy booting but fails with DT. I'm almost certain
>> the DT booting was working last week or so?
>>
>> This is what I now get with DT booting:
>>
>> omapdss
The USB host pins are named quite differently between OMAP3 and
OMAP4+ SoCs. To make this managable in code, we create a pin mapping
table (pin_names) that maps pin function to pin name.
This pin mapping table is populated at runtime based on a pin
name template. Templates are provided for OMAP3 a
On 22/04/13 10:38, Mark Jackson wrote:
> I'm trying to work out how to generate a "valid" UBI image, but I keep
> getting a "cannot get enough PEBs" warning.
> ...
> [0.792456] UBI: attaching mtd7 to ubi0
> [1.540858] UBI: scanning is finished
> [1.557578] UBI warning: print_rsvd_war
I'm trying to work out how to generate a "valid" UBI image, but I keep
getting a "cannot get enough PEBs" warning.
I generate my image (destined for a 64MB NAND partition) using:-
$ mkfs.ubifs -d output/target -e 0x1f000 -c 483 -m 0x800 -x none -F -o
output/images/rootfs.ubifs
$ ubinize -o output
On 2013-04-19 20:13, Tony Lindgren wrote:
> 3. DSS fails with DT booting
>
> Works with legacy booting but fails with DT. I'm almost certain
> the DT booting was working last week or so?
>
> This is what I now get with DT booting:
>
> omapdss DSI error: can't get VDDS_DSI regulator
> omapdss HD
When a gpio interrupt is masked, the gpio event will still be latched in
the interrupt status register so when you unmask it later you may get an
interrupt straight away. However, if the interrupt is disabled then gpio
events occurring will not be latched/stored.
Signed-off-by: Andreas Fenkart
--
Added kernel doc for mask/unmask, disable/enable functions.
Andreas Fenkart (1):
gpio/omap: implement irq mask/disable with proper semantic.
drivers/gpio/gpio-omap.c | 69 --
1 file changed, 60 insertions(+), 9 deletions(-)
--
1.7.10.4
--
To uns
Hi,
On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote:
Hi all,
Here's a list of breakage I've noticed so far while trying to
use linux next on my pandaboard es. Probably similar issues exist
on other boards as well.
Ideally we would not have any breakage by the merge window, so
let's try t
On 2013-04-19 21:45, Olof Johansson wrote:
> Hi,
>
> On Wed, Apr 17, 2013 at 08:39:37PM -0700, Tony Lindgren wrote:
>> The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
>>
>> Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
>>
>> are available in the git repository at:
>>
>>
Hi,
On Fri, Apr 19, 2013 at 10:13:19AM -0700, Tony Lindgren wrote:
> 2. MUSB fails with legacy booting and DT on panda es
>
> With both legacy and DT booting I get something like:
>
> HS USB OTG: no transceiver configured
> musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517
On 04/19/2013 06:43 PM, Tony Lindgren wrote:
> * Roger Quadros [130419 03:02]:
>> Hi Benoit/Tony
>>
>> I've consolidated all the USB host device tree patches for Panda and Beagles
>> to one place and addressed Tony's comments.
>>
>> NOTE: patch 1 depends on OMAP clock binding introduced in
>> http
46 matches
Mail list logo
