<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>76ec18dc - drm/vc4: tests: Add unit test suite for the PV muxing</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#76ec18dc</link>
        <description>drm/vc4: tests: Add unit test suite for the PV muxingThe HVS to PixelValve muxing code is fairly error prone and has a bunchof arbitrary constraints due to the hardware setup.Let&apos;s create a test suite that makes sure that the possible combinationswork and the invalid ones don&apos;t.Reviewed-by: Javier Martinez Canillas &lt;javierm@redhat.com&gt;Reviewed-by: Ma&#237;ra Canal &lt;mcanal@igalia.com&gt;Link: https://lore.kernel.org/r/20221123-rpi-kunit-tests-v3-19-4615a663a84a@cerno.techSigned-off-by: Maxime Ripard &lt;maxime@cerno.tech&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Thu, 01 Dec 2022 15:11:50 +0000</pubDate>
        <dc:creator>Maxime Ripard &lt;maxime@cerno.tech&gt;</dc:creator>
    </item>
<item>
        <title>f759f5b5 - drm/vc4: tests: Introduce a mocking infrastructure</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#f759f5b5</link>
        <description>drm/vc4: tests: Introduce a mocking infrastructureIn order to test the current atomic_check hooks we need to have a DRMdevice that has roughly the same capabilities and layout that the actualhardware. We&apos;ll also need a bunch of functions to create arbitraryatomic states.Let&apos;s create some helpers to create a device that behaves like the realone, and some helpers to maintain the atomic state we want to check.Reviewed-by: Javier Martinez Canillas &lt;javierm@redhat.com&gt;Reviewed-by: Ma&#237;ra Canal &lt;mcanal@igalia.com&gt;Link: https://lore.kernel.org/r/20221123-rpi-kunit-tests-v3-17-4615a663a84a@cerno.techSigned-off-by: Maxime Ripard &lt;maxime@cerno.tech&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Thu, 01 Dec 2022 15:11:48 +0000</pubDate>
        <dc:creator>Maxime Ripard &lt;maxime@cerno.tech&gt;</dc:creator>
    </item>
<item>
        <title>c457b8ae - drm/vc4: hdmi: Add PHY init and disable function</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#c457b8ae</link>
        <description>drm/vc4: hdmi: Add PHY init and disable functionThe HDMI PHY in the BCM2711 HDMI controller is significantly morecomplicated to setup than in the older BCM283x SoCs.Let&apos;s add hooks to enable and disable the PHY.Signed-off-by: Maxime Ripard &lt;maxime@cerno.tech&gt;Tested-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;Tested-by: Hoegeun Kwon &lt;hoegeun.kwon@samsung.com&gt;Tested-by: Stefan Wahren &lt;stefan.wahren@i2se.com&gt;Reviewed-by: Dave Stevenson &lt;dave.stevenson@raspberrypi.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/7216826284dbc60a58bdacd662805d20699e5c80.1599120059.git-series.maxime@cerno.tech

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Thu, 03 Sep 2020 08:01:25 +0000</pubDate>
        <dc:creator>Maxime Ripard &lt;maxime@cerno.tech&gt;</dc:creator>
    </item>
<item>
        <title>008095e0 - drm/vc4: Add support for the transposer block</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#008095e0</link>
        <description>drm/vc4: Add support for the transposer blockThe transposer block is providing support for mem-to-mem composition,which is exposed as a drm_writeback connector in DRM.Add a driver to support this feature.Signed-off-by: Boris Brezillon &lt;boris.brezillon@free-electrons.com&gt;Reviewed-by: Eric Anholt &lt;eric@anholt.net&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20180703075022.15138-9-boris.brezillon@bootlin.com

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Tue, 03 Jul 2018 07:50:22 +0000</pubDate>
        <dc:creator>Boris Brezillon &lt;boris.brezillon@free-electrons.com&gt;</dc:creator>
    </item>
<item>
        <title>65101d8c - drm/vc4: Expose performance counters to userspace</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#65101d8c</link>
        <description>drm/vc4: Expose performance counters to userspaceThe V3D engine has various hardware counters which might be interestingto userspace performance analysis tools.Expose new ioctls to create/destroy a performance monitor object andquery the counter values of this perfmance monitor.Note that a perfomance monitor is given an ID that is only valid on thefile descriptor it has been allocated from. A performance monitor can beattached to a CL submission and the driver will enable HW counters forthis request and update the performance monitor values at the end of thejob.Signed-off-by: Boris Brezillon &lt;boris.brezillon@free-electrons.com&gt;Reviewed-by: Eric Anholt &lt;eric@anholt.net&gt;Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20180112090926.12538-1-boris.brezillon@free-electrons.com

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Fri, 12 Jan 2018 09:09:26 +0000</pubDate>
        <dc:creator>Boris Brezillon &lt;boris.brezillon@free-electrons.com&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>ff58a15a - drm/vc4: Use correct path to trace include</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#ff58a15a</link>
        <description>drm/vc4: Use correct path to trace includeThe header comment in include/trace/define_trace.h specifies that theTRACE_INCLUDE_PATH needs to be relative to the define_trace.h headerrather than the trace file including it. Most instances get that wrongand work around it by adding the $(src) directory to the include path.While this works, it is preferable to refer to the correct path to thetrace file in the first place and avoid any workaround.Acked-by: Christian K&#246;nig &lt;christian.koenig@amd.com&gt;Acked-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20170901144954.19620-6-thierry.reding@gmail.com

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Fri, 01 Sep 2017 14:49:54 +0000</pubDate>
        <dc:creator>Thierry Reding &lt;treding@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>b7e8e25b - drm/vc4: fix include notation and remove -Iinclude/drm flag</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#b7e8e25b</link>
        <description>drm/vc4: fix include notation and remove -Iinclude/drm flagInclude &lt;drm/*.h&gt; instead of relative path from include/drm, thenremove the -Iinclude/drm compiler flag.While we are here, use &lt;...&gt; instead of &quot;...&quot; for include/linux/*.hand include/sound/*.h headers too.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;Link: http://patchwork.freedesktop.org/patch/msgid/1495081793-9707-2-git-send-email-yamada.masahiro@socionext.com

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Thu, 18 May 2017 04:29:38 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>cdec4d36 - drm/vc4: Expose dma-buf fences for V3D rendering.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#cdec4d36</link>
        <description>drm/vc4: Expose dma-buf fences for V3D rendering.This is needed for proper synchronization with display on another DRMdevice (pl111 or tinydrm) with buffers produced by vc4 V3D.  Fixes thenew igt vc4_dmabuf_poll testcase, and rendering of one of the glmark2desktop tests on pl111+vc4.This doesn&apos;t yet introduce waits on another device&apos;s fences beforevc4&apos;s rendering/display, because I don&apos;t have testcases for them.v2: Reuse dma_fence_free(), retitle commit message to clarify that    it&apos;s not a full dma-buf fencing implementation yet.Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;Link: http://patchwork.freedesktop.org/patch/msgid/20170412191202.22740-6-eric@anholt.netAcked-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Wed, 12 Apr 2017 19:12:02 +0000</pubDate>
        <dc:creator>Eric Anholt &lt;eric@anholt.net&gt;</dc:creator>
    </item>
<item>
        <title>4078f575 - drm/vc4: Add DSI driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#4078f575</link>
        <description>drm/vc4: Add DSI driverThe DSI0 and DSI1 blocks on the 2835 are related hardware blocks.Some registers move around, and the featureset is slightly different,as DSI1 (the 4-lane DSI) is a later version of the hardware block.This driver doesn&apos;t yet enable DSI0, since we don&apos;t have any hardwareto test against, but it does put a lot of the register definitions andcode in place.v2: Use the clk_hw interfaces, don&apos;t set CLK_IS_BASIC (from review by    Stephen Boyd)Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;Acked-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt; (v1)Link: http://patchwork.freedesktop.org/patch/msgid/20170131192912.11316-1-eric@anholt.net

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Tue, 31 Jan 2017 19:29:11 +0000</pubDate>
        <dc:creator>Eric Anholt &lt;eric@anholt.net&gt;</dc:creator>
    </item>
<item>
        <title>e4b81f8c - drm/vc4: Add support for the VEC (Video Encoder) IP</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#e4b81f8c</link>
        <description>drm/vc4: Add support for the VEC (Video Encoder) IPThe VEC IP is a TV DAC, providing support for PAL and NTSC standards.Signed-off-by: Boris Brezillon &lt;boris.brezillon@free-electrons.com&gt;Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Fri, 02 Dec 2016 13:48:10 +0000</pubDate>
        <dc:creator>Boris Brezillon &lt;boris.brezillon@free-electrons.com&gt;</dc:creator>
    </item>
<item>
        <title>08302c35 - drm/vc4: Add DPI driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#08302c35</link>
        <description>drm/vc4: Add DPI driverThe DPI interface involves taking a ton of our GPIOs to be used asoutputs, and routing display signals over them in parallel.v2: Use display_info.bus_formats[] to replace our custom DT    properties.v3: Rebase on V3D documentation changes.v4: Fix rebase detritus from V3D documentation changes.Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;Acked-by: Rob Herring &lt;robh@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Wed, 10 Feb 2016 19:42:32 +0000</pubDate>
        <dc:creator>Eric Anholt &lt;eric@anholt.net&gt;</dc:creator>
    </item>
<item>
        <title>d5b1a78a - drm/vc4: Add support for drawing 3D frames.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#d5b1a78a</link>
        <description>drm/vc4: Add support for drawing 3D frames.The user submission is basically a pointer to a command list and apointer to uniforms.  We copy those in to the kernel, validate andrelocate them, and store the result in a GPU BO which we queue forexecution.v2: Drop support for NV shader recs (not necessary for GL), simplify    vc4_use_bo(), improve bin flush/semaphore checks, use __u32 style    types.Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Mon, 30 Nov 2015 20:13:37 +0000</pubDate>
        <dc:creator>Eric Anholt &lt;eric@anholt.net&gt;</dc:creator>
    </item>
<item>
        <title>d3f5168a - drm/vc4: Bind and initialize the V3D engine.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#d3f5168a</link>
        <description>drm/vc4: Bind and initialize the V3D engine.This is the component of the GPU that does 3D rendering.Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Mon, 02 Mar 2015 21:01:12 +0000</pubDate>
        <dc:creator>Eric Anholt &lt;eric@anholt.net&gt;</dc:creator>
    </item>
<item>
        <title>463873d5 - drm/vc4: Add an API for creating GPU shaders in GEM BOs.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#463873d5</link>
        <description>drm/vc4: Add an API for creating GPU shaders in GEM BOs.Since we have no MMU, the kernel needs to validate that the submittedshader code won&apos;t make any accesses to memory that the user doesn&apos;tcontrol, which involves banning some operations (general purpose DMAwrites), and tracking where we need to write out pointers for otheroperations (texture sampling).  Once it&apos;s validated, we return a GEMBO containing the shader, which doesn&apos;t allow mapping for write orexporting to other subsystems.v2: Use __u32-style types.Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Mon, 30 Nov 2015 19:41:40 +0000</pubDate>
        <dc:creator>Eric Anholt &lt;eric@anholt.net&gt;</dc:creator>
    </item>
<item>
        <title>c8b75bca - drm/vc4: Add KMS support for Raspberry Pi.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vc4/Makefile#c8b75bca</link>
        <description>drm/vc4: Add KMS support for Raspberry Pi.This is enough for fbcon and bringing up X usingxf86-video-modesetting.  It doesn&apos;t support the 3D accelerator orpower management yet.v2: Drop FB_HELPER select thanks to Archit&apos;s patches.  Do manual init    ordering instead of using the .load hook.  Structure registration    more like tegra&apos;s, but still using the typical &quot;component&quot; code.    Drop no-op hooks for atomic_begin and mode_fixup() now that    they&apos;re optional.  Drop sentinel in Makefile.  Fix minor style    nits I noticed on another reread.v3: Use the new bcm2835 clk driver to manage pixel/HSM clocks instead    of having a fixed video mode.  Use exynos-style component driver    matching instead of devicetree nodes to list the component driver    instances.  Rename compatibility strings to say bcm2835, and    distinguish pv0/1/2.  Clean up some h/vsync code, and add in    interlaced mode setup.  Fix up probe/bind error paths.  Use    bitops.h macros for vc4_regs.hv4: Include i2c.h, allow building under COMPILE_TEST, drop msleep now    that other bugs have been fixed, add timeouts to cpu_relax()    loops, rename hpd-gpio to hpd-gpios.Signed-off-by: Eric Anholt &lt;eric@anholt.net&gt;Acked-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vc4/Makefile</description>
        <pubDate>Mon, 02 Mar 2015 21:01:12 +0000</pubDate>
        <dc:creator>Eric Anholt &lt;eric@anholt.net&gt;</dc:creator>
    </item>
</channel>
</rss>
