Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1294156pxk; Fri, 2 Oct 2020 06:13:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw3uZdsNN3N4W8GUof/YQKnL2I7kv+LkSkjVeCq4E2XR+cp6qMcUZfCOgfuNoQOp+6zTc5G X-Received: by 2002:a05:6402:718:: with SMTP id w24mr2231667edx.294.1601644390778; Fri, 02 Oct 2020 06:13:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601644390; cv=none; d=google.com; s=arc-20160816; b=JixokKO6AUcca9Ys4dEpmnxNPIr3CQ+L0DAoW4TowiOt/kz/i8/o1xT7FthY0VdMrr 3AGexYeTyLU86U9XbbEr07FtXefDSTt5ovEoVee8JJKQEgr8AP+9XouEZPXnBpIEd6yu b7pRMdQml95mo/IsscgAlY43fUmTWMFUsTmQFzDup9Mtvd3tThsAdZuwQuJCfz+34akL luLDfBWEtwL4H9m3uRqQuO1WW9PjWXAww9HWwKcRFFR43IsRP8gy7919cAcVst4KXyIh JtRbAcyXON7UxW2B5vPLFXfuURs60RrbURivr8VGKI3LHWqvnDGg3qjdq6lfB0Z8R/Uc 06OQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=CYVDUNUxdOqY0/+dGCfUcfj/HkIeXqrYaxLGr9jgweM=; b=kJ0K+1T27BmgxkCACksQ0cjWUJHkg8YM0FXvrL1mzr42WTTaQLKMqDd+4rsgLJUZbY 9HP8jDuEcLWD9pEIWjH6uryNyYKeCuBO45qcaQ9vdDPUlJBWfmsplyxQ5DDnEjKJAU+d AlHYpjHnf5S4yD5N6rQyLLZf3rDEmADKdXZRNd180J0bzQGA/OZWLlW9mZrdxAgXiS3Z perp4yBGG1zF4xtVZhom8lqydRxj15tePNCpXT6fzL/Wkx4O5kBs1vcj7HA9SZfnOt66 KfPNvIy/Hn0Qj1rH8tvqwaGWFv4hBrIxALb3ByBxp4xq4YxJFAH26XkfHDrlw3J4HZrJ oj2g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h1si885992edn.39.2020.10.02.06.12.46; Fri, 02 Oct 2020 06:13:10 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387862AbgJBNIw (ORCPT + 99 others); Fri, 2 Oct 2020 09:08:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42070 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726017AbgJBNIw (ORCPT ); Fri, 2 Oct 2020 09:08:52 -0400 Received: from smtp1.goneo.de (smtp1.goneo.de [IPv6:2001:1640:5::8:30]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D7112C0613D0; Fri, 2 Oct 2020 06:08:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by smtp1.goneo.de (Postfix) with ESMTP id 786B223F1E7; Fri, 2 Oct 2020 15:08:50 +0200 (CEST) X-Virus-Scanned: by goneo X-Spam-Flag: NO X-Spam-Score: -2.986 X-Spam-Level: X-Spam-Status: No, score=-2.986 tagged_above=-999 tests=[ALL_TRUSTED=-1, AWL=-0.086, BAYES_00=-1.9] autolearn=ham Received: from smtp1.goneo.de ([127.0.0.1]) by localhost (smtp1.goneo.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yx2oadCAFhM1; Fri, 2 Oct 2020 15:08:49 +0200 (CEST) Received: from lem-wkst-02.lemonage (hq.lemonage.de [87.138.178.34]) by smtp1.goneo.de (Postfix) with ESMTPSA id F1D1923F180; Fri, 2 Oct 2020 15:08:48 +0200 (CEST) Date: Fri, 2 Oct 2020 15:08:44 +0200 From: Lars Poeschel To: Greg Kroah-Hartman Cc: Thierry Reding , Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= , Lee Jones , "open list:PWM SUBSYSTEM" , open list Subject: Re: [PATCH 1/2] pwm: sysfs: Set class on pwm devices Message-ID: <20201002130844.udikqwzspp6zlyhh@lem-wkst-02.lemonage> References: <20201002123048.3073128-1-poeschel@lemonage.de> <20201002124616.GB3348424@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201002124616.GB3348424@kroah.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 02, 2020 at 02:46:16PM +0200, Greg Kroah-Hartman wrote: > On Fri, Oct 02, 2020 at 02:30:47PM +0200, poeschel@lemonage.de wrote: > > From: Lars Poeschel > > > > This adds a class to exported pwm devices. > > Exporting a pwm through sysfs did not yield udev events. The > > dev_uevent_filter function does filter-out devices without a bus or > > class. > > This was already addressed in commit > > commit 7e5d1fd75c3d ("pwm: Set class for exported channels in sysfs") > > but this did cause problems and the commit got reverted with > > commit c289d6625237 ("Revert "pwm: Set class for exported channels in > > sysfs"") > > Problem with the previous approach was, that there is a clash if we have > > multiple pwmchips: > > echo 0 > pwmchip0/export > > echo 0 > pwmchip1/export > > would both export /sys/class/pwm/pwm0 . > > > > Now this patch changes the sysfs interface. We do include the pwmchip > > number into the pwm directory that gets exported. > > With the example above we get: > > /sys/class/pwm/pwm-0-0 > > /sys/class/pwm/pwm-1-0 > > We maintain ABI backward compatibility through symlinks. > > /sys/class/pwm/pwmchip0/pwm0 > > /sys/class/pwm/pwmchip1/pwm0 > > are now symbolic links to the new names. > > > > Cc: Greg Kroah-Hartman > > Signed-off-by: Lars Poeschel > > --- > > drivers/pwm/sysfs.c | 57 +++++++++++++++++++++++++++++++++++++-------- > > 1 file changed, 47 insertions(+), 10 deletions(-) > > > > diff --git a/drivers/pwm/sysfs.c b/drivers/pwm/sysfs.c > > index 449dbc0f49ed..c708da17a857 100644 > > --- a/drivers/pwm/sysfs.c > > +++ b/drivers/pwm/sysfs.c > > @@ -240,8 +240,10 @@ static void pwm_export_release(struct device *child) > > > > static int pwm_export_child(struct device *parent, struct pwm_device *pwm) > > { > > + struct pwm_chip *chip = dev_get_drvdata(parent); > > struct pwm_export *export; > > char *pwm_prop[2]; > > + char *link_name; > > int ret; > > > > if (test_and_set_bit(PWMF_EXPORTED, &pwm->flags)) > > @@ -256,25 +258,39 @@ static int pwm_export_child(struct device *parent, struct pwm_device *pwm) > > export->pwm = pwm; > > mutex_init(&export->lock); > > > > + export->child.class = parent->class; > > export->child.release = pwm_export_release; > > export->child.parent = parent; > > export->child.devt = MKDEV(0, 0); > > export->child.groups = pwm_groups; > > - dev_set_name(&export->child, "pwm%u", pwm->hwpwm); > > + dev_set_name(&export->child, "pwm-%u-%u", chip->base, pwm->hwpwm); > > > > ret = device_register(&export->child); > > - if (ret) { > > - clear_bit(PWMF_EXPORTED, &pwm->flags); > > - put_device(&export->child); > > - export = NULL; > > - return ret; > > + if (ret) > > + goto error; > > + > > + link_name = kasprintf(GFP_KERNEL, "pwm%u", pwm->hwpwm); > > + if (link_name == NULL) { > > + ret = -ENOMEM; > > + goto dev_unregister; > > } > > - pwm_prop[0] = kasprintf(GFP_KERNEL, "EXPORT=pwm%u", pwm->hwpwm); > > + > > + pwm_prop[0] = kasprintf(GFP_KERNEL, "EXPORT=%s", > > + export->child.kobj.name); > > pwm_prop[1] = NULL; > > kobject_uevent_env(&parent->kobj, KOBJ_CHANGE, pwm_prop); > > Do you still need to do this by hand? Why can't this uevent field > belong to the class and have it create this for you automatically when > the device is added? I did not add this with my patch, it was there before and I wonder, what purpose it served, since the uevent was filtered because there was no class there. Now we have a class and now it works and this is what happens: /sys/class/pwm# echo 0 > pwmchip1/export KERNEL[2111.952725] add /devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip1/pwm-1-0 (pwm) ACTION=add DEVPATH=/devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip1/pwm-1-0 SEQNUM=1546 SUBSYSTEM=pwm KERNEL[2111.955155] change /devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip1 (pwm) ACTION=change DEVPATH=/devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip1 EXPORT=pwm-1-0 SEQNUM=1547 SUBSYSTEM=pwm The first event is the event from device_register. It informs us that we now have a new pwm-1-0. Nice. The second is the event done here "by hand". It informs us, that pwmchip1 changed. It has a new export now. For me personally this is not needed, but also I don't think it is wrong. You decide! > > kfree(pwm_prop[0]); > > > > - return 0; > > + ret = sysfs_create_link(&parent->kobj, &export->child.kobj, link_name); > > You create the link _after_ you told userspace it was there, you raced > and lost :( Are you sure ? We inform userspace that there is a "pwm-1-0" now available. We do not say anything about "pwm0". "pwm0" is the name of our symlink. This should not be a problem. > > + return ret; > > + > > +dev_unregister: > > + device_unregister(&export->child); > > +error: > > + clear_bit(PWMF_EXPORTED, &pwm->flags); > > + put_device(&export->child); > > + export = NULL; > > + return ret; > > } > > > > static int pwm_unexport_match(struct device *child, void *data) > > @@ -286,6 +302,7 @@ static int pwm_unexport_child(struct device *parent, struct pwm_device *pwm) > > { > > struct device *child; > > char *pwm_prop[2]; > > + char *link_name; > > > > if (!test_and_clear_bit(PWMF_EXPORTED, &pwm->flags)) > > return -ENODEV; > > @@ -294,7 +311,11 @@ static int pwm_unexport_child(struct device *parent, struct pwm_device *pwm) > > if (!child) > > return -ENODEV; > > > > - pwm_prop[0] = kasprintf(GFP_KERNEL, "UNEXPORT=pwm%u", pwm->hwpwm); > > + link_name = kasprintf(GFP_KERNEL, "pwm%u", pwm->hwpwm); > > + if (link_name) > > + sysfs_delete_link(&parent->kobj, &child->kobj, link_name); > > + > > + pwm_prop[0] = kasprintf(GFP_KERNEL, "UNEXPORT=%s", child->kobj.name); > > pwm_prop[1] = NULL; > > kobject_uevent_env(&parent->kobj, KOBJ_CHANGE, pwm_prop); > > Same uevent question here. > > Otherwise, this looks good, nice work in figuring out the is_visable > stuff and everything. Thanks! :-) And thank you for your help so far. Regards, Lars