[PATCH v4 2/2] test: gpio: Add tests for the managed API

Pratyush Yadav p.yadav at ti.com
Wed Sep 9 05:53:39 CEST 2020


On 08/09/20 05:56PM, Simon Glass wrote:
> On Mon, 7 Sep 2020 at 23:40, Pratyush Yadav <p.yadav at ti.com> wrote:
> >
> > From: Jean-Jacques Hiblot <jjhiblot at ti.com>
> >
> > Add a test to verify that GPIOs can be acquired/released using the managed
> > API. Also check that the GPIOs are released when the consumer device is
> > removed.
> >
> > Signed-off-by: Jean-Jacques Hiblot <jjhiblot at ti.com>
> > Signed-off-by: Pratyush Yadav <p.yadav at ti.com>
> > ---
> >  arch/sandbox/dts/test.dts |  10 ++++
> >  test/dm/bus.c             |   2 +-
> >  test/dm/gpio.c            | 102 ++++++++++++++++++++++++++++++++++++++
> >  test/dm/test-fdt.c        |   6 +--
> >  4 files changed, 116 insertions(+), 4 deletions(-)
> 
> Reviewed-by: Simon Glass <sjg at chromium.org>

Thanks.
 
> Although I don't see a change log, so this is a bit blind.

The changelog is in the cover letter [0]. Copy-pasing the parts relevant 
to this patch:

- Move "another-test" node down the order to make sure
  dm_test_fdt_uclass_seq() continues to work.
- Bump num_devices to 9 in dm_test_bus_children(), dm_test_fdt(), and
  dm_test_uclass_foreach() to fix broken tests.
- s/DM_TESTF/UT_TESTF/g

[0] I haven't figured out a workflow that lets me easily record the
changelog on a per-patch basis. Maybe I can write some scripts around 
git-notes for that? Dunno.

-- 
Regards,
Pratyush Yadav
Texas Instruments India


More information about the U-Boot mailing list