Hi!
Now that some other patches [1][2] have finally landed in -next, I
feel that it is time for this cleanup series that I have been hoarding
for a while waiting on those (weak) dependencies.
Cheers,
Peter
[1] https://lkml.org/lkml/2018/8/24/187
[2] https://lkml.org/lkml/2018/8/25/64
Peter
AT91_PINCTRL_OUTPUT_VAL(0) without AT91_PINCTRL_OUTPUT is a no-op, so
make sure the pins really output a zero.
Fixes: 0e4323899973 ("ARM: dts: at91: add devicetree for the Axentia Nattis
with Natte power")
Signed-off-by: Peter Rosin
---
arch/arm/boot/dts/at91-nattis-2-natte-2.dts | 6
The cd-gpios signal is assumed active-low by the driver, and the
cd-inverted property is needed if it is, in fact, active-high. Fix
this oversight.
Fixes: 0e4323899973 ("ARM: dts: at91: add devicetree for the Axentia Nattis
with Natte power")
Signed-off-by: Peter Rosin
---
arch/ar
Make the DT usable with the panel-lvds driver.
Signed-off-by: Peter Rosin
---
arch/arm/boot/dts/at91-nattis-2-natte-2.dts | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/at91-nattis-2-natte-2.dts
b/arch/arm/boot/dts/at91-nattis-2
Just to be explicit.
Signed-off-by: Peter Rosin
---
arch/arm/boot/dts/at91-nattis-2-natte-2.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/at91-nattis-2-natte-2.dts
b/arch/arm/boot/dts/at91-nattis-2-natte-2.dts
index 4308a07b792e..fbc796125c56 100644
On 2018-08-08 11:08, Andy Shevchenko wrote:
> On Wed, Aug 8, 2018 at 11:30 AM, Hans de Goede wrote:
>> On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node
>> per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1
>> i2c-device.
>>
>> But in some rare cas
On 2018-08-08 12:01, Andy Shevchenko wrote:
> On Wed, Aug 8, 2018 at 12:47 PM, Peter Rosin wrote:
>> On 2018-08-08 11:08, Andy Shevchenko wrote:
>>> On Wed, Aug 8, 2018 at 11:30 AM, Hans de Goede wrote:
>
>>>> + /* Count number of clients to insta
On 2018-08-21 01:43, Janusz Krzysztofik wrote:
> Most users of get/set array functions iterate consecutive bits of data,
> usually a single integer, while or processing array of results obtained
> from or building an array of values to be passed to those functions.
> Save time wasted on those itera
r symmetry
- reformatted comments a little bit
- spelling/grammar fixes
Peter Rosin (2):
drm/atmel-hlcdc: prefer a higher rate clock as pixel-clock base
drm/atmel-hlcdc: allow selecting a higher pixel-clock than requested
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 30 +++
base, the divider instead ends
up as 5 yielding a pixel-clock of 52.8Mhz, which is a definite
improvement.
While at it, clamp the divider so that it does not overflow in case
it gets big.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 18 +++---
1 file
On 2018-07-25 16:19, tip-bot for Peter Rosin wrote:
> Commit-ID: 7b94ea50514d1a0dc94f02723b603c27bc0ea597
> Gitweb:
> https://git.kernel.org/tip/7b94ea50514d1a0dc94f02723b603c27bc0ea597
> Author: Peter Rosin
> AuthorDate: Fri, 20 Jul 2018 10:39:14 +0200
> Commi
adap->timeout);
> +
> + spin_lock_irqsave(&i2c_dev->lock, flags);
> + if (time_left == 0) {
> + dev_err(&adap->dev, "Transaction timed out");
> + /* Send stop condition and release the bus */
> + owl_i2c_up
On 2018-07-19 15:43, Mircea Caprioru wrote:
> This patch adds basic support for Analog Device ADGS1408/09 SPI mux
> controller.
>
> The device is probed and set to a disabled state. It uses the new mux
> controller framework.
>
> Signed-off-by: Mircea Caprioru
> ---
> Changelog V2 -> V3
> - remo
On 2018-07-19 19:44, Manivannan Sadhasivam wrote:
> Add Actions Semiconductor Owl family S900 I2C driver.
>
> Signed-off-by: Manivannan Sadhasivam
> Acked-by: Peter Rosin
Ooops, now I noticed some missing newlines in your dbg_* prints. That
may produce garbled output, which is
m.
Cheers,
Peter
Peter Rosin (2):
rtmutex: allow specifying a subclass for nested locking
i2c: mux: annotate the nested rt_mutex usage
drivers/i2c/i2c-core-base.c | 2 +-
drivers/i2c/i2c-mux.c | 4 ++--
include/linux/rtmutex.h | 7 +++
kernel/locking/rtmutex
Needed for annotating rt_mutex locks.
Tested-by: John Sperbeck
Signed-off-by: Peter Rosin
---
include/linux/rtmutex.h | 7 +++
kernel/locking/rtmutex.c | 29 +
2 files changed, 32 insertions(+), 4 deletions(-)
diff --git a/include/linux/rtmutex.h b/include
Sperbeck
Signed-off-by: Peter Rosin
---
drivers/i2c/i2c-core-base.c | 2 +-
drivers/i2c/i2c-mux.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
index f5ec6ec6776f..1157a64c7be3 100644
--- a/drivers/i2c/i2c-core
On 2018-07-20 10:52, Arnd Bergmann wrote:
> On Thu, Jul 19, 2018 at 5:29 PM, Boris Brezillon
> wrote:
>
>> - the bus element is a separate object and is not implicitly described
>> by the master (as done in I2C). The reason is that I want to be able
>> to handle multiple master connected to t
On 2018-07-20 10:11, Mircea Caprioru wrote:
> This patch adds basic support for Analog Device ADGS1408/09 SPI mux
> controller.
>
> The device is probed and set to a disabled state. It uses the new mux
> controller framework.
>
> Signed-off-by: Mircea Caprioru
> ---
> Changelog V3 -> V4
> - name
On 2018-07-23 05:40, Manivannan Sadhasivam wrote:
> + /* Handle the remaining bytes which were not sent */
> + while (!(readl(i2c_dev->base + OWL_I2C_REG_FIFOSTAT) &
> +OWL_I2C_FIFOSTAT_TFF) && i2c_dev->msg_ptr < msg->len) {
You moved the OWL_ line to th
On 2018-07-23 09:24, Andy Shevchenko wrote:
> On Mon, Jul 23, 2018 at 9:12 AM, Peter Rosin wrote:
>> On 2018-07-23 05:40, Manivannan Sadhasivam wrote:
>>> + /* Handle the remaining bytes which were not sent */
>>> + while (!(readl(i2c_dev-&
controller]
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/mux/adi,adgs1408.txt | 48 ++
MAINTAINERS| 6 +++
2 files changed, 54 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mux/adi,adgs1408.txt
diff
From: Mircea Caprioru
This patch adds basic support for Analog Device ADGS1408/09 SPI mux
controller.
The device is probed and set to a disabled state. It uses the new mux
controller framework.
Signed-off-by: Mircea Caprioru
Signed-off-by: Peter Rosin
---
drivers/mux/Kconfig| 10
Hi Greg,
Here's a new mux driver for v4.19-rc1. It's been in -next for a
couple of days, and the risk is low since it is a completely
new driver with no strange entanglements. And it's tiny.
There was a report from -next about a trivial conflict in MAINTAINERS,
but I guess that's more or less sta
On 2018-07-12 10:08, Arnd Bergmann wrote:
> On Thu, Jul 12, 2018 at 6:41 AM, Peter Rosin wrote:
>> On 2018-07-11 19:12, Boris Brezillon wrote:
>>> On Wed, 11 Jul 2018 17:39:56 +0200 Arnd Bergmann wrote:
>>>
>>> That's exactly the sort of discussion I
Hi!
Thanks for your patches!
Please add a space after "mux:" in the subject. And the second part should
generally be the driver name and the text should not start with a capital
letter. So, I'd like the subject to be:
[...] mux: adgs1408: new driver for Analog Devices ADGS1408/1409 mux
On 2018-
On 2018-07-14 16:02, Lars-Peter Clausen wrote:
> On 07/14/2018 02:04 PM, Peter Rosin wrote:
> [...]
>>> +static int adgs140x_spi_reg_write(struct spi_device *spi,
>>> + u8 reg_addr, u8 reg_data)
>>> +{
>>> + u8 tx_
Hi Bartosz,
On 2018-01-24 22:34, Bartosz Golaszewski wrote:
> We now require all at24 users to use the "atmel," fallback in
> device tree for different manufacturers.
I think my patch [3/4] from about a week ago was just a tiny bit
better.
https://lkml.org/lkml/2018/1/16/609
Can we please pick t
As is, a failure message is printed unconditionally, which is confusing.
And noisy.
Fixes: 8d4d159f25a7 ("i2c: mux: provide more info on failure in
i2c_mux_add_adapter")
Signed-off-by: Peter Rosin
---
drivers/i2c/i2c-mux.c | 24 ++--
1 file changed, 14 inserti
From: Peter Rosin
Everything else is indented with two spaces, so fix the odd one out.
Acked-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
Documentation/driver-model/devres.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/driver-model/devres.txt
b
From: Peter Rosin
Hi Greg,
Philipp found problems in v14 with using a mutex for locking that was
the outcome of the review for v13, so I'm now using a semaphore instead
of the rwsem that was in v13. That at least got rid of the scary call
to downgrade_write. However, I'm still unsure
From: Peter Rosin
Analog Devices ADG792A/G is a triple 4:1 mux.
Acked-by: Jonathan Cameron
Reviewed-by: Rob Herring
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/mux/adi,adg792a.txt| 75 ++
1 file changed, 75 insertions(+)
create mode 100644
From: Peter Rosin
Describe how a general purpose multiplexer controller is used to mux an
i2c bus.
Acked-by: Jonathan Cameron
Reviewed-by: Rob Herring
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/i2c/i2c-mux-gpmux.txt | 99 ++
1 file changed, 99 insertions
From: Philipp Zabel
This adds device tree binding documentation for mmio-based syscon
multiplexers controlled by a bitfields in a syscon register range.
Signed-off-by: Philipp Zabel
Acked-by: Rob Herring
Signed-off-by: Peter Rosin
---
Documentation/devicetree/bindings/mux/mmio-mux.txt | 60
From: Peter Rosin
Allow specifying that a single multiplexer controller can be used to
control several parallel multiplexers, thus enabling sharing of the
multiplexer controller by different consumers.
Add a binding for a first mux controller in the form of a GPIO based mux
controller.
Acked
From: Peter Rosin
When a multiplexer changes how an iio device behaves (for example
by feeding different signals to an ADC), this driver can be used
to create one virtual iio channel for each multiplexer state.
Depends on the generic multiplexer subsystem.
Cache any ext_info values from the
From: Philipp Zabel
This adds a driver for mmio-based syscon multiplexers controlled by
bitfields in a syscon register range.
Signed-off-by: Philipp Zabel
Signed-off-by: Peter Rosin
---
drivers/mux/Kconfig| 13 +
drivers/mux/Makefile | 1 +
drivers/mux/mux-mmio.c | 141
From: Peter Rosin
Extend the inkern api with functions for reading and writing ext_info
of iio channels.
Acked-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
drivers/iio/inkern.c | 60
include/linux/iio/consumer.h | 37
From: Peter Rosin
This is a general purpose i2c mux that uses a multiplexer controlled by
the multiplexer subsystem to do the muxing.
The user can select if the mux is to be mux-locked and parent-locked
as described in Documentation/i2c/i2c-topology.
Acked-by: Jonathan Cameron
Acked-by
From: Peter Rosin
Describe how a multiplexer can be used to select which signal is fed to
an io-channel.
Acked-by: Jonathan Cameron
Acked-by: Rob Herring
Signed-off-by: Peter Rosin
---
.../bindings/iio/multiplexer/io-channel-mux.txt| 39 ++
MAINTAINERS
From: Peter Rosin
Analog Devices ADG792A/G is a triple 4:1 mux.
Reviewed-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
drivers/mux/Kconfig | 12
drivers/mux/Makefile | 1 +
drivers/mux/mux-adg792a.c | 157 ++
3 files
From: Peter Rosin
Add a new minimalistic subsystem that handles multiplexer controllers.
When multiplexers are used in various places in the kernel, and the
same multiplexer controller can be used for several independent things,
there should be one place to implement support for said multiplexer
From: Peter Rosin
The driver builds a single multiplexer controller using a number
of gpio pins. For N pins, there will be 2^N possible multiplexer
states. The GPIO pins can be connected (by the hardware) to several
multiplexers, which in that case will be operated in parallel.
Reviewed-by
On 2017-05-15 06:53, Leon Romanovsky wrote:
> On Sun, May 14, 2017 at 06:41:13PM +0200, Peter Rosin wrote:
>> As is, a failure message is printed unconditionally, which is confusing.
>> And noisy.
>>
>> Fixes: 8d4d159f25a7 ("i2c: mux: provide more info on fa
As is, a failure message is printed unconditionally, which is confusing.
And noisy.
Fixes: 8d4d159f25a7 ("i2c: mux: provide more info on failure in
i2c_mux_add_adapter")
Signed-off-by: Peter Rosin
---
drivers/i2c/i2c-mux.c | 26 --
1 file changed, 16 inserti
On 2018-01-29 18:38, Adrian Fiergolski wrote:
>>> On 22.01.2018 at 12:36, Peter Rosin wrote:
>>>> This series tries to check the I2C device id, but instead of open
>>>> coding the check in the pca954x driver, I have a new function in
>>>> the core doing
Make sure to not disallow the chips on adapters that are not capable
of reading the device id.
Signed-off-by: Peter Rosin
---
drivers/i2c/muxes/i2c-mux-pca954x.c | 43 +
1 file changed, 43 insertions(+)
diff --git a/drivers/i2c/muxes/i2c-mux-pca954x.c
b
chips.
Also, I'm not sure if I should list all manufacturers that I know
about in the header, or if I should settle for the one that is
actually used and leave the others to be added by whomever needs
them...
Cheers,
peda
Peter Rosin (2):
i2c: add i2c_get_device_id() to get the standar
Can be used during probe to double check that the probed device is
what is expected.
Loosely based on code from Adrian Fiergolski .
Signed-off-by: Peter Rosin
---
drivers/i2c/i2c-core-base.c | 33 +
include/linux/i2c.h | 30
I don't know for certain...
> Next week I will try to align only me i2c subdirectory with upstream.
> Provided it compiles, I will
> try then to apply and confirm your patches.
I'm looking forward to feedback, thanks!
Cheers,
Peter
> Regards,
> Adrian
>
> On 22.01.
Hi!
I have found that the drivers/mux/gpio.c driver fails to get
the required gpio pins when I test with next-20180116.
The driver calls devm_gpiod_get_array() during probe and that
request returns -EPROBE_DEFER in three probes long after the pinctrl
driver has been registered (verified with a fe
On 2018-01-16 17:30, Alexandre Belloni wrote:
> Hi,
>
> On 16/01/2018 at 17:08:33 +0100, Peter Rosin wrote:
>> The nattis currently relies on the cmdline to correctly configure the
>> MTD partition table, and the one given in the device tree is simply
>> ignored. Wh
On 2018-01-17 00:18, Linus Walleij wrote:
> On Tue, Jan 16, 2018 at 10:47 PM, Peter Rosin wrote:
>
>> diff between the two:
>>
>> --- bootlog.good2018-01-16 22:39:29.196022434 +0100
>> +++ bootlog.bad 2018-01-16 22:39:51.474264534 +0100
>> @@
On 2018-01-17 09:27, Rafał Miłecki wrote:
> On 2018-01-16 14:28, Peter Rosin wrote:
>> When trying next-20180116 I get the following panic during boot:
>>
>> Linux version 4.15.0-rc8-next-20180116 (peda@orc) (gcc version 4.9.2
>> 20140811 (prerelease) (crosstool-N
On 2018-01-17 10:35, Linus Walleij wrote:
> On Wed, Jan 17, 2018 at 12:57 AM, Peter Rosin wrote:
>> On 2018-01-17 00:18, Linus Walleij wrote:
>
>>> I think gpiod_set_transitory() calls chip->set_config(chip, gpio, packed);
>>> which calls gpio
Hi!
This series mainly fixes the gpio interaction, as discussed
in [1]. However, patch 1/3 addresses a problem that was not
mentioned there. It should probably be sent to stable...
Cheers,
Peter
[1] https://lkml.org/lkml/2018/1/16/952
Peter Rosin (3):
pinctrl: sx150x: unregister the pinctrl
Various gpiolib activity depend on the pinctrl to be up and kicking.
Therefore, register the pinctrl before adding a gpiochip.
Suggested-by: Linus Walleij
Signed-off-by: Peter Rosin
---
drivers/pinctrl/pinctrl-sx150x.c | 35 +--
1 file changed, 21 insertions
Without such a range, gpiolib fails with -EPROBE_DEFER, pending the
addition of the range. So, without a range, gpiolib will keep
deferring indefinitely.
Fixes: e10f72bf4b3e ("gpio: gpiolib: Generalise state persistence beyond sleep")
Suggested-by: Linus Walleij
Signed-off-by: P
There is no matching call to pinctrl_unregister, so switch to the
managed devm_pinctrl_register to clean up properly when done.
Fixes: 9e80f9064e73 ("pinctrl: Add SX150X GPIO Extender Pinctrl Driver")
Signed-off-by: Peter Rosin
---
drivers/pinctrl/pinctrl-sx150x.c | 2 +-
1 file
On 2018-01-17 16:05, Andrew Jeffery wrote:
> On Wed, 2018-01-17 at 14:34 +0100, Peter Rosin wrote:
>> Without such a range, gpiolib fails with -EPROBE_DEFER, pending the
>> addition of the range. So, without a range, gpiolib will keep
>> deferring indefinitely.
>>
&g
On 2018-01-18 08:58, Linus Walleij wrote:
> On Wed, Jan 17, 2018 at 2:34 PM, Peter Rosin wrote:
>
>> Without such a range, gpiolib fails with -EPROBE_DEFER, pending the
>> addition of the range. So, without a range, gpiolib will keep
>> deferring indefinitely.
>>
The lvds encoder chip was omitted by oversight. Add it.
Fixes: 0e4323899973 ("ARM: dts: at91: add devicetree for the Axentia Nattis
with Natte power")
Signed-off-by: Peter Rosin
---
arch/arm/boot/dts/at91-nattis-2-natte-2.dts | 31 ++---
1 file changed, 28
The node is referred to as a DAI from the sound node and should
therefore have a #sound-dai-cells property.
Fixes: 21dd0ece34c2 ("ARM: dts: at91: add devicetree for the Axentia TSE-850")
Signed-off-by: Peter Rosin
---
arch/arm/boot/dts/at91-tse850-3.dts | 1 +
1 file changed, 1
uld be 504MB, as the flash is 512MB total.
Sorry for the noise.
Cheers,
Peter
Peter Rosin (3):
ARM: dts: at91: nattis: use up-to-date mtd partitions
ARM: dts: at91: nattis: add lvds-encoder
ARM: dts: at91: tse850: make the sound dai cell count explicit
arch/arm/boot/dts/at91-natti
partition table
to match what is expected (i.e. what is normally provided on the cmdline).
In particular, the rootfs partition should be mtd6.
Fixes: 0e4323899973 ("ARM: dts: at91: add devicetree for the Axentia Nattis
with Natte power")
Signed-off-by: Peter Rosin
---
arch/arm/boo
From: Hans de Goede
class_find_device already does a get_device on the returned device.
So the device returned by of_find_mux_chip_by_node is already referenced
and we should not reference it again (and unref it on error).
Signed-off-by: Hans de Goede
Signed-off-by: Peter Rosin
---
drivers
: Peter Rosin
---
drivers/mux/Kconfig | 1 +
drivers/mux/Makefile | 1 +
drivers/mux/adg792a.c| 5 +
drivers/mux/core.c | 5 +
drivers/mux/gpio.c | 5 +
drivers/mux/mmio.c | 5 +
include/linux/mux/consumer.h | 5 +
include
On 2018-01-09 12:28, Philippe CORNU wrote:
> Hi all,
>
> Do you think the patch is "acceptable" or should I change it somehow?
> Any opinion is welcomed : )
Maybe you should try Daniel Vetter? He was very helpful (thanks) when
I worked on the clut changes...
Cheers,
Peter
Hi!
When trying next-20180116 I get the following panic during boot:
Linux version 4.15.0-rc8-next-20180116 (peda@orc) (gcc version 4.9.2 20140811
(prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.08 - Linaro GCC 4.9-2014.08))
#208 Tue Jan 16 14:23:44 CET 2018
CPU: ARMv7 Processor [410fc051] re
On 2018-01-16 14:36, Boris Brezillon wrote:
> Hi Peter,
>
> On Tue, 16 Jan 2018 14:28:38 +0100
> Peter Rosin wrote:
>
>> Hi!
>>
>> When trying next-20180116 I get the following panic during boot:
>>
>> Linux version 4.15.0-rc8-next-20180116 (peda@orc
On 2018-01-16 15:21, Boris Brezillon wrote:
> On Tue, 16 Jan 2018 14:56:52 +0100
> Peter Rosin wrote:
>
>> Hmmm, I guess the question is if the command line should override the
>> device tree or not?
>
> Yep, that's the problem. Now the core parses the compatibl
Makes them easier to find.
Signed-off-by: Peter Rosin
---
Documentation/devicetree/bindings/eeprom/at24.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/eeprom/at24.txt
b/Documentation/devicetree/bindings/eeprom/at24.txt
index
The used part does contain an eeprom compatible with an Atmel 24c02
chip and it is from NXP, but it is not called 24c02. It's actually a
se97b chip. Adjust the compatible accordingly.
Fixes: 21dd0ece34c2 ("ARM: dts: at91: add devicetree for the Axentia TSE-850")
Signed-off-
)
Signed-off-by: Peter Rosin
---
arch/arm/boot/dts/at91-nattis-2-natte-2.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/at91-nattis-2-natte-2.dts
b/arch/arm/boot/dts/at91-nattis-2-natte-2.dts
index 3ea1d26e1c68..c457eff25911 100644
--- a/arch/arm/boot/dt
The datasheet talks about the chip being an spd, but the chip is writable
so atmel,24c02 is more appropriate as fallback.
Signed-off-by: Peter Rosin
---
Documentation/devicetree/bindings/eeprom/at24.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/eeprom
Hi!
Here's a series that is of the "documentation" kind. It fixes things
that don't really need fixing, but the fixes are correct none-the-less
and should prevent possible confusion.
Cheers,
Peter
Peter Rosin (3):
ARM: dts: at91: nattis: use up-to-date mtd partitions
AR
atmel,24c02"
This series takes care of that, and throws in a sorting patch while at it.
Cheers,
Peter
Peter Rosin (4):
dt-bindings: at24: sort manufacturers alphabetically
dt-bindings: at24: add compatible for nxp,se97b
ARM: dts: at91: nattis: use the correct compatible for the eeprom
A
The lvds encoder chip was omitted by oversight. Add it.
Fixes: 0e4323899973 ("ARM: dts: at91: add devicetree for the Axentia Nattis
with Natte power")
Signed-off-by: Peter Rosin
---
arch/arm/boot/dts/at91-nattis-2-natte-2.dts | 31 ++---
1 file changed, 28
The node is referred to as a DAI from the sound node and should
therefore have a #sound-dai-cells property.
Fixes: 21dd0ece34c2 ("ARM: dts: at91: add devicetree for the Axentia TSE-850")
Signed-off-by: Peter Rosin
---
arch/arm/boot/dts/at91-tse850-3.dts | 1 +
1 file changed, 1
partition table
to match what is expected (i.e. what is normally provided on the cmdline).
In particular, the rootfs partition should be mtd6.
Fixes: 0e4323899973 ("ARM: dts: at91: add devicetree for the Axentia Nattis
with Natte power")
Signed-off-by: Peter Rosin
---
arch/arm/boo
On 2018-03-05 21:58, Peter Rosin wrote:
> Hi!
>
> This series tries to check the I2C device id, but instead of open
> coding the check in the pca954x driver, I have a new function in
> the core doing the work.
>
> Changes since v1:
> - Added Tested-by tag from Adrian
&
On 2018-03-10 17:15, Jonathan Cameron wrote:
> On Thu, 8 Mar 2018 20:58:30 +0100
> Peter Rosin wrote:
>
>> Add support for Microchip digital potentiometers and rheostats
>> MCP4017, MCP4018, MCP4019
>>
>> They all have one wiper with 128 steps a
On 2018-03-05 16:53, Wolfram Sang wrote:
>
>> @@ -97,59 +98,83 @@ static const struct chip_desc chips[] = {
>> .nchans = 2,
>> .enable = 0x4,
>> .muxtype = pca954x_ismux,
>> +.id = { .manufacturer_id = I2C_DEVICE_ID_NONE },
>
> Can't we just leav
On 2018-03-05 16:51, Wolfram Sang wrote:
> On Mon, Jan 22, 2018 at 12:36:56PM +0100, Peter Rosin wrote:
>> Can be used during probe to double check that the probed device is
>> what is expected.
>>
>> Loosely based on code from Adrian Fiergolski .
>>
>> Sign
the i2c_smbus_xfer call
Wolfram: I'll send a pull with the first patch in a few days, to
allow for a second round of feedback now that the RFC marker is gone.
Cheers,
peda
Peter Rosin (2):
i2c: add i2c_get_device_id() to get the standard i2c device id
i2c: mux: pca954x: verify the device i
Make sure to not disallow the chips on adapters that are not capable
of reading the device id, but also make sure to check the device id
before writing to the chip.
Tested-by: Adrian Fiergolski
Signed-off-by: Peter Rosin
---
drivers/i2c/muxes/i2c-mux-pca954x.c | 55
Can be used during probe to double check that the probed device is
what is expected.
Loosely based on code from Adrian Fiergolski .
Tested-by: Adrian Fiergolski
Reviewed-by: Wolfram Sang
Signed-off-by: Peter Rosin
---
drivers/i2c/i2c-core-base.c | 33
Hi Laurent,
Thanks for the feedback!
On 2018-03-20 14:56, Laurent Pinchart wrote:
> Hi Peter,
>
> Thank you for the patch.
>
> On Sunday, 18 March 2018 00:15:24 EET Peter Rosin wrote:
>> Useful if the bridge does some kind of conversion of the bus format.
>>
&g
ed fbdev frame-buffer that can be
reused over and over. But to do that I need to tell the driver that
16-bpp is the preferred depth. Add a module parameter to do just that.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 18 +-
1 file changed, 17 in
ode. This is cleaner but requires
changes to all display controller drivers wishing to participate.
- Add patch to adjust the atmel-hlcdc driver according to the above.
- Hook the new info into the bridge local to the lvds-encoder instead
of messing about with new interfaces for the panel-br
Start list of actual chips compatible with "lvds-encoder".
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/display/bridge/lvds-transmitter.txt | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
a/Documentation/devicetree/bindings/display/b
Bridges may affect the required bus output format of the encoder, in
which case it may be wrong to use the output format of the panel or
connector as is. Add infrastructure to address this problem.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/drm_bridge.c | 32
If the bridge changes the bus format, allow this to be described in
the bridge, instead of providing false information about the bus
format of the connector or panel.
Signed-off-by: Peter Rosin
---
.../bindings/display/bridge/lvds-transmitter.txt | 6 ++
drivers/gpu/drm/bridge/lvds
Bridges may affect the required bus output format of the encoder, in
which case it may be wrong to use the output format of the panel or
connector as is. So, examine if any of the intermediate bridges needs
specific bus formats (if there are intermediate bridges).
Signed-off-by: Peter Rosin
Add a common API to parse display bus format strings into fourcc codes.
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/display/bus-format.txt | 35 +
drivers/gpu/drm/drm_of.c | 59 ++
include/drm/drm_of.h
On 2018-03-24 15:03, Jonathan Cameron wrote:
> On Mon, 19 Mar 2018 18:02:46 +0100
> Peter Rosin wrote:
>
>> If an ADC channel measures the midpoint of a voltage divider, the
>> interesting voltage is often the voltage over the full resistance.
>> E.g. if the full vol
On 2018-03-27 00:23, Rob Herring wrote:
> On Mon, Mar 19, 2018 at 06:02:45PM +0100, Peter Rosin wrote:
>> Allow linear scaling and modification of the type of an io-channel.
>>
>> When an ADC channel measures the midpoint of a voltage divider, the
>> interesting voltag
Hi Jacopo,
Thanks for the feedback!
On 2018-03-27 11:47, jacopo mondi wrote:
> Hi Peter,
>thanks for the patches
>
> On Mon, Mar 26, 2018 at 11:24:44PM +0200, Peter Rosin wrote:
>> Bridges may affect the required bus output format of the encoder, in
>> which case it
Hi Jacopo,
Thanks for you feedback!
On 2018-03-27 12:27, jacopo mondi wrote:
> Hi Peter, Laurent,
>thanks for the patches,
>
> On Mon, Mar 26, 2018 at 11:24:46PM +0200, Peter Rosin wrote:
>> If the bridge changes the bus format, allow this to be described in
>>
On 2018-03-27 11:47, jacopo mondi wrote:
>> + * RETURNS:
>> + * The number of bus input formats the bridge accepts. Zero means that
>> + * the chain of bridges are not converting the bus format and that the
>> + * format of the drm_connector should be used.
>
> How do we get to the connector forma
101 - 200 of 1862 matches
Mail list logo
