<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/iio/dac, branch linux-5.7.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.7.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.7.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2020-08-21T11:07:22Z</updated>
<entry>
<title>iio: dac: ad5592r: fix unbalanced mutex unlocks in ad5592r_read_raw()</title>
<updated>2020-08-21T11:07:22Z</updated>
<author>
<name>Alexandru Ardelean</name>
</author>
<published>2020-07-06T11:02:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=13d49c2043a3c9dc40ece310b57962f5afaeaefa'/>
<id>urn:sha1:13d49c2043a3c9dc40ece310b57962f5afaeaefa</id>
<content type='text'>
commit 65afb0932a81c1de719ceee0db0b276094b10ac8 upstream.

There are 2 exit paths where the lock isn't held, but try to unlock the
mutex when exiting. In these places we should just return from the
function.

A neater approach would be to cleanup the ad5592r_read_raw(), but that
would make this patch more difficult to backport to stable versions.

Fixes 56ca9db862bf3: ("iio: dac: Add support for the AD5592R/AD5593R ADCs/DACs")
Reported-by: Charles Stanhope &lt;charles.stanhope@gmail.com&gt;
Signed-off-by: Alexandru Ardelean &lt;alexandru.ardelean@analog.com&gt;
Cc: &lt;Stable@vger.kernel.org&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>iio: dac: vf610: Fix an error handling path in 'vf610_dac_probe()'</title>
<updated>2020-05-02T18:17:08Z</updated>
<author>
<name>Christophe JAILLET</name>
</author>
<published>2020-04-26T19:44:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=aad4742fbf0a560c25827adb58695a4497ffc204'/>
<id>urn:sha1:aad4742fbf0a560c25827adb58695a4497ffc204</id>
<content type='text'>
A call to 'vf610_dac_exit()' is missing in an error handling path.

Fixes: 1b983bf42fad ("iio: dac: vf610_dac: Add IIO DAC driver for Vybrid SoC")
Signed-off-by: Christophe JAILLET &lt;christophe.jaillet@wanadoo.fr&gt;
Cc: &lt;Stable@vger.kernel.org&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: dac: ad5770r: fix off-by-one check on maximum number of channels</title>
<updated>2020-04-19T16:50:01Z</updated>
<author>
<name>Colin Ian King</name>
</author>
<published>2020-04-03T12:58:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dd6230ba1d6b413f1a60301dbd554b90870aabc6'/>
<id>urn:sha1:dd6230ba1d6b413f1a60301dbd554b90870aabc6</id>
<content type='text'>
Currently there is an off-by-one check on the number of channels that
will cause an arry overrun in array st-&gt;output_mode when calling the
function d5770r_store_output_range. Fix this by using &gt;= rather than &gt;
to check for maximum number of channels.

Addresses-Coverity: ("Out-of-bounds access")
Fixes: cbbb819837f6 ("iio: dac: ad5770r: Add AD5770R support")
Signed-off-by: Colin Ian King &lt;colin.king@canonical.com&gt;
Reviewed-by: Alexandru Ardelean &lt;alexandru.ardelean@analog.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: dac: Kconfig: sort symbols alphabetically</title>
<updated>2020-03-08T17:28:54Z</updated>
<author>
<name>Alexandru Ardelean</name>
</author>
<published>2020-03-04T13:55:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fe297f8f048a7a0663479dcf6447ec450b53b905'/>
<id>urn:sha1:fe297f8f048a7a0663479dcf6447ec450b53b905</id>
<content type='text'>
While adding a new device, I noticed these aren't sorted alphabetically [as
in the Makefile], which messed my head-up.
This change sorts the devices alphabetically in the drivers/iio/dac/Kconfig
file as well.

Signed-off-by: Alexandru Ardelean &lt;alexandru.ardelean@analog.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: dac: ad5770r: Add AD5770R support</title>
<updated>2020-03-08T17:28:41Z</updated>
<author>
<name>Alexandru Tachici</name>
</author>
<published>2020-02-18T12:10:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cbbb819837f6a2e13808d0529d14be460a7a4a07'/>
<id>urn:sha1:cbbb819837f6a2e13808d0529d14be460a7a4a07</id>
<content type='text'>
The AD5770R is a 6-channel, 14-bit resolution, low noise, programmable
current output digital-to-analog converter (DAC) for photonics control
applications.

It contains five 14-bit resolution current sourcing DAC channels and one
14-bit resolution current sourcing/sinking DAC channel.

Signed-off-by: Mircea Caprioru &lt;mircea.caprioru@analog.com&gt;
Signed-off-by: Alexandru Tachici &lt;alexandru.tachici@analog.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: dac: ltc2632: remove some unused defines</title>
<updated>2020-02-14T15:06:24Z</updated>
<author>
<name>Uwe Kleine-König</name>
</author>
<published>2020-02-03T20:31:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=55f82c00b2f345eed031ed189b16b1b2d8689901'/>
<id>urn:sha1:55f82c00b2f345eed031ed189b16b1b2d8689901</id>
<content type='text'>
These two defines are unused since the driver was introduced in commit
02b829f9e11f ("iio: dac: Add support for ltc2632 DACs").

Signed-off-by: Uwe Kleine-König &lt;u.kleine-koenig@pengutronix.de&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: dac: ltc2632: add support for LTC2636 family</title>
<updated>2020-02-14T15:06:24Z</updated>
<author>
<name>Uwe Kleine-König</name>
</author>
<published>2020-01-30T13:15:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9f15a4a0adc910a7bd535b755185f89c3e25b37e'/>
<id>urn:sha1:9f15a4a0adc910a7bd535b755185f89c3e25b37e</id>
<content type='text'>
The only difference between LTC2632 and LTC2636 is that the former has
two DAC channels while the latter has eight.

Signed-off-by: Uwe Kleine-König &lt;u.kleine-koenig@pengutronix.de&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: dac: ltc2632: drop some duplicated data</title>
<updated>2020-02-14T15:06:23Z</updated>
<author>
<name>Uwe Kleine-König</name>
</author>
<published>2020-01-30T13:15:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f243d0f0bd16c281ba5cce19eae86b433257fc2a'/>
<id>urn:sha1:f243d0f0bd16c281ba5cce19eae86b433257fc2a</id>
<content type='text'>
The channel data for ltc2632l12 and ltc2632h12 are identical. So there
is no gain in using two different (but identical) channel descriptions.
The only side effect of this change is some memory savings.

Signed-off-by: Uwe Kleine-König &lt;u.kleine-koenig@pengutronix.de&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: ad5755: fix spelling mistake "to" -&gt; "too" and grammar plus formatting</title>
<updated>2020-02-14T12:08:22Z</updated>
<author>
<name>Colin Ian King</name>
</author>
<published>2020-01-23T09:19:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ebf7a1126717a19fb638806d37dbdf27124a272d'/>
<id>urn:sha1:ebf7a1126717a19fb638806d37dbdf27124a272d</id>
<content type='text'>
There is a spelling mistake and grammar mistake in a dev_err
message. Fix it.

Also include Joe Perches' additional suggestions around:
* Missing newlines
* Excess braces
* Odd indentation
* Some grammar

Signed-off-by: Colin Ian King &lt;colin.king@canonical.com&gt;
Reviewed-by: Alexandru Ardelean &lt;alexandru.ardelean@analog.com&gt;
Suggested-by: Joe Perches &lt;joe@perches.com&gt; # Additional cleanups etc.
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: dac: stm32-dac: better handle reset controller failures</title>
<updated>2020-01-18T14:32:01Z</updated>
<author>
<name>Etienne Carriere</name>
</author>
<published>2020-01-13T13:14:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d344961f55fd6321937d3bc92ad3930dea31189f'/>
<id>urn:sha1:d344961f55fd6321937d3bc92ad3930dea31189f</id>
<content type='text'>
Use devm_reset_control_get_optional_exclusive() instead of
devm_reset_control_get_exclusive() as reset controller is optional.

Nevertheless if reset controller is expected but reports an
error, propagate the error code to the caller. In such case
a nice error trace is emitted unless we're deferring the probe
operation.

Signed-off-by: Etienne Carriere &lt;etienne.carriere@st.com&gt;
Signed-off-by: Fabrice Gasnier &lt;fabrice.gasnier@st.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
</feed>
