Hi,
I am not able to mount a filesyatem via NFS on OMAP4 SDP with the
current linux-next kernel. The same thing works fine with OMAP3 SDP.
Some more info:
- initramfs works fine with OMAP4 SDP.
- NFS mount on OMAP4 SDP works fine with mainline kernel.
- Logs below (No output on console after
On Tue, Jul 24, 2012 at 01:22:49, Thierry Reding wrote:
On Mon, Jul 23, 2012 at 03:05:26PM +, Philip, Avinash wrote:
On Mon, Jul 23, 2012 at 18:38:25, Thierry Reding wrote:
On Mon, Jul 23, 2012 at 12:51:11PM +, Philip, Avinash wrote:
On Mon, Jul 23, 2012 at 14:00:32, Thierry
Add device tree data for tps65910 regulator by adding all tps65910
regulator nodes. Regulator is initialized based on compatible name
provided in tps65910 DT file.
All tps65910 PMIC regulator device tree nodes are placed in a
separate device tree include file (tps65910.dtsi). This patch
was
This patch series add AM33XX regulators (tps65910/tps65217) device
tree data to am335x-evm and am335x-bone dts files. These patches
are based on Tony L devel-dt tree and tested on AM335x EVM and
Bone devices.
Changes from v1:
- Incorporated all Mark Brown's review comments on v1 by
Add tps65217 regulator device tree data to AM335x-Bone by adding
regulator consumers with tightened constraints and regulator-name.
TPS65217 regulator handle can be obtained by using this regulator
name.
This patch also add I2C node with I2C frequency and tps65217 PMIC
I2C slave address.
Add device tree data for tps65217 regulator by adding all tps65217
regulator nodes. Regulator is initialized based on compatible name
provided in tps65217 DT file.
All tps65217 PMIC regulator device tree nodes are placed in a
separate device tree include file (tps65217.dtsi). This patch
was
Add tps65910 regulator device tree data to AM335x-EVM by adding
regulator consumers with tightened constraints and regulator-name.
TPS65910 regulator handle can be obtained by using this regulator
name.
This patch also add I2C node with I2C frequency and tps65910 PMIC
I2C slave address.
Hi,
Comparing with working logs, I see this difference:
[1.502166] spi spi1.0: no RX DMA engine channel for McSPI
[1.507904] omap2_mcspi omap2_mcspi.1: can't setup spi1.0, status -11
[1.514862] omap2_mcspi omap2_mcspi.1: can't create new device for ks8851
I guess that's why it
On Tue, 2012-07-24 at 11:30 +1000, NeilBrown wrote:
On Mon, 23 Jul 2012 17:24:54 +0300 Tero Kristo t-kri...@ti.com wrote:
Hi Neil,
On Mon, 2012-07-23 at 21:06 +1000, NeilBrown wrote:
My GTA04 (mobile phone using OMAP3 and TWL4030 PMIC) has difficulty
rebooting
with 3.5.
The
On Mon, Jul 23, 2012 at 10:15:07PM +0200, Lars-Peter Clausen wrote:
On 07/23/2012 10:30 AM, Thierry Reding wrote:
On Wed, Jul 18, 2012 at 06:24:13PM +0530, Philip, Avinash wrote:
[...]
diff --git a/include/linux/pwm.h b/include/linux/pwm.h
index 21d076c..2e4e960 100644
---
On Tue, Jul 24, 2012 at 11:48 AM, Archit Taneja a0393...@ti.com wrote:
Hi,
Comparing with working logs, I see this difference:
[1.502166] spi spi1.0: no RX DMA engine channel for McSPI
[1.507904] omap2_mcspi omap2_mcspi.1: can't setup spi1.0, status -11
[1.514862] omap2_mcspi
On Tuesday 24 July 2012 12:23 PM, S, Venkatraman wrote:
On Tue, Jul 24, 2012 at 11:48 AM, Archit Taneja a0393...@ti.com wrote:
Hi,
Comparing with working logs, I see this difference:
[1.502166] spi spi1.0: no RX DMA engine channel for McSPI
[1.507904] omap2_mcspi omap2_mcspi.1: can't
On Monday 23 July 2012, Stephen Warren wrote:
3. A device with three channels, one of which has two alternatives:
s/three/four/ s/one of which/both of which/
This binding doc seems reasonable to me.
I asked a linguist about it who said that you can't have both together
with four. She
On Tue, 24 Jul 2012 09:28:24 +0300 Tero Kristo t-kri...@ti.com wrote:
On Tue, 2012-07-24 at 11:30 +1000, NeilBrown wrote:
Might there be some way to get it to scale higher than 600MHz?
The first message from U-boot says:
OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
On Mon, Jul 23, 2012 at 19:07:04, Thierry Reding wrote:
On Mon, Jul 23, 2012 at 12:44:38PM +, Philip, Avinash wrote:
On Mon, Jul 23, 2012 at 14:52:04, Thierry Reding wrote:
On Mon, Jul 23, 2012 at 09:10:09AM +, Philip, Avinash wrote:
On Mon, Jul 23, 2012 at 12:22:35, Thierry
On Tue, Jul 24, 2012 at 07:52:06AM +, Philip, Avinash wrote:
On Mon, Jul 23, 2012 at 19:07:04, Thierry Reding wrote:
On Mon, Jul 23, 2012 at 12:44:38PM +, Philip, Avinash wrote:
On Mon, Jul 23, 2012 at 14:52:04, Thierry Reding wrote:
On Mon, Jul 23, 2012 at 09:10:09AM +,
* Paul Walmsley p...@pwsan.com [120719 12:17]:
On Thu, 19 Jul 2012, Tony Lindgren wrote:
Well I'm still a bit confused :)
Which branch in arm-soc tree should this fix be applied then?
In terms of arm-soc, it's needed in arm-soc for-next, due to commit
On 07/24/2012 08:51 AM, Thierry Reding wrote:
How about the following?
/**
* enum pwm_polarity - polarity of a PWM signal
* @PWM_POLARITY_NORMAL: a high signal for the duration of the duty-
* cycle, followed by a low signal for the remainder of the pulse
* period
*
On Tue, Jul 24, 2012 at 10:25:17AM +0200, Lars-Peter Clausen wrote:
On 07/24/2012 08:51 AM, Thierry Reding wrote:
How about the following?
/**
* enum pwm_polarity - polarity of a PWM signal
* @PWM_POLARITY_NORMAL: a high signal for the duration of the duty-
* cycle, followed
* AnilKumar Ch anilku...@ti.com [120720 00:36]:
Adds GPIO pinctrl nodes to am3358_pinmux master node to control
user leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
arch/arm/boot/dts/am335x-bone.dts | 15 +++
1 files
* AnilKumar Ch anilku...@ti.com [120720 00:36]:
Add basic pinctrl support for AM33XX family of devices by adding DT
data to am33xx dtsi file. These patches are based on pinctrl-single
driver and tested on am335x-evm am335x-bone devices.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
On Tue, Jul 24, 2012 at 13:37:24, Thierry Reding wrote:
On Tue, Jul 24, 2012 at 07:52:06AM +, Philip, Avinash wrote:
On Mon, Jul 23, 2012 at 19:07:04, Thierry Reding wrote:
On Mon, Jul 23, 2012 at 12:44:38PM +, Philip, Avinash wrote:
On Mon, Jul 23, 2012 at 14:52:04, Thierry
On Tue, Jul 24, 2012 at 13:56:24, Thierry Reding wrote:
On Tue, Jul 24, 2012 at 10:25:17AM +0200, Lars-Peter Clausen wrote:
On 07/24/2012 08:51 AM, Thierry Reding wrote:
How about the following?
/**
* enum pwm_polarity - polarity of a PWM signal
* @PWM_POLARITY_NORMAL: a
The commit 9c17d08 [mmc: omap_hsmmc: ensure probe returns error upon
resource failure] introduced the below warning.
CC drivers/of/of_net.o
drivers/mmc/host/omap_hsmmc.c: In function 'omap_hsmmc_probe':
drivers/mmc/host/omap_hsmmc.c:1936: warning: statement with no effect
Fix the same by
On Tue, Jul 24, 2012 at 08:36:08AM +, Philip, Avinash wrote:
On Tue, Jul 24, 2012 at 13:37:24, Thierry Reding wrote:
On Tue, Jul 24, 2012 at 07:52:06AM +, Philip, Avinash wrote:
On Mon, Jul 23, 2012 at 19:07:04, Thierry Reding wrote:
On Mon, Jul 23, 2012 at 12:44:38PM +,
On Tue, 2012-07-24 at 17:34 +1000, NeilBrown wrote:
On Tue, 24 Jul 2012 09:28:24 +0300 Tero Kristo t-kri...@ti.com wrote:
On Tue, 2012-07-24 at 11:30 +1000, NeilBrown wrote:
Might there be some way to get it to scale higher than 600MHz?
The first message from U-boot says:
that platform_device is only registered by
board-h4.c, so there's no need to check which
machine is running as the driver won't bind
to anything.
Signed-off-by: Felipe Balbi ba...@ti.com
---
arch/arm/plat-omap/debug-leds.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git
there's no problem in registering debug-leds on
module_init() as that's not critical to board
boot up.
Signed-off-by: Felipe Balbi ba...@ti.com
---
arch/arm/plat-omap/debug-leds.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/plat-omap/debug-leds.c
Hi Tony,
here are a few changes for the debug-leds driver. This series tries to get the
driver closer to be moved away from arch/arm/plat-omap/ and under drivers/leds.
There's only the dependency with plat/fpga.h now.
I tried moving the needed definitions into the C file, but there's another
put our probe function on __devinit section, so
it can be freed on some cases.
Signed-off-by: Felipe Balbi ba...@ti.com
---
arch/arm/plat-omap/debug-leds.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/plat-omap/debug-leds.c b/arch/arm/plat-omap/debug-leds.c
while at that, also convert to module_platform_driver
Signed-off-by: Felipe Balbi ba...@ti.com
---
arch/arm/plat-omap/debug-leds.c | 25 -
1 file changed, 20 insertions(+), 5 deletions(-)
diff --git a/arch/arm/plat-omap/debug-leds.c b/arch/arm/plat-omap/debug-leds.c
instead of hardcoding the address space size, we
can calculate it using resource_size() helper.
Signed-off-by: Felipe Balbi ba...@ti.com
---
arch/arm/plat-omap/debug-leds.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/plat-omap/debug-leds.c
On Tue, Jul 24, 2012 at 14:02:04, Tony Lindgren wrote:
* AnilKumar Ch anilku...@ti.com [120720 00:36]:
Add basic pinctrl support for AM33XX family of devices by adding DT
data to am33xx dtsi file. These patches are based on pinctrl-single
driver and tested on am335x-evm am335x-bone
Hi Tony,
Thanks for the review.
On Tue, Jul 24, 2012 at 14:00:08, Tony Lindgren wrote:
* AnilKumar Ch anilku...@ti.com [120720 00:36]:
Adds GPIO pinctrl nodes to am3358_pinmux master node to control
user leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
Signed-off-by: AnilKumar
Hello.
On 24-07-2012 1:29, Stephen Warren wrote:
I think we're basically on the same page. Let's see if I have covered
all the cases we discussed so far. I've tried to update the binding that
Jon sent out initially with everything we've discussed, so please review
this to see if I understood
We have no reason to block in the error handler workqueue, so use msleep.
Signed-off-by: Jassi Brar jaswinder.si...@linaro.org
---
drivers/video/omap2/dss/dispc.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/omap2/dss/dispc.c
On Monday 23 July 2012, Uwe Kleine-König wrote:
this is the 2nd version of this series whose goal is to make struct
of_device_id.data const. Conceptually a driver must not modify the data
contained there so making it const is the right thing.
v1 of this series was sent with Message-id:
Hi,
On Mon, 2012-07-23 at 09:08 +0200, Yegor Yefremov wrote:
After getting MMC working I now have following issues: both musb and EHCI
make problems.
musb:
musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
musb-am35x musb-am35x: failed to get clock
musb-am35x: probe of musb-am35x
Adds pinctrl support to AM33XX family of devices. These patches were
tested on AM335x-Bone and AM335x-EVM
Changes from v2:
- user led pinmux comments updated according to Tony's
comment.
Changes from v1:
- Rebased the patches based on latest pinctrl-single driver
Adds GPIO pinctrl nodes to am3358_pinmux master node to control
user leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
arch/arm/boot/dts/am335x-bone.dts | 15 +++
1 file changed, 15 insertions(+)
diff --git
Adds basic pinctrl support for AM33XX family of devices. This patch
is based on the pinctrl-simple driver submitted by Tony Lindgren's
here: http://lwn.net/Articles/496075/
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi |9 +
1 file changed, 9
On 07/24/2012 01:19 AM, Arnd Bergmann wrote:
On Monday 23 July 2012, Stephen Warren wrote:
3. A device with three channels, one of which has two alternatives:
s/three/four/ s/one of which/both of which/
This binding doc seems reasonable to me.
I asked a linguist about it who said that
Currently this flag is not used anywhere and may be safely removed.
Signed-off-by: Ruslan Bilovol ruslan.bilo...@ti.com
---
arch/arm/mach-omap2/usb-host.c|1 -
arch/arm/plat-omap/include/plat/usb.h |4
2 files changed, 0 insertions(+), 5 deletions(-)
diff --git
Hi Vinod,
On 07/20/2012 04:37 AM, Vinod Koul wrote:
On Fri, 2012-07-20 at 08:39 +, Arnd Bergmann wrote:
On Friday 20 July 2012, Vinod Koul wrote:
Required property:
dmas: list of one or more dma specifiers, each consisting of
- phandle pointing to dma controller node
-
Hi,
using barebox to boot 3.5 kernel with device tree for pandaboard (A2)
stuck after some seconds. Any ideas?
Log:
bootm -o /boot/omap4-panda.dtb /boot/uImage
Image Name: Linux-3.5.0-01676-g84de33d-dirty
OS: Linux
Architecture: ARM
Type: Kernel Image
On Tuesday 24 July 2012, Stephen Warren wrote:
It seems that given there are two values for dma-names, there really are
two channels; it's just that one channel is bi-directional, and the
second has two alternatives.
Still, I guess you could also view this as three separate channels
On Tuesday 24 July 2012, Jon Hunter wrote:
Ok. The thought was that the user would have the following means of
requesting a channel ...
1. By name
2. By a filter parameter (flags)
3. By name and a filter parameter
So we would have the following APIs ...
struct dma_chan
On Tue, 24 Jul 2012, Tony Lindgren wrote:
OK looks like Linus fixed up part of it, care to check what's needed
against current mainline now?
Current mainline seems to be okay here.
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
Tero,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Tero Kristo
Sent: Friday, July 13, 2012 9:20 AM
To: linux-omap@vger.kernel.org; p...@pwsan.com; khil...@ti.com
Cc: linux-arm-ker...@lists.infradead.org
Subject:
49 matches
Mail list logo
