public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Christian Marangi <ansuelsmth@gmail.com>
To: Tom Rini <trini@konsulko.com>
Cc: Peter Robinson <pbrobinson@gmail.com>,
	Simon Glass <sjg@chromium.org>, Sean Anderson <seanga2@gmail.com>,
	Sughosh Ganu <sughosh.ganu@linaro.org>,
	Caleb Connolly <caleb.connolly@linaro.org>,
	Mattijs Korpershoek <mkorpershoek@baylibre.com>,
	Patrick Rudolph <patrick.rudolph@9elements.com>,
	Yang Xiwen <forbidden405@outlook.com>,
	Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	Marek Vasut <marex@denx.de>,
	Michael Polyntsov <michael.polyntsov@iopsys.eu>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v2 0/8] led: update LED boot/activity to new property implementation
Date: Wed, 13 Nov 2024 21:24:59 +0100	[thread overview]
Message-ID: <67350b1d.5d0a0220.2d4a95.bc9a@mx.google.com> (raw)
In-Reply-To: <20241113180059.GV3600562@bill-the-cat>

On Wed, Nov 13, 2024 at 12:00:59PM -0600, Tom Rini wrote:
> On Sun, Nov 10, 2024 at 12:50:19PM +0100, Christian Marangi wrote:
> 
> > This series is split in 2 part.
> > 
> > While adapting the LED boot and activity code to the new property
> > accepted by Rob in dt-schema repository, a big BUG was discovered.
> > 
> > The reason wasn't clear at start and took me some days to figure it
> > out.
> > 
> > This was triggered by adding a new phandle in the test.dts to
> > introduce test for the new OPs.
> > 
> > This single addition caused the sandbox CI test to fail in the
> > dm_test_ofnode_phandle_ot test.
> > 
> > This doesn't make sense as reverting the change made the CI test
> > to correctly finish. Also moving the uboot node down
> > after the first phandle (in test.dts the gpio one) also made
> > the CI test to correctly finish.
> > 
> > A little bit of searching and debugging made me realize the
> > parse phandle OPs didn't support other.dts at all and they
> > were still referencing phandle index from test.dts.
> > (more info in the related commit)
> > 
> > In short the test was broken all along and was working by
> > pure luck. The first 4 patch address and fix the problem for good.
> > 
> > The other 4 patch expand and address the property change for
> > LED boot/activity.
> > 
> > Posting in a single series as changes are trivial and just
> > to speedup review process. (and also because the second
> > part depends on the first)
> > 
> > All CI tested with azure pipeline.
> > 
> > Changes v2:
> > - Fix handling of flat tree for phandle
> > - Fix test and other.dts changes
> > 
> > Christian Marangi (8):
> >   dm: core: implement oftree variant of parse_phandle OPs
> >   test: dm: fix broken dm_test_ofnode_phandle_ot and get_by_phandle_ot
> >   dm: core: implement ofnode/tree_parse_phandle() helper
> >   test: dm: Expand dm_test_ofnode_phandle(_ot) with new
> >     ofnode/tree_parse_phandle
> >   dm: core: implement phandle ofnode_options helper
> >   test: dm: Add test for ofnode options phandle helper
> >   led: update LED boot/activity to new property implementation
> >   test: dm: Update test for LED activity and boot
> > 
> >  arch/sandbox/dts/other.dts |  31 ++++++++-
> >  arch/sandbox/dts/test.dts  |  16 +++--
> >  drivers/core/of_access.c   |  61 ++++++++++++-----
> >  drivers/core/ofnode.c      | 124 ++++++++++++++++++++++++++++++++-
> >  drivers/led/led-uclass.c   |  30 +++++---
> >  include/dm/of_access.h     |  86 +++++++++++++++++++++++
> >  include/dm/ofnode.h        | 107 +++++++++++++++++++++++++++++
> >  test/dm/led.c              |  18 +++--
> >  test/dm/ofnode.c           | 136 ++++++++++++++++++++++++++++++++-----
> >  9 files changed, 551 insertions(+), 58 deletions(-)
> 
> My main issue with the series is a lack of documentation updates, as the
> biggest challenge thus far has been that for example Peter couldn't
> figure out how to make use of this on PinePhone. We generate
> documentation today based on include/led.h for this API, yes? Thanks.
> 

Hi Tom,

actually quite the oppisite, led.h describe how these works and was
instructed to first have the options property merged in dt-schema. [1]

Here we have all the option documented under a yaml.

I notice there is a series from Simon that is also pushing a .yaml
here locally in U-Boot and I was waiting for that to be merged to also
include the additional entry there.

Also led.h description and API have info on where to look about the
handling of /options/u-boot/

I feel the main problem with documentation is currently the fact that we
are migrating to a more robust schema and people are used to using Doc
directory? Anyway happy to get any hint on how to improve this.

[1] https://github.com/devicetree-org/dt-schema

-- 
	Ansuel

  reply	other threads:[~2024-11-13 20:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 11:50 [PATCH v2 0/8] led: update LED boot/activity to new property implementation Christian Marangi
2024-11-10 11:50 ` [PATCH v2 1/8] dm: core: implement oftree variant of parse_phandle OPs Christian Marangi
2024-11-20 13:46   ` Simon Glass
2024-11-10 11:50 ` [PATCH v2 2/8] test: dm: fix broken dm_test_ofnode_phandle_ot and get_by_phandle_ot Christian Marangi
2024-11-20 13:46   ` Simon Glass
2024-11-10 11:50 ` [PATCH v2 3/8] dm: core: implement ofnode/tree_parse_phandle() helper Christian Marangi
2024-11-20 13:48   ` Simon Glass
2024-11-10 11:50 ` [PATCH v2 4/8] test: dm: Expand dm_test_ofnode_phandle(_ot) with new ofnode/tree_parse_phandle Christian Marangi
2024-11-20 13:48   ` Simon Glass
2024-11-10 11:50 ` [PATCH v2 5/8] dm: core: implement phandle ofnode_options helper Christian Marangi
2024-11-20 13:48   ` Simon Glass
2024-11-10 11:50 ` [PATCH v2 6/8] test: dm: Add test for ofnode options phandle helper Christian Marangi
2024-11-20 13:48   ` Simon Glass
2024-11-10 11:50 ` [PATCH v2 7/8] led: update LED boot/activity to new property implementation Christian Marangi
2024-11-10 11:50 ` [PATCH v2 8/8] test: dm: Update test for LED activity and boot Christian Marangi
2024-11-20 13:48   ` Simon Glass
2024-11-13 18:00 ` [PATCH v2 0/8] led: update LED boot/activity to new property implementation Tom Rini
2024-11-13 20:24   ` Christian Marangi [this message]
2024-11-23  2:41     ` Tom Rini
2024-12-06 17:30       ` Christian Marangi
2024-12-06 17:56         ` Tom Rini
2024-12-06 22:30 ` Tom Rini

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=67350b1d.5d0a0220.2d4a95.bc9a@mx.google.com \
    --to=ansuelsmth@gmail.com \
    --cc=caleb.connolly@linaro.org \
    --cc=forbidden405@outlook.com \
    --cc=marex@denx.de \
    --cc=michael.polyntsov@iopsys.eu \
    --cc=mikhail.kshevetskiy@iopsys.eu \
    --cc=mkorpershoek@baylibre.com \
    --cc=patrick.rudolph@9elements.com \
    --cc=pbrobinson@gmail.com \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=seanga2@gmail.com \
    --cc=sjg@chromium.org \
    --cc=sughosh.ganu@linaro.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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