From: Rob Herring <robh@kernel.org>
To: frowand.list@gmail.com
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
pantelis.antoniou@konsulko.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Alan Tull <atull@kernel.org>
Subject: Re: [PATCH v2 1/2] of: unittest: add overlay gpio test to catch gpio hog problem
Date: Wed, 26 Feb 2020 10:42:06 -0600 [thread overview]
Message-ID: <20200226164206.GA10128@bogus> (raw)
In-Reply-To: <1582224021-12827-2-git-send-email-frowand.list@gmail.com>
On Thu, 20 Feb 2020 12:40:20 -0600, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> Geert reports that gpio hog nodes are not properly processed when
> the gpio hog node is added via an overlay reply and provides an
> RFC patch to fix the problem [1].
>
> Add a unittest that shows the problem. Unittest will report "1 failed"
> test before applying Geert's RFC patch and "0 failed" after applying
> Geert's RFC patch.
>
> [1] https://lore.kernel.org/linux-devicetree/20191230133852.5890-1-geert+renesas@glider.be/
>
> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
> ---
>
> changes since v1:
> - base on 5.6-rc1
> - fixed node names in overlays
> - removed unused fields from struct unittest_gpio_dev
> - of_unittest_overlay_gpio() cleaned up comments
> - of_unittest_overlay_gpio() moved saving global values into
> probe_pass_count and chip_request_count more tightly around
> test code expected to trigger changes in the global values
>
> v1 of this patch incorrectly reported that it had made changes
> since the RFC version, but it was mistakenly created from the
> wrong branch.
>
> There are checkpatch warnings.
> - New files are in a directory already covered by MAINTAINERS
> - The undocumented compatibles are restricted to use by unittest
> and should not be documented under Documentation
> - The printk() KERN_<LEVEL> warnings are false positives. The level
> is supplied by a define parameter instead of a hard coded constant
> - The lines over 80 characters are consistent with unittest.c style
>
> This unittest was also valuable in that it allowed me to explore
> possible issues related to the proposed solution to the gpio hog
> problem.
>
>
> drivers/of/unittest-data/Makefile | 8 +-
> drivers/of/unittest-data/overlay_gpio_01.dts | 23 +++
> drivers/of/unittest-data/overlay_gpio_02a.dts | 16 ++
> drivers/of/unittest-data/overlay_gpio_02b.dts | 16 ++
> drivers/of/unittest-data/overlay_gpio_03.dts | 23 +++
> drivers/of/unittest-data/overlay_gpio_04a.dts | 16 ++
> drivers/of/unittest-data/overlay_gpio_04b.dts | 16 ++
> drivers/of/unittest.c | 253 ++++++++++++++++++++++++++
> 8 files changed, 370 insertions(+), 1 deletion(-)
> create mode 100644 drivers/of/unittest-data/overlay_gpio_01.dts
> create mode 100644 drivers/of/unittest-data/overlay_gpio_02a.dts
> create mode 100644 drivers/of/unittest-data/overlay_gpio_02b.dts
> create mode 100644 drivers/of/unittest-data/overlay_gpio_03.dts
> create mode 100644 drivers/of/unittest-data/overlay_gpio_04a.dts
> create mode 100644 drivers/of/unittest-data/overlay_gpio_04b.dts
>
Applied, thanks.
Rob
next prev parent reply other threads:[~2020-02-26 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 18:40 [PATCH v2 0/2] of: unittest: add overlay gpio test to catch gpio hog problem frowand.list
2020-02-20 18:40 ` [PATCH v2 1/2] " frowand.list
2020-02-26 16:42 ` Rob Herring [this message]
2020-03-13 16:40 ` Frank Rowand
2020-03-16 8:45 ` Anders Roxell
2020-03-26 1:56 ` Frank Rowand
2020-03-26 10:39 ` Anders Roxell
2020-03-26 15:33 ` Frank Rowand
2020-04-08 12:27 ` Anders Roxell
2020-02-20 18:40 ` [PATCH v2 2/2] of: unittest: annotate warnings triggered by unittest frowand.list
2020-02-26 16:42 ` Rob Herring
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=20200226164206.GA10128@bogus \
--to=robh@kernel.org \
--cc=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox