<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/mtd/devices/mtdram.c, branch linux-4.9.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.9.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.9.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2016-03-07T21:06:27Z</updated>
<entry>
<title>mtd: mtdram: Add parameter for setting writebuf size</title>
<updated>2016-03-07T21:06:27Z</updated>
<author>
<name>Alexander Stein</name>
</author>
<published>2016-03-02T15:26:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c67682c5e0a43bdcb049c7775b78200835f12b95'/>
<id>urn:sha1:c67682c5e0a43bdcb049c7775b78200835f12b95</id>
<content type='text'>
ubifs uses the write buffer size in recovery algorithm. When inspecting
an unclean ubifs recovery fails with writebuf size 64 in mtdram while
recovery on actual mtd device with writebuf size of 1024 succeeds.
So add a parameter for setting this property.

Signed-off-by: Alexander Stein &lt;alexander.stein@systec-electronic.com&gt;
Reviewed-by: Richard Weinberger &lt;richard@nod.at&gt;
Signed-off-by: Brian Norris &lt;computersforpeace@gmail.com&gt;
</content>
</entry>
<entry>
<title>mtd: mtdram: check offs and len in mtdram-&gt;erase</title>
<updated>2015-10-20T01:08:33Z</updated>
<author>
<name>Dongsheng Yang</name>
</author>
<published>2015-09-30T01:01:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ab84fce518175aa09ec6e1bb50c2b41dad3e610a'/>
<id>urn:sha1:ab84fce518175aa09ec6e1bb50c2b41dad3e610a</id>
<content type='text'>
We should prevent user to erasing mtd device with
an unaligned offset or length.

Signed-off-by: Dongsheng Yang &lt;yangds.fnst@cn.fujitsu.com&gt;
Signed-off-by: Brian Norris &lt;computersforpeace@gmail.com&gt;
</content>
</entry>
<entry>
<title>Revert "mtd: mtdram: check offs and len in mtdram-&gt;erase"</title>
<updated>2015-09-30T00:29:17Z</updated>
<author>
<name>Brian Norris</name>
</author>
<published>2015-09-30T00:28:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d489ff42db9179647004ca2b12c614cb71ac81ea'/>
<id>urn:sha1:d489ff42db9179647004ca2b12c614cb71ac81ea</id>
<content type='text'>
This reverts commit 7827e3acad2df1c6537e5fe7211d216dabc60399.

There are some 64-bit arithmetic issues on some architectures, so let's
wait until we get a better patch for this.

Signed-off-by: Brian Norris &lt;computersforpeace@gmail.com&gt;
</content>
</entry>
<entry>
<title>mtd: mtdram: check offs and len in mtdram-&gt;erase</title>
<updated>2015-09-29T22:43:15Z</updated>
<author>
<name>Dongsheng Yang</name>
</author>
<published>2015-07-21T08:30:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7827e3acad2df1c6537e5fe7211d216dabc60399'/>
<id>urn:sha1:7827e3acad2df1c6537e5fe7211d216dabc60399</id>
<content type='text'>
We should prevent user to erasing mtd device with
an unaligned offset or length.

Signed-off-by: Dongsheng Yang &lt;yangds.fnst@cn.fujitsu.com&gt;
Signed-off-by: Brian Norris &lt;computersforpeace@gmail.com&gt;
</content>
</entry>
<entry>
<title>mtd: mtdram: add missing 'const'</title>
<updated>2014-01-20T19:55:23Z</updated>
<author>
<name>Brian Norris</name>
</author>
<published>2014-01-11T23:51:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0a8899b31a7d6c4a3bc7fdbd7c8c1fc79e726363'/>
<id>urn:sha1:0a8899b31a7d6c4a3bc7fdbd7c8c1fc79e726363</id>
<content type='text'>
mtdram_init_device() wasn't updated along with mtd_partition.name.

Signed-off-by: Brian Norris &lt;computersforpeace@gmail.com&gt;
Cc: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
</content>
</entry>
<entry>
<title>mtd: harmonize mtd_point interface implementation</title>
<updated>2012-03-26T23:32:11Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-02-08T13:13:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0dd5235f51fb0eb0b8cef3fed35be39b8a06d7bd'/>
<id>urn:sha1:0dd5235f51fb0eb0b8cef3fed35be39b8a06d7bd</id>
<content type='text'>
Some MTD drivers return -EINVAL if the 'phys' parameter is not NULL, trying to
convey that they cannot return the physical address. However, this is not very
logical because they still can return the virtual address ('virt'). But some
drivers (lpddr) just ignore the 'phys' parameter instead, which is a more
logical thing to do.

Let's harmonize this and:

1. Always initialize 'virt' and 'phys' to 'NULL' in 'mtd_point()'.
2. Do not return an error if the physical address cannot be found.

So as a result, all drivers will set 'phys' to 'NULL' if it is not supported.
None of the 'mtd_point()' users use 'phys' anyway, so this should not break
anything. I guess we could also just delete this parameter later.

Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>mtd: do not duplicate length and offset checks in drivers</title>
<updated>2012-03-26T23:28:18Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-02-03T14:23:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5def48982b778aaebe201f85af7170b7d0a6619f'/>
<id>urn:sha1:5def48982b778aaebe201f85af7170b7d0a6619f</id>
<content type='text'>
We already verify that offset and length are within the MTD device size
in the MTD API functions. Let's remove the duplicated checks in drivers.
This patch only affects the following API's:

'mtd_erase()'
'mtd_point()'
'mtd_unpoint()'
'mtd_get_unmapped_area()'
'mtd_read()'
'mtd_write()'
'mtd_panic_write()'
'mtd_lock()'
'mtd_unlock()'
'mtd_is_locked()'
'mtd_block_isbad()'
'mtd_block_markbad()'

This patch adds a bit of noise by removing too sparse empty lines, but this is
not too bad.

Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>mtd: return error code from mtd_unpoint</title>
<updated>2012-03-26T23:27:19Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-02-03T11:20:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5e4e6e3fdf48c1b012e2b6e80ed1d7e99d4fa6d1'/>
<id>urn:sha1:5e4e6e3fdf48c1b012e2b6e80ed1d7e99d4fa6d1</id>
<content type='text'>
The 'mtd_unpoint()' API function should be able to return an error code because
it may fail if you specify incorrect offset. This patch changes this MTD API
function and amends all the drivers correspondingly.

Also return '-EOPNOTSUPP' from 'mtd_unpoint()' when the '-&gt;unpoint()' method is
undefined. We do not really need this currently, but this just makes
sense to be consistent with 'mtd_point()'.

Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>mtd: add leading underscore to all mtd functions</title>
<updated>2012-03-26T23:20:01Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2012-01-30T12:58:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3c3c10bba1e4ccb75b41442e45c1a072f6cded19'/>
<id>urn:sha1:3c3c10bba1e4ccb75b41442e45c1a072f6cded19</id>
<content type='text'>
This patch renames all MTD functions by adding a "_" prefix:

mtd-&gt;erase -&gt; mtd-&gt;_erase
mtd-&gt;read_oob -&gt; mtd-&gt;_read_oob
...

The reason is that we are re-working the MTD API and from now on it is
an error to use MTD function pointers directly - we have a corresponding
API call for every pointer. By adding a leading "_" we achieve the following:

1. Make sure we convert every direct pointer users
2. A leading "_" suggests that this interface is internal and it becomes
   less likely that people will use them directly
3. Make sure all the out-of-tree modules stop compiling and the owners
   spot the big API change and amend them.

Signed-off-by: Artem Bityutskiy &lt;artem.bityutskiy@linux.intel.com&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>mtd: convert remaining users to mtd_device_register()</title>
<updated>2011-05-25T01:25:00Z</updated>
<author>
<name>Jamie Iles</name>
</author>
<published>2011-05-23T09:23:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ee0e87b174bb41f0310cf089262bf5dd8f95a212'/>
<id>urn:sha1:ee0e87b174bb41f0310cf089262bf5dd8f95a212</id>
<content type='text'>
The older add_mtd_device()/add_mtd_partitions() and their removal
counterparts will soon be gone.  Replace uses with mtd_device_register()
and mtd_device_unregister().

Signed-off-by: Jamie Iles &lt;jamie@jamieiles.com&gt;
Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
</feed>
