<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-linux/drivers/iio/dac, branch jd/unified-crypt-queue</title>
<subtitle>WireGuard for the Linux kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-linux/atom/drivers/iio/dac?h=jd%2Funified-crypt-queue</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-linux/atom/drivers/iio/dac?h=jd%2Funified-crypt-queue'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/'/>
<updated>2020-03-08T17:28:54Z</updated>
<entry>
<title>iio: dac: Kconfig: sort symbols alphabetically</title>
<updated>2020-03-08T17:28:54Z</updated>
<author>
<name>Alexandru Ardelean</name>
<email>alexandru.ardelean@analog.com</email>
</author>
<published>2020-03-04T13:55:44Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/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>
<email>alexandru.tachici@analog.com</email>
</author>
<published>2020-02-18T12:10:30Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/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>
<email>u.kleine-koenig@pengutronix.de</email>
</author>
<published>2020-02-03T20:31:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/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>
<email>u.kleine-koenig@pengutronix.de</email>
</author>
<published>2020-01-30T13:15:49Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/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>
<email>u.kleine-koenig@pengutronix.de</email>
</author>
<published>2020-01-30T13:15:48Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/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>
<email>colin.king@canonical.com</email>
</author>
<published>2020-01-23T09:19:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/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>
<email>etienne.carriere@st.com</email>
</author>
<published>2020-01-13T13:14:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/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>
<entry>
<title>iio: dac: stm32-dac: use reset controller only at probe time</title>
<updated>2020-01-18T14:30:15Z</updated>
<author>
<name>Etienne Carriere</name>
<email>etienne.carriere@st.com</email>
</author>
<published>2020-01-13T13:14:25Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=4a001c96b1c6d39831be3ef957968404be96d75e'/>
<id>urn:sha1:4a001c96b1c6d39831be3ef957968404be96d75e</id>
<content type='text'>
This change removes the reset controller reference from the local
DAC instance since it is used only at probe time.

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>
<entry>
<title>iio: ad5592r: Drop surplus GPIO header</title>
<updated>2019-12-15T11:42:16Z</updated>
<author>
<name>Linus Walleij</name>
<email>linus.walleij@linaro.org</email>
</author>
<published>2019-12-02T08:58:48Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=b747e352499e4fca6e2e824852f5d91f4e29bf0e'/>
<id>urn:sha1:b747e352499e4fca6e2e824852f5d91f4e29bf0e</id>
<content type='text'>
This driver uses all the modern GPIO APIs from
&lt;linux/gpio/driver.h&gt; and &lt;linux/gpio/consumer.h&gt; so
just drop the unused legacy header &lt;linux/gpio.h&gt;.

Signed-off-by: Linus Walleij &lt;linus.walleij@linaro.org&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: ad7303: use regulator get optional to check for ext supply</title>
<updated>2019-11-23T14:25:02Z</updated>
<author>
<name>Alexandru Tachici</name>
<email>alexandru.tachici@analog.com</email>
</author>
<published>2019-11-18T10:58:07Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=a8b26c2ddc83fab7f582405c468df2cbb9b5348a'/>
<id>urn:sha1:a8b26c2ddc83fab7f582405c468df2cbb9b5348a</id>
<content type='text'>
Previously, the code was using the of_read_property_bool() to check if
an external regulator was provided. However, this is redundant, as it's
more simple/direct to just ask the regulator is provided, via a
`devm_regulator_get_optional()` call.

Signed-off-by: Alexandru Tachici &lt;alexandru.tachici@analog.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
</feed>
