Hi
On Fri, 13 Jul 2012, Rob Herring wrote:
I'm not sure this is really a good use of aliases. UARTs use aliases
because it is important that the UART number to tty number is known and
fixed. IIUC, as an example you are picking timer1 because it has
properties X, Y and Z. If so, then you
* Dennis Gilmore den...@ausil.us [120713 06:13]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 12 Jul 2012 23:57:00 -0700
Tony Lindgren t...@atomide.com wrote:
* Dennis Gilmore den...@ausil.us [120711 06:53]:
On Wed, 11 Jul 2012 00:42:33 -0700
Tony Lindgren t...@atomide.com
* Tony Lindgren t...@atomide.com [120712 23:52]:
* Kevin Hilman khil...@ti.com [120712 10:55]:
Paul Walmsley p...@pwsan.com writes:
Commit 3dd50d0545bd5a8ad83d4339f07935cd3e883271 (Merge tag
'omap-cleanup-for-v3.6' into tmp-merge) inadvertently caused a
clockdomain to be
On 07/14/2012 01:56 AM, Paul Walmsley wrote:
Hi
On Fri, 13 Jul 2012, Rob Herring wrote:
I'm not sure this is really a good use of aliases. UARTs use aliases
because it is important that the UART number to tty number is known and
fixed. IIUC, as an example you are picking timer1 because
On Fri, Jul 13, 2012 at 07:30:42PM -1000, Mitch Bradley wrote:
I'm not sure this is really a good use of aliases. UARTs use aliases
because it is important that the UART number to tty number is known and
fixed.
This brings up an issue that I've been meaning to comment on.
The use of
On 7/14/2012 6:37 AM, David Gibson wrote:
On Fri, Jul 13, 2012 at 07:30:42PM -1000, Mitch Bradley wrote:
I'm not sure this is really a good use of aliases. UARTs use aliases
because it is important that the UART number to tty number is known and
fixed.
This brings up an issue that I've been
Hi Rob,
thanks for your response.
On Sat, 14 Jul 2012, Rob Herring wrote:
On 07/14/2012 01:56 AM, Paul Walmsley wrote:
On Fri, 13 Jul 2012, Rob Herring wrote:
I'm not sure this is really a good use of aliases. UARTs use aliases
because it is important that the UART number to tty
On Sat, 14 Jul 2012, Tony Lindgren wrote:
As the tmp-merge branch has other branches and never goes upstream, the
commit should say:
Commit 472fd5401561f94698f4c8f9dbbbfbf76ab55626 (Merge branch 'cleanup-hwmod'
into cleanup)... So I've updated the patch and applied it into l-o master.
On Tue, Jul 10, 2012 at 11:11 AM, Tony Lindgren t...@atomide.com wrote:
OK so no comments for a while. Here's the patch updated to leave out
the comments in the binding example.
I reason like this:
- My fears is that the code gets hopeless to understand the mux, the
only way to understand
From: Domenico Andreoli domenico.andre...@linux.com
There is not point in having arch_id as parameter of __arch_decomp_setup(),
nothing in it uses arch_id. The machine id is already exported (and used)
with symbol __machine_arch_type as per mach-types.h.
Removing the pointless macro as well.
On Thu, Jul 12, 2012 at 7:48 PM, Kevin Hilman khil...@ti.com wrote:
In the case of OMAP GPIO, unless it's an obvious fix, I would recommend
you wait at least until you see some acks/tested tags from any of
- Santosh Shilimkar santosh.shilim...@ti.com
- Rajendra Nayak rna...@ti.com
- Benoit
commit 13f30fc893e4610f67dd7a8b0b67aec02eac1775
Author: Russell King rmk+ker...@arm.linux.org.uk
Date: Sat Apr 21 22:41:10 2012 +0100
mmc: omap: remove private DMA API implementation
removed the private DMA API implementation from the OMAP mmc host to
make it use exclusively the DMA engine
12 matches
Mail list logo
