[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPoCmY+mNYSV8gq7VCcSJHDpmoq-i7SDJ6uQ5VbLpMZB=b0waQ@mail.gmail.com>
Date: Fri, 28 Sep 2018 17:19:18 -0700
From: Gottfried Haider <gottfried.haider@...il.com>
To: Thierry Reding <thierry.reding@...il.com>
Cc: fabrice.gasnier@...com, stefan.wahren@...e.com,
gohai@...zessiv.net,
H Hartley Sweeten <hsweeten@...ionengravers.com>,
loic.pallardy@...com, broonie@...nel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rpi-kernel@...ts.infradead.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-pwm@...r.kernel.org, michal.vokac@...ft.com
Subject: Re: [RESEND PATCH] Revert "pwm: Set class for exported channels in sysfs"
Hello Thierry & Fabrice,
>> Still, it is possible to send uevent (KOBJ_CHANGE) on pwmchipN device,
>> to notify of a change, e.g. pwmX channel being exported/unexported.
I tested this patch, and I am happy to report that it works with the
udev rule that Raspbian (Raspberry Pi's Debian derivative) has in
place:
SUBSYSTEM=="pwm*", PROGRAM="/bin/sh -c '\
chown -R root:gpio /sys/class/pwm && chmod -R 770 /sys/class/pwm;\
chown -R root:gpio
/sys/devices/platform/soc/*.pwm/pwm/pwmchip* && chmod -R 770
/sys/devices/platform/soc/*.pwm/pwm/pwmchip*\
'"
So while I can't comment on the uevent semantics, it would solve what
the original patch attempted to enable (non-root use of pwm).
Tested-by: Gottfried Haider <gottfried.haider@...il.com>
Best,
Gottfried
Powered by blists - more mailing lists