diff options
| author | Matti Vaittinen <mazziesaccount@gmail.com> | 2025-10-27 14:12:06 +0200 |
|---|---|---|
| committer | Lee Jones <lee@kernel.org> | 2025-11-06 16:02:11 +0000 |
| commit | 1810b210872ffc9985febca0880702a7102aad31 (patch) | |
| tree | bf14cb14a218c74e1d31b57dc6d3eff99ea3bdb3 /scripts/generate_rust_analyzer.py | |
| parent | 049929c5a159c8671b9b0c12a7da963fef535b00 (diff) | |
mfd: bd718x7: Use regmap_reg_range() for pmic_status_range
Initializing the regmap_ranges using direct assignment to the range_min
and range_max members is a slightly verbose. In general we can make it a
tad cleaner when using the regmap_reg_range() macro.
The rohm-bd718x7.c is doing this open-coded initialization. It's not
really bad as there is only one range defined, but it is still worth
converting it to use the regmap_reg_range() so no-one uses it as a bad
example.
Additionally, the regmap_access_table expects a pointer to an array of
ranges. This is a tad more obvious when we use an array with single
range, instead of claiming a pointer to a range struct being a single
element array.
Use regmap_reg_range() when initializing the regmap_range structure and
use a real one-element array instead of a pointer to a struct.
Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
Link: https://patch.msgid.link/aP9hlpRO-0vmEHBZ@mva-rohm
Signed-off-by: Lee Jones <lee@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions
