Re: Single SPI Protocol Driver with multiple SPI Slaves

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 06, 2017 at 01:49:25PM +0200, Lars-Peter Clausen wrote:

> There are currently no facilities in the kernel to do this. I've have had a
> similar problem with a different driver and given this some thought.

The kernel really can't cope with this at all, it's got a fairly clear
idea that a device will only have one control bus.

> Conceptually I think the best approach is to have something like
> i2c_new_dummy() that creates a second slave device with a different address
> for an existing device.

> The main issue with implementing this is the global spi_add_lock mutex which
> prevents a SPI device from being created from within the probe() callback of
> another SPI device.

There's also the devices that want to use multiple buses simultaneously
that cause problems here, it's not just SPI vs SPI - there's one audio
CODEC upstream that's got mixed I2C and SPI control.

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux