On Mon, Apr 8, 2013 at 2:04 PM, Luis R. Rodriguez
wrote:
> Do we have a central place to centrally document ARM development
> upstream? I'd like to start using a central place to start documenting
> things for some stuff I'd like to work on and I don't want to use any
> vendor specific stuff. Are
Andreas Fenkart writes:
> 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.
>
* Tony Lindgren [130423 14:37]:
> * Tony Lindgren [130423 10:28]:
> > * Kishon Vijay Abraham I [130423 08:15]:
> > > >>>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 conf
The following changes since commit 31880c37c11e28cb81c70757e38392b42e695dc6:
Linux 3.9-rc6 (2013-04-07 20:49:54 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v3.9-rc6/fixes-signed
for you to fetch changes up to
* Tony Lindgren [130423 10:28]:
> * Kishon Vijay Abraham I [130423 08:15]:
> > >>>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_
* Arnd Bergmann [130423 14:28]:
> ARM: OMAP: remove unused variable
>
> Commit 0583fe478a7 "ARM: convert arm/arm64 arch timer to use CLKSRC_OF init"
> has left the omap5_realtime_timer_init() function with a stale variable and
> broken whitespace. This fixes both.
>
> Signed-off-by: Arnd
ARM: OMAP: remove unused variable
Commit 0583fe478a7 "ARM: convert arm/arm64 arch timer to use CLKSRC_OF init"
has left the omap5_realtime_timer_init() function with a stale variable and
broken whitespace. This fixes both.
Signed-off-by: Arnd Bergmann
---
I've applied this patch on top o
Olof Johansson writes:
> On Wed, Apr 10, 2013 at 11:14:52AM -0700, Tony Lindgren wrote:
>> Hi,
>>
>> Added Olof to cc, I suggest Olof pull this directly as we're starting
>> to run out of time.
>
> Hi,
>
> I'm terribly sorry for dropping this one on the floor, in spite of repeated
> pings from T
On Tue, 23 Apr 2013, Vivek Gautam wrote:
> Hi,
>
>
> On Tue, Apr 23, 2013 at 10:23 PM, Alan Stern
> wrote:
> > On Tue, 23 Apr 2013, Vivek Gautam wrote:
> >
> >> >> Alright, so here's my understanding:
> >> >>
> >> >> I suggested letting e.g. DWC3 enable the PHY's runtime_pm; Alan said
> >> >>
Hi,
On Tue, Apr 23, 2013 at 10:23 PM, Alan Stern wrote:
> On Tue, 23 Apr 2013, Vivek Gautam wrote:
>
>> >> Alright, so here's my understanding:
>> >>
>> >> I suggested letting e.g. DWC3 enable the PHY's runtime_pm; Alan said
>> >> that it could be done before that so that DWC3 sees an enabled PH
On Wed, Apr 10, 2013 at 11:14:52AM -0700, Tony Lindgren wrote:
> Hi,
>
> Added Olof to cc, I suggest Olof pull this directly as we're starting
> to run out of time.
Hi,
I'm terribly sorry for dropping this one on the floor, in spite of repeated
pings from Tony. :(
If it wasn't for the fact that
On 04/23/2013 08:34 PM, Tony Lindgren wrote:
* Grygorii Strashko [130423 06:25]:
Hi
There are two public discussions now related to OMAP boot and drivers
initialization issues:
"Multiple issues with omap4 panda es in linux next"
http://www.spinics.net/lists/linux-omap/msg90241.html
"[BUG] o
* Kishon Vijay Abraham I [130422 23:19]:
> 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 fun
* Grygorii Strashko [130423 06:25]:
> Hi
>
> There are two public discussions now related to OMAP boot and drivers
> initialization issues:
> "Multiple issues with omap4 panda es in linux next"
> http://www.spinics.net/lists/linux-omap/msg90241.html
> "[BUG] omap: mfd/regulator: twl/core: init
* Grygorii Strashko [130423 06:59]:
>
> I've posted two patches to fix I2C/TWL initialization and they should fix
> DSS indirectly (if not - DSS need to be shifted to init later).
> lkml.org/lkml/2013/4/23/215
> lkml.org/lkml/2013/4/23/217
OK, thanks. We may want to wait a bit on those, but I'll
On 4/23/2013 9:48 PM, Markus Brunner wrote:
If operating in dual emac mode all packets sent by the CPSW contain vlan
headers with the reserved VID 0,
which gets stripped away by all somewhat recent Linux versions. Operating
systems without that behaviour will fail to communicate.
This patch fix
* Kishon Vijay Abraham I [130423 08:15]:
> >>>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
> >>
>
* Tomi Valkeinen [130422 01:37]:
> 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
On Tue, 23 Apr 2013, Vivek Gautam wrote:
> >> Alright, so here's my understanding:
> >>
> >> I suggested letting e.g. DWC3 enable the PHY's runtime_pm; Alan said
> >> that it could be done before that so that DWC3 sees an enabled PHY
> >> during probe.
> >
> > Basically right. Help me to understa
If operating in dual emac mode all packets sent by the CPSW contain vlan
headers with the reserved VID 0,
which gets stripped away by all somewhat recent Linux versions. Operating
systems without that behaviour will fail to communicate.
This patch fixes that behaviour by disabling the VLAN_AWAR
Hi Tony,
On Monday 22 April 2013 11:33 PM, Tony Lindgren wrote:
* 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 issu
On 04/22/2013 09:08 PM, Tony Lindgren wrote:
* 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
The OMAP I2C driver has a relation to pinctrl-single driver. As result,
its probe will be deferred during system boot until late init time,
because the pinctrl-single is initizalized as moudle/device init time.
This, in turn, will delay initialization of all I2C devices (like mfd,
I2C regulators an
Shift TWL initialization to module/device init layer, because I2C now is
not initialized on subsys init layer and shifted to module/device init
layer instead.
The I2C <--> TWL dependency should be resolved in drivers/Makefile now.
Cc: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org
Cc: linux-ke
Hi
There are two public discussions now related to OMAP boot and drivers
initialization issues:
"Multiple issues with omap4 panda es in linux next"
http://www.spinics.net/lists/linux-omap/msg90241.html
"[BUG] omap: mfd/regulator: twl/core: init order"
http://www.spinics.net/lists/linux-omap/ms
Hi,
On Thu, Apr 4, 2013 at 8:16 PM, Alan Stern wrote:
Apologies for delay in replying.
> On Thu, 4 Apr 2013, Felipe Balbi wrote:
>
>> > >> Some subsystems handle this issue by calling pm_runtime_get_sync()
>> > >> before probing a driver and pm_runtime_put_sync() after unbinding the
>> > >> dr
OMAP devices support various NAND transfer modes.
Currently all device-tree definitions will use the default "prefetch
polled" mode, so this patch enables the transfer mode to be specified
in the device-tree.
Signed-off-by: Mark Jackson
---
Changes in v2:
- Fixed line wrapping
.../devicetree/b
Hi,
On Thu, Apr 18, 2013 at 05:20:11PM +0530, Kishon Vijay Abraham I wrote:
> >Adding APIs to handle runtime power management on PHY
> >devices. PHY consumers may need to wake-up/suspend PHYs
> >when they work across autosuspend.
> >
> >Signed-off-by: Vivek Gautam
> >---
On Tuesday 23 April 2013 02:49 PM, Grygorii Strashko wrote:
On 04/23/2013 08:19 AM, Sourav Poddar wrote:
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,
On 04/23/2013 08:19 AM, Sourav Poddar wrote:
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 dev
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.
>
> I generate my image (destined for a 64MB NAND partition) using:-
>
> $ mkfs.ubifs -d output/target -e 0x1f000 -c 483 -m 0x800 -x none -
Hi Rajendra,
On Thu, 18 Apr 2013, Rajendra Nayak wrote:
> >>> _enable_wakeup() and _disable_wakeup() are expected to program the
> >>> OCP_SYSCONFIG.ENAWAKEUP bit.
> >>
> >> These functions were originally intended to take care of everything needed
> >> for the IP block to wake up the chip, incl
On Mon, Apr 22, 2013 at 11:50:35PM +0530, Mugunthan V N wrote:
> 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 fix
Hi,
On 04/22/2013 04:38 PM, Felipe Balbi wrote:
>> Is it possible to handle ABE no_idle_on_suspend uscase the way I am
>> trying to handle it for UART in the 2nd patch of this series?
>
> let's ask Péter.
>
> Péter, OMAP_DEVICE_NO_IDLE_ON_SUSPEND should be removed as driver's can
> get same beh
34 matches
Mail list logo
