<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/bus/ti-sysc.c, branch linux-4.18.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.18.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.18.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2018-10-03T23:59:22Z</updated>
<entry>
<title>bus: ti-sysc: Fix no_console_suspend handling</title>
<updated>2018-10-03T23:59:22Z</updated>
<author>
<name>Tony Lindgren</name>
</author>
<published>2018-08-08T08:07:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f7468a7160e1086a7960d6fea8735f49c3c3c900'/>
<id>urn:sha1:f7468a7160e1086a7960d6fea8735f49c3c3c900</id>
<content type='text'>
[ Upstream commit 4f3530f4a41d49c41015020cd9a5ed5c95b5d2db ]

If no_console_suspend is set, we should keep console enabled during suspend.
Lets fix this by only producing a warning if we can't idle hardware during
suspend.

Fixes: ef55f8215a78 ("bus: ti-sysc: Improve suspend and resume handling")
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bus: ti-sysc: Fix module register ioremap for larger offsets</title>
<updated>2018-10-03T23:59:21Z</updated>
<author>
<name>Tony Lindgren</name>
</author>
<published>2018-08-08T08:07:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=67eb28b0f832136b8af0a8f3d9831c450b4d20ae'/>
<id>urn:sha1:67eb28b0f832136b8af0a8f3d9831c450b4d20ae</id>
<content type='text'>
[ Upstream commit 0ef8e3bb974af56346b34393e643d491d9141c66 ]

We can have the interconnect target module control registers pretty
much anywhere within the module range. The current code attempts an
incomplete optimization of the ioremap size but does it wrong and
it only works for registers at the beginning of the module.

Let's just use the largest control register to calculate the ioremap
size. The ioremapped range is for most part cached anyways so there
is no need for size optimization. Let's also update the comments
accordingly.

Fixes: 0eecc636e5a2 ("bus: ti-sysc: Add minimal TI sysc interconnect
target driver")
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bus: ti-sysc: Use 2-factor allocator arguments</title>
<updated>2018-07-02T11:24:44Z</updated>
<author>
<name>Kees Cook</name>
</author>
<published>2018-06-18T17:45:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=207490517cf80d99f471d1b54e747eb95a4b8bea'/>
<id>urn:sha1:207490517cf80d99f471d1b54e747eb95a4b8bea</id>
<content type='text'>
This adjusts the allocator calls to use 2-factor argument call style, as
done treewide already for improved defense against allocation overflows.

Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
</content>
</entry>
<entry>
<title>bus: ti-sysc: Fix optional clocks array access</title>
<updated>2018-05-18T14:54:44Z</updated>
<author>
<name>Tony Lindgren</name>
</author>
<published>2018-05-18T14:54:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c97c8620833e4a55ddb7a43961d3205184a487f0'/>
<id>urn:sha1:c97c8620833e4a55ddb7a43961d3205184a487f0</id>
<content type='text'>
We should be checking ddata-&gt;clocks[i] instead of clock_names[i]
for the optional clocks. Currently this just happens to work for
the typical case of one fck and one optional clock.

Fixes: 09dfe5810762 ("bus: ti-sysc: Add handling for clkctrl opt clocks")
Cc: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Reported-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
</content>
</entry>
<entry>
<title>bus: ti-sysc: Show module information for suspend if DEBUG is enabled</title>
<updated>2018-05-01T13:54:17Z</updated>
<author>
<name>Tony Lindgren</name>
</author>
<published>2018-04-16T17:26:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dc4c85eac6bc8cfe25144936c5636aa1415bbc12'/>
<id>urn:sha1:dc4c85eac6bc8cfe25144936c5636aa1415bbc12</id>
<content type='text'>
Let's show module info if DEBUG is enabled to make it easier to follow
what happens on the suspend and resume path.

Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
</content>
</entry>
<entry>
<title>bus: ti-sysc: Tag sdio and wdt with legacy mode for suspend</title>
<updated>2018-05-01T13:54:17Z</updated>
<author>
<name>Tony Lindgren</name>
</author>
<published>2018-04-20T21:54:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7e27e5d05a13bdee494442faf3e78bd544d4ccdf'/>
<id>urn:sha1:7e27e5d05a13bdee494442faf3e78bd544d4ccdf</id>
<content type='text'>
Looks like these two device drivers don't yet behave properly for suspend
unless configured with the legacy option.

Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
</content>
</entry>
<entry>
<title>bus: ti-sysc: Detect UARTs for SYSC_QUIRK_LEGACY_IDLE quirk on omap4</title>
<updated>2018-05-01T13:54:17Z</updated>
<author>
<name>Tony Lindgren</name>
</author>
<published>2018-04-16T17:25:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d708bb14971ce797ac6d64aea19e2f8f41859f54'/>
<id>urn:sha1:d708bb14971ce797ac6d64aea19e2f8f41859f54</id>
<content type='text'>
Starting with omap4, UARTs have different revision register that we need to
detect to enable SYSC_QUIRK_LEGACY_IDLE. Otherwise UARTs won't idle properly.

Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
</content>
</entry>
<entry>
<title>bus: ti-sysc: Detect omap4 type timers for quirk</title>
<updated>2018-05-01T13:54:17Z</updated>
<author>
<name>Tony Lindgren</name>
</author>
<published>2018-04-16T17:25:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8cde5d5f7361fd152dd67df552596919d89ac404'/>
<id>urn:sha1:8cde5d5f7361fd152dd67df552596919d89ac404</id>
<content type='text'>
Starting with omap4 some timers have different sysc registers (type2) compared
to the omap2 timers (type1). We need to detect these to enable the quirk for
SYSC_QUIRK_LEGACY_IDLE, otherwise these won't be idling properly.

Siganed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
</content>
</entry>
<entry>
<title>bus: ti-sysc: Add initial support for external resets</title>
<updated>2018-05-01T13:54:17Z</updated>
<author>
<name>Tony Lindgren</name>
</author>
<published>2018-04-16T17:20:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5062236ec458768f61efc6d0a5198c395e55d097'/>
<id>urn:sha1:5062236ec458768f61efc6d0a5198c395e55d097</id>
<content type='text'>
Some modules need to use external resets in the rstctrl bits. Typically
only one of the rstctrl bits is for the interconnect target module while
the others are for various child devices.

For ti-sysc driver, we just need the module rstctrl bit mapped. The rest
of the rstctrl bits can be directly mapped to the child devices.

Cc: Suman Anna &lt;s-anna@ti.com&gt;
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
</content>
</entry>
<entry>
<title>bus: ti-sysc: Improve suspend and resume handling</title>
<updated>2018-05-01T13:54:17Z</updated>
<author>
<name>Tony Lindgren</name>
</author>
<published>2018-04-16T17:27:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ef55f8215a78b7021401281e8a7fe056fd5ecdab'/>
<id>urn:sha1:ef55f8215a78b7021401281e8a7fe056fd5ecdab</id>
<content type='text'>
Based on testing with more devices I noticed that some devices
don't suspend or resume properly. We need to PM runtime suspend
and resume devices if we have ddata-&gt;needs_resume set.

Let's also improve the error handling and add few debug statements
to make it easier to notice suspend and resume related issues if
DEBUG is set.

Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
</content>
</entry>
</feed>
