From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
pantelis.antoniou@konsulko.com,
Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Tull <atull@kernel.org>
Subject: Re: [RFC PATCH 0/2] of: unittest: add overlay gpio test to catch gpio hog problem
Date: Wed, 15 Jan 2020 11:28:57 -0600 [thread overview]
Message-ID: <578a2d41-e146-1f26-6bf4-30509ebe6941@gmail.com> (raw)
In-Reply-To: <1579070828-18221-1-git-send-email-frowand.list@gmail.com>
On 1/15/20 12:47 AM, 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.
>
> I did not have a development system for which it would be easy to
> experiment with applying an overlay containing a gpio hog, so I
> instead created this unittest that uses a fake gpio node.
>
> This series is a work in progress and I have not properly reviewed
> it yet myself. The work behind the series has resulted in my
> following several paths and distractions, resulting in more delay
> than I would desire in continuing to review Geert's RFC patches.
> I am thus releasing these patches as an RFC so that my work
> behind the review is visible and available for Geert and other
> reviewers of his patch.
>
> The annotations added in patch 2/2 add a small amount of verbosity
> to the console output. I have created a proof of concept tool to
> explore (1) how test harnesses could use the annotations and
> (2) how to make the resulting console output easier to read and
> understand as a human being. The tool 'of_unittest_expect' is
> available at https://github.com/frowand/dt_tools
>
I will reply to this email with examples of console boot message
changes as a result of this patch series.
(1) boot before patches
(2) boot after this patch series
(3) messages from (2) processed by of_unittest_expect
(4) meesages from boot after Geert's patches on top of this patch
series processed by of_unittest_expect
-Frank
>
> [1] https://lore.kernel.org/linux-devicetree/20191230133852.5890-1-geert+renesas@glider.be/
>
>
> Frank Rowand (2):
> of: unittest: add overlay gpio test to catch gpio hog problem
> of: unittest: annotate warnings triggered by unittest
>
> 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 | 632 ++++++++++++++++++++++++--
> 8 files changed, 719 insertions(+), 31 deletions(-)
> 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
>
next prev parent reply other threads:[~2020-01-15 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 6:47 [RFC PATCH 0/2] of: unittest: add overlay gpio test to catch gpio hog problem frowand.list
2020-01-15 6:47 ` [RFC PATCH 1/2] " frowand.list
2020-01-21 23:02 ` Rob Herring
2020-01-23 2:32 ` Frank Rowand
2020-01-28 2:34 ` Frank Rowand
2020-01-15 6:47 ` [RFC PATCH 2/2] of: unittest: annotate warnings triggered by unittest frowand.list
2020-01-15 17:28 ` Frank Rowand [this message]
2020-01-15 18:03 ` [RFC PATCH 0/2] of: unittest: add overlay gpio test to catch gpio hog problem Frank Rowand
2020-01-15 18:03 ` Frank Rowand
2020-01-15 18:04 ` Frank Rowand
2020-01-15 18:05 ` Frank Rowand
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=578a2d41-e146-1f26-6bf4-30509ebe6941@gmail.com \
--to=frowand.list@gmail.com \
--cc=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=panto@antoniou-consulting.com \
--cc=robh+dt@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