<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/extcon, branch v5.1</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v5.1</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v5.1'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2019-04-05T01:08:37Z</updated>
<entry>
<title>extcon: ptn5150: fix COMPILE_TEST dependencies</title>
<updated>2019-04-05T01:08:37Z</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2019-03-06T11:08:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=86baf800de84eb89615c138d368b14bff5ee7d8a'/>
<id>urn:sha1:86baf800de84eb89615c138d368b14bff5ee7d8a</id>
<content type='text'>
The PTN5150 dependencies look like they were meant to do the
right thing, but they actually should not allow building without
I2C for compile testing, as that results in a Kconfig warning
and subsequent build failure:

WARNING: unmet direct dependencies detected for REGMAP_I2C
  Depends on [m]: I2C [=m]
  Selected by [y]:
  - EXTCON_PTN5150 [=y] &amp;&amp; EXTCON [=y] &amp;&amp; (I2C [=m] &amp;&amp; GPIOLIB [=y] || COMPILE_TEST [=y])
  Selected by [m]:
  - EEPROM_AT24 [=m] &amp;&amp; I2C [=m] &amp;&amp; SYSFS [=y]
  - KEYBOARD_CAP11XX [=m] &amp;&amp; !UML &amp;&amp; INPUT [=y] &amp;&amp; INPUT_KEYBOARD [=y] &amp;&amp; OF [=y] &amp;&amp; I2C [=m]
  - INPUT_DRV260X_HAPTICS [=m] &amp;&amp; !UML &amp;&amp; INPUT_MISC [=y] &amp;&amp; INPUT [=y] &amp;&amp; I2C [=m] &amp;&amp; (GPIOLIB [=y] || COMPILE_TEST [=y])
  - ... [many others]

Add parentheses around the expression so we can compile-test
without GPIOLIB but not without I2C.

Fixes: 4ed754de2d66 ("extcon: Add support for ptn5150 extcon driver")
Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;
</content>
</entry>
<entry>
<title>extcon: ptn5150: Fix return value check in ptn5150_i2c_probe()</title>
<updated>2019-02-11T08:21:38Z</updated>
<author>
<name>Wei Yongjun</name>
<email>weiyongjun1@huawei.com</email>
</author>
<published>2019-01-25T01:45:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3dfed89512d3b65f6f092cfaaee53b0698bbf75e'/>
<id>urn:sha1:3dfed89512d3b65f6f092cfaaee53b0698bbf75e</id>
<content type='text'>
In case of error, the function devm_gpiod_get() returns ERR_PTR() and
never returns NULL. The NULL test in the return value check should be
replaced with IS_ERR().

Signed-off-by: Wei Yongjun &lt;weiyongjun1@huawei.com&gt;
Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;
</content>
</entry>
<entry>
<title>extcon: Add support for ptn5150 extcon driver</title>
<updated>2019-02-11T08:21:38Z</updated>
<author>
<name>Vijai Kumar K</name>
<email>vijaikumar.kanagarajan@gmail.com</email>
</author>
<published>2019-01-23T12:46:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4ed754de2d66084d4a7785f565d7c42ad89a3ea9'/>
<id>urn:sha1:4ed754de2d66084d4a7785f565d7c42ad89a3ea9</id>
<content type='text'>
PTN5150 is a small thin low power CC (Configurationn Channel)
Logic chip supporting the USB Type-C connector application with
CC control logic detection and indication functions.

Signed-off-by: Vijai Kumar K &lt;vijaikumar.kanagarajan@gmail.com&gt;
[cw00.choi: Fix bulid dependency and clean-up code]
Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;
</content>
</entry>
<entry>
<title>extcon: max8997: Fix lack of path setting in USB device mode</title>
<updated>2018-11-14T00:06:32Z</updated>
<author>
<name>Marek Szyprowski</name>
<email>m.szyprowski@samsung.com</email>
</author>
<published>2018-11-13T15:38:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a2dc50914744eea9f83a70a5db0486be625e5dc0'/>
<id>urn:sha1:a2dc50914744eea9f83a70a5db0486be625e5dc0</id>
<content type='text'>
MAX8997 driver disables automatic path selection from MicroUSB connector
and manually sets path to either UART or USB lines. However the code for
setting USB path worked only for USB host mode (when ID pin is set
to ground). When standard USB cable (USB device mode) is connected, path
registers are not touched. This means that once the non-USB accessory is
connected to MAX8997-operated micro USB port, the path is no longer set
to USB and USB device mode doesn't work. This patch fixes it by setting
USB path both for USB and USB host modes.

Signed-off-by: Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;
Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;
</content>
</entry>
<entry>
<title>extcon: max8997: Avoid forcing UART path on drive probe</title>
<updated>2018-11-12T00:17:13Z</updated>
<author>
<name>Marek Szyprowski</name>
<email>m.szyprowski@samsung.com</email>
</author>
<published>2018-11-08T13:45:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3e34c819896091d0f1bbf6ece8a620552f8dc04e'/>
<id>urn:sha1:3e34c819896091d0f1bbf6ece8a620552f8dc04e</id>
<content type='text'>
Driver unconditionally forces UART path during probe, probably to ensure
that one can get kernel serial log as soon as possible.

This approach causes some issues, especially when board is booted with
non-UART cable connected to micro-USB port. For example, when USB cable is
connected, UART TX/RX lines are unconditionally short-circuited to USB
D+/D- lines. This is in turn recognized by a series of serial BREAK
signals and some random characters when USB host tries to perform
enumeration procedure.

To solve the above issue and keep UART console operational as early as
possible, set UART path only when USB ID reports UART capable cable.

Signed-off-by: Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;
Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;
</content>
</entry>
<entry>
<title>extcon: max14577: Avoid forcing UART path on drive probe</title>
<updated>2018-11-12T00:17:13Z</updated>
<author>
<name>Marek Szyprowski</name>
<email>m.szyprowski@samsung.com</email>
</author>
<published>2018-11-08T13:45:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5a196c29bb27d606c4bd82f6893462a39766ff7a'/>
<id>urn:sha1:5a196c29bb27d606c4bd82f6893462a39766ff7a</id>
<content type='text'>
Driver unconditionally forces UART path during probe, probably to ensure
that one can get kernel serial log as soon as possible.

This approach causes some issues, especially when board is booted with
non-UART cable connected to micro-USB port. For example, when USB cable is
connected, UART TX/RX lines are unconditionally short-circuited to USB
D+/D- lines. This is in turn recognized by a series of serial BREAK
signals and some random characters when USB host tries to perform
enumeration procedure.

To solve the above issue and keep UART console operational as early as
possible, set UART path only when USB ID reports UART capable cable.

Signed-off-by: Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;
Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;
</content>
</entry>
<entry>
<title>extcon: max77693: Avoid forcing UART path on drive probe</title>
<updated>2018-11-12T00:17:13Z</updated>
<author>
<name>Marek Szyprowski</name>
<email>m.szyprowski@samsung.com</email>
</author>
<published>2018-11-08T13:45:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6865f2ef9d6576508498fe6127d252b22a70ab39'/>
<id>urn:sha1:6865f2ef9d6576508498fe6127d252b22a70ab39</id>
<content type='text'>
Driver unconditionally forces UART path during probe, probably to ensure
that one can get kernel serial log as soon as possible.

This approach causes some issues, especially when board is booted with
non-UART cable connected to micro-USB port. For example, when USB cable is
connected, UART TX/RX lines are unconditionally short-circuited to USB
D+/D- lines. This is in turn recognized by a series of serial BREAK
signals and some random characters when USB host tries to perform
enumeration procedure.

To solve the above issue and keep UART console operational as early as
possible, set UART path only when USB ID reports UART capable cable.

Signed-off-by: Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;
Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;
</content>
</entry>
<entry>
<title>extcon: max77843: Avoid forcing UART path on drive probe</title>
<updated>2018-11-12T00:17:13Z</updated>
<author>
<name>Marek Szyprowski</name>
<email>m.szyprowski@samsung.com</email>
</author>
<published>2018-11-08T13:45:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d9204acb37569579fc49af1689c0ae32bdd4710f'/>
<id>urn:sha1:d9204acb37569579fc49af1689c0ae32bdd4710f</id>
<content type='text'>
Driver unconditionally forces UART path during probe, probably to ensure
that one can get kernel serial log as soon as possible.

This approach causes some issues, especially when board is booted with
non-UART cable connected to micro-USB port. For example, when USB cable is
connected, UART TX/RX lines are unconditionally short-circuited to USB
D+/D- lines. This is in turn recognized by a series of serial BREAK
signals and some random characters when USB host tries to perform
enumeration procedure.

To solve the above issue and keep UART console operational as early as
possible, set UART path only when USB ID reports UART capable cable.

Signed-off-by: Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;
Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;
</content>
</entry>
<entry>
<title>extcon: int3496: Convert to use SPDX identifier</title>
<updated>2018-08-28T02:21:15Z</updated>
<author>
<name>Andy Shevchenko</name>
<email>andriy.shevchenko@linux.intel.com</email>
</author>
<published>2018-08-27T15:35:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=2e464ff0a9b1ab0fbb56e2ca8b1f5ff8c9f4e02f'/>
<id>urn:sha1:2e464ff0a9b1ab0fbb56e2ca8b1f5ff8c9f4e02f</id>
<content type='text'>
Convert driver to use SPDX identifier.

While here, fix MODULE_LICENSE() string to be the same as license text states.

Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;
</content>
</entry>
<entry>
<title>extcon: cht-wc: Convert to use SPDX identifier</title>
<updated>2018-08-28T02:21:15Z</updated>
<author>
<name>Andy Shevchenko</name>
<email>andriy.shevchenko@linux.intel.com</email>
</author>
<published>2018-08-27T15:35:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=900ed55571941c5b61869954dc96e082e2ded78d'/>
<id>urn:sha1:900ed55571941c5b61869954dc96e082e2ded78d</id>
<content type='text'>
Convert driver to use SPDX identifier.

Signed-off-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;
</content>
</entry>
</feed>
