Kevin,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Hilman, Kevin
Sent: Friday, April 22, 2011 2:05 AM
To: linux-omap@vger.kernel.org
Cc: Varadarajan, Charulatha
Subject: [PATCH 0/9] OMAP: GPIO: cleanup,
Kevin,
[...]
Here's an updated version of my work-in-progress GPIO cleanups.
I now understand that others have some similar work in progress, so
these are posted (to linux-omap only, for now) so that we can begin
collaboration on the GPIO cleanups.
This series applies on top of
In driver probe use sys_timer_reserved to identify which all timers
have already been used for clocksource and clockevent. Mark all those
timers as reserved so that no one else can use them.
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
---
Changed CONFIG_ARCH_OMAP2 to
[...]
- * acpi_processor_setup_cpuidle - prepares and configures CPUIDLE
+ * acpi_processor_setup_cpuidle_cx - prepares and configures CPUIDLE
+ * device i.e. per-cpu data
+ *
* @pr: the ACPI processor
*/
-static int acpi_processor_setup_cpuidle(struct acpi_processor *pr)
+static int
Kevin,
On Sat, Apr 23, 2011 at 04:31, Kevin Hilman khil...@ti.com wrote:
Remove the OMAP1 #ifdef and MPUIO special case for _clear_gpio_irqbank()
The MPUIOs do not need a register access to ack/clear the IRQ status,
since reading the IRQ status clears it. In addition, the MPUIO
irq_chip has
Kevin,
Thanks for your comments.
On Sat, Apr 23, 2011 at 04:04, Kevin Hilman khil...@ti.com wrote:
Hi Charu,
Charulatha V ch...@ti.com writes:
Modifies the OMAP GPIO driver to avoid usage of cpu_is* checks
for different OMAP architectures. This is done by moving some
architecture specific
On 04/24/2011 02:37 AM, Keshava Munegowda wrote:
-Original Message-
From: Alan Ott [mailto:a...@signal11.us]
Sent: Friday, April 22, 2011 6:41 AM
To: Keshava Munegowda
Cc: Dmitry Artamonow; Steve Sakoman; Steve Calfee; Felipe Balbi;
linux-...@vger.kernel.org; linux-
On Mon, Apr 25, 2011 at 7:11 AM, Alan Ott a...@signal11.us wrote:
On 04/24/2011 02:37 AM, Keshava Munegowda wrote:
-Original Message-
From: Alan Ott [mailto:a...@signal11.us]
Sent: Friday, April 22, 2011 6:41 AM
To: Keshava Munegowda
Cc: Dmitry Artamonow; Steve Sakoman; Steve Calfee;
-Original Message-
From: Steve Sakoman [mailto:sako...@gmail.com]
Sent: Monday, April 25, 2011 7:46 PM
To: Alan Ott
Cc: Keshava Munegowda; Dmitry Artamonow; Steve Calfee; Felipe Balbi;
linux-...@vger.kernel.org;
linux-omap@vger.kernel.org; linux-ker...@vger.kernel.org
Subject: Re:
On 04/25/11 09:41, Keshava Munegowda wrote:
-Original Message-
From: Steve Sakoman [mailto:sako...@gmail.com]
Sent: Monday, April 25, 2011 7:46 PM
To: Alan Ott
Cc: Keshava Munegowda; Dmitry Artamonow; Steve Calfee; Felipe Balbi;
linux-...@vger.kernel.org;
linux-omap@vger.kernel.org;
On 04/25/11 10:23, Steve Calfee wrote:
On 04/25/11 09:41, Keshava Munegowda wrote:
-Original Message-
From: Steve Sakoman [mailto:sako...@gmail.com]
Sent: Monday, April 25, 2011 7:46 PM
To: Alan Ott
Cc: Keshava Munegowda; Dmitry Artamonow; Steve Calfee; Felipe Balbi;
Hi Keshava,
I rebuilt my system to boot from flash and now I see what happened. I
even remember it being discussed on this list. Someone renamed my usb
ethernet device from usb0 to eth0 !!! The boot log shows it on this
line:
[4.596130] smsc95xx 1-2.1:1.0: eth0: register 'smsc95xx' at
12 matches
Mail list logo
