<?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>85a55eee - soc: qcom: smp2p: Introduce tracepoint support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#85a55eee</link>
        <description>soc: qcom: smp2p: Introduce tracepoint supportIntroduce tracepoint support for smp2p to enablecommunication logging between local and remote processors.Include tracepoints with information about the remote subsystemname, negotiation details, supported features, bit changenotifications, and ssr activity. These logs are useful fordebugging issues between subsystems.Signed-off-by: Sudeepgoud Patil &lt;quic_sudeepgo@quicinc.com&gt;Link: https://lore.kernel.org/r/20240716173835.997259-3-quic_sudeepgo@quicinc.comSigned-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Tue, 16 Jul 2024 17:38:34 +0000</pubDate>
        <dc:creator>Sudeepgoud Patil &lt;quic_sudeepgo@quicinc.com&gt;</dc:creator>
    </item>
<item>
        <title>1ebcde04 - soc: qcom: add pd-mapper implementation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#1ebcde04</link>
        <description>soc: qcom: add pd-mapper implementationExisting userspace protection domain mapper implementation has severalissue. It doesn&apos;t play well with CONFIG_EXTRA_FIRMWARE, it doesn&apos;treread JSON files if firmware location is changed (or if firmware wasnot available at the time pd-mapper was started but the correspondingdirectory is mounted later), etc.Provide in-kernel service implementing protection domain mappingrequired to work with several services, which are provided by the DSPfirmware.This module is loaded automatically by the remoteproc drivers whennecessary via the symbol dependency. It uses a root node to match aprotection domains map for a particular board. It is not possible toimplement it as a &apos;driver&apos; as there is no corresponding device.Tested-by: Steev Klimaszewski &lt;steev@kali.org&gt;Tested-by: Alexey Minnekhanov &lt;alexeymin@postmarketos.org&gt;Reviewed-by: Chris Lew &lt;quic_clew@quicinc.com&gt;Tested-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt; # on SM8550-QRDSigned-off-by: Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;Link: https://lore.kernel.org/r/20240622-qcom-pd-mapper-v9-4-a84ee3591c8e@linaro.org[bjorn: include linux/slab.h]Signed-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Fri, 21 Jun 2024 22:03:43 +0000</pubDate>
        <dc:creator>Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>0ac5c7d9 - soc: qcom: pdr: extract PDR message marshalling data</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#0ac5c7d9</link>
        <description>soc: qcom: pdr: extract PDR message marshalling dataThe in-kernel PD mapper is going to use same message structures as theQCOM_PDR_HELPERS module. Extract message marshalling data to separatemodule that can be used by both PDR helpers and by PD mapper.Reviewed-by: Bryan O&apos;Donoghue &lt;bryan.odonoghue@linaro.org&gt;Tested-by: Steev Klimaszewski &lt;steev@kali.org&gt;Tested-by: Alexey Minnekhanov &lt;alexeymin@postmarketos.org&gt;Tested-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt; # on SM8550-QRDSigned-off-by: Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;Link: https://lore.kernel.org/r/20240622-qcom-pd-mapper-v9-3-a84ee3591c8e@linaro.orgSigned-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Fri, 21 Jun 2024 22:03:42 +0000</pubDate>
        <dc:creator>Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>5b2dd77b - soc: qcom: add QCOM PBS driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#5b2dd77b</link>
        <description>soc: qcom: add QCOM PBS driverAdd the Qualcomm PBS (Programmable Boot Sequencer) driver. The QCOM PBSdriver supports configuring software PBS trigger events through PBS RAMon Qualcomm Technologies, Inc (QTI) PMICs.Signed-off-by: Anjelique Melendez &lt;quic_amelende@quicinc.com&gt;Link: https://lore.kernel.org/r/20240201204421.16992-6-quic_amelende@quicinc.comSigned-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Thu, 01 Feb 2024 20:44:24 +0000</pubDate>
        <dc:creator>Anjelique Melendez &lt;quic_amelende@quicinc.com&gt;</dc:creator>
    </item>
<item>
        <title>651893a7 - soc: qcom: aoss: Add tracepoints in qmp_send()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#651893a7</link>
        <description>soc: qcom: aoss: Add tracepoints in qmp_send()Add tracepoint for tracing the messages being sent and the successthereof. This is useful as the system has a variety of clients sendingrequests to the always-on subsystem.Signed-off-by: Bjorn Andersson &lt;quic_bjorande@quicinc.com&gt;Reviewed-by: Chris Lew &lt;quic_clew@quicinc.com&gt;Link: https://lore.kernel.org/r/20240123-qcom-aoss-tracepoints-v2-1-bd73baa31977@quicinc.comSigned-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Wed, 24 Jan 2024 03:40:33 +0000</pubDate>
        <dc:creator>Bjorn Andersson &lt;quic_bjorande@quicinc.com&gt;</dc:creator>
    </item>
<item>
        <title>4d2b810f - soc: qcom: pmic_pdcharger_ulog: Search current directory for headers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#4d2b810f</link>
        <description>soc: qcom: pmic_pdcharger_ulog: Search current directory for headersAs specified in samples/trace_events/Makefile:    If you include a trace header outside of include/trace/events    then the file that does the #define CREATE_TRACE_POINTS must    have that tracer file in its main search path. This is because    define_trace.h will include it, and must be able to find it from    the include/trace directory.Without this the following compilation error is seen:      CC      drivers/soc/qcom/pmic_pdcharger_ulog.o    In file included from drivers/soc/qcom/pmic_pdcharger_ulog.h:36,                     from drivers/soc/qcom/pmic_pdcharger_ulog.c:15:    ./include/trace/define_trace.h:95:42: fatal error: ./pmic_pdcharger_ulog.h: No such file or directory       95 | #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)          |                                          ^    compilation terminated.Fixes: 086fdb48bc65 (&quot;soc: qcom: add ADSP PDCharger ULOG driver&quot;)Signed-off-by: Andrew Halaney &lt;ahalaney@redhat.com&gt;Reviewed-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt;Link: https://lore.kernel.org/r/20231205-pmicpdcharger-ulog-fixups-v1-1-71c95162cb84@redhat.comSigned-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Tue, 05 Dec 2023 23:05:09 +0000</pubDate>
        <dc:creator>Andrew Halaney &lt;ahalaney@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>086fdb48 - soc: qcom: add ADSP PDCharger ULOG driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#086fdb48</link>
        <description>soc: qcom: add ADSP PDCharger ULOG driverThe Qualcomm PMIC PDCharger ULOG driver provides access to logs ofthe ADSP firmware PDCharger module in charge of Battery and PowerDelivery on modern systems.Implement trace events as a simple rpmsg driver with an 1s intervalto retrieve the messages.The interface allows filtering the messages by subsystem and prioritylevel, this could be implemented later on.Signed-off-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt;Reviewed-by: Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;Tested-by: Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;Link: https://lore.kernel.org/r/20230908-topic-sm8550-upstream-pdcharge-ulog-v1-1-d1b16b02ced2@linaro.orgSigned-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Fri, 08 Sep 2023 10:53:49 +0000</pubDate>
        <dc:creator>Neil Armstrong &lt;neil.armstrong@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>84e9c58c - soc: qcom: Move power-domain drivers to the genpd dir</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#84e9c58c</link>
        <description>soc: qcom: Move power-domain drivers to the genpd dirTo simplify with maintenance let&apos;s move the qcom power-domain drivers tothe new genpd directory. Going forward, patches are intended to be managedthrough a separate git tree, according to MAINTAINERS.Cc: Bjorn Andersson &lt;andersson@kernel.org&gt;Cc: Konrad Dybcio &lt;konrad.dybcio@linaro.org&gt;Cc: Andy Gross &lt;agross@kernel.org&gt;Cc: &lt;linux-arm-msm@vger.kernel.org&gt;Acked-by: Bjorn Andersson &lt;andersson@kernel.org&gt;Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Wed, 05 Jul 2023 15:23:33 +0000</pubDate>
        <dc:creator>Ulf Hansson &lt;ulf.hansson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>8ddfa81d - soc: qcom: Add RPM processor/subsystem driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#8ddfa81d</link>
        <description>soc: qcom: Add RPM processor/subsystem driverAdd a simple driver for the qcom,rpm-proc compatible that registers the&quot;smd-edge&quot; and populates other children defined in the device tree.Note that the DT schema belongs to the remoteproc subsystem while thisdriver is added inside soc/qcom. I argue that the RPM *is* a remoteproc,but as an implementation detail in Linux it can currently not benefitfrom anything provided by the remoteproc subsystem. The RPM firmware isusually already loaded and started by earlier components in the bootchain and is not meant to be ever restarted.To avoid breaking existing kernel configurations the driver is alwaysbuilt when smd-rpm.c is also built. They belong closely together anyway.To avoid build errors CONFIG_RPMSG_QCOM_SMD must be also built-in ifrpm-proc is.Reviewed-by: Konrad Dybcio &lt;konrad.dybcio@linaro.org&gt;Signed-off-by: Stephan Gerhold &lt;stephan@gerhold.net&gt;Link: https://lore.kernel.org/r/20230531-rpm-rproc-v3-9-a07dcdefd918@gerhold.netSigned-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Thu, 15 Jun 2023 16:50:42 +0000</pubDate>
        <dc:creator>Stephan Gerhold &lt;stephan@gerhold.net&gt;</dc:creator>
    </item>
<item>
        <title>47820d32 - soc: qcom: Rename ice to qcom_ice to avoid module name conflict</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#47820d32</link>
        <description>soc: qcom: Rename ice to qcom_ice to avoid module name conflictThe following error was reported when building x86_64 allmodconfig:error: the following would cause module name conflict:  drivers/soc/qcom/ice.ko  drivers/net/ethernet/intel/ice/ice.koSeems the &apos;ice&apos; module name is already used by some Intel ethernetdriver, so lets rename the Qualcomm Inline Crypto Engine (ICE) modulefrom &apos;ice&apos; to &apos;qcom_ice&apos; to avoid any kind of errors/confusions.Reported-by: Stephen Rothwell &lt;sfr@canb.auug.org.au&gt;Fixes: 2afbf43a4aec (&quot;soc: qcom: Make the Qualcomm UFS/SDCC ICE a dedicated driver&quot;)Acked-by: Mukesh Ojha &lt;quic_mojha@quicinc.com&gt;Signed-off-by: Abel Vesa &lt;abel.vesa@linaro.org&gt;Signed-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;Link: https://lore.kernel.org/r/20230516082856.150214-1-abel.vesa@linaro.org

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Tue, 16 May 2023 08:28:56 +0000</pubDate>
        <dc:creator>Abel Vesa &lt;abel.vesa@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>a77b2a0b - soc: qcom: Introduce RPM master stats driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#a77b2a0b</link>
        <description>soc: qcom: Introduce RPM master stats driverIntroduce a driver to query and expose detailed, per-subsystem (as opposedto the existing qcom_stats driver which exposes SoC-wide data) about lowpower mode states of a given RPM master. That includes the APSS (ARM),MPSS (modem) and other remote cores, depending on the platformconfiguration.This is a vastly cleaned up and restructured version of a similardriver found in msm-5.4.Reviewed-by: Manivannan Sadhasivam &lt;mani@kernel.org&gt;Signed-off-by: Konrad Dybcio &lt;konrad.dybcio@linaro.org&gt;Signed-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;Link: https://lore.kernel.org/r/20230405-topic-master_stats-v6-2-2277b4433748@linaro.org

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Thu, 20 Apr 2023 17:36:18 +0000</pubDate>
        <dc:creator>Konrad Dybcio &lt;konrad.dybcio@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>2afbf43a - soc: qcom: Make the Qualcomm UFS/SDCC ICE a dedicated driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#2afbf43a</link>
        <description>soc: qcom: Make the Qualcomm UFS/SDCC ICE a dedicated driverThis takes the already existing duplicated support in both ufs-qcomand sdhci-msm drivers and makes it a dedicated driver that can be usedby both mentioned drivers.The reason for this is because, staring with SM8550, the ICE IP blockis shared between UFS and SDCC, which means we need to probe a dedicateddevice and share it between those two consumers.So let&apos;s add the ICE dedicated driver as a soc driver.Platforms that already have ICE supported, will use it as a libraryas the of_qcom_ice_get will return an ICE instance created for theconsumer device. This allows the backwards compatibility with old-styledevicetree approach.Also, add support to HW version 4.x since it works out-of-the-box withthe current driver. The 4.x HW version is found on SM8550 platform.Signed-off-by: Abel Vesa &lt;abel.vesa@linaro.org&gt;Reviewed-by: Bjorn Andersson &lt;andersson@kernel.org&gt;Signed-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;Link: https://lore.kernel.org/r/20230407105029.2274111-4-abel.vesa@linaro.org

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Fri, 07 Apr 2023 10:50:26 +0000</pubDate>
        <dc:creator>Abel Vesa &lt;abel.vesa@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>080b4e24 - soc: qcom: pmic_glink: Introduce altmode support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#080b4e24</link>
        <description>soc: qcom: pmic_glink: Introduce altmode supportWith the PMIC GLINK service, the host OS subscribes to USB-C altmodemessages, which are sent by the firmware to notify the host OS aboutstate updates and HPD interrupts.The pmic_glink_altmode driver registers for these notifications andpropagates the notifications as typec_mux, typec_switch and DRM OOBnotifications as necessary to implement DisplayPort altmode support.Signed-off-by: Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;Acked-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt;Tested-by: Konrad Dybcio &lt;konrad.dybcio@linaro.org&gt; # SM8350 PDX215Reviewed-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt;Tested-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt; # on SM8550-MTP &amp; SM8450-HDKSigned-off-by: Bjorn Andersson &lt;quic_bjorande@quicinc.com&gt;Signed-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;Link: https://lore.kernel.org/r/20230201041853.1934355-4-quic_bjorande@quicinc.com

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Wed, 01 Feb 2023 04:18:52 +0000</pubDate>
        <dc:creator>Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>58ef4ece - soc: qcom: pmic_glink: Introduce base PMIC GLINK driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#58ef4ece</link>
        <description>soc: qcom: pmic_glink: Introduce base PMIC GLINK driverThe PMIC GLINK service runs on one of the co-processors of some modernQualcomm platforms and implements USB-C and battery managements. It usesa message based protocol over GLINK for communication with the OS, hencethe name.The driver implemented provides the rpmsg device for communication anduses auxiliary bus to spawn off individual devices in respectivesubsystem. The auxiliary devices are spawned off from aplatform_device, so that the drm_bridge is available early, to allow theDisplayPort driver to probe even before the remoteproc has spun up.Signed-off-by: Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;Tested-by: Konrad Dybcio &lt;konrad.dybcio@linaro.org&gt; # SM8350 PDX215Reviewed-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt;Tested-by: Neil Armstrong &lt;neil.armstrong@linaro.org&gt; # on SM8550-MTP &amp; SM8450-HDKSigned-off-by: Bjorn Andersson &lt;quic_bjorande@quicinc.com&gt;Signed-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;Link: https://lore.kernel.org/r/20230201041853.1934355-3-quic_bjorande@quicinc.com

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Wed, 01 Feb 2023 04:18:51 +0000</pubDate>
        <dc:creator>Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>c5d52d7b - soc: qcom: dcc: Drop driver for now</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#c5d52d7b</link>
        <description>soc: qcom: dcc: Drop driver for nowArnd asks for the DCC driver to be dropped for now, in order to allowfor more thorough review, by a wider audience, of the ABI introduced.The Devicetree binding is adequately describing the hardware block, sothis is kept.Requested-by:  Arnd Bergmann &lt;arnd@arndb.de&gt;Signed-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Tue, 31 Jan 2023 02:30:54 +0000</pubDate>
        <dc:creator>Bjorn Andersson &lt;andersson@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>4cbe60cf - soc: qcom: dcc: Add driver support for Data Capture and Compare unit(DCC)</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#4cbe60cf</link>
        <description>soc: qcom: dcc: Add driver support for Data Capture and Compare unit(DCC)The DCC is a DMA Engine designed to capture and store dataduring system crash or software triggers. The DCC operatesbased on user inputs via the debugfs interface. The user givesaddresses as inputs and these addresses are stored in thedcc sram. In case of a system crash or a manual softwaretrigger by the user through the debugfs interface,the dcc captures and stores the values at these addresses.This patch contains the driver which has all the methodspertaining to the debugfs interface, auxiliary functions tosupport all the four fundamental operations of dcc namelyread, write, read/modify/write and loop. The probe methodhere instantiates all the resources necessary for dcc tooperate mainly the dedicated dcc sram where it stores thevalues. The DCC driver can be used for debugging purposeswithout going for a reboot since it can perform softwaretriggers as well based on user inputs.Also add the documentation for debugfs entries which explainsthe functionalities of each debugfs file that has been createdfor dcc.The following is the justification of using debugfs interfaceover the other alternatives like sysfs/ioctlsi) As can be seen from the debugfs attribute descriptions,some of the debugfs attribute files here contains multiplearguments which needs to be accepted from the user. This goesagainst the design style of sysfs.ii) The user input patterns have been made simple and convenientin this case with the use of debugfs interface as user doesn&apos;tneed to shuffle between different files to execute one instructionas was the case on using other alternatives.Signed-off-by: Souradeep Chowdhury &lt;quic_schowdhu@quicinc.com&gt;Reviewed-by: Alex Elder &lt;elder@linaro.org&gt;[bjorn: Fixed up a few indents and line wraps]Signed-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;Link: https://lore.kernel.org/r/644b4f66a358492a8a6738454035c3b120092fe7.1672148732.git.quic_schowdhu@quicinc.com

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Tue, 27 Dec 2022 15:22:46 +0000</pubDate>
        <dc:creator>Souradeep Chowdhury &lt;quic_schowdhu@quicinc.com&gt;</dc:creator>
    </item>
<item>
        <title>a723c95f - soc: qcom: Add Qualcomm Ramp Controller driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#a723c95f</link>
        <description>soc: qcom: Add Qualcomm Ramp Controller driverThe Ramp Controller is used to program the sequence ID for pulseswallowing, enable sequence and linking sequence IDs for the CPUcores on some Qualcomm SoCs.Signed-off-by: AngeloGioacchino Del Regno &lt;angelogioacchino.delregno@collabora.com&gt;Reviewed-by: Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;Signed-off-by: Bjorn Andersson &lt;andersson@kernel.org&gt;Link: https://lore.kernel.org/r/20221117132956.169432-3-angelogioacchino.delregno@collabora.com

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Thu, 17 Nov 2022 13:29:56 +0000</pubDate>
        <dc:creator>AngeloGioacchino Del Regno &lt;angelogioacchino.delregno@collabora.com&gt;</dc:creator>
    </item>
<item>
        <title>b9c2ae6c - soc: qcom: icc-bwmon: Add bandwidth monitoring driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#b9c2ae6c</link>
        <description>soc: qcom: icc-bwmon: Add bandwidth monitoring driverBandwidth monitoring (BWMON) sits between various subsytems like CPU,GPU, Last Level caches and memory subsystem.  The BWMON can beconfigured to monitor the data throuhput between memory and othersubsytems.  The throughput is measured within specified sampling windowand is used to vote for corresponding interconnect bandwidth.Current implementation brings support for BWMON v4, used for example onSDM845 to measure bandwidth between CPU (gladiator_noc) and Last LevelCache (memnoc).  Usage of this BWMON allows to remove fixed bandwidthvotes from cpufreq (CPU nodes) thus achieve high memory throughput evenwith lower CPU frequencies.The driver was tested on SDM845.Co-developed-by: Thara Gopinath &lt;thara.gopinath@gmail.com&gt;Signed-off-by: Thara Gopinath &lt;thara.gopinath@gmail.com&gt;Signed-off-by: Krzysztof Kozlowski &lt;krzysztof.kozlowski@linaro.org&gt;Signed-off-by: Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;Link: https://lore.kernel.org/r/20220704121730.127925-3-krzysztof.kozlowski@linaro.org

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Mon, 04 Jul 2022 12:17:28 +0000</pubDate>
        <dc:creator>Krzysztof Kozlowski &lt;krzysztof.kozlowski@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>1d772469 - soc: qcom: Add Sleep stats driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#1d772469</link>
        <description>soc: qcom: Add Sleep stats driverLet&apos;s add a driver to read the stats from remote processor andexport to debugfs.The driver creates &quot;qcom_sleep_stats&quot; directory in debugfs andadds files for various low power mode available. Below is sampleoutput with commandcat /sys/kernel/debug/qcom_sleep_stats/ddrcount = 0Last Entered At = 0Last Exited At = 0Accumulated Duration = 0Signed-off-by: Mahesh Sivasubramanian &lt;msivasub@codeaurora.org&gt;Signed-off-by: Lina Iyer &lt;ilina@codeaurora.org&gt;[mkshah: add subsystem sleep stats, create one file for each stat]Signed-off-by: Maulik Shah &lt;mkshah@codeaurora.org&gt;Tested-by: Shawn Guo &lt;shawn.guo@linaro.org&gt;Signed-off-by: Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;Link: https://lore.kernel.org/r/1634107104-22197-3-git-send-email-mkshah@codeaurora.org

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Wed, 13 Oct 2021 06:38:21 +0000</pubDate>
        <dc:creator>Mahesh Sivasubramanian &lt;msivasub@codeaurora.org&gt;</dc:creator>
    </item>
<item>
        <title>60f3692b - cpuidle: qcom_spm: Detach state machine from main SPM handling</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/soc/qcom/Makefile#60f3692b</link>
        <description>cpuidle: qcom_spm: Detach state machine from main SPM handlingIn commit a871be6b8eee (&quot;cpuidle: Convert Qualcomm SPM driver to a genericCPUidle driver&quot;) the SPM driver has been converted to ageneric CPUidle driver: that was mainly made to simplify thedriver and that was a great accomplishment;Though, at that time, this driver was only applicable to ARM 32-bit SoCs,lacking logic about the handling of newer generation SAW.In preparation for the enablement of SPM features on AArch64/ARM64,split the cpuidle-qcom-spm driver in two: the CPUIdle relatedstate machine (currently used only on ARM SoCs) stays there, whilethe SPM communication handling lands back in soc/qcom/spm.c andalso making sure to not discard the simplifications that wereintroduced in the aforementioned commit.Since now the &quot;two drivers&quot; are split, the SCM dependency in themain SPM handling is gone and for this reason it was also possibleto move the SPM initialization early: this will also make sure thatwhenever the SAW CPUIdle driver is getting initialized, the SPMdriver will be ready to do the job.Please note that the anticipation of the SPM initialization wasalso done to optimize the boot times on platforms that have theirCPU/L2 idle states managed by other means (such as PSCI), whileneeding SAW initialization for other purposes, like AVS control.Signed-off-by: AngeloGioacchino Del Regno &lt;angelogioacchino.delregno@somainline.org&gt;Reviewed-by: Stephan Gerhold &lt;stephan@gerhold.net&gt;Tested-by: Stephan Gerhold &lt;stephan@gerhold.net&gt;Acked-by: Daniel Lezcano &lt;daniel.lezcano@linaro.org&gt;Signed-off-by: Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;Link: https://lore.kernel.org/r/20210729155609.608159-2-angelogioacchino.delregno@somainline.org

            List of files:
            /linux-6.15/drivers/soc/qcom/Makefile</description>
        <pubDate>Thu, 29 Jul 2021 15:56:05 +0000</pubDate>
        <dc:creator>AngeloGioacchino Del Regno &lt;angelogioacchino.delregno@somainline.org&gt;</dc:creator>
    </item>
</channel>
</rss>
