regmap: Add managed API, regmap fields, regmap config
Get series with b4
b4 am 20200930152517.GY14816@bill-the-catVersions newest first
- v3 Latest9 patches 0 repliesNew
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/9 | regmap: Add devm_regmap_init() | +0 | 0 replies | |
| 2/9 | regmap: zero out the regmap on allocation | +0 | 0 replies | |
| 3/9 | regmap: Allow specifying read/write width | +0 | 0 replies | |
| 4/9 | regmap: Allow left shifting register offset before access | +0 | 0 replies | |
| 5/9 | regmap: Add regmap_init_mem_range() | +0 | 0 replies | |
| 6/9 | regmap: Allow devices to specify regmap range start and size in config | +0 | 0 replies | |
| 7/9 | regmap: Add support for regmap fields | +0 | 0 replies | |
| 8/9 | test/py: allow multi-digit index in in_tree() | +0 | 0 replies | |
| 9/9 | test: dm: Add tests for regmap managed API and regmap fields | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH v3 0/9] regmap: Add managed API, regmap fields, regmap config
Quoted 35 lines · Pratyush Yadav
Quoted 27 lines · Pratyush Yadav
Hi,
This series is a re-spin of Jean-Jacques' earlier effort [0], the goal of which was to facilitate porting drivers from the Linux kernel. It adds the managed API, using the same API as Linux. It also adds support for regmap fields.
Jean-Jacques' series added support for custom regmap read/write callbacks. The design was argued against by Simon [1]. He argued that using the driver model was a better idea instead of the custom functions. That would mean slightly more memory usage and a more involved change.
The main aim of adding the custom functions is to support the Cadence Sierra PHY driver from Linux [2]. The driver's custom functions aren't very complicated, so they can be replaced by some simple formatting options. So, add the struct
regmap_configwhich contains fields to alter the behaviour of the regmap. This includes specifying the size of the read/write operations via 'width', specifying the start and size of range from code instead of device tree via 'r_start' and 'r_size', and specifying a left shift of the register offset before access via 'reg_offset_shift'. The driver can't be ported verbatim now, but this allows the changes to be very isolated and minimal.These config options allow us to avoid converting to driver model until we really need it.
Quoted 6 lines
The Travis CI run can be found at [3].
[0] https://patchwork.ozlabs.org/project/uboot/cover/20191105114700.24989-1-jjhiblot at ti.com/
[1] https://patchwork.ozlabs.org/comment/2426186/
[2] https://elixir.bootlin.com/linux/latest/source/drivers/phy/cadence/phy-cadence-sierra.c
[3] https://travis-ci.org/github/prati0100/uboot/builds/729588518
Quoted 4 lines
Ping.
Tom, do you have any comments? If not can you please pick this series up?
I will review this and the gpio/reset APIs for next shortly.
Signature · 8 lines
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/20200930/42e7c363/attachment.sig>