From mboxrd@z Thu Jan  1 00:00:00 1970
From: Hannes Schmelzer <hannes@schmelzer.or.at>
Date: Wed, 3 Aug 2016 22:05:36 +0200
Subject: [U-Boot] [PATCH] mtd: nand: mxs: fix cache alignment for cache
 lines >32
In-Reply-To: <20160803180908.GA9942@bill-the-cat>
References: <20160802065518.24140-1-stefan@agner.ch>
 <CAOMZO5C8eSkDsT9eiU8eW4Lthsk+g+1evWh7EVWJw4x1gwuERw@mail.gmail.com>
 <25dc4a8aeadcdc3698ce4f59b619dc01@agner.ch>
 <CAOMZO5CSQC6+5DSv-NDm34wGQC-nZQy82y5po4wpkvbJRZkP1w@mail.gmail.com>
 <20160803180908.GA9942@bill-the-cat>
Message-ID: <57A24E90.5030104@schmelzer.or.at>
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 08/03/2016 08:09 PM, Tom Rini wrote:
> On Wed, Aug 03, 2016 at 02:39:47PM -0300, Fabio Estevam wrote:
>> On Wed, Aug 3, 2016 at 1:13 PM, Stefan Agner <stefan@agner.ch> wrote:
>>
>>> As you noted, this particular case is due to cache flush of the page
>>> table and should be fixed with:
>>> arm: cache: always flush cache line size for page table
>> Yes, just noticed that on a imx7d-sdb I still get these cache warnings
>> even with "arm: cache: always flush cache line size for page table"
>> applied:
>>
>> ....
>> Filename 'zImage'.
>> Load address: 0x80800000
>> Loading: #################################################################
>>           #################################################################
>>           #################################################################
>>           #################################################################
>>           #################################################################
>>           #################################################################
>>           #################################################################
>>           #############################################
>>           9.1 MiB/s
>> done
>> Bytes transferred = 7334512 (6fea70 hex)
>> CACHE: Misaligned operation at range [80800000, 80efea70]
> I feel like we must have done something wrong of late, can you bisect
> when these came in?  Thanks!
The mistake(s) must have been long time ago, but since commit 
bcc53bf095893fbdae531a9a7b5d4ef4a125a7fc it comes out visible.

I think we have to check every those warning for correct alignment.

cheers,
Hannes