Djam/u-boot
1
0
Fork 0
mirror of https://github.com/u-boot/u-boot.git synced 2025-05-09 03:21:51 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

regmap: Add regmap_init_mem_range()

Browse source 
Right now, the base of a regmap can only be obtained from the device
tree. This makes it impossible for devices which calculate the base at
runtime to use a regmap. An example of such a device is the Cadence
Sierra PHY.

Allow creating a regmap with one range whose start and size can be
specified by the driver based on calculations at runtime.

Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Pratyush Yadav 2020-09-24 10:04:14 +05:30 • committed by Tom Rini
parent 7aa5ddffe7
commit 0e01a7c3f4
2 changed files with 46 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
include/regmap.h
View file

@ -350,6 +350,25 @@ int regmap_init_mem_platdata(struct udevice *dev, fdt_val_t *reg, int count,
int regmap_init_mem_index(ofnode node, struct regmap **mapp, int index);
/**
* regmap_init_mem_range() - Set up a new memory region for ofnode with the
* specified range.
*
* @node: The ofnode for the map.
* @r_start: Start of the range.
* @r_size: Size of the range.
* @mapp: Returns allocated map.
*
* Return: 0 in success, -errno otherwise
*
* This creates a regmap with one range where instead of extracting the range
* from 'node', it is created based on the parameters specified. This is
* useful when a driver needs to calculate the base of the regmap at runtime,
* and can't specify it in device tree.
*/
int regmap_init_mem_range(ofnode node, ulong r_start, ulong r_size,
struct regmap **mapp);
/**
* devm_regmap_init() - Initialise register map (device managed)
*