is disabled. Enable Pull up on sdmmc5_clk to detect SDIO
>> card.
> Cool, does this fix the issue with the WLAN not coming up after a warm reset
> on panda?
>
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
for clock binding
v3:
- Rebased on top of 3.13-rc7
cheers,
-roger
Roger Quadros (5):
mfd: omap-usb-host: Update DT clock binding information
ARM: dts: OMAP5: Add 60MHz clock reference to USB Host module
ARM: dts: omap4-panda: Provide USB PHY clock
ARM: dts: omap5-uevm: Provide USB PHY c
with
device tree boots on Panda and uEVM.
Looks like this one got missed out.
Could it be because you promised to resend it (see [1]). I was upgrading
our test stuff to 3.11-rc1 and made a DT appended image. Boot went fine,
but no USB/ethernet. Should I pickup all four patches?
Regards,
Arend
* Santosh Shilimkar [140513 07:40]:
> On OMAP4 panda board, there have been several bug reports about boot
> hang and lock-ups with CPU_IDLE enabled. The root cause of the issue
> is missing interrupts while in idle state. Commit cb7094e8 {cpuidle / omap4 :
> use CPUIDLE_FLAG_TIM
t support self-hosted debug.
> Pandaboard (A9) is one such hardware and Dietmar's orginial
> patch did mention this issue.
> Without that check on Panda with CPUIDLE enabled, a flood of
> below messages thrown.
>
> [ 3.597930] hw-breakpoint: CPU 0 failed to disable vector
local
> testing here.
I reviewed and tested v2 of this (Rajendra forgot to add the tags in
v3) and also just sanity tested v3 of this on 4430/panda DT boot to
verify the console issue is resolved. Feel free to add:
Reviewed-by: Kevin Hilman
Tested-by: Kevin Hilman # OMAP4/Panda
Kevin
--
To
e following changes since commit e4aa937ec75df0eea0bee03bffa3303ad36c986b:
> Linus Torvalds (1):
> Linux 3.10-rc3
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
> dts-fixes-for-3.10
>
> Kevin Hilman (1):
>
gt; Build: uImage+dtb:
> Pass (13/13): omap2plus_defconfig_am33xx_only/am335x-bone,
> omap2plus_defconfig/omap4-panda,
> omap2plus_defconfig/omap4-panda-es,
> omap2plus_defconfig/omap4-var-som,
>
/off)
- am335x-bone: boot
- am335x-boneblack: boot
- dra7xx-evm: boot
- omap5-uevm: boot
- omap4-panda: boot
- omap4-panda-es: boot, suspend/resume (ret)
- omap2430-sdp: boot
- omap3430-sdp: boot
- omap4430-sdp-es23plus: boot
Test branch location:
tree: https://github.com/t-kristo/linux-pm.git
On Sun, Nov 1, 2015 at 11:23 PM, Guenter Roeck wrote:
> On 11/01/2015 03:11 PM, Peter Robinson wrote:
>>
>> Hi Lars,
>>
>> I'm seeing the following crash in omap_wdt in omap_wdt_get_timeleft
>> when I just run wdctl on a couple of different TI devices, the
OMAP4 and OMAP3
SDPs. Same observation with Panda
With omap3_defconfig, MMC while mounting the rootfs over MMC, the
boot hangs. Same observation with Panda
[5.794616] regulator_init_complete: incomplete constraints, leaving VUSIM on
[5.802764] regulator_init_complete: incomplete constraints
g when the
> > > > board's kernel boots up.
> > > >
> > > > I've attached the configs I have tried.
> > >
> > > try this patch:
> > >
> > > commit d5f42190e7cf11b20face63ee96f26c7d2067b63
> > > Author: Ming L
P3: http://paste.pocoo.org/show/352960/)
>
> I'm currently traveling for this week so I have quite limited ability to
> test this. Mythri still haven't been able to reproduce any of these
> errors, right?
>
That's right i have not been able to reproduce the error. I h
On Thursday 24 March 2011, Andy Green wrote:
> The following series solves a problem Panda suffers from where
> because there is no local MAC address storage on the board, a
> new random MAC address is applied to the onboard Ethernet
> interface each time, and the wl12xx module'
Hi Manju,
Few "minor" comments about your subjects in this series.
Patch series reworked from:
http://permalink.gmane.org/gmane.linux.ports.arm.omap/61674
Also added support for i2c1 controller on omap4 based panda
board.
Baseline:
=
git://git.secretlab.ca/git/linux-2.6.
truct platform_device *dsidev, bool
enable_hsclk,
vdds_dsi = regulator_get(&dsi->pdev->dev, "vdds_dsi");
+ /* DT HACK: try VCXIO to make omapdss work for o4 sdp/panda */
+ if (IS_ERR(vdds_dsi))
+ vdds_dsi = regulator_ge
PRM/CM clean-up work. It is a
> > refresh of the patches Rajendra sent out a while back[1], with the
> > addition of several fixes for PM regressions[2] across several
> > platforms.
> >
> > I have tested on OMAP4430 Panda including PRCM diffing against pre-CCF
> &g
is to have it usable with DT. And USB and
>> Ethernet certainly are part of what I call usable. So is MMC, WLAN and
>> DSS. I've certainly spent quite a bit of time on making sure panda works
>> with DT, and I can assure you that fixing the USB extclock is easier than
>
gt; >> > have any network because it was easier to maintain, is not something
>> >> > they will understand imho.
>> >>
>> >> Right, like I said: the idea is to have it usable with DT. And USB and
>> >> Ethernet certainly are pa
From: Mythri P K
Disables the internal pull resistor for SDA and SCL which are enabled by
default, as there are expernal pull up's in 4460 and 4430 ES2.3
SDP, Blaze and Panda Boards, It is done to avoid the EDID read failure.
Signed-off-by: Ricardo Salveti de Araujo
Signed-off-by: Mythr
From: Mythri P K
Disables the internal pull resistor for SDA and SCL which are enabled by
default, as there are expernal pull up's in 4460 and 4430 ES2.3
SDP, Blaze and Panda Boards, It is done to avoid the EDID read failure.
Signed-off-by: Ricardo Salveti de Araujo
Signed-off-by: Mythr
we provide the same for struct clk. These stock callbacks
mean there won't be any code duplication caused in the common case.
Fourth we remove all the struct regulator code from ehci-omap.
Fifth we implement Panda HUB+ETH (smsc95xx chip) regulator control
using the device_asset scheme. Sin
From: G, Manjunath Kondaiah
The generic board file is created and derived from omap4 panda board file.
The changes here focus on minimal configuration to boot panda board with
dt enabled which provides basic platform for converting device drivers for
using dt.
Signed-off-by: G, Manjunath
On Tue, Aug 23, 2011 at 03:05:01PM +0200, Cousson, Benoit wrote:
> From: G, Manjunath Kondaiah
> >The generic board file is created and derived from omap4 panda board file.
> >
> >The changes here focus on minimal configuration to boot panda board with
> >dt enabled wh
/pastebin.com/qwJHw9Ev (no DT)
> omap3-beagle-xm -OMAP3630 compatible - http://pastebin.com/tVEXeVZC
> Pandaboard -(OMAP4430 ES2.2) verified with omapconf -
> http://pastebin.com/cAtytfW0
> Pandaboard-ES -(OMAP4460 ES1.1) verified with omapconf -
> http://pastebin.c
+Viresh and linux-pm
On 12/16/2014 10:59 AM, Kevin Hilman wrote:
> FYI... New boot failures in today's linux-next for omap4-panda-es and
> omap5-uevm:
>
>http://status.armcloud.us/boot/?lab-khilman&fail&omap
http://storage.armcloud.us/kernel-ci/next/next-20141216/a
ed DTB support in .config
>>>>>>>>
>>>>>>>>CONFIG_ARM_APPENDED_DTB=y
>>>>>>>>CONFIG_ARM_ATAG_DTB_COMPAT=y
>>>>>>>>CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND=y
>>>>>>>>
>>&g
+-
arch/arm/boot/dts/omap3.dtsi |1 +
arch/arm/boot/dts/omap4-panda-a4.dts |6 +-
arch/arm/boot/dts/omap4-panda-common.dtsi | 50
arch/arm/boot/dts/omap4-panda-es.dts |6 +-
arch/arm/boot/dts/omap4-sdp-es23plus.dts |6 +-
arch/arm/boot
-igep.dtsi | 32 +-
arch/arm/boot/dts/omap3.dtsi |1 +
arch/arm/boot/dts/omap4-panda-a4.dts |6 +-
arch/arm/boot/dts/omap4-panda-common.dtsi | 50
arch/arm/boot/dts/omap4-panda-es.dts |6 +-
arch/arm/boot/dts/omap4-sdp
arch/arm/boot/dts/omap3-igep.dtsi | 34 +-
arch/arm/boot/dts/omap3.dtsi |1 +
arch/arm/boot/dts/omap4-panda-a4.dts |6 +-
arch/arm/boot/dts/omap4-panda-common.dtsi | 54
arch/arm/boot/dts/omap4-panda-es.dts |6 +-
arch/arm
rg/raw/s20ty0Z6i5 (not
>>>> expected)
>>>> 19: pandaboard-vanilla: Boot FAIL: http://slexy.org/raw/s20BYfaMd2 (not
>>>> expected)
>>>
>>> If I read the log correctly, the serial port stops responding after a while?
>>
>> yeah - dug at t
routing of GIC to
> >>>> UART2 and not via WUGEN
> >>>> IRQ branch: with my fix applied:
> >>>> -
> >>>
> >>> [...]
> >>>
> >>>> 18: pandaboard-es: Boot FAIL: http://slexy.org
OMAP3_CORE1_IOPAD pinmux macro
> ARM: dts: omap3-n900: Use OMAP3_CORE1_IOPAD pinmux macro
> ARM: dts: omap3-n9: Use OMAP3_CORE1_IOPAD pinmux macro
> ARM: dts: omap3-zoom3: Use OMAP3_*_IOPAD pinmux macros
> ARM: dts: twl4030: Use OMAP3_CORE1_IOPAD pinmux macro
> ARM: dts:
cro
ARM: dts: omap3-n900: Use OMAP3_CORE1_IOPAD pinmux macro
ARM: dts: omap3-n9: Use OMAP3_CORE1_IOPAD pinmux macro
ARM: dts: omap3-zoom3: Use OMAP3_*_IOPAD pinmux macros
ARM: dts: twl4030: Use OMAP3_CORE1_IOPAD pinmux macro
ARM: dts: omap4-panda-a4: Use OMAP4_IOPAD pinmux macro
ARM: d
for l-o master branch, I think this
should probably be squashed to:
commit ec787afd05aad0cdb0b0d2948b356569805e5b30
Author: Felipe Balbi
Date: Wed Dec 1 13:48:54 2010 +0200
arm: omap4: panda: initialize musb
initialize the musb port on pandaboard.
Signed-off-by: Felipe Balbi
On Tue, Jan 04, 2011 at 04:29:04PM -0800, Kevin Hilman wrote:
> tom.leim...@gmail.com writes:
>
> > From: Ming Lei
> >
> > Panda uses twl6030 otg phy instead of internal phy,
This is wrong, it uses both. TWL6030 handles VBUS and ID pin
and the internal PHY handles Data
From: Panduranga Mallireddy
Add board muxing to support the wlan wl1271 chip that is
hardwired to mmc5 (fifth mmc controller) on the PANDA.
Based on the wlan board muxing for zoom3 by Ohad Ben-Cohen
Signed-off-by: Panduranga Mallireddy
---
arch/arm/mach-omap2/board-omap4panda.c | 13
nitramfs) and the shell
>> prompt works OK.
>>
>> Board details: Panda A1, OMAP4430 ES2
>> Kernel details: l-o tree master, using the omap2plus_defconfig +
>> initramfs. WDOG is enabled in the config.
>>
>> From some investigation I can see that PM runtime d
Add board muxing to support the wlan wl1271 chip that is
hardwired to mmc5 (fifth mmc controller) on the PANDA.
Based on the wlan board muxing for zoom3 by Ohad Ben-Cohen
Signed-off-by: Panduranga Mallireddy
---
arch/arm/mach-omap2/board-omap4panda.c | 13 +
1 files changed, 13
e = &sdp4430_hdmi_device,
>> +};
>> +
>> +void omap_panda_display_init(void)
Using omap4_panda_display_init would be a good option as most of the
other init in this file are using omap4 not omap
>> +{
>> +sdp4430_hdmi_mux_init();
>> +omap_display_ini
custom cook the
whole userland thing per-device, but it ain't so from a generic rootfs
perspective.
Why should Ubuntu, Fedora etc stink up their OSes with Panda-specific
workarounds? And Panda is not the only device with this issue.
-Andy
--
To unsubscribe from this list: send the
#x27;s working for somebody!
> What is your kernel commit ID that you applied the patches on top of?
7cf543bc ("Linux-omap rebuilt: Updated to -rc6, merged in pending branches,
please test"). Is there something else I need too?
> What board are you using? Blaze, panda, etc, and i
On Tue, 2012-05-29 at 14:30 -0700, Kevin Hilman wrote:
> Tero Kristo writes:
>
> > Current I2C timing parameters do not work with Panda board at least.
> > Parameters updated based on TI recommendation.
> >
> > Signed-off-by: Tero Kristo
>
> Let's f
Add DT support for dmic, and McPDM on OMAP4 platforms.
Panda board does not have DMIC lines accessable, so
disable the dmic on panda.
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/omap4-panda.dts |4
arch/arm/boot/dts/omap4.dtsi |9 +
2 files changed, 13
driver
> - Based on the board type the driver selects different audio routings
> - Registration of the needed platform devices in board files (sdp4403, panda)
>
> After this series the sound card names will be different for easier UCM
> integration:
> "OMAP4-SDP4430" fo
to
> > read the first byte, as that's "00". Everything after that are 'XX'es.
>
> Hmm I suggest git bisect, I'm pretty sure I was using my panda es
> with my omap4 DT conversion patches against v3.10-rc1.
As I mentioned, it doesn't work on v3.10-rc1 e
On Thu, Jun 13, 2013 at 7:05 PM, Tony Lindgren wrote:
> * Sricharan R [130613 03:18]:
>> >
>> > I tried your cleanup branch omap-for-v3.11/cleanup on panda board and it
>> > booted
>> > to prompt fine.
>> > Hardware: Pandaboard A1
, USB Host & Ethernet will not be functional with
device tree boots on Panda and uEVM.
Looks like this one got missed out.
Could it be because you promised to resend it (see [1]). I was upgrading
our test stuff to 3.11-rc1 and made a DT appended image. Boot went fine,
but no USB/ethernet. Shou
On Friday 16 May 2014 03:41 AM, Alex Shi wrote:
> On 05/16/2014 02:36 AM, Santosh Shilimkar wrote:
>>>>>> yes.
>>>>>> My board is panda ES. without this revert, it works.
>>>>
>>>> Care to specify what linux version you are testin
On Thu, May 16, 2013 at 10:35 AM, Dan Murphy wrote:
> I am not sure you really want to do this.
> If I make the pinctrl part of the led structure then the only way the
> gpio_wk7 on a1-a3 to be configured is when
> the CONFIG_LEDS_GPIO flag is set.
>
> Do you really want that dependency? You did
30/Overo, 3730/Overo-STORM, 4430/Panda,
> 4460/Panda-ES.
>
> Cc: Tony Lindgren
> Signed-off-by: Kevin Hilman
Totally agree:
Acked-by: Tony Lindgren
> ---
> drivers/mfd/twl-core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/
patc...@linaro.org; nicolas.pi...@linaro.org;
>a...@arndb.de; x0132...@ti.com; s-...@ti.com;
>t...@atomide.com; Alan Cox; Andy Green
>Subject: [RFC PATCH 2/2] OMAP2+: PANDA: Fix up random or
>missing MAC addresses for eth0 and wlan0
>
>This patch registers a network device notifier callba
On 07/18/2013 02:24 PM, Arend van Spriel wrote:
> On 07/18/2013 01:18 PM, Roger Quadros wrote:
>> Hi Arend,
>>
>> On 07/18/2013 11:41 AM, Arend van Spriel wrote:
>>> Hi Tony,
>>>
>>>
>>> We are using the panda board (es variant) for testi
that reading, and the fact that not correctly muxing that pad
to mode 2 on *both* 4430 and 4460 makes the RTC work, I'm rather
convinced that the offset should be the same for 4430 and 4460.
What am I missing?
Hi Kevin,
I've rechecked it too.
According to:
Panda ES:
http://pandaboard.
FYI... New boot failures in today's linux-next for omap4-panda-es and
omap5-uevm:
http://status.armcloud.us/boot/?lab-khilman&fail&omap
The omap3-beagle-xm one has been fixed by Tero, but the fix hasn't hit
-next yet. I haven't had a chance to bisect these yet.
Kevin
b21
>>> (omap: Adding beagle i2c eeprom driver to read EDID)
>>>
>>> Reviewed-by: Manjunath G Kondaiah
>>> Reviewed-by: Anand Gadiyar
>>
>> I've also tested it on the Panda, and gone through this and most
>> of the other patches in the
ould have been better.
Understood. Live and learn and try not to repeat the same mistakes.
Hopefully others pick up on this one.
>
>> The use of the OMAP die id below makes this OMAP specific and the list
>> referenced below of the devices to be referenced makes it Panda
>
tely those
two patches doesn't help in our case. I tested the driver with 3.5-rc3
mainline kernel and the issue is still there. I can only "fix" the
hang by either reverting the commit or disabling
CONFIG_PM_RUNTIME. Also, the hang only happens on Panda ES board. Old
Panda with 4430
based on for_3.2/2_omap_device_dt + devicetree/test
and are available here:
git://gitorious.org/omap-pm/linux.git for_3.2/3_omap4_dt_base
Thanks to your latest hack, for people who want to play with appended dtb:
make uImage-dtb.omap4-panda
make uImage-dtb.omap4-sdp
Comments are welcome.
Regards
lizer
> arch/arm/mach-omap2/board-omap4panda.c:287: warning: large integer implicitly
> truncated to unsigned type
Yes, I have also noticed it.
This is because part of the twl6040 i2c conversion series has been taken
by Samuel.
He will stop carrying it further (I hope), and we are going to
tunately) are not upstream (or which are upstream
>>> but without the wl12xx-specific definitions on it, such as Beagle).
>>>
>> i preferred adding this capability only for boards i can test.
>> unfortunately, i don't a panda/beagle setup.
>> anyway, i don&#x
PandaBoard has twl6040 codec for audio.
Register the omap4-abe-twl6040 platform device.
Add platform data to enable the twl6040 codec.
Since there is a difference in audio between PandaBoard 4430
and PandaBoard ES (4460):
Use different name for the sound card:
"OMAP4-Panda" for Panda
PandaBoard has twl6040 codec for audio.
Register the omap4-abe-twl6040 platform device.
Add platform data to enable the twl6040 codec.
Since there is a difference in audio between PandaBoard 4430
and PandaBoard ES (4460):
Use different name for the sound card:
"OMAP4-Panda" for Panda
the functional pwrst code
> - added patch #8 for fixing a regression with MUSB PHY power handling
> (not quite sure if this is the correct way to fix this or not)
>
> Tested with omap4460 gp panda + omap4430 emu blaze boards, with cpuidle +
> suspend.
>
> Branch also available h
As a temporary solution to enable DSS for selected boards when booting
with DT, a hack was added to board-generic.c in
63d5fc0c2f748e20f38a0a0ec1c8494bddf5c288 (OMAP: board-generic: enable
DSS for panda & sdp boards).
We're now adding proper DT support, so the hack can be removed.
Sign
;t support self-hosted debug.
Pandaboard (A9) is one such hardware and Dietmar's orginial
patch did mention this issue.
Without that check on Panda with CPUIDLE enabled, a flood of
below messages thrown.
[ 3.597930] hw-breakpoint: CPU 0 failed to disable vector catch
[ 3.597991] hw-breakpoint: CPU
Add initial support for the OMAP4 based Panda Board.
Signed-off-by: David Anders
---
arch/arm/mach-omap2/Kconfig|4 +
arch/arm/mach-omap2/Makefile |2 +
arch/arm/mach-omap2/board-omap4panda.c | 305
3 files changed, 311 insertions
On 06/26/2012 12:21 AM, DebBarma, Tarun Kanti wrote:
On Tue, Jun 26, 2012 at 2:22 AM, Franky Lin wrote:
Hi Kevin, Tarun,
We are using the expansion connector A on Panda board to mount a SDIO WiFi
dongle on MMC2 with a level triggered interrupt signal connected to GPIO
138. It's been wo
ged in
> the -rc series, so that we get EHCI and ethernet functional on the Panda.
>
> Ming Lei,
>
> Could you please test this and confirm it fixes the issue for you?
Yes, the patch does fix the issue on my panda board even
CONFIG_OMAP_RESET_CLOCKS is enabled.
thanks,
--
Lei Ming
--
'nosmp' on the kernel
>> > command line?
>>
>> Yeah, I think so, since Sebastien reported that 'nosmp' doesn't work either.
>
> Will try to find time to give this a shot. You might want to try a build
> without CONFIG_SMP set to see if it helps.
>
On Thursday 24 March 2011, Andy Green wrote:
> Introduce a generic helper function that can set a MAC address using
> data from the OMAP unique CPU ID register.
>
> For comparison purposes this produces a MAC address of
>
> 2e:40:70:f0:12:06
>
> for the eth
On Tue, 2012-07-10 at 20:58 +0800, "Andy Green (林安廸)" wrote:
> On 10/07/12 20:37, the mail apparently from Florian Fainelli included:
>
> Why should Ubuntu, Fedora etc stink up their OSes with Panda-specific
> workarounds? And Panda is not the only device with this issue.
'll fold the fixed patch into your original patch. Will also
> > > keep the new board files in testing-board because of the code
> > > coalescing and device tree conversion effort.
> >
> > So there is no way to get the board mainline yet?
>
> Well we can
From: Santosh Shilimkar
HIGMEM support in kernel is quite mature now and we have boards
like ZOOM, PANDA, SDP where 1 GB memories are installed. With
HIGHMEM disabled not all of the 1GB of RAM (only ~700MB) can be
accessed. Hence, enable HIGMEM to make use of the entire memory.
On the boards
o update with the warnings produced?
>
> Ah, sure. Updated patch below:
>
> From e96ddeb7d783d48a15a32f8ef5a7bae3089f66b9 Mon Sep 17 00:00:00 2001
> From: Tomi Valkeinen
> Date: Wed, 28 Mar 2012 11:38:58 +0300
> Subject: [PATCH] OMAP4: panda: add statics to remove warnings
+static struct twl6040_platform_data twl6040_data = {
.codec = &twl6040_codec,
.audpwron_gpio = 127,
- .naudint_irq= OMAP44XX_IRQ_SYS_2N,
.irq_base = TWL6040_CODEC_IRQ_BASE,
};
/* Panda board uses the common PMIC configuration */
-static struct tw
also be communicated more broadly for those board
> files which (unfortunately) are not upstream (or which are upstream
> but without the wl12xx-specific definitions on it, such as Beagle).
>
i preferred adding this capability only for boards i can test.
unfortunately, i don't a panda/b
K, the whole idea of DT is to drop board-*.c. It would be best to see
> the "missing initialization" being added to board-generic/dts files.
Yes I agree, let's rather get board-generic.c to work with panda.
The other board-*.c files will be dropped as soon as we have
things usabl
The port1 of omap4 panda board is used in ULPI PHY mode.
The pin mux of usbhs (usbb1) port 1 is configured accordingly.
Signed-off-by: Keshava Munegowda
---
arch/arm/boot/dts/omap4-panda.dts | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/omap4
The port1 of omap4 panda board is used in ULPI PHY mode.
The pin mux of usbhs (usbb1) port 1 is configured accordingly.
Signed-off-by: Keshava Munegowda
---
arch/arm/boot/dts/omap4-panda.dts | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/omap4
From: Keshava Munegowda
The port1 of omap4 panda board is used in ULPI PHY mode.
The pin mux of usbhs (usbb1) port 1 is configured accordingly.
Signed-off-by: Keshava Munegowda
---
arch/arm/boot/dts/omap4-panda.dts | 18 ++
1 files changed, 18 insertions(+), 0 deletions
t a spin across a handful of OMAP boards using v3.12-rc2 +
these 2 patches.
Boot tested successfully with DT boot:
omap3530/beagle
omap3730/beagle-xm
omap3530/overo (Tobi w/GPIO IRQ networking)
omap3730/overo STORM (w/GPIO IRQ for networking)
am335x/beaglebone
am335x/beaglebone black
omap4430/pan
04b349f).
>>
>> In both cases the device appears to hang shortly before one would expect
>> init to start as seen in the boot output below. I'm booting with the
>> omap4-panda-es devicetree. As far as I can tell, the machine is
>> completely dead and will not res
just looks that way, looking at the curly brackets
thing do get moved properly.
> >> SDIO card is not detected after moving pin mux to omap4_pmx_core since
> >> sdmmc5_clk pull is disabled. Enable Pull up on sdmmc5_clk to detect SDIO
> >> card.
> > Cool, does this
10 line of code (led_wkgpio_pins) further down :-)
SDIO card is not detected after moving pin mux to omap4_pmx_core since
sdmmc5_clk pull is disabled. Enable Pull up on sdmmc5_clk to detect SDIO card.
Cool, does this fix the issue with the WLAN not coming up after a warm reset
on panda?
Regards
Quadros wrote:
>>> With u-boot 2013.10, USB devices are sometimes not detected
>>> on OMAP4 Panda. To make us independent of what bootloader does
>>> with the USB Host module, we must RESET it to get it to a known
>>> good state. This patch Soft RESETs the USB H
* Tomi Valkeinen [131204 02:01]:
> On 2013-12-03 16:25, Roger Quadros wrote:
> > Hi,
> >
> > This is a follow up solution to the original series in [1]
> >
> > The first patch fixes the OMAP4 Panda USB detection problems on 3.13-rc1
> > with u-boot v2013.1
On Tue, Apr 22, 2014 at 02:20:43PM -0400, Santosh Shilimkar wrote:
> On Tuesday 22 April 2014 04:28 AM, Sekhar Nori wrote:
> > This patch series adds L2 cache support for AM437x
> > and does some clean-ups for existing OMAP4 support
> > along the way (no functional cha
Hi,
Nishant pointed me to a booting issue with omap4-panda-es on linux-next but I'm
observing
similar issues, although less frequent, with v3.15-rc4 as well.
Configuration:
- kernel v3.15-rc4 or linux-next (20140507)
- multi_v7_defconfig with LEDS_TRIGGER_HEARTBEAT and LEDS_GPIO enable
On Thu, May 16, 2013 at 3:22 PM, Dan Murphy wrote:
> On 05/16/2013 01:18 PM, Nishanth Menon wrote:
>> On Thu, May 16, 2013 at 10:35 AM, Dan Murphy wrote:
>>> I am not sure you really want to do this.
>>> If I make the pinctrl part of the led structure then the only way the
>>> gpio_wk7 on a1-a3
sc handling from serial driver.
>>
>> These look good to me. Will queue them for v3.10-rc once they pass local
>> testing here.
>
> I reviewed and tested v2 of this (Rajendra forgot to add the tags in
Oops, sorry about that Kevin, and thanks for the repeated reviews
next-20141204 fails to boot, but next-20141203 boots fine with
omap2plus_defconfig.
Panda-ES(4460):
https://github.com/nmenon/kernel-test-logs/blob/next-20141204/omap2plus_defconfig/pandaboard-es.txt
Panda(4430):
https://github.com/nmenon/kernel-test-logs/blob/next-20141204/omap2plus_defconfig
to move to DT
only for OMAP4.
> For omap4 we are only carrying SDP and panda support to
> make this transition easier. The only bindings missing AFAIK are wl12xx and
> USB.
>
> If we add this, then it implies we're somehow supporting it, which is not
> the way to go I
e
>>> two patches doesn't help in our case. I tested the driver with 3.5-rc3
>>> mainline kernel and the issue is still there. I can only "fix" the
>>> hang by either reverting the commit or disabling
>>> CONFIG_PM_RUNTIME. Also, the hang only
From: Andy Green
This provides the board-specific device paths needed to get
the panda boardfile working with the mac-la-ap api.
On Pandaboard / ES, neither the onboard Ethernet or onboard WLAN
module have onboard arrangements for MAC storage, without this
series yielding randomized MAC per
From: Andy Green
This provides the board-specific device paths needed to get
the panda boardfile working with the mac-platform api.
On Pandaboard / ES, neither the onboard Ethernet or onboard WLAN
module have onboard arrangements for MAC storage, without this
series yielding randomized MAC per
From: Andy Green
This provides the board-specific device paths needed to get
the panda boardfile working with the mac-platform api.
On Pandaboard / ES, neither the onboard Ethernet or onboard WLAN
module have onboard arrangements for MAC storage, without this
series yielding randomized MAC per
From: Andy Green
This provides the board-specific device paths needed to get
the panda boardfile working with the eth-mac-platform api.
On Pandaboard / ES, neither the onboard Ethernet or onboard WLAN
module have onboard arrangements for MAC storage, without this
series yielding randomized MAC
> On Friday 08 June 2012 04:26 PM, Tony Lindgren wrote:
>>>>>
>>>>> * Rajendra Nayak [120608 03:40]:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I don;t seem to be able to get suspend to work on 3.5-rc1 on
>&g
e based on v3.11-rc5.
Tested leacy boot on omap3-beagle and omap3-beagle-xm
Tested DT boot on omap3-beagle, omap3-beagle-xm and omap4-panda-es
cheers,
-roger
---
Roger Quadros (9):
usb: phy: nop: Add gpio_reset to platform data
usb: phy: nop: Don't use regulator framework for RESET li
501 - 600 of 2260 matches
Mail list logo
