<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/arc/mm/cache.c, branch linux-4.10.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.10.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.10.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2017-04-08T07:35:07Z</updated>
<entry>
<title>ARCv2: SLC: Make sure busy bit is set properly on SLC flushing</title>
<updated>2017-04-08T07:35:07Z</updated>
<author>
<name>Alexey Brodkin</name>
</author>
<published>2017-03-29T14:15:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=61e6e72e9f9c0ba43bc6c0d8b2c891f773e23b02'/>
<id>urn:sha1:61e6e72e9f9c0ba43bc6c0d8b2c891f773e23b02</id>
<content type='text'>
commit c70c473396cbdec1168a6eff60e13029c0916854 upstream.

As reported in STAR 9001165532, an SLC control reg read (for checking
busy state) right after SLC invalidate command may incorrectly return
NOT busy causing software to NOT spin-wait while operation is underway.
(and for some reason this only happens if L1 cache is also disabled - as
required by IOC programming model)

Suggested workaround is to do an additional Control Reg read, which
ensures the 2nd read gets the right status.

Signed-off-by: Alexey Brodkin &lt;abrodkin@synopsys.com&gt;
[vgupta: reworte changelog a bit]
Signed-off-by: Vineet Gupta &lt;vgupta@synopsys.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ARC: Revert "ARC: mm: IOC: Don't enable IOC by default"</title>
<updated>2017-01-19T03:21:06Z</updated>
<author>
<name>Vineet Gupta</name>
</author>
<published>2017-01-17T19:09:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d0e73e2ac6a6b157159e1e62f981c06d29f42336'/>
<id>urn:sha1:d0e73e2ac6a6b157159e1e62f981c06d29f42336</id>
<content type='text'>
The programming model has been fixed with prev patches so re-enable it
by default

This reverts commit 23cb1f644019bac49d87b4dd7c1eac0569cc4f53.

Signed-off-by: Vineet Gupta &lt;vgupta@synopsys.com&gt;
</content>
</entry>
<entry>
<title>ARC: mm: split arc_cache_init to allow __init reaping of bulk</title>
<updated>2017-01-19T03:21:02Z</updated>
<author>
<name>Vineet Gupta</name>
</author>
<published>2017-01-18T23:10:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=76894a72a0d7e0759de272bf3f4d2279ebd86d0b'/>
<id>urn:sha1:76894a72a0d7e0759de272bf3f4d2279ebd86d0b</id>
<content type='text'>
arc_cache_init() is called for each core so can't be tagged __init.
However bulk of it is only executed by master core and thus is candidate
for __init reaping.

So split it up to allow that.

Signed-off-by: Vineet Gupta &lt;vgupta@synopsys.com&gt;
</content>
</entry>
<entry>
<title>ARCv2: IOC: Use actual memory size to setup aperture size</title>
<updated>2017-01-18T22:52:43Z</updated>
<author>
<name>Vineet Gupta</name>
</author>
<published>2017-01-18T20:59:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e497c8e52a83ebb5309ab41c8851c9cb53f28b73'/>
<id>urn:sha1:e497c8e52a83ebb5309ab41c8851c9cb53f28b73</id>
<content type='text'>
vs. fixed 512M before.

But this still assumes that all of memory is under IOC which may not be
true for the SoC. Improve that later when this becomes a real issue, by
specifying this from DT.

Signed-off-by: Vineet Gupta &lt;vgupta@synopsys.com&gt;
</content>
</entry>
<entry>
<title>ARCv2: IOC: Adhere to progamming model guidelines to avoid DMA corruption</title>
<updated>2017-01-18T22:48:33Z</updated>
<author>
<name>Vineet Gupta</name>
</author>
<published>2016-06-22T10:31:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8c47f83ba45928ce9495fcf1b29e828c28e3c839'/>
<id>urn:sha1:8c47f83ba45928ce9495fcf1b29e828c28e3c839</id>
<content type='text'>
On AXS103 release bitfiles, DMA data corruptions were seen because IOC
setup was not following the recommended way in documentation.

Flipping IOC on when caches are enabled or coherency transactions are in
flight, might cause some of the memory operations to not observe
coherency as expected.

So strictly follow the programming model recommendations as documented
in comment header above arc_ioc_setup()

Signed-off-by: Vineet Gupta &lt;vgupta@synopsys.com&gt;
</content>
</entry>
<entry>
<title>ARCv2: IOC: refactor the IOC and SLC operations into own functions</title>
<updated>2017-01-18T22:35:10Z</updated>
<author>
<name>Vineet Gupta</name>
</author>
<published>2016-06-22T10:13:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d4911cdd3270da45d3a1c55bf28e88a932bbba7b'/>
<id>urn:sha1:d4911cdd3270da45d3a1c55bf28e88a932bbba7b</id>
<content type='text'>
 - Move IOC setup into arc_ioc_setup()
 - Move SLC disabling into arc_slc_disable()

Signed-off-by: Vineet Gupta &lt;vgupta@synopsys.com&gt;
</content>
</entry>
<entry>
<title>ARC: mmu: clarify the MMUv3 programming model</title>
<updated>2017-01-05T01:12:09Z</updated>
<author>
<name>Vineet Gupta</name>
</author>
<published>2017-01-04T20:02:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fa84d7310d19e0b77979019df82e357b1e8443e3'/>
<id>urn:sha1:fa84d7310d19e0b77979019df82e357b1e8443e3</id>
<content type='text'>
Signed-off-by: Vineet Gupta &lt;vgupta@synopsys.com&gt;
</content>
</entry>
<entry>
<title>ARC: mm: arc700: Don't assume 2 colours for aliasing VIPT dcache</title>
<updated>2016-12-19T19:55:17Z</updated>
<author>
<name>Vineet Gupta</name>
</author>
<published>2016-12-19T19:38:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=08fe007968b2b45e831daf74899f79a54d73f773'/>
<id>urn:sha1:08fe007968b2b45e831daf74899f79a54d73f773</id>
<content type='text'>
An ARC700 customer reported linux boot crashes when upgrading to bigger
L1 dcache (64K from 32K). Turns out they had an aliasing VIPT config and
current code only assumed 2 colours, while theirs had 4. So default to 4
colours and complain if there are fewer. Ideally this needs to be a
Kconfig option, but heck that's too much of hassle for a single user.

Cc: stable@vger.kernel.org
Signed-off-by: Vineet Gupta &lt;vgupta@synopsys.com&gt;
</content>
</entry>
<entry>
<title>ARC: mm: No need to save cache version in @cpuinfo</title>
<updated>2016-12-19T19:54:41Z</updated>
<author>
<name>Vineet Gupta</name>
</author>
<published>2016-12-19T19:24:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f64915be2d8c629e7b55ad37f90bd8db2713426e'/>
<id>urn:sha1:f64915be2d8c629e7b55ad37f90bd8db2713426e</id>
<content type='text'>
Historical MMU revisions have been paired with Cache revision updates
which are captured in MMU and Cache Build Configuration Registers respectively.

This was used in boot code to check for configurations mismatches,
speically in simulations (such as running with non existent caches,
non pairing MMU and Cache version etc). This can instead be inferred
from other cache params such as line size. So remove @ver from post
processed @cpuinfo which could be used later to save soem other
interesting info.

Signed-off-by: Vineet Gupta &lt;vgupta@synopsys.com&gt;
</content>
</entry>
<entry>
<title>ARC: mm: IOC: Don't enable IOC by default</title>
<updated>2016-11-28T17:18:36Z</updated>
<author>
<name>Vineet Gupta</name>
</author>
<published>2016-11-28T17:18:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=23cb1f644019bac49d87b4dd7c1eac0569cc4f53'/>
<id>urn:sha1:23cb1f644019bac49d87b4dd7c1eac0569cc4f53</id>
<content type='text'>
Signed-off-by: Vineet Gupta &lt;vgupta@synopsys.com&gt;
</content>
</entry>
</feed>
