From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Wed, 5 Feb 2014 03:35:46 +0100
Subject: [U-Boot] [PATCH 4/6] usb:udc:samsung: Zero copy approach for
	data passed to Samsung's UDC driver
In-Reply-To: <20140204224924.7f947ed5@jawa>
References: <1391170589-14340-1-git-send-email-l.majewski@samsung.com>
	<201402042121.16272.marex@denx.de> <20140204224924.7f947ed5@jawa>
Message-ID: <201402050335.46222.marex@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Tuesday, February 04, 2014 at 10:49:24 PM, Lukasz Majewski wrote:

[...]

> > > Maybe other ARM architectures shall have the cache management code
> > > updated to work in a similar way to cache_v7.c ?
> > 
> > Not all CPUs are ARM architecture ... there're others, you know ;-)
> :
> :-) ... but who cares about the rest :-)

Me, duh. I have mips, sparc and m68k devices here and I'm not afraid to use 
them!

> To be serious (quite), I do believe that checking if unaligned
> cache flush/invalidation is performed, shall be handled at the code
> which is responsible for cache management.
> 
> Conceptually, it shall not be done at UDC code.

You have a point, ACK. Even better, we should have a wrapper for that which will 
only then call the cache management routine.
[...]

Best regards,
Marek Vasut