From: "weiyongjun (A)" <weiyongjun1@huawei.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bamvor Jian Zhang <bamv2005@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] gpio: mockup: remove gpio debugfs when remove device
Date: Mon, 22 Aug 2022 11:39:29 +0800 [thread overview]
Message-ID: <fe049f3e-6924-342b-a5ba-f460ddce436c@huawei.com> (raw)
In-Reply-To: <CAMRc=McG5Pf4b5HymV1iaFAGqMMEtyYSQi23z9LmjvzmbF4rYg@mail.gmail.com>
On 2022/8/19 20:49, Bartosz Golaszewski wrote:
> On Tue, Aug 16, 2022 at 4:34 PM Wei Yongjun <weiyongjun1@huawei.com> wrote:
>> GPIO mockup debugfs is created in gpio_mockup_probe() but
>> forgot to remove when remove device. This patch add a devm
>> managed callback for removing them.
>>
> The tag -next is for patches that address issues that are in next but
> not yet in master.
Got it. Thanks.
>
>> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
>> ---
>> drivers/gpio/gpio-mockup.c | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/drivers/gpio/gpio-mockup.c b/drivers/gpio/gpio-mockup.c
>> index 8943cea92764..1fdc444b093b 100644
>> --- a/drivers/gpio/gpio-mockup.c
>> +++ b/drivers/gpio/gpio-mockup.c
>> @@ -373,6 +373,13 @@ static void gpio_mockup_debugfs_setup(struct device *dev,
>> }
>> }
>>
>> +static void gpio_mockup_debugfs_cleanup(void *data)
>> +{
>> + struct gpio_mockup_chip *chip = data;
>> +
>> + debugfs_remove_recursive(chip->dbg_dir);
>> +}
>> +
>> static void gpio_mockup_dispose_mappings(void *data)
>> {
>> struct gpio_mockup_chip *chip = data;
>> @@ -455,6 +462,10 @@ static int gpio_mockup_probe(struct platform_device *pdev)
>>
>> gpio_mockup_debugfs_setup(dev, chip);
>>
>> + rv = devm_add_action_or_reset(dev, gpio_mockup_debugfs_cleanup, chip);
>> + if (rv)
>> + return rv;
>> +
> Please return that function directly.
Will fix it.
>
>> return 0;
>> }
>>
>> --
>> 2.34.1
>>
> This isn't very relevant as the module needs to be unloaded anyway in
> order to reconfigure the simulated device but I'll apply it as it's
> technically correct. Did you see we have a new one - gpio-sim - that
> uses configfs?
>
gpio-mockup is used for testing other drivers with overlay dts, and
triggered
this issue. I though gpio-sim not work with dts, but it should works well.
I will have a try to using the new gpio-sim module.
next prev parent reply other threads:[~2022-08-22 3:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 14:52 Wei Yongjun
2022-08-19 12:49 ` Bartosz Golaszewski
2022-08-22 3:39 ` weiyongjun (A) [this message]
2022-08-22 13:27 ` weiyongjun (A)
2022-08-28 14:00 ` Bartosz Golaszewski
2022-08-29 1:15 ` weiyongjun (A)
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=fe049f3e-6924-342b-a5ba-f460ddce436c@huawei.com \
--to=weiyongjun1@huawei.com \
--cc=bamv2005@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®