Re: [PATCH 0/6] GPIO character device skeleton

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

 



On Thu, Nov 5, 2015 at 10:40 AM, Johan Hovold <johan@xxxxxxxxxx> wrote:
> On Tue, Nov 03, 2015 at 06:18:42PM +0100, Linus Walleij wrote:

>> It'd be nice if devices could be uniquely identified in the chardev alone
>> I think, then we don't need to much reliance on external assumptions
>> and traversing sysfs somehow for more info.
>
> Point is that this is not a gpio-specific problem. Userspace needs to
> deal with this for any resource it wants to access (e.g. i2c or spi).

Yeah let's see what others have to say.

> And you should be able to use libudev for tree-traversal without actually
> using udevd, right?

Well libudev depends on libsystemd and is using it's subcomponent
sd-device to traverse sysfs. It's a pretty fat dependency for a
space-constrained embedded system, and the source code is not
maintained outside systemd anymore, leading to an
all-or-nothing approach it seems to me.

I don't think it used to be like that but it is like that now...

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux SPI]     [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