<?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>f1a22417 - usb: typec: ucsi: Implement ChromeOS UCSI driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#f1a22417</link>
        <description>usb: typec: ucsi: Implement ChromeOS UCSI driverImplementation of a UCSI transport driver for ChromeOS.This driver will be loaded if the ChromeOS EC implements a PPM.Signed-off-by: Pavan Holla &lt;pholla@chromium.org&gt;Co-developed-by: Abhishek Pandit-Subedi &lt;abhishekpandit@chromium.org&gt;Signed-off-by: Abhishek Pandit-Subedi &lt;abhishekpandit@chromium.org&gt;Co-developed-by: &#321;ukasz Bartosik &lt;ukaszb@chromium.org&gt;Signed-off-by: &#321;ukasz Bartosik &lt;ukaszb@chromium.org&gt;Link: https://lore.kernel.org/r/20241231131047.1757434-3-ukaszb@chromium.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Tue, 31 Dec 2024 13:10:47 +0000</pubDate>
        <dc:creator>Pavan Holla &lt;pholla@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>2ea6d07e - usb: typec: ucsi: add Lenovo Yoga C630 glue driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#2ea6d07e</link>
        <description>usb: typec: ucsi: add Lenovo Yoga C630 glue driverThe Lenovo Yoga C630 WOS laptop provides implements UCSI interface inthe onboard EC. Add glue driver to interface the platform&apos;s UCSIimplementation.Reviewed-by: Bryan O&apos;Donoghue &lt;bryan.odonoghue@linaro.org&gt;Reviewed-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Reviewed-by: Ilpo J&#228;rvinen &lt;ilpo.jarvinen@linux.intel.com&gt;Signed-off-by: Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;Link: https://lore.kernel.org/r/20240624-ucsi-yoga-ec-driver-v9-2-53af411a9bd6@linaro.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Mon, 24 Jun 2024 15:08:13 +0000</pubDate>
        <dc:creator>Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>df0383ff - usb: typec: ucsi: Add debugfs for ucsi commands</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#df0383ff</link>
        <description>usb: typec: ucsi: Add debugfs for ucsi commandsAdd support for UCSI commands through the following debugfs:  # /sys/kernel/debug/usb/ucsi/$UCSI_DEVICE/command  # /sys/kernel/debug/usb/ucsi/$UCSI_DEVICE/responseEg: To execute UCSI GetCapabilities:  # echo 0x6 &gt; /sys/kernel/debug/usb/ucsi/&lt;ucsi device&gt;/commandThen read the result,  # cat /sys/kernel/debug/usb/ucsi/&lt;ucsi device&gt;/response    0x02000320000000020000ff0400000445UCSI command will be written into the command file and theresponse for the command can be viewed under the response file.Reviewed-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;Signed-off-by: Saranya Gopal &lt;saranya.gopal@intel.com&gt;Co-developed-by: Rajaram Regupathy &lt;rajaram.regupathy@intel.com&gt;Signed-off-by: Rajaram Regupathy &lt;rajaram.regupathy@intel.com&gt;Reviewed-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Link: https://lore.kernel.org/r/20230807105205.742819-1-saranya.gopal@intel.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Mon, 07 Aug 2023 10:52:05 +0000</pubDate>
        <dc:creator>Saranya Gopal &lt;saranya.gopal@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>62b5412b - usb: typec: ucsi: add PMIC Glink UCSI driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#62b5412b</link>
        <description>usb: typec: ucsi: add PMIC Glink UCSI driverIntroduce the UCSI PMIC Glink aux driver that communicateswith the aDSP firmware with the UCSI protocol which handlesthe USB-C Port(s) Power Delivery.The UCSI messaging is necessary on newer Qualcomm SoCs toprovide USB role switch and altmode notifications.Reviewed-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Signed-off-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt;Reviewed-by: Bjorn Andersson &lt;andersson@kernel.org&gt;Link: https://lore.kernel.org/r/20230130-topic-sm8450-upstream-pmic-glink-v5-1-552f3b721f9e@linaro.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Tue, 21 Mar 2023 13:21:41 +0000</pubDate>
        <dc:creator>Neil Armstrong &lt;neil.armstrong@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>72849d4f - usb: typec: ucsi: stm32g0: add support for stm32g0 controller</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#72849d4f</link>
        <description>usb: typec: ucsi: stm32g0: add support for stm32g0 controllerSTM32G0 provides an integrated USB Type-C and power delivery interface.It can be programmed with a firmware to handle UCSI protocol over I2Cinterface. A GPIO is used as an interrupt line.Type-C connector can be used as a wakeup source (typically to detectchanges on the port, like attach or detach). PM suspend / resume routinesare used to enable wake irqs, and signal a wakeup event in case the IRQhas fired while in suspend. The i2c core is doing the necessaryinitialization when the &quot;wakeup-source&quot; flag is provided.Note: the interrupt handler shouldn&apos;t be called before the i2c bus resumes.So, the interrupts are disabled during suspend period, and re-enabledupon resume, to avoid i2c transfer while suspended, from the irq handler.Acked-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Signed-off-by: Fabrice Gasnier &lt;fabrice.gasnier@foss.st.com&gt;Link: https://lore.kernel.org/r/20220713120842.560902-3-fabrice.gasnier@foss.st.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Wed, 13 Jul 2022 12:08:41 +0000</pubDate>
        <dc:creator>Fabrice Gasnier &lt;fabrice.gasnier@foss.st.com&gt;</dc:creator>
    </item>
<item>
        <title>992a60ed - usb: typec: ucsi: register with power_supply class</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#992a60ed</link>
        <description>usb: typec: ucsi: register with power_supply classWith this change the UCSI device will show up in/sys/class/power_supply/. The following values are exported:- online- usb_type- voltage_min- voltage_max- voltage_now- current_max- current_nowOnce a PD-capable type-C power source is connected to the system, GET_PDOSUCSI command is used to query all source capabilities. Request data object(RDO) is used to get current values.Signed-off-by: K V, Abhilash &lt;abhilash.k.v@intel.com&gt;Signed-off-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Link: https://lore.kernel.org/r/20200423132058.6972-7-heikki.krogerus@linux.intel.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Thu, 23 Apr 2020 13:20:58 +0000</pubDate>
        <dc:creator>K V, Abhilash &lt;abhilash.k.v@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>af8622f6 - usb: typec: ucsi: Support for DisplayPort alt mode</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#af8622f6</link>
        <description>usb: typec: ucsi: Support for DisplayPort alt modeThis makes it possible to bind a driver to a DisplayPortalt mode adapter devices.The driver attempts to cope with the limitations of UCSI by&quot;emulating&quot; behaviour and attempting to guess things whenever possible in order to satisfy the requirements thestandard DisplayPort alt mode driver has.Tested-by: Ajay Gupta &lt;ajayg@nvidia.com&gt;Signed-off-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Tue, 23 Apr 2019 14:21:49 +0000</pubDate>
        <dc:creator>Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>247c554a - usb: typec: ucsi: add support for Cypress CCGx</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#247c554a</link>
        <description>usb: typec: ucsi: add support for Cypress CCGxLatest NVIDIA GPU cards have a Cypress CCGx Type-C controllerover I2C interface.This UCSI I2C driver uses I2C bus driver interface for communicatingwith Type-C controller.Signed-off-by: Ajay Gupta &lt;ajayg@nvidia.com&gt;Acked-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Signed-off-by: Wolfram Sang &lt;wsa@the-dreams.de&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Fri, 26 Oct 2018 16:36:59 +0000</pubDate>
        <dc:creator>Ajay Gupta &lt;ajayg@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>2f860691 - usb: typec: ucsi: fix tracepoint related build error</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#2f860691</link>
        <description>usb: typec: ucsi: fix tracepoint related build errorThere is the following build error with CONFIG_TYPEC_UCSI=m, CONFIG_FTRACE=yand CONFIG_TRACING=n:ERROR: &quot;__tracepoint_ucsi_command&quot; [drivers/usb/typec/ucsi/typec_ucsi.ko] undefined!ERROR: &quot;__tracepoint_ucsi_register_port&quot; [drivers/usb/typec/ucsi/typec_ucsi.ko] undefined!ERROR: &quot;__tracepoint_ucsi_notify&quot; [drivers/usb/typec/ucsi/typec_ucsi.ko] undefined!ERROR: &quot;__tracepoint_ucsi_reset_ppm&quot; [drivers/usb/typec/ucsi/typec_ucsi.ko] undefined!ERROR: &quot;__tracepoint_ucsi_run_command&quot; [drivers/usb/typec/ucsi/typec_ucsi.ko] undefined!ERROR: &quot;__tracepoint_ucsi_ack&quot; [drivers/usb/typec/ucsi/typec_ucsi.ko] undefined!ERROR: &quot;__tracepoint_ucsi_connector_change&quot; [drivers/usb/typec/ucsi/typec_ucsi.ko] undefined!This compination is quite hard to create because CONFIG_TRACING gets selectedonly in rare cases without CONFIG_FTRACE.The build failure is caused by conditionally compiling trace.c depending onthe wrong option CONFIG_FTRACE. Change this to depend on CONFIG_TRACING likeother users of tracepoints do.Fixes: c1b0bc2dabfa (&quot;usb: typec: Add support for UCSI interface&quot;)Signed-off-by: Tobias Regnery &lt;tobias.regnery@gmail.com&gt;Acked-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Tue, 10 Apr 2018 08:38:06 +0000</pubDate>
        <dc:creator>Tobias Regnery &lt;tobias.regnery@gmail.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/usb/typec/ucsi/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/usb/typec/ucsi/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>8243edf4 - usb: typec: ucsi: Add ACPI driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#8243edf4</link>
        <description>usb: typec: ucsi: Add ACPI driverDriver for ACPI UCSI interface method. This driver replacesthe previous UCSI driver drivers/usb/misc/ucsi.c.Signed-off-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Reviewed-by: Guenter Roeck &lt;linux@roeck-us.net&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Fri, 16 Jun 2017 08:21:25 +0000</pubDate>
        <dc:creator>Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>c1b0bc2d - usb: typec: Add support for UCSI interface</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/usb/typec/ucsi/Makefile#c1b0bc2d</link>
        <description>usb: typec: Add support for UCSI interfaceUCSI - USB Type-C Connector System Software Interface - is aspecification that defines set of registers and datastructures for controlling the USB Type-C ports. It&apos;sdesigned for systems where an embedded controller (EC) is incharge of the USB Type-C PHY or USB Power Deliverycontroller. It is designed for systems with EC, but it isnot limited to them, and for example some USB Power Deliverycontrollers will use it as their direct control interface.With UCSI the EC (or USB PD controller) acts as the portmanager, implementing all USB Type-C and Power Delivery statemachines. The OS can use the interfaces for reading thestatus of the ports and controlling basic operations likerole swapping.The UCSI specification highlights the fact that it does notdefine the interface method (PCI/I2C/ACPI/etc.).Therefore the driver is implemented as library and everysupported interface method needs its own driver. Driver forACPI is provided in separate patch following this one.The initial driver includes support for all requiredfeatures from UCSI specification version 1.0 (gettingconnector capabilities and status, and support for power anddata role swapping), but none of the optional UCSI features(alternate modes, power source capabilities, and cablecapabilities).Signed-off-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Reviewed-by: Guenter Roeck &lt;linux@roeck-us.net&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/usb/typec/ucsi/Makefile</description>
        <pubDate>Fri, 16 Jun 2017 08:21:24 +0000</pubDate>
        <dc:creator>Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
