binz8t4k_0ZSO.bin
Description: iso-8859-1
binZdJucJYmRx.bin
Description: iso-8859-1
* Aaro Koskinen [130304 15:26]:
> Hi,
>
> How should I upgrade my .config files when upgrading to 3.9-rc1?
>
> So far I have been doing it like this:
>
> cp .config
> make ARCH=arm oldnoconfig
>
>
> But now I see that none of my boards boot up... Except OMAP1 (well, after
>
Hi,
How should I upgrade my .config files when upgrading to 3.9-rc1?
So far I have been doing it like this:
cp .config
make ARCH=arm oldnoconfig
But now I see that none of my boards boot up... Except OMAP1 (well, after
fixing the build issues). I believe this is becaus
Hi,
* Aaro Koskinen [130304 13:08]:
> Fix the following build regression in 3.9-rc1 by including
> :
>
> drivers/video/omap/lcd_ams_delta.c: In function 'ams_delta_lcd_set_power':
> drivers/video/omap/lcd_ams_delta.c:48:4: error: implicit declaration of
> function 'omap_writeb' [-Werror=implici
On Sat, Feb 09, 2013 at 08:08:50PM +, Russell King wrote:
> On Sat, Feb 09, 2013 at 09:35:53PM +0530, Sekhar Nori wrote:
> > On 2/1/2013 11:52 PM, Matt Porter wrote:
> > > + ret = of_address_to_resource(node, 1, &res);
> >
> > of_address_to_resource() needs
> >
> > > + if (IS_ERR_VALUE(ret))
On Sat, Feb 09, 2013 at 09:35:53PM +0530, Sekhar Nori wrote:
> Hi Matt,
>
> This version introduces build/bisect issues.
Ok, see later comment which addresses this...
> On 2/1/2013 11:52 PM, Matt Porter wrote:
> > Move mach-davinci/dma.c to common/edma.c so it can be used
> > by OMAP (specifical
* Arnd Bergmann [130304 12:36]:
> On Monday 04 March 2013, Tony Lindgren wrote:
> > > Arnd & Olof, can you please apply this to your non-critical fixes
> > > or some other branch that gets merged early on during the merge
> > > window?
> >
> > I'll apply this into omap-for-v3.9-rc1/fixes.
> >
>
Fix the following build regression in 3.9-rc1 by including
:
drivers/video/omap/lcd_ams_delta.c: In function 'ams_delta_lcd_set_power':
drivers/video/omap/lcd_ams_delta.c:48:4: error: implicit declaration of
function 'omap_writeb' [-Werror=implicit-function-declaration]
drivers/video/omap/lcd_ams
Fix the following build regression in 3.9-rc1 by including
:
drivers/video/omap/omapfb_main.c: In function 'set_fb_var':
drivers/video/omap/omapfb_main.c:505:3: error: implicit declaration of function
'cpu_is_omap15xx' [-Werror=implicit-function-declaration]
Signed-off-by: Aaro Koskinen
---
dr
The binding documentation for the OMAP GPIO controller has the description
for the "#interrupt-cells" property after the "interrupt-controller".
This is confusing so is better to move the "interrupt-controller" after
"#interrupt-cells" description.
While being there, change the properties order to
On Mon, Mar 4, 2013 at 8:23 PM, Jon Hunter wrote:
>
> On 03/04/2013 12:35 PM, Javier Martinez Canillas wrote:
>> The binding documentation for the OMAP GPIO controller has the description
>> for the "#interrupt-cells" property after the "interrupt-controller"
>> definition. This is confusing so is
On Monday 04 March 2013, Russell King - ARM Linux wrote:
> Versatile randconfig:
>
> ERROR: "irq_domain_add_simple" [drivers/gpio/gpio-em.ko] undefined!
>
I'm pretty sure I submitted a patch for this one before. I'll go looking
for it. IIRC the solution was to export that symbol.
Arnd
On Monday 04 March 2013, Tony Lindgren wrote:
> > Arnd & Olof, can you please apply this to your non-critical fixes
> > or some other branch that gets merged early on during the merge
> > window?
>
> I'll apply this into omap-for-v3.9-rc1/fixes.
>
I totally missed this one from you, and I have a
On Mon, Mar 04, 2013 at 11:18:31AM -0800, Tony Lindgren wrote:
> * Felipe Balbi [130219 02:28]:
> > OMAP's debugfs interface creates one file
> > for each signal in the mux table, such file
> > provides a read method but didn't provide
> > read permission. Fix it.
> >
> > Signed-off-by: Felipe Ba
On 03/04/2013 12:53 PM, Tony Lindgren wrote:
> * Ezequiel Garcia [130212 11:26]:
>> This patchset is v3 of the small cleanup consisting in:
>> * mark some functions as 'static' when appropriate
>> * remove an unused function from gpmc.c
>> * improve error messages when a CS request fails
>> *
On 03/04/2013 12:35 PM, Javier Martinez Canillas wrote:
> The binding documentation for the OMAP GPIO controller has the description
> for the "#interrupt-cells" property after the "interrupt-controller"
> definition. This is confusing so is better to move "interrupt-controller"
> after the "#inte
* Felipe Balbi [130219 02:28]:
> OMAP's debugfs interface creates one file
> for each signal in the mux table, such file
> provides a read method but didn't provide
> read permission. Fix it.
>
> Signed-off-by: Felipe Balbi
Heh indeed, although read still seems to work without it.
Applying into
* Tony Lindgren [130211 14:49]:
> Commit 16559ae4 (kgdb: remove #include from kgdb.h)
> had a side effect of breaking omap1_defconfig build as some headers
> were included indirectly:
>
> arch/arm/mach-omap1/board-h2.c:249: error: ‘INT_KEYBOARD’ undeclared here
> (not in a function)
> ...
>
>
* Andreas Müller [130228 04:50]:
Can you please add a description here? Preferrably something
like "With commit XYZ overo poweroff stopped working. Fix this
by blah blah blah" so this can be queued as a fix.
Regards,
Tony
> Signed-off-by: Andreas Müller
> ---
> arch/arm/mach-omap2/board-over
* Nishanth Menon [130301 06:42]:
> On Fri, Mar 1, 2013 at 1:47 AM, Ивайло Димитров wrote:
> >
> > They look similar, but they are not equivalent :). The first major
> > difference is here (code taken from omap-smc.S)
> >
> >> ENTRY(omap_smc2)
> >> stmfd sp!, {r4-r12, lr}
> >>
* Felipe Balbi [130304 10:56]:
> Hi,
>
> On Mon, Mar 04, 2013 at 10:46:50AM -0800, Tony Lindgren wrote:
> > > The last three are caused by incorrect use of 'select':
> > >
> > > warning: (MACH_OMAP_ZOOM2 && MACH_OMAP_ZOOM3 && MWAVE) selects
> > > SERIAL_8250 which has unmet direct dependencies
* Ezequiel Garcia [130212 11:26]:
> This patchset is v3 of the small cleanup consisting in:
> * mark some functions as 'static' when appropriate
> * remove an unused function from gpmc.c
> * improve error messages when a CS request fails
> * migrate to dev_err and dev_warn
>
> Changes from v2
Hi,
On Mon, Mar 04, 2013 at 10:46:50AM -0800, Tony Lindgren wrote:
> > The last three are caused by incorrect use of 'select':
> >
> > warning: (MACH_OMAP_ZOOM2 && MACH_OMAP_ZOOM3 && MWAVE) selects SERIAL_8250
> > which has unmet direct dependencies (TTY && HAS_IOMEM && GENERIC_HARDIRQS)
> > war
* Paul Walmsley [130208 09:57]:
> Hi,
>
> The following changes since commit 88b62b915b0b7e25870eb0604ed9a92ba4bfc9f7:
>
> Linux 3.8-rc6 (2013-02-01 12:08:14 +1100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
> tags/om
On 12:17-20130302, Santosh Shilimkar wrote:
> On Saturday 02 March 2013 05:55 AM, Nishanth Menon wrote:
> > On 17:41-20130301, Santosh Shilimkar wrote:
> >> The OMAP5 idle driver can re-use OMAP4 CPUidle driver implementation thanks
> >> to compatible MPUSS design.
> >>
> >> Though unlike OMAP4, on
Hi,
On Mon, Mar 04, 2013 at 11:58:23AM -0600, Jon Hunter wrote:
> >>> while (isr) {
> >>> unsigned long bit = __ffs(isr);
> >>>
> >>> /* clear this bit */
> >>> isr &= ~bit;
> >>>
> >>> generic_handle_irq(irq_find_mapping(bank->domain, bit);
> >>> }
> >>>
> >>> this way you will only itera
Hi Rob & Felipe,
* Russell King - ARM Linux [130304 01:56]:
> Last nights automated ARM build found the following errors with randconfig.
>
> All information as usual at http://www.arm.linux.org.uk/developer/build/
>
>
> Versatile randconfig:
>
> ERROR: "irq_domain_add_simple" [drivers/gpio/g
On 11:54-20130302, Santosh Shilimkar wrote:
> On Saturday 02 March 2013 05:13 AM, Nishanth Menon wrote:
> > On 17:41-20130301, Santosh Shilimkar wrote:
> >> When the entire MPUSS cluster is powered down in device off state, L2 cache
> >> memory looses it's content and hence while targetting such a
On 11:44-20130302, Santosh Shilimkar wrote:
> On Saturday 02 March 2013 03:06 AM, Nishanth Menon wrote:
> > On 17:40-20130301, Santosh Shilimkar wrote:
> >> Add power management code to handle the CPU off mode. Separate
> >> suspend finisher is used for OMAP5(Cortex-A15) because it doesn't
> >> use
The binding documentation for the OMAP GPIO controller has the description
for the "#interrupt-cells" property after the "interrupt-controller"
definition. This is confusing so is better to move "interrupt-controller"
after the "#interrupt-cells" description.
Reported-by: Stephen Warren
Signed-of
On 11:30-20130302, Santosh Shilimkar wrote:
> On Saturday 02 March 2013 01:42 AM, Nishanth Menon wrote:
> > On 17:40-20130301, Santosh Shilimkar wrote:
> >> diff --git a/arch/arm/mach-omap2/io.c b/arch/arm/mach-omap2/io.c
> >> index 2c3fdd6..e6ba596 100644
> >> --- a/arch/arm/mach-omap2/io.c
> >> +
On 11:22-20130302, Santosh Shilimkar wrote:
> On Saturday 02 March 2013 01:12 AM, Nishanth Menon wrote:
> > On 17:40-20130301, Santosh Shilimkar wrote:
> >> In addition to the standard power-management technique, the OMAP5
> >> MPU subsystem also employs an SR3-APG (mercury) power management
> >> t
On 11:17-20130302, Santosh Shilimkar wrote:
> On Saturday 02 March 2013 01:07 AM, Nishanth Menon wrote:
> > On 17:40-20130301, Santosh Shilimkar wrote:
> >> Enables MPUSS ES2 power management mode using ES2_PM_MODE in
> >> AMBA_IF_MODE register.
> >>
> >> 0x0: ES1 behavior, CPU cores would enter an
On 11:13-20130302, Santosh Shilimkar wrote:
> On Friday 01 March 2013 11:13 PM, Nishanth Menon wrote:
> > On 17:40-20130301, Santosh Shilimkar wrote:
> >> diff --git a/arch/arm/mach-omap2/pm44xx.c
> >> b/arch/arm/mach-omap2/pm_omap4plus.c
> >> similarity index 74%
[..]
> >>mpuss_clkdm = clkdm_
On 03/04/2013 11:51 AM, Jon Hunter wrote:
>
> On 03/04/2013 05:57 AM, Ezequiel Garcia wrote:
>> Hi Jon,
>>
>> On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter wrote:
>>> +
>>> +Example:
>>> +
>>> +gpmc: gpmc@6e00 {
>>> + compatible = "ti,omap3430-gpmc", "simple-bus";
>>
>> I'm concern about
* Santosh Shilimkar [130215 01:38]:
> Tony,
>
> On Friday 08 February 2013 08:41 PM, Santosh Shilimkar wrote:
> >Commit bbd707ac {ARM: omap2: use machine specific hook for late init}
> >accidentally added two declarations for omap4430_init_late().
> >
> >Remove the duplicate declaration.
> >
> >C
* Santosh Shilimkar [130219 05:20]:
> On Tuesday 19 February 2013 06:28 PM, Rajendra Nayak wrote:
> >The .init_late callback for OMAP3 has been missing for DT
> >builds, which causes a lot of late PM initializations to
> >be missed in turn.
> >
> >Signed-off-by: Rajendra Nayak
> >---
> Acked-by:
On 03/04/2013 11:11 AM, Felipe Balbi wrote:
> On Mon, Mar 04, 2013 at 11:06:12AM -0600, Jon Hunter wrote:
>>
>> On 03/02/2013 05:48 AM, Felipe Balbi wrote:
>>> On Fri, Mar 01, 2013 at 11:22:47AM -0600, Jon Hunter wrote:
Currently the OMAP GPIO driver uses a legacy mapping for the GPIO IRQ
>>>
On 03/04/2013 05:57 AM, Ezequiel Garcia wrote:
> Hi Jon,
>
> On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter wrote:
>> +
>> +Example:
>> +
>> +gpmc: gpmc@6e00 {
>> + compatible = "ti,omap3430-gpmc", "simple-bus";
>
> I'm concern about using simple-bus, and I'm not entirely sure this will
* Jon Hunter [130206 06:43]:
>
> On 02/06/2013 08:15 AM, Mark Jackson wrote:
> > When setting the GPMC device type, make sure any previous
> > bits are cleared down, before applying the new setting.
> >
> > Signed-off-by: Mark Jackson
> > ---
> > arch/arm/mach-omap2/gpmc.c |4
> > 1 f
* Ruslan Bilovol [130202 16:18]:
> This is needed because the omap_mux_get_by_name()
> function calls the _omap_mux_get_by_name subfunction
> for each mux partition until needed mux is not found.
> As a result, we get messages like
> "Could not find signal XXX" for each partition
> where this mux
* Jon Hunter [130218 06:01]:
> Commit "ARM: OMAP2+: Prevent potential crash if GPMC probe fails" added
> code to ensure that GPMC chip-selects could not be requested until the
> device probe was successful. The chip-selects should have been
> unreserved at the end of the probe function, but the co
On Mon, Mar 04, 2013 at 11:06:12AM -0600, Jon Hunter wrote:
>
> On 03/02/2013 05:48 AM, Felipe Balbi wrote:
> > On Fri, Mar 01, 2013 at 11:22:47AM -0600, Jon Hunter wrote:
> >> Currently the OMAP GPIO driver uses a legacy mapping for the GPIO IRQ
> >> domain. This is not necessary because we do no
On 03/02/2013 05:48 AM, Felipe Balbi wrote:
> On Fri, Mar 01, 2013 at 11:22:47AM -0600, Jon Hunter wrote:
>> Currently the OMAP GPIO driver uses a legacy mapping for the GPIO IRQ
>> domain. This is not necessary because we do not need to assign a
>> specific interrupt number to the GPIO IRQ domain
I'm encountering an oops when remounting my ubifs volume as read/write.
# mount -o remount,rw /
[ 89.434974] UBIFS assert failed in ubifs_write_node at 869 (pid 628)
[ 89.442122] [] (unwind_backtrace+0x0/0xf0) from []
(ubifs_write_node+0x180/0x1c4)
[ 89.451896] [] (ubifs_write_node+0x180/0x
Here are some basic OMAP test results for Linux v3.8.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.8/20130218214403/
Test summary
Boot to userspace:
Pass ( 9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
3730beaglexm, 37xxevm,
Hi guys,
On Wed, 27 Feb 2013, Tero Kristo wrote:
> It looks like we need to start putting more effort into this clock data
> move now, as this is starting to hinder us on several fronts.
> Unfortunately I still can't personally participate in this work myself
> as I am now allocated to some hwmod
On Sun, 3 Mar 2013, Felipe Balbi wrote:
> > > this is good point and, in fact, a doubt I have myself. How are we
> > > supposed to check if device is suspended ? In case it _is_ suspended we
> > > might not be able to read device's registers due to clocks possibly
> > > being gated.
> >
> > That'
Hi,
On Sat, Mar 02, 2013 at 06:53:02PM +0530, Vivek Gautam 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
> ---
> include/linux/usb/phy.h | 26 ++
On Mon, 4 Mar 2013, Vivek Gautam wrote:
> >> @@ -149,6 +150,8 @@ static int xhci_plat_probe(struct platform_device
> >> *pdev)
> >> if (ret)
> >> goto put_usb3_hcd;
> >>
> >> + pm_runtime_enable(&pdev->dev);
> >
> > This is generally not a good idea. You shouldn't enable
Hi,
On Fri, Mar 01, 2013 at 08:41:29AM +0200, Felipe Balbi wrote:
> > >> >> >> Moreover, SoCs having multiple dwc3 controllers will have multiple
> > >> >> >> PHYs, which eventually be added using usb_add_phy_dev(), and not
> > >> >> >> using usb_add_phy(). So each dwc3 controller won't be able to
Hi Jon,
On Tue, Feb 26, 2013 at 2:30 PM, Jon Hunter wrote:
> +
> +Example:
> +
> +gpmc: gpmc@6e00 {
> + compatible = "ti,omap3430-gpmc", "simple-bus";
I'm concern about using simple-bus, and I'm not entirely sure this will work.
AFAIK, you can't correlate a parent-child relationship i
From: Vaibhav Hiremath
In the original hwmod data file, DebugSS entry was disabled,
since we didn't (and do not) have SW to control it.
This patch enables it back with right data, as now we will
have control through command line argument "omap_debugss_en".
Signed-off-by: Vaibhav Hiremath
Cc: K
From: Vaibhav Hiremath
Currently there is no clean mechanism to control debugSS module and
you have to always keep clocks enabled, either,
- By enabling it during boot as part of clk_init function.
Or
- By having HWMOD_INIT_NO_IDLE flag in hwmod data.
Based on the discussion,
http:/
From: Vaibhav Hiremath
Currently there is no clean mechanism to control debugSS module and
you have to always keep clocks enabled, either,
- By enabling it during boot as part of clk_init function
(post common-clock migration).
Or
- By having HWMOD_INIT_NO_IDLE flag in hwmod da
From: Vaibhav Hiremath
Represent debugSS clock interface as provided in
CM_WKUP_DEBUGSS_CLKCTRL register, which includes,
- Clock gate for optional DEBUG_CLKA and DBGSYSCLK
- Clock Mux for TRC_PMD and STM_PMD
- Clock divider for STM and TPIU
Signed-off-by: Vaibhav Hiremat
On Fri, Mar 01, 2013 at 21:13:37, Hunter, Jon wrote:
>
> On 02/28/2013 11:33 PM, Philip, Avinash wrote:
> > On Thu, Feb 28, 2013 at 22:42:37, Hunter, Jon wrote:
> >>
> >> On 02/28/2013 09:52 AM, Jon Hunter wrote:
> >>>
> >>> On 02/28/2013 12:05 AM, Philip, Avinash wrote:
> On Tue, Feb 26, 201
Last nights automated ARM build found the following errors with randconfig.
All information as usual at http://www.arm.linux.org.uk/developer/build/
Versatile randconfig:
ERROR: "irq_domain_add_simple" [drivers/gpio/gpio-em.ko] undefined!
OMAP4430 randconfig:
drivers/gpu/drm/tilcdc/tilcdc_sla
I'm testing 3.9-rc1 on a pandaboard 4430. I have built using
omap2plus_defconfig and CONFIG_USB_ARCH_HAS_HCD=y. My rootfs is on NFS
[ 10.538665] [ BUG: swapper/0/1 still has locks held! ]
[ 10.544097] 3.9.0-rc1-svn #1 Not tainted
[ 10.548217] -
[ 10.5531
Hi,
On Sat, Mar 2, 2013 at 9:23 PM, Alan Stern wrote:
> On Sat, 2 Mar 2013, Vivek Gautam wrote:
>
>> By enabling runtime pm in this driver allows users of
>> xhci-plat to enter into runtime pm. This is not full
>> runtime pm support (AKA xhci-plat doesn't actually power
>> anything off when in r
61 matches
Mail list logo
