From: Pratyush Yadav <p.yadav@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 2/2] test: gpio: Add tests for the managed API
Date: Wed, 9 Sep 2020 09:23:39 +0530 [thread overview]
Message-ID: <20200909035337.2q6ktgnfxtpsiked@ti.com> (raw)
In-Reply-To: <CAPnjgZ2asB_YK_9RAyzLpidzhny7bMQ17YTbSqwWKyOp8Xodxw@mail.gmail.com>
On 08/09/20 05:56PM, Simon Glass wrote:
> On Mon, 7 Sep 2020 at 23:40, Pratyush Yadav <p.yadav@ti.com> wrote:
> >
> > From: Jean-Jacques Hiblot <jjhiblot@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@ti.com>
> > Signed-off-by: Pratyush Yadav <p.yadav@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@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
next prev parent reply other threads:[~2020-09-09 3:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 5:40 [PATCH v4 0/2] gpio: Add a managed API Pratyush Yadav
2020-09-08 5:40 ` [PATCH v4 1/2] drivers: gpio: Add a managed API to get a GPIO from the device-tree Pratyush Yadav
2020-09-08 14:12 ` Heinrich Schuchardt
2020-09-08 15:15 ` Pratyush Yadav
2020-09-08 15:26 ` Heinrich Schuchardt
2020-09-08 5:40 ` [PATCH v4 2/2] test: gpio: Add tests for the managed API Pratyush Yadav
2020-09-08 23:56 ` Simon Glass
2020-09-09 3:53 ` Pratyush Yadav [this message]
2020-09-09 14:35 ` Simon Glass
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=20200909035337.2q6ktgnfxtpsiked@ti.com \
--to=p.yadav@ti.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