On 03/09/2017 09:08 PM, Mauro Carvalho Chehab wrote:
> Currently, IMX_VDOA and VIDEO_CODA only builds on ARCH_MXC.
>
> That prevented me to build-test the driver, causing a bad patch
> to be applied, and to see other warnings on this driver.
Huh, must be the time of year. I just made a similar pa
On 09/03/17 21:17, Mauro Carvalho Chehab wrote:
> drivers/media/platform/coda/coda-common.c: In function ‘coda_alloc_aux_buf’:
> ./include/linux/kern_levels.h:4:18: warning: format ‘%u’ expects argument of
> type ‘unsigned int’, but argument 4 has type ‘size_t {aka long unsigned int}’
> [-Wformat
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-by: Jonathan Cameron
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/Documentation/driver-
Hi!
This series is also available on gitlab in the mux branch of the repo
https://gitlab.com/peda-linux/mux.git
The series is also included in linux-next. v9 + tags from Rob was first in
next-20170307 and v10 will probably be in next-20170320. Or something like
that; there will be no lin
Comparing a size_t with less than zero is always false as size_t
is unsigned. So, change the type of the variable to ssize_t and
replicate the size check from mux_configure_channel() into
mux_write_ext_info() thus ensuring that the size will fit in the
ssize_t variable.
Detected by CoverityScan, C
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 parent iio channel, cre
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: Wolfram Sang
Signed-off-b
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 +++
2 files
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(+)
create mode 1006
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 Documentation/devicetree/binding
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 | 140 ++
3 files changed, 153 insertions(+)
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
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
controller.
A singl
Hi,
On Friday 10 March 2017 03:29 AM, Rami Rosen wrote:
> Hi,
> Minor comment: typo, should be: don't care:
Thanks for spotting this. Will fix it in my next revision.
Cheers
Kishon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.
On Thu, Mar 02, 2017 at 12:49:11AM +0530, Yury Norov wrote:
> The newer prlimit64 syscall provides all the functionality provided by
> the getrlimit and setrlimit syscalls and adds the pid of target process,
> so future architectures won't need to include getrlimit and setrlimit.
>
> Therefore dro
On Thu, Mar 9, 2017 at 2:29 PM, Michael S. Tsirkin wrote:
> Some guests call mwait without checking the cpu flags. We currently
"Some guests"? What guests other than Mac OS X are so ill-behaved?
> emulate that as a NOP but on VMX we can do better: let guest stop the
> CPU until timer or IPI. C
Support for ASPEED AST2400/AST2500 PWM and Fan Tach driver.
Patches based on the upstream tag 4.9. Changes made in Version 4 are indicated
in the individual patches.
The AST2400/AST2500 PWM controller can support 8 PWM output ports.
The AST2400/AST2500 Fan Tach controller can support 16 tachometer
The ASPEED AST2400/2500 PWM controller supports 8 PWM output ports.
The ASPEED AST2400/2500 Fan tach controller supports 16 tachometer inputs.
The device driver matches on the device tree node. The configuration values
are read from the device tree and written to the respective registers.
The drive
This binding provides interface for adding values related to ASPEED
AST2400/2500 PWM and Fan tach controller support.
The PWM controller can support upto 8 PWM output ports.
The Fan tach controller can support upto 16 tachometer inputs.
Signed-off-by: Jaghathiswari Rankappagounder Natarajan
---
20 matches
Mail list logo
