On 17.05.2013 18:51, Kevin Hilman wrote:
> Yegor Yefremov writes:
>
>> On 15.05.2013 10:37, Yegor Yefremov wrote:
>>> On 14.05.2013 15:01, Yegor Yefremov wrote:
On 14.05.2013 14:52, Felipe Balbi wrote:
> On Tue, May 14, 2013 at 11:24:44AM +0200, Yegor Yefremov wrote:
>> Trying to boot
On Tue, May 21, 2013 at 12:05 AM, Tony Lindgren wrote:
> * Yegor Yefremov [130517 14:34]:
>> On Fri, May 17, 2013 at 8:56 PM, Mark A. Greer
>> wrote:
>> > On Thu, May 16, 2013 at 12:19:20PM +0200, Yegor Yefremov wrote:
>> >> On 15.05.2013 23:50, Mark A. Greer wrote:
>> >> > On Wed, May 15, 2013
Resending the same patch series as it is dropped which was sent
during merge window
This patch series adds the following features
* Adding pinctrl PM support for CPSW and MDIO for Power Optimization
* Adding phy address to the CPSW node for EVMsk board
Hebbar Gururaja (1):
net: cpsw: enhance pi
From: Hebbar Gururaja
Amend cpsw controller to optionally take a pin control handle and set
the state of the pins to:
- "default" on boot, resume
- "sleep" on suspend()
This should make it possible to optimize energy usage for the pins
for the suspend/resume cycle.
If any of the above pin stat
Amend cpsw controller to optionally take a pin control handle and set
the state of the pins to:
- "default" on boot, resume
- "sleep" on suspend()
This should make it possible to optimize energy usage for the pins
for the suspend/resume cycle.
If any of the above pin states are missing in dt, a
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
Add pinmux configurations for MII based CPSW ethernet to AM335x EVMsk.
In this patch, only single named mode/state is added and these pins
are configured during pinctrl driver initialization.
Default mode is nothing but the values required for the module during
active state. With this configuratio
Add pinmux configurations for RGMII based CPSW ethernet to am335x-evm.
In this patch, only single named mode/state is added and these pins
are configured during pinctrl driver initialization.
Default mode is nothing but the values required for the module during
active state. With this configuratio
Add pinmux configurations for MII based CPSW ethernet to am335x-bone.
In this patch, only single named mode/state is added and these pins
are configured during pinctrl driver initialization.
Default mode is nothing but the values required for the module during
active state. With this configuration
Hi All,
typically on OMAP4, Cortex-A9 will load the Cortex-M3 firmware and let
M3 run from the firmware. for example, on Android, Linux kernel will
use remoteproc module to load ducati-m3-core0.xem3 of Ducati.
but after reading the datasheet of OMAP4, there are internal 16KB ROM
and 64KB RAM for Co
On Saturday 18 May 2013 12:48 AM, Tony Lindgren wrote:
This is omap4+ only and no longer needed as omap4+ can be booted
using device tree.
Also remove the related pdata handling from the driver and the
now unneeded platform_data/omap_ocp2scp.h.
Cc: Kishon Vijay Abraham I
Cc: Felipe Balbi
Cc:
On 05/17/2013 07:23 PM, Tony Lindgren wrote:
* Kishon Vijay Abraham I [130516 22:45]:
Hi,
On Thursday 16 May 2013 09:50 PM, Tony Lindgren wrote:
* Tomi Valkeinen [130516 09:11]:
On 16/05/13 18:58, Tony Lindgren wrote:
* Tomi Valkeinen [130515 03:59]:
Just checking.. Do you have CONFIG_O
The reset GPIO should be set for the SMSC911x, otherwise the controller
will not work and probing will fail. In the case of the tobi-duo
expansion board, the second controller shares the same GPIO, thus no
more changes are required (not tested).
Signed-off-by: Florian Vaussard
---
arch/arm/mach-
On Tue, May 21, 2013 at 12:04 PM, Barry Song <21cn...@gmail.com> wrote:
> Hi All,
> typically on OMAP4, Cortex-A9 will load the Cortex-M3 firmware and let
> M3 run from the firmware. for example, on Android, Linux kernel will
> use remoteproc module to load ducati-m3-core0.xem3 of Ducati.
> but aft
* Olof Johansson [130520 23:43]:
> On Fri, May 17, 2013 at 12:25:16PM -0700, Tony Lindgren wrote:
> > The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
> >
> > Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
> >
> > are available in the git repository at:
> >
> > git:/
Hi Nicolas,
thanks very much for your reply.
2013/5/21 Nicolas Dechesne :
> On Tue, May 21, 2013 at 12:04 PM, Barry Song <21cn...@gmail.com> wrote:
>> Hi All,
>> typically on OMAP4, Cortex-A9 will load the Cortex-M3 firmware and let
>> M3 run from the firmware. for example, on Android, Linux kerne
On Mon, May 20, 2013 at 03:05:40PM -0700, Tony Lindgren wrote:
> * Yegor Yefremov [130517 14:34]:
> > On Fri, May 17, 2013 at 8:56 PM, Mark A. Greer
> > wrote:
> > > On Thu, May 16, 2013 at 12:19:20PM +0200, Yegor Yefremov wrote:
> > >> On 15.05.2013 23:50, Mark A. Greer wrote:
> > >> > On Wed,
On Mon, May 20, 2013 at 10:46:21AM -0700, Tony Lindgren wrote:
> * Tony Lindgren [130516 14:50]:
> > * Aaro Koskinen [130516 14:05]:
> > > On Thu, May 16, 2013 at 11:09:34AM -0700, Tony Lindgren wrote:
> > > > * Aaro Koskinen [130513 13:58]:
> > > > > I tested 3.10-rc1 on OMAP1 / Nokia 770, and
Paul Walmsley writes:
[...]
> PM: chip retention via suspend:
> FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
> Pass ( 2/ 6): 3530es3beagle, 3730beaglexm
FYI...
I also just noticed that 3730beaglexm has stopped waking from suspend
via RTC (non-DT boot.) Waking from UART co
Olof,
Care to pull this into your fixes directly?
Regards,
Tony
* Paul Walmsley [130519 16:39]:
> The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
>
> Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.
Tony Lindgren writes:
> * Yegor Yefremov [130517 14:34]:
>> On Fri, May 17, 2013 at 8:56 PM, Mark A. Greer
>> wrote:
>> > On Thu, May 16, 2013 at 12:19:20PM +0200, Yegor Yefremov wrote:
>> >> On 15.05.2013 23:50, Mark A. Greer wrote:
>> >> > On Wed, May 15, 2013 at 10:07:35AM -0700, Tony Lindg
On 21/05/13 18:39, Aaro Koskinen wrote:
> On Mon, May 20, 2013 at 10:46:21AM -0700, Tony Lindgren wrote:
>> * Tony Lindgren [130516 14:50]:
>>> * Aaro Koskinen [130516 14:05]:
On Thu, May 16, 2013 at 11:09:34AM -0700, Tony Lindgren wrote:
> * Aaro Koskinen [130513 13:58]:
>> I test
Forwarding as suggested by Tony Lindgren.
https://bugzilla.kernel.org/show_bug.cgi?id=58611
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
When booted in legacy mode device_init_wakeup() gets called
by drivers/mfd/twl-core.c when the children are initialized.
However, when booted using device tree, the children are
created with of_platform_populate() instead add_children().
This means that the RTC driver will not have device_init_wak
when omap_get_control_dev faild, we should release related platform_device
* Changelog from v1:
* fix spell: s/fail/fails/, s/relational/related/ , thank Sergei
Signed-off-by: Libo Chen
---
drivers/usb/musb/omap2430.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff
25 matches
Mail list logo
