<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/video/fbdev/offb.c, branch v5.14</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v5.14</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v5.14'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2020-08-23T22:36:59Z</updated>
<entry>
<title>treewide: Use fallthrough pseudo-keyword</title>
<updated>2020-08-23T22:36:59Z</updated>
<author>
<name>Gustavo A. R. Silva</name>
<email>gustavoars@kernel.org</email>
</author>
<published>2020-08-23T22:36:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=df561f6688fef775baa341a0f5d960becd248b11'/>
<id>urn:sha1:df561f6688fef775baa341a0f5d960becd248b11</id>
<content type='text'>
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
fall-through markings when it is the case.

[1] https://www.kernel.org/doc/html/v5.7/process/deprecated.html?highlight=fallthrough#implicit-switch-case-fall-through

Signed-off-by: Gustavo A. R. Silva &lt;gustavoars@kernel.org&gt;
</content>
</entry>
<entry>
<title>video: constify fb ops across all drivers</title>
<updated>2019-12-05T08:57:53Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani.nikula@intel.com</email>
</author>
<published>2019-12-03T16:38:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=8a48ac339398f21282985bff16552447d41dcfb2'/>
<id>urn:sha1:8a48ac339398f21282985bff16552447d41dcfb2</id>
<content type='text'>
Now that the fbops member of struct fb_info is const, we can start
making the ops const as well.

This does not cover all drivers; some actually modify the fbops struct,
for example to adjust for different configurations, and others do more
involved things that I'd rather not touch in practically obsolete
drivers. Mostly this is the low hanging fruit where we can add "const"
and be done with it.

v3:
- un-constify atyfb, mb862xx, nvidia and uvesabf (0day)

v2:
- fix typo (Christophe de Dinechin)
- use "static const" instead of "const static" in mx3fb.c
- also constify smscufx.c

Cc: linux-fbdev@vger.kernel.org
Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/ce67f14435f3af498f2e8bf35ce4be11f7504132.1575390740.git.jani.nikula@intel.com
</content>
</entry>
<entry>
<title>video: offb: annotate implicit fall throughs</title>
<updated>2019-02-08T18:24:46Z</updated>
<author>
<name>Mathieu Malaterre</name>
<email>malat@debian.org</email>
</author>
<published>2019-02-08T18:24:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=89ef5c6a7584f9d7f8f11def67d2e8a2312ec9fe'/>
<id>urn:sha1:89ef5c6a7584f9d7f8f11def67d2e8a2312ec9fe</id>
<content type='text'>
There is a plan to build the kernel with -Wimplicit-fallthrough and
these places in the code produced warnings (W=1). Fix them up.

This commit remove the following warnings:

  drivers/video/fbdev/offb.c:211:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
  drivers/video/fbdev/offb.c:142:3: warning: this statement may fall through [-Wimplicit-fallthrough=]

Signed-off-by: Mathieu Malaterre &lt;malat@debian.org&gt;
Acked-by: Gustavo A. R. Silva &lt;gustavo@embeddedor.com&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;b.zolnierkie@samsung.com&gt;
</content>
</entry>
<entry>
<title>fbdev: Use of_node_name_eq for node name comparisons</title>
<updated>2019-02-08T18:24:45Z</updated>
<author>
<name>Rob Herring</name>
<email>robh@kernel.org</email>
</author>
<published>2019-02-08T18:24:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a6f13af4d115a1afb97a9215c491f0bbc5362af7'/>
<id>urn:sha1:a6f13af4d115a1afb97a9215c491f0bbc5362af7</id>
<content type='text'>
Convert string compares of DT node names to use of_node_name_eq helper
instead. This removes direct access to the node name pointer.

For instances using of_node_cmp, this has the side effect of now using
case sensitive comparisons. This should not matter for any FDT based
system which omap is.

Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;
Cc: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;b.zolnierkie@samsung.com&gt;
</content>
</entry>
<entry>
<title>fbdev: offb: Fix OF node name handling</title>
<updated>2019-01-11T13:34:39Z</updated>
<author>
<name>Rob Herring</name>
<email>robh@kernel.org</email>
</author>
<published>2019-01-11T13:34:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=00257e0cc550c4a8df5f99c0a4fc74fec0656144'/>
<id>urn:sha1:00257e0cc550c4a8df5f99c0a4fc74fec0656144</id>
<content type='text'>
Commit 5c63e407aaab ("fbdev: Convert to using %pOFn instead of
device_node.name") changed how the OF FB driver handles the OF node
name. This missed the case where the node name is passed to
offb_init_palette_hacks(). This results in a NULL ptr dereference
in strncmp and breaks any system except ones using bootx with no display
node.

Fix this by making offb_init_palette_hacks() use the OF node pointer and
use of_node_name_prefix() helper function instead for node name
comparisons. This helps in moving all OF node name accesses to helper
functions in preparation to remove struct device_node.name pointer.

Fixes: 5c63e407aaab ("fbdev: Convert to using %pOFn instead of device_node.name")
Reported-by: Mathieu Malaterre &lt;malat@debian.org&gt;
Tested-by: Mathieu Malaterre &lt;malat@debian.org&gt;
Cc: stable@vger.kernel.org # v4.19+
Cc: Elimar Riesebieter &lt;riesebie@lxtec.de&gt;
Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;b.zolnierkie@samsung.com&gt;
</content>
</entry>
<entry>
<title>fbdev: Convert to using %pOFn instead of device_node.name</title>
<updated>2018-10-08T10:57:36Z</updated>
<author>
<name>Rob Herring</name>
<email>robh@kernel.org</email>
</author>
<published>2018-10-08T10:57:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5c63e407aaabb0464236cfc6279a2d79aede7073'/>
<id>urn:sha1:5c63e407aaabb0464236cfc6279a2d79aede7073</id>
<content type='text'>
In preparation to remove the node name pointer from struct device_node,
convert printf users to use the %pOFn format specifier.

Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;b.zolnierkie@samsung.com&gt;
</content>
</entry>
<entry>
<title>video: offb: Deallocate the color map</title>
<updated>2018-03-12T16:06:54Z</updated>
<author>
<name>Mathieu Malaterre</name>
<email>malat@debian.org</email>
</author>
<published>2018-03-12T16:06:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=9cbaf4d969ec4f5eb7a4e97afade374ee8056ef1'/>
<id>urn:sha1:9cbaf4d969ec4f5eb7a4e97afade374ee8056ef1</id>
<content type='text'>
The function offb_destroy did not deallocate the color map leaving some
memory around after destruction. Call the color map deallocate function to
remove the memory leak.

Handle another case where color map should have been deallocated during an
error code path.

Fix memory leaks reported by kmemleak:

# dmesg
...
[ 1884.719941] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
# cat /sys/kernel/debug/kmemleak
unreferenced object 0xde3d9000 (size 512):
  comm "swapper", pid 1, jiffies 4294892827 (age 1906.784s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 aa aa aa aa aa aa aa aa  ................
    55 55 55 55 55 55 55 55 ff ff ff ff ff ff ff ff  UUUUUUUU........
  backtrace:
    [&lt;f1433400&gt;] fb_alloc_cmap_gfp+0x54/0x15c
    [&lt;cb6b409b&gt;] offb_init_nodriver+0x8e8/0xa3c
    [&lt;b5a1c019&gt;] offb_init+0xd0/0x164
    [&lt;322f82a3&gt;] do_one_initcall+0x4c/0x178
    [&lt;b592db9f&gt;] kernel_init_freeable+0x138/0x1cc
    [&lt;2a17fa0e&gt;] kernel_init+0x24/0x118
    [&lt;4079749a&gt;] ret_from_kernel_thread+0x5c/0x64
unreferenced object 0xde3d9200 (size 512):
  comm "swapper", pid 1, jiffies 4294892827 (age 1906.784s)
  hex dump (first 32 bytes):
    00 00 00 00 aa aa aa aa 00 00 00 00 55 55 aa aa  ............UU..
    55 55 55 55 ff ff ff ff 55 55 55 55 ff ff ff ff  UUUU....UUUU....
  backtrace:
    [&lt;4bf3594d&gt;] fb_alloc_cmap_gfp+0x6c/0x15c
    [&lt;cb6b409b&gt;] offb_init_nodriver+0x8e8/0xa3c
    [&lt;b5a1c019&gt;] offb_init+0xd0/0x164
    [&lt;322f82a3&gt;] do_one_initcall+0x4c/0x178
    [&lt;b592db9f&gt;] kernel_init_freeable+0x138/0x1cc
    [&lt;2a17fa0e&gt;] kernel_init+0x24/0x118
    [&lt;4079749a&gt;] ret_from_kernel_thread+0x5c/0x64
unreferenced object 0xde3d9600 (size 512):
  comm "swapper", pid 1, jiffies 4294892827 (age 1906.784s)
  hex dump (first 32 bytes):
    00 00 aa aa 00 00 aa aa 00 00 aa aa 00 00 aa aa  ................
    55 55 ff ff 55 55 ff ff 55 55 ff ff 55 55 ff ff  UU..UU..UU..UU..
  backtrace:
    [&lt;23a3ea03&gt;] fb_alloc_cmap_gfp+0x84/0x15c
    [&lt;cb6b409b&gt;] offb_init_nodriver+0x8e8/0xa3c
    [&lt;b5a1c019&gt;] offb_init+0xd0/0x164
    [&lt;322f82a3&gt;] do_one_initcall+0x4c/0x178
    [&lt;b592db9f&gt;] kernel_init_freeable+0x138/0x1cc
    [&lt;2a17fa0e&gt;] kernel_init+0x24/0x118
    [&lt;4079749a&gt;] ret_from_kernel_thread+0x5c/0x64

Signed-off-by: Mathieu Malaterre &lt;malat@debian.org&gt;
Cc: Rob Herring &lt;robh@kernel.org&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;b.zolnierkie@samsung.com&gt;
</content>
</entry>
<entry>
<title>video: fbdev: Convert to using %pOF instead of full_name</title>
<updated>2017-08-07T15:22:13Z</updated>
<author>
<name>Rob Herring</name>
<email>robh@kernel.org</email>
</author>
<published>2017-08-07T15:22:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6d7e653300e30fd433a845c8c9f48557e799a8de'/>
<id>urn:sha1:6d7e653300e30fd433a845c8c9f48557e799a8de</id>
<content type='text'>
Now that we have a custom printf format specifier, convert users of
full_name to use %pOF instead. This is preparation to remove storing
of the full path string for each node.

Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;b.zolnierkie@samsung.com&gt;
</content>
</entry>
<entry>
<title>video: fbdev: offb: switch to using for_each_node_by_type</title>
<updated>2017-02-08T15:43:59Z</updated>
<author>
<name>Dmitry Torokhov</name>
<email>dmitry.torokhov@gmail.com</email>
</author>
<published>2017-02-08T15:43:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=8d22556873cbe36f30a0d018b9d8238425117515'/>
<id>urn:sha1:8d22556873cbe36f30a0d018b9d8238425117515</id>
<content type='text'>
Instead of open-coding loops let's switch to a nice macro.

Cc: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
Cc: Yongji Xie &lt;xyjxie@linux.vnet.ibm.com&gt;
Signed-off-by: Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;b.zolnierkie@samsung.com&gt;
</content>
</entry>
<entry>
<title>video: fbdev: offb: Call pci_enable_device() before using the PCI VGA device</title>
<updated>2016-09-27T07:55:02Z</updated>
<author>
<name>Yongji Xie</name>
<email>xyjxie@linux.vnet.ibm.com</email>
</author>
<published>2016-09-13T05:53:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5bda8f7b54687ab6397a383db38d53fd51bb1c6e'/>
<id>urn:sha1:5bda8f7b54687ab6397a383db38d53fd51bb1c6e</id>
<content type='text'>
Currently the offb module will use the PCI VGA device as frame
buffer device without calling something like pci_enable_device().
However, this would cause some problem if we disable memory
decoding of the upstream bridge before. When the console driver
issued memory access to the VGA device, the access cannot be
supported by the bridge which will cause EEH error on Power machine.

Signed-off-by: Yongji Xie &lt;xyjxie@linux.vnet.ibm.com&gt;
Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
</feed>
