On 09/05/12 18:44, Paul Walmsley wrote:
Here are some basic boot and power management test results for v3.6-rc4:
http://www.pwsan.com/omap/testlogs/test_v3.6-rc4/20120904122415/
Some observations:
[...]
* CM-T3517: L3 in-band error with USB OTG during boot
- Cause unknown;
Hi Jean,
My bad, I didn't follow up with this. My guess is that it has not been
picked up. Tony, Kevin?
regards,
-roger
On 09/06/2012 09:59 PM, Jean Pihet wrote:
Fixed Paul's email address
On Thu, Sep 6, 2012 at 8:56 PM, Jean Pihet jean.pi...@newoldbits.com wrote:
Hi Roger,
On Fri, Aug
On Fri, Sep 07, 2012 at 05:39:35, Marek Vasut wrote:
Dear Tony Lindgren,
* Marek Vasut ma...@denx.de [120905 19:05]:
Hi Tony,
* Marek Vasut ma...@denx.de [120904 20:13]:
Dear Bryan Wu,
On Sat, Sep 1, 2012 at 4:16 PM, AnilKumar Ch anilku...@ti.com
wrote:
On Thu, Sep 6, 2012 at 8:58 PM, Tony Lindgren t...@atomide.com wrote:
Add pinctrl driver entries for omap2+. These all use
the generic pinctrl-single driver for the padconf
registers.
Note that as 2420 and 2430 have different padmux
registers, we now need to include omap2420.dtsi from
Dear AnilKumar, Chimata,
On Fri, Sep 07, 2012 at 05:39:35, Marek Vasut wrote:
Dear Tony Lindgren,
* Marek Vasut ma...@denx.de [120905 19:05]:
Hi Tony,
* Marek Vasut ma...@denx.de [120904 20:13]:
Dear Bryan Wu,
On Sat, Sep 1, 2012 at 4:16 PM, AnilKumar Ch
On Wed, Sep 05, 2012 at 16:42:44, AnilKumar, Chimata wrote:
Adds suspend resume support to DCAN driver which enables
DCAN power down mode bit (PDR). Then DCAN will ack the local
power-down mode by setting PDA bit in STATUS register.
Marc,
I missed out this patch, I will remove raminit calls
Hi Anil,
On 09/07/2012 07:30 AM, AnilKumar, Chimata wrote:
On Thu, Sep 06, 2012 at 15:08:21, AnilKumar, Chimata wrote:
Add pinctrl and d_can device tree data to AM33XX family of devices.
First two patches add support for pinctrl DT data and third one
adds dcan DT data.
Reason behind
Hi Anil,
On 09/07/2012 07:45 AM, AnilKumar, Chimata wrote:
On Wed, Sep 05, 2012 at 20:11:11, Hiremath, Vaibhav wrote:
On Wed, Sep 05, 2012 at 19:01:55, Cousson, Benoit wrote:
Hi Vaibhav,
On 09/05/2012 11:15 AM, Hiremath, Vaibhav wrote:
On Wed, Sep 05, 2012 at 13:53:58, Ujfalusi, Peter
Op 6 sep. 2012, om 11:38 heeft AnilKumar Ch anilku...@ti.com het volgende
geschreven:
Adds GPIO pinctrl nodes to am3358_pinmux master node to control
user leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
[k...@dominion.thruhere.net: led0, led1 suggested by koen]
Signed-off-by:
Add the support for D6 and D7 LEDs on Beagle board.
- D6 will be used for heartbeat
- D7 will be used for mmc0
Signed-off-by: Benoit Cousson b-cous...@ti.com
---
It is based on top of the LEDB support added by Florian.
Regards,
Benoit
arch/arm/boot/dts/omap3-beagle.dts | 12
1
On 09/06/2012 10:51 PM, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [120905 07:42]:
Hi Florian,
On 09/05/2012 09:46 AM, Florian Vaussard wrote:
Hello,
A number of platform data are missing when using twl4030/gpio from a
device tree. This patchset adds the missing properties,
Made *ocp2scp_usb_phy_phy_48m* as the main_clk for ocp2scp.
Since this ocp2scp module does not have any fck but does have a
single opt_clock, it is added as the main_clk for ocp2scp. Also
removed phy_48m as the optional clock since it is now made as the
main clock. By this the driver need not
Hi Domenico,
On Fri, Sep 07, 2012 at 14:18:39, Domenico Andreoli wrote:
On Sat, Sep 1, 2012 at 10:16 AM, AnilKumar Ch anilku...@ti.com wrote:
Adopt pinctrl support to leds-gpio driver based on leds-gpio
device pointer, pinctrl driver configure SoC pins to GPIO
mode according to definitions
On Mon, 2012-08-06 at 16:31 -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
This patch fixes the usecount tracking for omap3+, previously the
usecount numbers were rather bogus and were not really useful for
any purpose. Now usecount numbers track the number of really
On Mon, 2012-08-06 at 12:14 +0200, Jean Pihet wrote:
Hi Tero,
On Mon, Jul 30, 2012 at 10:40 AM, Tero Kristo t-kri...@ti.com wrote:
On Fri, 2012-07-27 at 12:36 -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
mpu / core powerdomain usecounts are now statically increased
On Wed, 2012-09-05 at 11:25 +0300, Tomi Valkeinen wrote:
dss_mgr_set_timings() can only be called when the output is not active.
This means that most of the code in the function is extra, as there's no
need to write the values to registers, etc, because that will be handled
when the output
On Thu, 2012-09-06 at 13:13 -0700, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [120904 00:23]:
Hi Tony,
Can you check the arch/arm patches below, and suggest how you'd like to
go forward with them?
Acked them, then as soon as we have the initial immutable header
move
On Fri, 2012-09-07 at 07:55 +0200, Marek Szyprowski wrote:
Hello,
On Wednesday, September 05, 2012 12:09 PM Tomi Valkeinen wrote:
OMAP has a custom video ram allocator, which I'd like to remove and use
the standard dma allocation functions.
There are two problems for which I'd like
On Fri, Sep 07, 2012 at 09:10:50AM +, AnilKumar, Chimata wrote:
Hi Domenico,
Hi,
On Fri, Sep 07, 2012 at 14:18:39, Domenico Andreoli wrote:
On Sat, Sep 1, 2012 at 10:16 AM, AnilKumar Ch anilku...@ti.com wrote:
Adopt pinctrl support to leds-gpio driver based on leds-gpio
device
On Thu, Sep 06, 2012 at 12:30:15PM +0530, Philip, Avinash wrote:
Add McSPI data node to AM33XX device tree file. The McSPI module (and so
as the driver) is reused from OMAP4.
Signed-off-by: Philip, Avinash avinashphi...@ti.com
---
Resenting patch because ARM OMAP mailing list was not
Hi Dmitry,
On 09/06/2012 07:19 PM, Dmitry Torokhov wrote:
In patch 6 you added a stub for of_find_node_by_name(), so do you really
need this #ifdef?
True. I'll resend the series since I left the #ifdef also in other patch.
Otherwise it looks good.
Acked-by: Dmitry Torokhov
Hi
On Tue, Sep 04, 2012 at 05:41:24PM +0300, Aaro Koskinen wrote:
Convert omap_wdt to new watchdog core. On OMAP boards, there are usually
multiple watchdogs. Since the new watchdog core supports multiple
watchdogs, all watchdog drivers used on OMAP should be converted.
The legacy watchdog
On Fri, Sep 07, 2012 at 16:32:51, Domenico Andreoli wrote:
On Fri, Sep 07, 2012 at 09:10:50AM +, AnilKumar, Chimata wrote:
Hi Domenico,
Hi,
On Fri, Sep 07, 2012 at 14:18:39, Domenico Andreoli wrote:
On Sat, Sep 1, 2012 at 10:16 AM, AnilKumar Ch anilku...@ti.com wrote:
Adopt
Hi,
On Thursday 06 September 2012 16:36:54 Tomi Valkeinen wrote:
Hi,
On Sun, 2012-09-02 at 22:12 +0300, Dimitar Dimitrov wrote:
Very rare kernel crashes are reported on a custom OMAP4 board. Kernel
panics due to corrupted completion structure while executing
dispc_irq_wait_handler().
Hi Tony,
On 09/06/2012 10:10 PM, Tony Lindgren wrote:
Hi Peter,
* Peter Ujfalusi peter.ujfal...@ti.com [120905 02:02]:
With pinctrl-single,bits it is possible to update just part of the register
within the pinctrl-single,function-mask area.
This is useful when one register configures mmore
Thanks to Vaibhav hvaib...@ti.com omap_device fix
(ARM: OMAP: omap_device: Fix up resource names when booted with devicetre),
we can now specify reg and interrupts using standard device tree
attributes.
Update the OMAP4 dtsi file with missing reg and interrupts attributes.
Signed-off-by: Benoit
On Fri, Sep 07, 2012 at 08:25:31AM +0300, Felipe Balbi wrote:
when rebasing patches on top of Greg's tty-next,
it looks like automerge broke a few things which
I didn't catch (for whatever reason I didn't
have OMAP Serial enabled on .config) so I ended
up breaking the build on Greg's tty-next
when rebasing patches on top of Greg's tty-next,
it looks like automerge broke a few things which
I didn't catch (for whatever reason I didn't
have OMAP Serial enabled on .config) so I ended
up breaking the build on Greg's tty-next branch.
Fix the breakage by re-adding the three missing
members
On Fri, Sep 07, 2012 at 06:34:19PM +0300, Felipe Balbi wrote:
when rebasing patches on top of Greg's tty-next,
it looks like automerge broke a few things which
I didn't catch (for whatever reason I didn't
have OMAP Serial enabled on .config) so I ended
up breaking the build on Greg's tty-next
Hi Tony,
On 09/06/2012 08:58 PM, Tony Lindgren wrote:
The extra serial port is not available on 34xx. And the current
omap3-beagle.dts file is for omap3-beagle-xm.dts as it lists 512MB
of memory.
Indeed, my Beagle is in fact a xM :-)
It is too bad that we do have to duplicate the DTS file
On Fri, Sep 07, 2012 at 04:31:07PM +0300, Jarkko Nikula wrote:
On Tue, Sep 04, 2012 at 05:41:24PM +0300, Aaro Koskinen wrote:
Convert omap_wdt to new watchdog core. On OMAP boards, there are usually
multiple watchdogs. Since the new watchdog core supports multiple
watchdogs, all watchdog
On Fri, Sep 07, 2012 at 02:30:59PM +, AnilKumar, Chimata wrote:
On Fri, Sep 07, 2012 at 16:32:51, Domenico Andreoli wrote:
On Fri, Sep 07, 2012 at 09:10:50AM +, AnilKumar, Chimata wrote:
On Fri, Sep 07, 2012 at 14:18:39, Domenico Andreoli wrote:
On Sat, Sep 1, 2012 at 10:16 AM,
On Fri, Sep 7, 2012 at 3:59 PM, AnilKumar, Chimata anilku...@ti.com wrote:
On Fri, Sep 07, 2012 at 05:39:35, Marek Vasut wrote:
Dear Tony Lindgren,
* Marek Vasut ma...@denx.de [120905 19:05]:
Hi Tony,
* Marek Vasut ma...@denx.de [120904 20:13]:
Dear Bryan Wu,
On Sat,
* Tomi Valkeinen tomi.valkei...@ti.com [120823 06:46]:
We currently manage HDMI GPIOs in the board files via
platform_enable/disable calls. This won't work with device tree, and in
any case the correct place to manage the GPIOs is in the HDMI driver.
This patch moves the handling of the
* Tomi Valkeinen tomi.valkei...@ti.com [120907 03:16]:
On Thu, 2012-09-06 at 13:13 -0700, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [120904 00:23]:
Hi Tony,
Can you check the arch/arm patches below, and suggest how you'd like to
go forward with them?
Acked
* Domenico Andreoli cav...@gmail.com [120907 09:01]:
So is this the preferred way to attach gpio users to gpio provides in DT
whenever gpios are muxed?
I would well see these info hidden in the gpio controller so, at least
for gpios, no magic numbers would be required in the DT (except the
* Peter Ujfalusi peter.ujfal...@ti.com [120907 08:13]:
On 09/06/2012 10:10 PM, Tony Lindgren wrote:
Is it now safe to assume that we always have width of three if
pinctrl-single,bits is specified? The reason I'm asking is..
@@ -657,18 +664,29 @@ static int
* AnilKumar Ch anilku...@ti.com [120906 02:39]:
Adds basic pinctrl device tree data for AM33XX family of devices.
This patch is based on the pinctrl-single driver.
Signed-off-by: AnilKumar Ch anilku...@ti.com
Assuming Benoit will queue this series:
Acked-by: Tony Lindgren t...@atomide.com
On Fri, 2012-09-07 at 09:22 -0700, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [120907 03:16]:
On Thu, 2012-09-06 at 13:13 -0700, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [120904 00:23]:
Hi Tony,
Can you check the arch/arm patches below, and
* Koen Kooi k...@dominion.thruhere.net [120907 01:46]:
Op 6 sep. 2012, om 11:38 heeft AnilKumar Ch anilku...@ti.com het volgende
geschreven:
Adds GPIO pinctrl nodes to am3358_pinmux master node to control
user leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
* Benoit Cousson b-cous...@ti.com [120907 01:38]:
Hi Anil,
On 09/07/2012 07:30 AM, AnilKumar, Chimata wrote:
On Thu, Sep 06, 2012 at 15:08:21, AnilKumar, Chimata wrote:
Add pinctrl and d_can device tree data to AM33XX family of devices.
First two patches add support for pinctrl DT data
* Benoit Cousson b-cous...@ti.com [120907 08:26]:
Thanks to Vaibhav hvaib...@ti.com omap_device fix
(ARM: OMAP: omap_device: Fix up resource names when booted with devicetre),
we can now specify reg and interrupts using standard device tree
attributes.
Update the OMAP4 dtsi file with
* AnilKumar, Chimata anilku...@ti.com [120906 20:27]:
Hi Tony,
On Fri, Sep 07, 2012 at 00:28:32, Tony Lindgren wrote:
Request pins using pinctrl framework. Only show a warning
on error as some boards set the pins in the bootloader
even if CONFIG_PINCTRL is enabled.
Cc:
Hi,
On Fri, Sep 07, 2012 at 05:25:24PM +0200, Benoit Cousson wrote:
Thanks to Vaibhav hvaib...@ti.com omap_device fix
(ARM: OMAP: omap_device: Fix up resource names when booted with devicetre),
we can now specify reg and interrupts using standard device tree
attributes.
Update the OMAP4
* Felipe Balbi ba...@ti.com [120907 10:30]:
Hi,
On Fri, Sep 07, 2012 at 10:06:22AM -0700, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [120907 08:26]:
Thanks to Vaibhav hvaib...@ti.com omap_device fix
(ARM: OMAP: omap_device: Fix up resource names when booted with
Hi Florian,
I've just noticed that this patch is reporting some CHECK issues.
d1f5052 - gpio/twl4030: get platform data from device tree
CHECK: Alignment should match open parenthesis
#66: FILE: drivers/gpio/gpio-twl4030.c:412:
+ of_property_read_u32(dev-of_node, ti,debounce,
+
On 09/07/2012 07:23 PM, Felipe Balbi wrote:
Hi,
On Fri, Sep 07, 2012 at 05:25:24PM +0200, Benoit Cousson wrote:
Thanks to Vaibhav hvaib...@ti.com omap_device fix
(ARM: OMAP: omap_device: Fix up resource names when booted with devicetre),
we can now specify reg and interrupts using standard
Hi Vaibhav,
The following patch is hacing some checkpatch issues.
CHECK: Alignment should match open parenthesis
#169: FILE: arch/arm/plat-omap/omap_device.c:591:
+ dev_dbg(pdev-dev, %s(): resources already allocated
%d\n,
+ __func__,
* Greg KH gre...@linuxfoundation.org [120907 08:43]:
On Fri, Sep 07, 2012 at 06:34:19PM +0300, Felipe Balbi wrote:
when rebasing patches on top of Greg's tty-next,
it looks like automerge broke a few things which
I didn't catch (for whatever reason I didn't
have OMAP Serial enabled on
Request pins using pinctrl framework. Only show a warning
on error as some boards set the pins in the bootloader
even if CONFIG_PINCTRL is enabled.
Signed-off-by: Tony Lindgren t...@atomide.com
---
Note that this has only so far been tested with the legacy
non-devicetree boot as devicetree boot
From: Rob Clark r...@ti.com
Without these, DVI is broken.
Signed-off-by: Rob Clark r...@ti.com
---
Greg, it looks like the omapdss changes which added these fields, as
well as the interlaced field, where merged in Linux 3.5-rc5. So I
think both this and the 'update for interlaced' patch are
* Tony Lindgren t...@atomide.com [120907 10:29]:
* AnilKumar, Chimata anilku...@ti.com [120906 20:27]:
@@ -1570,6 +1578,8 @@ static int serial_omap_remove(struct
platform_device *dev)
pm_runtime_disable(up-pdev-dev);
uart_remove_one_port(serial_omap_reg, up-port);
Hi Vaibhav,
The following patch is having some checkpatch issues.
CHECK: Alignment should match open parenthesis
#169: FILE: arch/arm/plat-omap/omap_device.c:591:
+ dev_dbg(pdev-dev, %s(): resources already allocated
%d\n,
+ __func__,
* Felipe Balbi ba...@ti.com [120907 11:15]:
OMAP Architecture code, passes a few function
pointers for UART driver to use in order to
properly implement Power Management and Wakeup
capabilities.
The problem is that those function pointers,
which are passed (ab)using platform_data on
* Tony Lindgren t...@atomide.com [120907 11:00]:
Request pins using pinctrl framework. Only show a warning
on error as some boards set the pins in the bootloader
even if CONFIG_PINCTRL is enabled.
Signed-off-by: Tony Lindgren t...@atomide.com
---
Note that this has only so far been
On Fri, Sep 07, 2012 at 23:17:37, Cousson, Benoit wrote:
Hi Vaibhav,
The following patch is hacing some checkpatch issues.
CHECK: Alignment should match open parenthesis
#169: FILE: arch/arm/plat-omap/omap_device.c:591:
+ dev_dbg(pdev-dev, %s(): resources already
On Fri, Sep 07, 2012 at 06:51:43PM +0300, Aaro Koskinen wrote:
Thanks for the report! I'll look into this and test with other
Nokia boards. I tested the patch only with N800 and v3.6-rc4
(4cbe5a555fa58a79b6ecbb6c531b8bab0650778d) and did not see any issues
with normal use cases (boot,
Hi Tony,
On 08/30/2012 03:14 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [120816 08:05]:
On 08/15/2012 04:11 AM, Vaibhav Hiremath wrote:
Did we get conclude on this? I haven't got anything further on this
thread, this may block baseport support for the new devices in omap2
Felipe Balbi ba...@ti.com writes:
Hi,
On Thu, Sep 06, 2012 at 03:44:13PM -0700, Kevin Hilman wrote:
Felipe Balbi ba...@ti.com writes:
Hi guys,
here's v4 of the omap uart patchset. No changes other than a rebase on top
of
Greg's tty-next branch and Tony's Acked-by being added to a
* Jon Hunter jon-hun...@ti.com [120907 13:27]:
Hi Tony,
On 08/30/2012 03:14 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [120816 08:05]:
On 08/15/2012 04:11 AM, Vaibhav Hiremath wrote:
Did we get conclude on this? I haven't got anything further on this
thread, this may
AnilKumar, Chimata anilku...@ti.com writes:
Hi Kevin,
On Fri, Sep 07, 2012 at 05:07:56, Kevin Hilman wrote:
AnilKumar Ch anilku...@ti.com writes:
Add Runtime PM support to C_CAN/D_CAN controller. The runtime PM
APIs control clocks for C_CAN/D_CAN IP and prevent access to the
register
On Thu, Sep 6, 2012 at 8:59 PM, Tony Lindgren t...@atomide.com wrote:
* Peter Ujfalusi peter.ujfal...@ti.com [120905 02:02]:
Use the pcs-fmask to make sure that the value is not changing (setting)
bits in areas where it should not.
To avoid situations like this:
pmx_dummy: pinmux@4a100040 {
On 09/07/2012 03:56 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [120907 13:27]:
Hi Tony,
On 08/30/2012 03:14 PM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [120816 08:05]:
On 08/15/2012 04:11 AM, Vaibhav Hiremath wrote:
Did we get conclude on this? I haven't got
On Sat, Sep 1, 2012 at 10:16 AM, AnilKumar Ch anilku...@ti.com wrote:
Adopt pinctrl support to leds-gpio driver based on leds-gpio
device pointer, pinctrl driver configure SoC pins to GPIO
mode according to definitions provided in .dts file.
Signed-off-by: AnilKumar Ch anilku...@ti.com
Hi Neil,
NeilBrown ne...@suse.de writes:
On Thu, 6 Sep 2012 11:18:09 +0530 Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Thu, Sep 6, 2012 at 8:35 AM, NeilBrown ne...@suse.de wrote:
On Mon, 3 Sep 2012 22:59:06 -0700 Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
After
* Linus Walleij linus.wall...@linaro.org [120907 14:13]:
On Thu, Sep 6, 2012 at 8:59 PM, Tony Lindgren t...@atomide.com wrote:
* Peter Ujfalusi peter.ujfal...@ti.com [120905 02:02]:
Use the pcs-fmask to make sure that the value is not changing (setting)
bits in areas where it should not.
On Thu, Sep 6, 2012 at 7:45 PM, Tony Lindgren t...@atomide.com wrote:
The warning should be pinctrl related as the pinctrl drivers may not be
device tree based drivers.
Exactly my concern. Also the warning shouldnt be present on systems where
pinctrl is disabled.
But pinctrl_get_select()
* Linus Walleij linus.wall...@linaro.org [120907 14:40]:
On Thu, Sep 6, 2012 at 7:45 PM, Tony Lindgren t...@atomide.com wrote:
The warning should be pinctrl related as the pinctrl drivers may not be
device tree based drivers.
Exactly my concern. Also the warning shouldnt be present on
Tero Kristo t-kri...@ti.com writes:
On Mon, 2012-08-06 at 12:14 +0200, Jean Pihet wrote:
Hi Tero,
On Mon, Jul 30, 2012 at 10:40 AM, Tero Kristo t-kri...@ti.com wrote:
On Fri, 2012-07-27 at 12:36 -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
mpu / core powerdomain
Roger Quadros rog...@ti.com writes:
Hi Jean,
My bad, I didn't follow up with this. My guess is that it has not been
picked up. Tony, Kevin?
Wasn't picked up by me (but should've been, sorry.) Care to refresh
against v3.6-rc4 and resend?
Thanks,
Kevin
On 09/06/2012 09:59 PM, Jean
On Fri, Sep 7, 2012 at 6:00 PM, Domenico Andreoli cav...@gmail.com wrote:
On Fri, Sep 07, 2012 at 02:30:59PM +, AnilKumar, Chimata wrote:
How can gpio driver knows that leds-gpio driver require
these 4 pins?
because leds-gpio requests each gpio (specified in the DT against a specific
Venkatraman S svenk...@ti.com writes:
omap hsmmc controller IP has a built in timer that can be programmed to
guard against unresponsive operations. But its range is very narrow,
and the maximum countable time is a few seconds.
Card maintenance operations like BKOPS and MMC_ERASE and long
On Fri, Sep 7, 2012 at 6:35 PM, Tony Lindgren t...@atomide.com wrote:
In the pure GPIO pins only case it could be all done in the GPIO controller,
but it's probably best to have the pins muxed by the drivers using them.
Yes, that's an easier way to say the long unreadable thing I just
posted
Wei Yongjun weiyj...@gmail.com writes:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
pdata and pdata-regs have been allocated in this function and
should be freed before leaving it, and in the other error handling
cases too.
spatch with a semantic match is used to found this problem.
* Afzal Mohammed af...@ti.com [120905 05:37]:
Hi,
Basic gpmc driver conversion series. Driver that is now created out of
gpmc code is a simple one, it handles tasks that were earlier executed
by gpmc_init. Now instead of relying on cpu_is_* checks, it obtains
resources and clk handle in the
* Jon Hunter jon-hun...@ti.com [120905 12:05]:
The dmtimer functions to read and write the dmtimer registers are currently
defined as follows ...
static inline u32 __omap_dm_timer_read(struct omap_dm_timer *timer, u32 reg,
int posted);
static
* Kevin Hilman khil...@deeprootsystems.com [120907 15:07]:
Wei Yongjun weiyj...@gmail.com writes:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
pdata and pdata-regs have been allocated in this function and
should be freed before leaving it, and in the other error handling
cases
Tony Lindgren t...@atomide.com writes:
* Kevin Hilman khil...@deeprootsystems.com [120907 15:07]:
Wei Yongjun weiyj...@gmail.com writes:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
pdata and pdata-regs have been allocated in this function and
should be freed before leaving it,
On Wed, Sep 5, 2012 at 5:44 PM, Paul Walmsley p...@pwsan.com wrote:
Here are some basic boot and power management test results for v3.6-rc4:
http://www.pwsan.com/omap/testlogs/test_v3.6-rc4/20120904122415/
Some observations:
* N800: panics during kernel init
- This is caused by an
Hi,
On Sat, 8 Sep 2012, Andreas Müller wrote:
On Wed, Sep 5, 2012 at 5:44 PM, Paul Walmsley p...@pwsan.com wrote:
Here are some basic boot and power management test results for v3.6-rc4:
http://www.pwsan.com/omap/testlogs/test_v3.6-rc4/20120904122415/
Some observations:
*
This series, intended for 3.7 cleanup, cleans up the Makefile in
arch/arm/mach-omap2. It places PRCM-related lines in the PRCM
sections, clock lines in the clock sections, etc.; and fixes some
formatting and whitespace. This is meant to serve as a base for
future cleanups to avoid conflicts as
Move the omap_hwmod_common_data.o build directive down to the hwmod
data Makefile section where it belongs. Move the omap_hwmod.o build
directive to the top 'Common support' line, since we have no separate
hwmod code Makefile section, and it's currently needed for all OMAP2+.
Signed-off-by: Paul
Convert spaces that should be tabs into tabs. Fix another minor
formatting issue.
Signed-off-by: Paul Walmsley p...@pwsan.com
---
arch/arm/mach-omap2/Makefile | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/arch/arm/mach-omap2/Makefile
The prm44xx.o and sleep44xx.o build directives belong with the other
PRCM- and PM-related build sections in the Makefile; move them there.
Signed-off-by: Paul Walmsley p...@pwsan.com
---
arch/arm/mach-omap2/Makefile | 18 +++---
1 file changed, 7 insertions(+), 11 deletions(-)
Clean up the OMAP clock code sections of the Makefile to save
some lines of diff.
Signed-off-by: Paul Walmsley p...@pwsan.com
---
arch/arm/mach-omap2/Makefile | 21 -
1 file changed, 8 insertions(+), 13 deletions(-)
diff --git a/arch/arm/mach-omap2/Makefile
Clean up the PRCM sections of the Makefile; this saves a few lines.
Signed-off-by: Paul Walmsley p...@pwsan.com
---
arch/arm/mach-omap2/Makefile | 35 ++-
1 file changed, 10 insertions(+), 25 deletions(-)
diff --git a/arch/arm/mach-omap2/Makefile
On Wed, Sep 05, 2012 at 05:06:04PM +0530, Sourav Poddar wrote:
+static struct regmap_config smsc_regmap_config = {
+ .reg_bits = 8,
+ .val_bits = 8,
+ .max_register = SMSC_MAX_REGISTER - 1;
That max_register setup looks very odd...
+
87 matches
Mail list logo
