From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v3 9/9] test: dm: Add tests for regmap managed API and regmap fields
Date: Thu, 1 Oct 2020 10:09:10 -0400 [thread overview]
Message-ID: <20201001140910.GE14816@bill-the-cat> (raw)
In-Reply-To: <20200924043418.5355-10-p.yadav@ti.com>
On Thu, Sep 24, 2020 at 10:04:18AM +0530, Pratyush Yadav wrote:
> From: Jean-Jacques Hiblot <jjhiblot@ti.com>
>
> The tests rely on a dummy driver to allocate and initialize the regmaps
> and the regmap fields using the managed API. The first test checks if
> the regmap config fields like width, reg_offset_shift, range specifiers,
> etc work. The second test checks if regmap fields behave properly (mask
> and shift are ok) by peeking into the regmap.
>
> Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
> Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/next, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201001/3440da70/attachment.sig>
next prev parent reply other threads:[~2020-10-01 14:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 4:34 [PATCH v3 0/9] regmap: Add managed API, regmap fields, regmap config Pratyush Yadav
2020-09-24 4:34 ` [PATCH v3 1/9] regmap: Add devm_regmap_init() Pratyush Yadav
2020-10-01 14:08 ` Tom Rini
2020-09-24 4:34 ` [PATCH v3 2/9] regmap: zero out the regmap on allocation Pratyush Yadav
2020-10-01 14:08 ` Tom Rini
2020-09-24 4:34 ` [PATCH v3 3/9] regmap: Allow specifying read/write width Pratyush Yadav
2020-10-01 14:08 ` Tom Rini
2020-09-24 4:34 ` [PATCH v3 4/9] regmap: Allow left shifting register offset before access Pratyush Yadav
2020-10-01 14:08 ` Tom Rini
2020-09-24 4:34 ` [PATCH v3 5/9] regmap: Add regmap_init_mem_range() Pratyush Yadav
2020-10-01 14:08 ` Tom Rini
2020-09-24 4:34 ` [PATCH v3 6/9] regmap: Allow devices to specify regmap range start and size in config Pratyush Yadav
2020-10-01 14:08 ` Tom Rini
2020-09-24 4:34 ` [PATCH v3 7/9] regmap: Add support for regmap fields Pratyush Yadav
2020-10-01 14:08 ` Tom Rini
2020-09-24 4:34 ` [PATCH v3 8/9] test/py: allow multi-digit index in in_tree() Pratyush Yadav
2020-10-01 14:09 ` Tom Rini
2020-09-24 4:34 ` [PATCH v3 9/9] test: dm: Add tests for regmap managed API and regmap fields Pratyush Yadav
2020-10-01 14:09 ` Tom Rini [this message]
2020-09-30 13:58 ` [PATCH v3 0/9] regmap: Add managed API, regmap fields, regmap config Pratyush Yadav
2020-09-30 15:25 ` 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=20201001140910.GE14816@bill-the-cat \
--to=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