<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-dev/drivers/staging/mt7621-mmc, branch master</title>
<subtitle>Linux kernel development work - see feature branches</subtitle>
<id>https://git.zx2c4.com/linux-dev/atom/drivers/staging/mt7621-mmc?h=master</id>
<link rel='self' href='https://git.zx2c4.com/linux-dev/atom/drivers/staging/mt7621-mmc?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/'/>
<updated>2019-04-03T09:10:15Z</updated>
<entry>
<title>staging: m57621-mmc: delete driver from the tree.</title>
<updated>2019-04-03T09:10:15Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-04-02T10:31:50Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=441bf7332d55c4d34afae9ffc3bbec621093f4d1'/>
<id>urn:sha1:441bf7332d55c4d34afae9ffc3bbec621093f4d1</id>
<content type='text'>
The license text in this driver is "interesting" and not really obvious
that it is supposed to be able to be distributed in the kernel source
tree.  Yes, the MODULE_LICENSE() text says GPL, so it's probably ok, but
to be safe, I am deleting this driver.  I will be glad to add it back if
the license is properly sorted out, but for now, this isn't worth the
potential risk, I should have never taken it in the first place.

Cc: Matthias Brugger &lt;matthias.bgg@gmail.com&gt;
Cc: NeilBrown &lt;neil@brown.name&gt;
Cc: George Hilliard &lt;thirtythreeforty@gmail.com&gt;
Cc: "Christian Lütke-Stetzkamp" &lt;christian@lkamp.de&gt;
Cc: Nishad Kamdar &lt;nishadkamdar@gmail.com&gt;
Cc: Sergej Perschin &lt;ser.perschin@gmail.com&gt;
Cc: John Crispin &lt;blogic@openwrt.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: add missing SPDX lines to Kconfig files</title>
<updated>2019-04-03T09:10:15Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-04-02T10:31:48Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=99b75a4e3275e85814db0fa2f49274bd3d5359d3'/>
<id>urn:sha1:99b75a4e3275e85814db0fa2f49274bd3d5359d3</id>
<content type='text'>
There are a few remaining drivers/staging/*/Kconfig files that do not
have SPDX identifiers in them.  Add the correct GPL-2.0 identifier to
them to make scanning tools happy.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: mt7621-mmc: Initialize completions a single time during probe</title>
<updated>2019-03-27T14:39:31Z</updated>
<author>
<name>George Hilliard</name>
<email>thirtythreeforty@gmail.com</email>
</author>
<published>2019-03-27T01:50:57Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=7ca8c2c8bbeda2a2a2a9898cd35066bc1dc83836'/>
<id>urn:sha1:7ca8c2c8bbeda2a2a2a9898cd35066bc1dc83836</id>
<content type='text'>
The module was initializing completions whenever it was going to wait on
them, and not when the completion was allocated.  This is incorrect
according to the completion docs:

    Calling init_completion() on the same completion object twice is
    most likely a bug [...]

Re-initialization is also unnecessary because the module never uses
complete_all().  Fix this by only ever initializing the completion a
single time, and log if the completions are not consumed as intended
(this is not a fatal problem, but should not go unnoticed).

Signed-off-by: George Hilliard &lt;thirtythreeforty@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: mt7621-mmc: Remove obsolete Kconfig flags</title>
<updated>2019-03-27T14:37:30Z</updated>
<author>
<name>George Hilliard</name>
<email>thirtythreeforty@gmail.com</email>
</author>
<published>2019-03-27T01:50:56Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=4195b4f11fbb5a103a81ee257d60d027695eebf6'/>
<id>urn:sha1:4195b4f11fbb5a103a81ee257d60d027695eebf6</id>
<content type='text'>
These values are not referred to anywhere else in the kernel. Card
detect is controlled by the device tree property "mediatek,cd-poll",
and there is no driver support for eMMC whatsoever.

Signed-off-by: George Hilliard &lt;thirtythreeforty@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: mt7621-mmc: Check for nonzero number of scatterlist entries</title>
<updated>2019-03-22T14:20:27Z</updated>
<author>
<name>George Hilliard</name>
<email>thirtythreeforty@gmail.com</email>
</author>
<published>2019-03-20T22:42:05Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=d4223e06b6aed581625f574ad8faa71b6c0fc903'/>
<id>urn:sha1:d4223e06b6aed581625f574ad8faa71b6c0fc903</id>
<content type='text'>
The buffer descriptor setup loop is correct only if it is setting up at
least one bd struct.  Besides, there is an error if dma_map_sg() returns
0, which is possible and must be handled.

Additionally, remove the BUG_ON() checking sglen, which is unnecessary
because we configure DMA with that constraint during init.

Signed-off-by: George Hilliard &lt;thirtythreeforty@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: mt7621-mmc: Fix warning when reloading module with debug msgs enabled</title>
<updated>2019-03-22T14:20:27Z</updated>
<author>
<name>George Hilliard</name>
<email>thirtythreeforty@gmail.com</email>
</author>
<published>2019-03-20T22:42:03Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=f2778bb3cb6c7544578c45688f3d5bcb09e0ac87'/>
<id>urn:sha1:f2778bb3cb6c7544578c45688f3d5bcb09e0ac87</id>
<content type='text'>
The kernel complained:

    [  510.277151] WARNING: CPU: 0 PID: 395 at fs/proc/generic.c:360 proc_register+0xf0/0x108
    [  510.292891] proc_dir_entry '/proc/msdc_debug' already registered

when doing a modprobe/rmmod/modprobe of this module if debug messages
are compiled in.  Fix this by removing the proc entry when the module is
unloaded.

Signed-off-by: George Hilliard &lt;thirtythreeforty@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: mt7621-mmc: Only unmap_sg if mapped</title>
<updated>2019-03-20T07:23:18Z</updated>
<author>
<name>George Hilliard</name>
<email>thirtythreeforty@gmail.com</email>
</author>
<published>2019-03-19T02:20:12Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=b8585eb51e74034a7c1dd534a667400b8fd58787'/>
<id>urn:sha1:b8585eb51e74034a7c1dd534a667400b8fd58787</id>
<content type='text'>
A failure while processing the start command could cause dma_unmap_sg()
to be called without first calling dma_map_sg().

Since calling dma_unmap_sg() is only needed when data != NULL, move the
unmap call into the corresponding if {} block.

Signed-off-by: George Hilliard &lt;thirtythreeforty@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: mt7621-mmc: Fix BRUST -&gt; BURST typo</title>
<updated>2019-03-20T07:23:18Z</updated>
<author>
<name>George Hilliard</name>
<email>thirtythreeforty@gmail.com</email>
</author>
<published>2019-03-19T02:20:11Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=b22f49923ac873beb77f1e1082022985054fb702'/>
<id>urn:sha1:b22f49923ac873beb77f1e1082022985054fb702</id>
<content type='text'>
Obvious typo.  It is specified as BURST in the datasheet.

Signed-off-by: George Hilliard &lt;thirtythreeforty@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: mt7621-mmc: Immediately notify mmc layer of card change detection</title>
<updated>2019-03-20T07:23:18Z</updated>
<author>
<name>George Hilliard</name>
<email>thirtythreeforty@gmail.com</email>
</author>
<published>2019-03-19T02:20:10Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=983b2fd7235b1c0c0ed36accb7069ef45703308a'/>
<id>urn:sha1:983b2fd7235b1c0c0ed36accb7069ef45703308a</id>
<content type='text'>
There is no need to delay notifying the mmc layer.  Schedule the delayed
work to run immediately.

Signed-off-by: George Hilliard &lt;thirtythreeforty@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: mt7621-mmc: Remove redundant host-&gt;mmc-&gt;f_max write</title>
<updated>2019-03-20T07:23:18Z</updated>
<author>
<name>George Hilliard</name>
<email>thirtythreeforty@gmail.com</email>
</author>
<published>2019-03-19T02:20:09Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=6d0e4698c89aaf4c420817c66348a006e260b101'/>
<id>urn:sha1:6d0e4698c89aaf4c420817c66348a006e260b101</id>
<content type='text'>
This is set once during initialization and never changed.  Don't bother
setting it again in the interrupt handler.

Signed-off-by: George Hilliard &lt;thirtythreeforty@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
