<feed xmlns='http://www.w3.org/2005/Atom'>
<title>blackbird-op-linux/drivers/staging/axis-fifo, branch master</title>
<subtitle>Blackbird™ Linux sources for OpenPOWER</subtitle>
<id>https://git.raptorcs.com/git/blackbird-op-linux/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/blackbird-op-linux/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/'/>
<updated>2020-01-22T08:58:01+00:00</updated>
<entry>
<title>staging: axis-fifo: replace spinlock with mutex</title>
<updated>2020-01-22T08:58:01+00:00</updated>
<author>
<name>Quentin Deslandes</name>
<email>quentin.deslandes@itdev.co.uk</email>
</author>
<published>2020-01-21T10:40:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=0443b3f4436321e1098fdf74432c8867016339da'/>
<id>urn:sha1:0443b3f4436321e1098fdf74432c8867016339da</id>
<content type='text'>
Following the device's documentation guidance, reading a packet from the
device or writing a packet to it must be atomic. Previously, only
reading device's vacancy (before writing on it) or occupancy (before
reading from it) was locked. Hence, effectively reading the packet or
writing the packet wasn't locked at all. However, reading a packet (and
writing one, to a lesser extent) requires to read 3 different registers
in a specific order, without missing one or else we should reset the
device.

This patch fixes the device's locking mechanism on the FIFO character
device. As the device was using copy_from_user() and copy_to_user(), we
need to replace spinlocks with mutexes.

Signed-off-by: Quentin Deslandes &lt;quentin.deslandes@itdev.co.uk&gt;
Link: https://lore.kernel.org/r/20200121103958.12941-1-quentin.deslandes@itdev.co.uk
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: axis-fifo: add unspecified HAS_IOMEM dependency</title>
<updated>2019-12-17T08:22:11+00:00</updated>
<author>
<name>Brendan Higgins</name>
<email>brendanhiggins@google.com</email>
</author>
<published>2019-12-11T19:27:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=d3aa8de6b5d0853c43c616586b4e232aa1fa7de9'/>
<id>urn:sha1:d3aa8de6b5d0853c43c616586b4e232aa1fa7de9</id>
<content type='text'>
Currently CONFIG_XIL_AXIS_FIFO=y implicitly depends on
CONFIG_HAS_IOMEM=y; consequently, on architectures without IOMEM we get
the following build error:

ld: drivers/staging/axis-fifo/axis-fifo.o: in function `axis_fifo_probe':
drivers/staging/axis-fifo/axis-fifo.c:809: undefined reference to `devm_ioremap_resource'

Fix the build error by adding the unspecified dependency.

Reported-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;
Signed-off-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;
Link: https://lore.kernel.org/r/20191211192742.95699-7-brendanhiggins@google.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: axis-fifo: remove unused pointer to memory resource</title>
<updated>2019-11-03T12:09:01+00:00</updated>
<author>
<name>Quentin Deslandes</name>
<email>quentin.deslandes@itdev.co.uk</email>
</author>
<published>2019-11-01T21:42:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=354e27a86b4c6479cbc51a8e9e347665a73e8d12'/>
<id>urn:sha1:354e27a86b4c6479cbc51a8e9e347665a73e8d12</id>
<content type='text'>
Remove unused resource pointer from the device's internal structure.

Signed-off-by: Quentin Deslandes &lt;quentin.deslandes@itdev.co.uk&gt;
Link: https://lore.kernel.org/r/20191101214232.16960-4-quentin.deslandes@itdev.co.uk
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: axis-fifo: request resources using managed functions</title>
<updated>2019-11-03T12:09:01+00:00</updated>
<author>
<name>Quentin Deslandes</name>
<email>quentin.deslandes@itdev.co.uk</email>
</author>
<published>2019-11-01T21:42:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=6a20d283ed68670e9301c4a951ea84fefbb2df53'/>
<id>urn:sha1:6a20d283ed68670e9301c4a951ea84fefbb2df53</id>
<content type='text'>
Request device's resources (memory, interrupt...) using managed
function.

Signed-off-by: Quentin Deslandes &lt;quentin.deslandes@itdev.co.uk&gt;
Link: https://lore.kernel.org/r/20191101214232.16960-3-quentin.deslandes@itdev.co.uk
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: axis-fifo: avoid parsing ignored device tree properties</title>
<updated>2019-11-03T12:09:01+00:00</updated>
<author>
<name>Quentin Deslandes</name>
<email>quentin.deslandes@itdev.co.uk</email>
</author>
<published>2019-11-01T21:42:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=ed6daf2b2832d9b07582a6ff884039afa9063206'/>
<id>urn:sha1:ed6daf2b2832d9b07582a6ff884039afa9063206</id>
<content type='text'>
Some properties were parsed from the device tree and then ignored by the
driver. Some would return an error if absent from the device tree, then
return an error if they were found because they are unsupported by the
driver.

Avoid parsing unused properties and clearly explain in the documentation
the ignored / unsupported properties.

Signed-off-by: Quentin Deslandes &lt;quentin.deslandes@itdev.co.uk&gt;
Link: https://lore.kernel.org/r/20191101214232.16960-2-quentin.deslandes@itdev.co.uk
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: remove redundant 'default n' from Kconfig</title>
<updated>2019-04-16T11:39:01+00:00</updated>
<author>
<name>Bartlomiej Zolnierkiewicz</name>
<email>b.zolnierkie@samsung.com</email>
</author>
<published>2019-04-12T10:13:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=031ba1fd9172dba01e0193b1d047a2af4868a101'/>
<id>urn:sha1:031ba1fd9172dba01e0193b1d047a2af4868a101</id>
<content type='text'>
'default n' is the default value for any bool or tristate Kconfig
setting so there is no need to write it explicitly.

Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOO
is not set' for visible symbols") the Kconfig behavior is the same
regardless of 'default n' being present or not:

    ...
    One side effect of (and the main motivation for) this change is making
    the following two definitions behave exactly the same:

        config FOO
                bool

        config FOO
                bool
                default n

    With this change, neither of these will generate a
    '# CONFIG_FOO is not set' line (assuming FOO isn't selected/implied).
    That might make it clearer to people that a bare 'default n' is
    redundant.
    ...

Signed-off-by: Bartlomiej Zolnierkiewicz &lt;b.zolnierkie@samsung.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: axis-fifo: Add elaborate description in Kconfig</title>
<updated>2019-04-16T11:38:15+00:00</updated>
<author>
<name>Moses Christopher</name>
<email>moseschristopherb@gmail.com</email>
</author>
<published>2019-04-13T16:29:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=827ad2c7b303dc0102b61820868d4c01d0d8e0b2'/>
<id>urn:sha1:827ad2c7b303dc0102b61820868d4c01d0d8e0b2</id>
<content type='text'>
  - The Xilinx AXI-Stream FIFO IP core driver description is elaborated.
  - References: Xilinx PG080 document, axis-fifo.txt

Signed-off-by: Moses Christopher &lt;moseschristopherb@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: add missing SPDX lines to Makefile files</title>
<updated>2019-04-03T09:10:15+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-04-02T10:31:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=97ed8eab2a0067bee21aa634c938454660e76a38'/>
<id>urn:sha1:97ed8eab2a0067bee21aa634c938454660e76a38</id>
<content type='text'>
There are a few remaining drivers/staging/*/Makefile files that do not
have SPDX identifiers in them.  Add the correct GPL-2.0 identifier to
them to make scanning tools happy.

Reviewed-by: Mukesh Ojha &lt;mojha@codeaurora.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:15+00:00</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2019-04-02T10:31:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/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: axis-fifo: add CONFIG_OF dependency</title>
<updated>2019-03-18T06:57:58+00:00</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2019-03-04T19:43:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=1beea6204e2304dd11600791d8dad8e7350af6ad'/>
<id>urn:sha1:1beea6204e2304dd11600791d8dad8e7350af6ad</id>
<content type='text'>
When building without CONFIG_OF, the compiler loses track of the flow
control in axis_fifo_probe(), and thinks that many variables are used
without an initialization even though we actually leave the function
before the first use:

drivers/staging/axis-fifo/axis-fifo.c: In function 'axis_fifo_probe':
drivers/staging/axis-fifo/axis-fifo.c:900:5: error: 'rxd_tdata_width' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  if (rxd_tdata_width != 32) {
     ^
drivers/staging/axis-fifo/axis-fifo.c:907:5: error: 'txd_tdata_width' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  if (txd_tdata_width != 32) {
     ^
drivers/staging/axis-fifo/axis-fifo.c:914:5: error: 'has_tdest' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  if (has_tdest) {
     ^
drivers/staging/axis-fifo/axis-fifo.c:919:5: error: 'has_tid' may be used uninitialized in this function [-Werror=maybe-uninitialized]

When CONFIG_OF is set, this does not happen, and since the driver cannot
work without it, just add that option as a Kconfig dependency.

Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
