From: Thierry Reding <thierry.reding@gmail.com>
To: Fabrice Gasnier <fabrice.gasnier@st.com>
Cc: stefan.wahren@i2se.com, gohai@sukzessiv.net,
hsweeten@visionengravers.com, gottfried.haider@gmail.com,
loic.pallardy@st.com, broonie@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org
Subject: Re: [RESEND PATCH] Revert "pwm: Set class for exported channels in sysfs"
Date: Mon, 24 Sep 2018 13:53:01 +0200 [thread overview]
Message-ID: <20180924115301.GV21032@ulmo> (raw)
In-Reply-To: <1537538567-5377-1-git-send-email-fabrice.gasnier@st.com>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
On Fri, Sep 21, 2018 at 04:02:47PM +0200, Fabrice Gasnier wrote:
> This reverts commit 7e5d1fd75c3dde9fc10c4472b9368089d1b81d00 as it causes
> regression with multiple pwm chip. It creates a new entry in
> '/sys/class/pwm' every time a 'pwmX' is exported with 'echo X > export':
> - 1st time export will create an entry in /sys/class/pwm/pwmX
> - when another export happens on another pwmchip, it can't be created
> (e.g. -EEXIST)
>
> This also changes existing ABI (Documentation/ABI/testing/sysfs-class-pwm):
> - pmwX should be there: /sys/class/pwm/pwmchipN/pwmX
>
> Example on stm32 (stm32429i-eval) platform:
> $ ls /sys/class/pwm
> pwmchip0 pwmchip4
>
> $ cd /sys/class/pwm/pwmchip0/
> $ echo 0 > export
> $ ls /sys/class/pwm
> pwm0 pwmchip0 pwmchip4
>
> $ cd /sys/class/pwm/pwmchip4/
> $ echo 0 > export
> sysfs: cannot create duplicate filename '/class/pwm/pwm0'
> ...Exception stack follows...
>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
> ---
> drivers/pwm/sysfs.c | 1 -
> 1 file changed, 1 deletion(-)
Can we come up with an alternative that allows us to have both? We want
uevent and proper sysfs creation, or is that not possible?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] Revert "pwm: Set class for exported channels in sysfs"
Date: Mon, 24 Sep 2018 13:53:01 +0200 [thread overview]
Message-ID: <20180924115301.GV21032@ulmo> (raw)
In-Reply-To: <1537538567-5377-1-git-send-email-fabrice.gasnier@st.com>
On Fri, Sep 21, 2018 at 04:02:47PM +0200, Fabrice Gasnier wrote:
> This reverts commit 7e5d1fd75c3dde9fc10c4472b9368089d1b81d00 as it causes
> regression with multiple pwm chip. It creates a new entry in
> '/sys/class/pwm' every time a 'pwmX' is exported with 'echo X > export':
> - 1st time export will create an entry in /sys/class/pwm/pwmX
> - when another export happens on another pwmchip, it can't be created
> (e.g. -EEXIST)
>
> This also changes existing ABI (Documentation/ABI/testing/sysfs-class-pwm):
> - pmwX should be there: /sys/class/pwm/pwmchipN/pwmX
>
> Example on stm32 (stm32429i-eval) platform:
> $ ls /sys/class/pwm
> pwmchip0 pwmchip4
>
> $ cd /sys/class/pwm/pwmchip0/
> $ echo 0 > export
> $ ls /sys/class/pwm
> pwm0 pwmchip0 pwmchip4
>
> $ cd /sys/class/pwm/pwmchip4/
> $ echo 0 > export
> sysfs: cannot create duplicate filename '/class/pwm/pwm0'
> ...Exception stack follows...
>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
> ---
> drivers/pwm/sysfs.c | 1 -
> 1 file changed, 1 deletion(-)
Can we come up with an alternative that allows us to have both? We want
uevent and proper sysfs creation, or is that not possible?
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180924/fadb97fa/attachment.sig>
next prev parent reply other threads:[~2018-09-24 11:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 14:02 [RESEND PATCH] Revert "pwm: Set class for exported channels in sysfs" Fabrice Gasnier
2018-09-21 14:02 ` Fabrice Gasnier
2018-09-21 14:02 ` Fabrice Gasnier
2018-09-24 11:53 ` Thierry Reding [this message]
2018-09-24 11:53 ` Thierry Reding
2018-09-24 13:59 ` Fabrice Gasnier
2018-09-24 13:59 ` Fabrice Gasnier
2018-09-24 13:59 ` Fabrice Gasnier
2018-09-24 14:23 ` Thierry Reding
2018-09-24 14:23 ` Thierry Reding
2018-09-24 15:50 ` Fabrice Gasnier
2018-09-24 15:50 ` Fabrice Gasnier
2018-09-24 15:50 ` Fabrice Gasnier
2018-09-25 13:59 ` Fabrice Gasnier
2018-09-25 13:59 ` Fabrice Gasnier
2018-09-25 13:59 ` Fabrice Gasnier
2018-09-25 15:20 ` Thierry Reding
2018-09-25 15:20 ` Thierry Reding
2018-09-29 0:19 ` Gottfried Haider
2018-09-29 0:19 ` Gottfried Haider
2018-10-01 13:28 ` Fabrice Gasnier
2018-10-01 13:28 ` Fabrice Gasnier
2018-10-01 13:28 ` Fabrice Gasnier
-- strict thread matches above, loose matches on Subject: below --
2018-07-20 7:27 Fabrice Gasnier
2018-07-20 7:27 ` Fabrice Gasnier
2018-07-20 7:27 ` Fabrice Gasnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180924115301.GV21032@ulmo \
--to=thierry.reding@gmail.com \
--cc=broonie@kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=gohai@sukzessiv.net \
--cc=gottfried.haider@gmail.com \
--cc=hsweeten@visionengravers.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=loic.pallardy@st.com \
--cc=stefan.wahren@i2se.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.