<?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 ti-sysc.c</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>1fac9f8b - bus: Switch back to struct platform_driver::remove()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#1fac9f8b</link>
        <description>bus: Switch back to struct platform_driver::remove()After commit 0edb555a65d1 (&quot;platform: Make platform_driver::remove()return void&quot;) .remove() is (again) the right callback to implement forplatform drivers.Convert all platform drivers below drivers/bus to use .remove(), withthe eventual goal to drop struct platform_driver::remove_new(). As.remove() and .remove_new() have the same prototypes, conversion is doneby just changing the structure member name in the driver initializer.Signed-off-by: Uwe Kleine-K&#246;nig &lt;u.kleine-koenig@baylibre.com&gt;Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Tue, 12 Nov 2024 08:35:19 +0000</pubDate>
        <dc:creator>Uwe Kleine-K&#246;nig &lt;u.kleine-koenig@baylibre.com&gt;</dc:creator>
    </item>
<item>
        <title>a80a3d92 - bus: ti-sysc: Remove excess struct member &apos;disable_on_idle&apos; description</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#a80a3d92</link>
        <description>bus: ti-sysc: Remove excess struct member &apos;disable_on_idle&apos; descriptionWhen built with W=1, the driver throws the following warning:../drivers/bus/ti-sysc.c:169: warning: Excess struct member&apos;disable_on_idle&apos; description in &apos;sysc&apos;Fix it by removing the excess description.Signed-off-by: Dhruva Gole &lt;d-gole@ti.com&gt;Reviewed-by: Roger Quadros &lt;rogerq@kernel.org&gt;Link: https://lore.kernel.org/r/20240805101118.427133-1-d-gole@ti.comSigned-off-by: Kevin Hilman &lt;khilman@baylibre.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Mon, 05 Aug 2024 10:11:18 +0000</pubDate>
        <dc:creator>Dhruva Gole &lt;d-gole@ti.com&gt;</dc:creator>
    </item>
<item>
        <title>0070dc29 - bus: ti-sysc: Use of_property_present()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#0070dc29</link>
        <description>bus: ti-sysc: Use of_property_present()Use of_property_present() to test for property presence rather thanof_get_property(). This is part of a larger effort to remove callersof of_get_property() and similar functions. of_get_property() leaksthe DT property data pointer which is a problem for dynamicallyallocated nodes which may be freed.The code was also incorrectly assigning the return value to a &apos;structproperty&apos; pointer. It didn&apos;t matter as &quot;prop&quot; was never dereferenced.Signed-off-by: Rob Herring (Arm) &lt;robh@kernel.org&gt;Reviewed-by: Roger Quadros &lt;rogerq@kernel.org&gt;Link: https://lore.kernel.org/r/20240731191312.1710417-1-robh@kernel.orgSigned-off-by: Kevin Hilman &lt;khilman@baylibre.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Wed, 31 Jul 2024 19:12:39 +0000</pubDate>
        <dc:creator>Rob Herring (Arm) &lt;robh@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>9722c3b6 - of: remove internal arguments from of_property_for_each_u32()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#9722c3b6</link>
        <description>of: remove internal arguments from of_property_for_each_u32()The of_property_for_each_u32() macro needs five parameters, two of whichare primarily meant as internal variables for the macro itself (in thefor() clause). Yet these two parameters are used by a few drivers, and thiscan be considered misuse or at least bad practice.Now that the kernel uses C11 to build, these two parameters can be avoidedby declaring them internally, thus changing this pattern:  struct property *prop;  const __be32 *p;  u32 val;  of_property_for_each_u32(np, &quot;xyz&quot;, prop, p, val) { ... }to this:  u32 val;  of_property_for_each_u32(np, &quot;xyz&quot;, val) { ... }However two variables cannot be declared in the for clause even with C11,so declare one struct that contain the two variables we actually need. Asthe variables inside this struct are not meant to be used by users of thismacro, give the struct instance the noticeable name &quot;_it&quot; so it is visibleduring code reviews, helping to avoid new code to use it directly.Most usages are trivially converted as they do not use those twoparameters, as expected. The non-trivial cases are: - drivers/clk/clk.c, of_clk_get_parent_name(): easily doable anyway - drivers/clk/clk-si5351.c, si5351_dt_parse(): this is more complex as the   checks had to be replicated in a different way, making code more verbose   and somewhat uglier, but I refrained from a full rework to keep as much   of the original code untouched having no hardware to test my changesAll the changes have been build tested. The few for which I have thehardware have been runtime-tested too.Reviewed-by: Andre Przywara &lt;andre.przywara@arm.com&gt; # drivers/clk/sunxi/clk-simple-gates.c, drivers/clk/sunxi/clk-sun8i-bus-gates.cAcked-by: Bartosz Golaszewski &lt;bartosz.golaszewski@linaro.org&gt; # drivers/gpio/gpio-brcmstb.cAcked-by: Nicolas Ferre &lt;nicolas.ferre@microchip.com&gt; # drivers/irqchip/irq-atmel-aic-common.cAcked-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt; # drivers/iio/adc/ti_am335x_adc.cAcked-by: Uwe Kleine-K&#246;nig &lt;u.kleine-koenig@baylibre.com&gt; # drivers/pwm/pwm-samsung.cAcked-by: Richard Leitner &lt;richard.leitner@linux.dev&gt; # drivers/usb/misc/usb251xb.cAcked-by: Mark Brown &lt;broonie@kernel.org&gt; # sound/soc/codecs/arizona.cReviewed-by: Richard Fitzgerald &lt;rf@opensource.cirrus.com&gt; # sound/soc/codecs/arizona.cAcked-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt; # arch/powerpc/sysdev/xive/spapr.cAcked-by: Stephen Boyd &lt;sboyd@kernel.org&gt; # clkSigned-off-by: Luca Ceresoli &lt;luca.ceresoli@bootlin.com&gt;Acked-by: Lee Jones &lt;lee@kernel.org&gt;Link: https://lore.kernel.org/r/20240724-of_property_for_each_u32-v3-1-bea82ce429e2@bootlin.comSigned-off-by: Rob Herring (Arm) &lt;robh@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Wed, 24 Jul 2024 16:33:06 +0000</pubDate>
        <dc:creator>Luca Ceresoli &lt;luca.ceresoli@bootlin.com&gt;</dc:creator>
    </item>
<item>
        <title>4bcc2e91 - bus: ti-sysc: Drop legacy idle quirk handling</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#4bcc2e91</link>
        <description>bus: ti-sysc: Drop legacy idle quirk handlingThere are no more users that need the legacy idle quirk so let&apos;s dropthe legacy idle quirk handling. This simplifies the PM code to justsysc_pm_ops with unified handling for all the interconnect targets.Reviewed-by: Dhruva Gole &lt;d-gole@ti.com&gt;Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Thu, 11 Apr 2024 04:44:30 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>2414277f - bus: ti-sysc: Drop legacy quirk handling for smartreflex</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#2414277f</link>
        <description>bus: ti-sysc: Drop legacy quirk handling for smartreflexWith the smartreflex driver no longer relying on the use ofpm_runtime_irq_safe(), we can finally drop the related legacy quirkhandling.Reviewed-by: Dhruva Gole &lt;d-gole@ti.com&gt;Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Thu, 11 Apr 2024 04:44:30 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>5f711f03 - bus: ti-sysc: Drop legacy quirk handling for uarts</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#5f711f03</link>
        <description>bus: ti-sysc: Drop legacy quirk handling for uartsWith the 8250_omap and omap-serial drivers no longer relying on the useof pm_runtime_irq_safe(), we can finally drop the related legacy quirkhandling for uarts.Reviewed-by: Dhruva Gole &lt;d-gole@ti.com&gt;Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Thu, 11 Apr 2024 04:44:30 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>5a85fd3c - bus: ti-sysc: Add a description and copyrights</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#5a85fd3c</link>
        <description>bus: ti-sysc: Add a description and copyrightsThe ti-sysc driver is missing coprights and description, let&apos;s addthose.Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Thu, 11 Apr 2024 04:44:30 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>f2bd2761 - bus: ti-sysc: Move check for no-reset-on-init</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#f2bd2761</link>
        <description>bus: ti-sysc: Move check for no-reset-on-initWe are wrongly checking SYSC_QUIRK_NO_RESET_ON_INIT flag in sysc_reset(),it can be called also after init from sysc_reinit_module(). Let&apos;s movethe check to the init code in preparation for adding reset control supportin the future.Note that this change is not needed as a fix as there are no known issuescaused by it currently.Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Thu, 11 Apr 2024 04:44:30 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>097948af - bus: ti-sysc: constify the struct device_type usage</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#097948af</link>
        <description>bus: ti-sysc: constify the struct device_type usageSince commit aed65af1cc2f (&quot;drivers: make device_type const&quot;), the drivercore can properly handle constant struct device_type. Move thesysc_device_type variable to be a constant structure as well, placing itinto read-only memory which can not be modified at runtime.Cc: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Signed-off-by: Ricardo B. Marliere &lt;ricardo@marliere.net&gt;Message-ID: &lt;20240219-device_cleanup-ti-sysc-v1-1-13b53177d0a5@marliere.net&gt;Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Mon, 19 Feb 2024 12:10:00 +0000</pubDate>
        <dc:creator>Ricardo B. Marliere &lt;ricardo@marliere.net&gt;</dc:creator>
    </item>
<item>
        <title>999f052e - bus: ti-sysc: Convert to platform remove callback returning void</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#999f052e</link>
        <description>bus: ti-sysc: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it&apos;s possible to do error handling byreturning an error code. However the value returned is ignored (apartfrom emitting a warning) and this typically results in resource leaks.To improve here there is a quest to make the remove callback returnvoid. In the first step of this quest all drivers are converted to.remove_new(), which already returns void. Eventually after all driversare converted, .remove_new() will be renamed to .remove().Trivially convert this driver from always returning zero in the removecallback to the void returning variant.Reviewed-by: Tony Lindgren &lt;tony@atomide.com&gt;Link: https://lore.kernel.org/r/20231109202830.4124591-12-u.kleine-koenig@pengutronix.deSigned-off-by: Uwe Kleine-K&#246;nig &lt;u.kleine-koenig@pengutronix.de&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Thu, 09 Nov 2023 20:28:41 +0000</pubDate>
        <dc:creator>Uwe Kleine-K&#246;nig &lt;u.kleine-koenig@pengutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>f71f6ff8 - bus: ti-sysc: Flush posted write only after srst_udelay</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#f71f6ff8</link>
        <description>bus: ti-sysc: Flush posted write only after srst_udelayCommit 34539b442b3b (&quot;bus: ti-sysc: Flush posted write on enable beforereset&quot;) caused a regression reproducable on omap4 duovero where the ISStarget module can produce interconnect errors on boot. Turns out theregisters are not accessible until after a delay for devices needinga ti,sysc-delay-us value.Let&apos;s fix this by flushing the posted write only after the reset delay.We do flushing also for ti,sysc-delay-us using devices as that shouldtrigger an interconnect error if the delay is not properly configured.Let&apos;s also add some comments while at it.Fixes: 34539b442b3b (&quot;bus: ti-sysc: Flush posted write on enable before reset&quot;)Cc: stable@vger.kernel.orgSigned-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Fri, 24 Nov 2023 08:50:56 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>e5deb8f7 - bus: ti-sysc: Fix SYSC_QUIRK_SWSUP_SIDLE_ACT handling for uart wake-up</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#e5deb8f7</link>
        <description>bus: ti-sysc: Fix SYSC_QUIRK_SWSUP_SIDLE_ACT handling for uart wake-upThe uarts should be tagged with SYSC_QUIRK_SWSUP_SIDLE instead ofSYSC_QUIRK_SWSUP_SIDLE_ACT. The difference is that SYSC_QUIRK_SWSUP_SIDLEis used to force idle target modules rather than block idle during usage.The SYSC_QUIRK_SWSUP_SIDLE_ACT should disable autoidle and wake-up whena target module is active, and configure autoidle and wake-up when atarget module is inactive. We are missing configuring the target moduleon sysc_disable_module(), and missing toggling of the wake-up bit.Let&apos;s fix the issue to allow uart wake-up to work.Fixes: fb685f1c190e (&quot;bus: ti-sysc: Handle swsup idle mode quirks&quot;)Tested-by: Dhruva Gole &lt;d-gole@ti.com&gt;Tested-by: Kevin Hilman &lt;khilman@baylibre.com&gt;Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Thu, 07 Sep 2023 05:53:28 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>11729caa - bus: ti-sysc: Fix missing AM35xx SoC matching</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#11729caa</link>
        <description>bus: ti-sysc: Fix missing AM35xx SoC matchingCommit feaa8baee82a (&quot;bus: ti-sysc: Implement SoC revision handling&quot;)created a list of SoC types searching for strings based on namesand wildcards which associates the SoC to different families.The OMAP34xx and OMAP35xx are treated as SOC_3430 whileOMAP36xx and OMAP37xx are treated as SOC_3630, but the AM35xxisn&apos;t listed.The AM35xx is mostly an OMAP3430, and a later commit a12315d6d270(&quot;bus: ti-sysc: Make omap3 gpt12 quirk handling SoC specific&quot;) looksfor the SOC type and behaves in a certain way if it&apos;s SOC_3430.This caused a regression on the AM3517 causing it to return twoerrors: ti-sysc: probe of 48318000.target-module failed with error -16 ti-sysc: probe of 49032000.target-module failed with error -16Fix this by treating the creating SOC_AM35 and inserting it betweenthe SOC_3430 and SOC_3630.  If it is treaed the same way as theSOC_3430 when checking the status of sysc_check_active_timer,the error conditions will disappear.Fixes: a12315d6d270 (&quot;bus: ti-sysc: Make omap3 gpt12 quirk handling SoC specific&quot;)Fixes: feaa8baee82a (&quot;bus: ti-sysc: Implement SoC revision handling&quot;)Signed-off-by: Adam Ford &lt;aford173@gmail.com&gt;Message-ID: &lt;20230906233442.270835-1-aford173@gmail.com&gt;Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Wed, 06 Sep 2023 23:34:42 +0000</pubDate>
        <dc:creator>Adam Ford &lt;aford173@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d929b2b7 - bus: ti-sysc: Use fsleep() instead of usleep_range() in sysc_reset()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#d929b2b7</link>
        <description>bus: ti-sysc: Use fsleep() instead of usleep_range() in sysc_reset()The am335x-evm started producing boot errors because of subtle timingchanges:Unhandled fault: external abort on non-linefetch (0x1008) at 0xf03c1010...sysc_reset from sysc_probe+0xf60/0x1514sysc_probe from platform_probe+0x5c/0xbc...The fix consists in using the appropriate sleep function in sysc reset.For flexible sleeping, fsleep is recommended. Here, sysc delay parametercan take any value in [0 - 255] us range. As a result, fsleep() shouldbe used, calling udelay() for a sysc delay lower than 10 us.Signed-off-by: Julien Panis &lt;jpanis@baylibre.com&gt;Fixes: e709ed70d122 (&quot;bus: ti-sysc: Fix missing reset delay handling&quot;)Message-ID: &lt;20230821-fix-ti-sysc-reset-v1-1-5a0a5d8fae55@baylibre.com&gt;Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Mon, 21 Aug 2023 14:24:18 +0000</pubDate>
        <dc:creator>Julien Panis &lt;jpanis@baylibre.com&gt;</dc:creator>
    </item>
<item>
        <title>de44bf2f - bus: ti-sysc: Fix cast to enum warning</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#de44bf2f</link>
        <description>bus: ti-sysc: Fix cast to enum warningFix warning for &quot;cast to smaller integer type &apos;enum sysc_soc&apos; from &apos;constvoid *&apos;&quot;.Cc: Nishanth Menon &lt;nm@ti.com&gt;Reported-by: kernel test robot &lt;lkp@intel.com&gt;Closes: https://lore.kernel.org/oe-kbuild-all/202308150723.ziuGCdM3-lkp@intel.com/Fixes: e1e1e9bb9d94 (&quot;bus: ti-sysc: Fix build warning for 64-bit build&quot;)Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Tue, 15 Aug 2023 05:49:05 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>40a4f49c - bus: ti-sysc: Fix a build warning with W=1 for sysconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#40a4f49c</link>
        <description>bus: ti-sysc: Fix a build warning with W=1 for sysconfigDhruva reported a build warning with W=1 for &quot;Function parameter or member&apos;sysconfig&apos; not described in &apos;sysc&apos;&quot;. Let&apos;s document sysconfig to fix this.Reported-by: Dhruva Gole &lt;d-gole@ti.com&gt;Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Wed, 09 Aug 2023 09:53:23 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>03a711d3 - bus: ti-sysc: Configure uart quirks for k3 SoC</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#03a711d3</link>
        <description>bus: ti-sysc: Configure uart quirks for k3 SoCEnable the uart quirks similar to the earlier SoCs. Let&apos;s assume we arelikely going to need a k3 specific quirk mask separate from the earlierSoCs, so let&apos;s not start changing the revision register mask at this point.Note that SYSC_QUIRK_LEGACY_IDLE will be needed until we can remove theneed for pm_runtime_irq_safe() from 8250_omap driver.Reviewed-by: Nishanth Menon &lt;nm@ti.com&gt;Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Fri, 04 Aug 2023 10:38:01 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>e1e1e9bb - bus: ti-sysc: Fix build warning for 64-bit build</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#e1e1e9bb</link>
        <description>bus: ti-sysc: Fix build warning for 64-bit buildFix &quot;warning: cast from pointer to integer of different size&quot; on 64-bitbuilds.Note that this is a cosmetic fix at this point as the driver is not yetused for 64-bit systems.Fixes: feaa8baee82a (&quot;bus: ti-sysc: Implement SoC revision handling&quot;)Reviewed-by: Dhruva Gole &lt;d-gole@ti.com&gt;Reviewed-by: Nishanth Menon &lt;nm@ti.com&gt;Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Fri, 04 Aug 2023 10:38:01 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
<item>
        <title>34539b44 - bus: ti-sysc: Flush posted write on enable before reset</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bus/ti-sysc.c#34539b44</link>
        <description>bus: ti-sysc: Flush posted write on enable before resetThe am335x devices started producing boot errors for resetting musb modulein because of subtle timing changes:Unhandled fault: external abort on non-linefetch (0x1008)...sysc_poll_reset_sysconfig from sysc_reset+0x109/0x12sysc_reset from sysc_probe+0xa99/0xeb0...The fix is to flush posted write after enable before reset duringprobe. Note that some devices also need to specify the delay after enablewith ti,sysc-delay-us, but this is not needed for musb on am335x based onmy tests.Reported-by: kernelci.org bot &lt;bot@kernelci.org&gt;Closes: https://storage.kernelci.org/next/master/next-20230614/arm/multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y/gcc-10/lab-cip/baseline-beaglebone-black.htmlFixes: 596e7955692b (&quot;bus: ti-sysc: Add support for software reset&quot;)Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;

            List of files:
            /linux-6.15/drivers/bus/ti-sysc.c</description>
        <pubDate>Wed, 14 Jun 2023 07:18:23 +0000</pubDate>
        <dc:creator>Tony Lindgren &lt;tony@atomide.com&gt;</dc:creator>
    </item>
</channel>
</rss>
