On 12/21/2011 1:09 AM, Colin Cross wrote:
On some ARM SMP SoCs (OMAP4460, Tegra 2, and probably more), the
cpus cannot be independently powered down, either due to
sequencing restrictions (on Tegra 2, cpu 0 must be the last to
power down), or due to HW bugs (on OMAP4460, a cpu powering up
Hi,
On 21.12.2011 10:07, Hiremath, Vaibhav wrote:
+static struct resource am35xx_mdio_resources[] = {
+{
+.start = AM35XX_IPSS_EMAC_BASE + AM35XX_EMAC_MDIO_OFFSET,
+.end= AM35XX_IPSS_EMAC_BASE + AM35XX_EMAC_MDIO_OFFSET +
+ SZ_4K - 1,
+
Hi Ilya,
On 12/20/11 22:07, Ilya Yanok wrote:
Hi Igor,
+static struct omap2_hsmmc_info mmc[] = {
+ {
+ .mmc= 1,
+ .caps = MMC_CAP_4_BIT_DATA,
+ .gpio_cd= SD_CARD_CD,
+ .gpio_wp= SD_CARD_WP,
+
Hi guys,
i tried cpuhotplug on pandaboard for both
Pandroid_Froyo_L27.8.2_release_pkg and Linaro 11.11. It has failed to
work stably.
On Pandroid_Froyo_L27.8.2_release_pkg, unplugging cpu1 works well:
# echo 0 /sys/devices/system/cpu/cpu1/online
CPU1: shutdown
if i enable the cpu1 again by echo
On Wed, Dec 21, 2011 at 1:02 AM, Arjan van de Ven ar...@linux.intel.com wrote:
On 12/21/2011 1:09 AM, Colin Cross wrote:
On some ARM SMP SoCs (OMAP4460, Tegra 2, and probably more), the
cpus cannot be independently powered down, either due to
sequencing restrictions (on Tegra 2, cpu 0 must be
On 12/21/2011 10:40 AM, Colin Cross wrote:
this smells fundamentally racey to me; you can get an interrupt one
cycle after you think you're done, but before the last guy enters WFI...
how do you solve that issue ?
All the cpus have interrupts off when they increment the counter, so
they
On Wed, Dec 21, 2011 at 05:23:48PM +0800, Barry Song wrote:
Hi guys,
i tried cpuhotplug on pandaboard for both
Pandroid_Froyo_L27.8.2_release_pkg and Linaro 11.11. It has failed to
work stably.
On Pandroid_Froyo_L27.8.2_release_pkg, unplugging cpu1 works well:
# echo 0
-Original Message-
From: Ilya Yanok [mailto:ya...@emcraft.com]
Sent: Wednesday, December 21, 2011 2:45 PM
To: Hiremath, Vaibhav
Cc: linux-omap@vger.kernel.org; sash...@emcraft.com
Subject: Re: [PATCH V2] am35xx-emac: move generic EMAC init to separate
file
Hi,
On 21.12.2011
On Wed, Dec 21, 2011 at 1:44 AM, Arjan van de Ven ar...@linux.intel.com wrote:
On 12/21/2011 10:40 AM, Colin Cross wrote:
this smells fundamentally racey to me; you can get an interrupt one
cycle after you think you're done, but before the last guy enters WFI...
how do you solve that issue ?
2011/12/21 Russell King - ARM Linux li...@arm.linux.org.uk:
On Wed, Dec 21, 2011 at 05:23:48PM +0800, Barry Song wrote:
Hi guys,
i tried cpuhotplug on pandaboard for both
Pandroid_Froyo_L27.8.2_release_pkg and Linaro 11.11. It has failed to
work stably.
On Pandroid_Froyo_L27.8.2_release_pkg,
On Wed, Dec 21, 2011 at 05:59:07PM +0800, Barry Song wrote:
2011/12/21 Russell King - ARM Linux li...@arm.linux.org.uk:
cpu hotplug is basically totally buggered - the preconditions placed
upon the bringup code path are basically impossible to satisfy in any
shape or form at the moment.
Thanks for ur response,
Iam using omap 3430 processor for the custom board, for 32 kernel tty port of
console was ttyO3 only, I have enabled DEBUG_LL also, and I am using putc
function of uncompress.h file to print early prints. Iam suppose to work on the
custom board in which UART address
On 12/21/2011 10:55 AM, Colin Cross wrote:
On Wed, Dec 21, 2011 at 1:44 AM, Arjan van de Ven ar...@linux.intel.com
wrote:
On 12/21/2011 10:40 AM, Colin Cross wrote:
this smells fundamentally racey to me; you can get an interrupt one
cycle after you think you're done, but before the last guy
plit into two parts:
1. Device tree only to be used with board-generic (only serial works)
2. Full board support via custom machine file for board-testing
Ilya Yanok (2):
mcx: very basic support for HTKW mcx board
mcx: support for HTKW mcx board
arch/arm/boot/dts/mcx.dts
Very basic support for HTKW mcx board. Able to boot via board-generic
and ramdisk/initramfs, however most of peripherals is unsupported.
Produces tons of twl4030 related errors as this board doesn't have
twl4030 installed.
Signed-off-by: Ilya Yanok ya...@emcraft.com
---
Changes from V2:
- None
Support for the HTKW mcx board (TI AM3517 based) including serial,
Ethernet, I2C, USB host, HSMMC, DSS and RTC.
Signed-off-by: Ilya Yanok ya...@emcraft.com
---
Requires updated machine-type file, recently posted AM35xx-EMAC patch
and Disable PM init on AM35{05,17} patch.
Changes from V2:
-
Split into two parts:
1. Device tree only to be used with board-generic (only serial works)
2. Full board support via custom machine file for board-testing
Sorry for double-posting: I've put wrong linux-arm-kernel address in
the first post.
Ilya Yanok (2):
mcx: very basic support for HTKW
Support for the HTKW mcx board (TI AM3517 based) including serial,
Ethernet, I2C, USB host, HSMMC, DSS and RTC.
Signed-off-by: Ilya Yanok ya...@emcraft.com
---
Requires updated machine-type file, recently posted AM35xx-EMAC patch
and Disable PM init on AM35{05,17} patch.
Changes from V2:
-
Very basic support for HTKW mcx board. Able to boot via board-generic
and ramdisk/initramfs, however most of peripherals is unsupported.
Produces tons of twl4030 related errors as this board doesn't have
twl4030 installed.
Signed-off-by: Ilya Yanok ya...@emcraft.com
---
Changes from V2:
- None
If platform data is provided by the caller gpio_pendown is put into
unused static ads7846_config structure and effectively has no effect.
Of course caller can set gpio_pendown field in platform data himself
but it seems natural to do this in ads7846_init to remove duplication.
Signed-off-by: Ilya
Hi Ilya,
Please, Cc the linux-arm-ker...@lists.infradead.org for patches,
so Tony, or whoever will not need to resend them...
On 12/21/11 18:31, Ilya Yanok wrote:
If platform data is provided by the caller gpio_pendown is put into
unused static ads7846_config structure and effectively has no
Hi Arnd,
On Mon, Dec 12, 2011 at 1:33 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
On Fri, 9 Dec 2011 16:55:27 +0200 Ohad Ben-Cohen o...@wizery.com wrote:
Can you please add the following remoteproc tree to linux-next ?
git://git.kernel.org/pub/scm/linux/kernel/git/ohad/remoteproc.git
Hi Igor,
On 21.12.2011 21:22, Igor Grinberg wrote:
Please, Cc the linux-arm-ker...@lists.infradead.org for patches,
so Tony, or whoever will not need to resend them...
Uh.. Actually I thought that linux-omap ML is a good place for really
OMAP-specific patches like this one and there is no much
On Wed, 2011-12-14 at 11:46 +0200, Peter Ujfalusi wrote:
Hello,
the following series will add ASoC support for PandaBoards.
PandaBoards have different audio routings compared to SDP4430/Blaze boards,
but
the differences not that big to justify a new ASoC machine driver.
Main changes:
-
On Sun, 2011-12-11 at 21:12 +0100, Janusz Krzysztofik wrote:
Don't use Amstrad Delta custom I/O functions any longer, replace them
with GPIO. Old pin definitions, no longer used by the modem bits either,
can be dropped.
Depends on patch 2/10 ARM: OMAP1: Convert Amstrad E3 latches to
On Wed, Dec 21, 2011 at 4:12 AM, Arjan van de Ven ar...@linux.intel.com wrote:
On 12/21/2011 10:55 AM, Colin Cross wrote:
On Wed, Dec 21, 2011 at 1:44 AM, Arjan van de Ven ar...@linux.intel.com
wrote:
On 12/21/2011 10:40 AM, Colin Cross wrote:
this smells fundamentally racey to me; you can
* Janusz Krzysztofik jkrzy...@tis.icnet.pl [111220 13:23]:
In preparation to converting Amstrad Delta on-board latches to
basic_mmio_gpio devices, registration of platform devices which depend
on latches and will require initialization of their GPIO pins first,
should be moved out of
* Janusz Krzysztofik jkrzy...@tis.icnet.pl [111220 13:39]:
Don't use Amstrad Delta custom I/O functions once GPIO interface is
available for the underlying hardware.
While requesting and initializing GPIO pins used, also take care of one
extra pin KEYBRD_DATAOUT which, even if not used by
* Janusz Krzysztofik jkrzy...@tis.icnet.pl [111219 14:41]:
Don't use Amstrad Delta custom I/O functions for controlling the device,
use GPIO API instead.
While being at it, add missing gpio_free(AMS_DELTA_GPIO_PIN_NAND_RB).
Depends on patch 2/7 ARM: OMAP1: ams-delta: convert latches to
* Cousson, Benoit b-cous...@ti.com [111220 04:48]:
Hi Tony,
What about that patch?
This is the only one that is missing in lo.
I know it is not a big deal, but it will make things a little bit cleaner.
I think we should wait on this one and combine it later on into
some other clean-up
.. or it enters WFI, and a physical device sends it an interrupt,
at which point it exits.
None of the cpus will return to the idle loop until all cpus have
decremented the ready counter back to 0, so they can't wrap around
again.
yikes, so you IPI all the cpus on the first exit.
that
On Wed, Dec 21, 2011 at 11:36 AM, Arjan van de Ven
ar...@linux.intel.com wrote:
.. or it enters WFI, and a physical device sends it an interrupt,
at which point it exits.
None of the cpus will return to the idle loop until all cpus have
decremented the ready counter back to 0, so they can't
On Wednesday 21 of December 2011 at 20:12:12, Tony Lindgren wrote:
* Janusz Krzysztofik jkrzy...@tis.icnet.pl [111219 14:41]:
Don't use Amstrad Delta custom I/O functions for controlling the device,
use GPIO API instead.
While being at it, add missing
On Wednesday 21 of December 2011 at 20:08:15, Tony Lindgren wrote:
* Janusz Krzysztofik jkrzy...@tis.icnet.pl [111220 13:23]:
In preparation to converting Amstrad Delta on-board latches to
basic_mmio_gpio devices, registration of platform devices which depend
on latches and will require
On Wednesday 21 of December 2011 at 20:09:45, Tony Lindgren wrote:
* Janusz Krzysztofik jkrzy...@tis.icnet.pl [111220 13:39]:
Don't use Amstrad Delta custom I/O functions once GPIO interface is
available for the underlying hardware.
While requesting and initializing GPIO pins used, also
* Janusz Krzysztofik jkrzy...@tis.icnet.pl [111221 11:20]:
On Wednesday 21 of December 2011 at 20:08:15, Tony Lindgren wrote:
* Janusz Krzysztofik jkrzy...@tis.icnet.pl [111220 13:23]:
In preparation to converting Amstrad Delta on-board latches to
basic_mmio_gpio devices, registration of
On Tue, 2011-12-20 at 00:08 +0100, Janusz Krzysztofik wrote:
Don't use Amstrad Delta custom I/O functions for controlling the device,
use GPIO API instead.
While being at it, add missing gpio_free(AMS_DELTA_GPIO_PIN_NAND_RB).
Depends on patch 2/7 ARM: OMAP1: ams-delta: convert latches to
On Wednesday 21 of December 2011 at 19:33:44, Liam Girdwood wrote:
On Sun, 2011-12-11 at 21:12 +0100, Janusz Krzysztofik wrote:
Don't use Amstrad Delta custom I/O functions any longer, replace them
with GPIO. Old pin definitions, no longer used by the modem bits either,
can be dropped.
Resetting DISPC when a DISPC output is enabled causes the DSS to go into
an inconsistent state.
commit b923d40dd4211c4ef7d4efa2bd81b7ca1d8744c1
Author: Archit Taneja arc...@ti.com
Date: Thu Oct 6 18:04:08 2011 -0600
ARM: OMAP2PLUS: DSS: Ensure DSS works correctly if display is
enabled in
Hi Archit, Paul,
On 20.12.2011 16:23, Archit Taneja wrote:
There was a patch which got into the kernel in 3.2-rc4:
b923d40dd4211c4ef7d4efa2bd81b7ca1d8744c1
ARM: OMAP2PLUS: DSS: Ensure DSS works correctly if display is enabled in
bootloader
This tries to disable any display outputs if
40 matches
Mail list logo
