[PATCH 2/3] arm: tegra: enable igb, stmpe, i2c chardev, spidev, lm95245, pwm leds
Marcel Ziswiler
marcel at ziswiler.com
Tue Jun 3 23:20:59 PDT 2014
- Previous message: [PATCH 2/3] arm: tegra: enable igb, stmpe, i2c chardev, spidev, lm95245, pwm leds
- Next message: [PATCH 2/3] arm: tegra: enable igb, stmpe, i2c chardev, spidev, lm95245, pwm leds
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On 06/03/2014 11:45 AM, Mark Brown wrote:
> When you say "generic user space access" you are describing a specific
> detail of how this device happens to be controlled with your software.
No, not at all. In fact I did not even specify neither the exact type of
device apart from it being a SPI device nor any property of the software
apart from the generic user space access thereof implemented in the
Linux kernel. I really don't see any difference to i2c chardev which is
already enabled in multi_v7_defconfig.
> This is not a description of your hardware, it is a description of how
> it is controlled with your current software.
Sorry, but I really don't know what you are referring to. It's a pure
hardware description of some pins being the SPI bus namely MISO/MOSI and
the clock plus an accompanying chip-select pin.
I fear for some reason or another you have some affinity against spidev
which strikes me odd. Admittedly it is not perfect but it is the only
generic SPI user space access currently implemented in the Linux kernel
and so far did its job perfectly for many of our customers.
- Previous message: [PATCH 2/3] arm: tegra: enable igb, stmpe, i2c chardev, spidev, lm95245, pwm leds
- Next message: [PATCH 2/3] arm: tegra: enable igb, stmpe, i2c chardev, spidev, lm95245, pwm leds
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the linux-arm-kernel
mailing list