| Message ID | 20240217183610.2621132-6-jonas@kwiboo.se |
|---|---|
| State | Superseded |
| Delegated to: | Kever Yang |
| Headers | show |
| Series | rockchip: rk3399: Migrate to use IO-domain driver | expand |
Hi Jonas, On 2/17/24 19:35, Jonas Karlman wrote: > Port the RK3399 part of the Rockchip IO-domain driver from linux. > > This differs from linux version in that pmu io iodomain bit is enabled > in the write ops instead of in an init ops as in linux, this way we can > avoid keeping a full state of all supply that have been configured. > > Signed-off-by: Jonas Karlman <jonas@kwiboo.se> Suggestions below, otherwise I only have one concern: This actually postpones the moment the IO domain is properly set. Before, we knew almost for sure when this was set, as it was pretty early in the boot process (misc_init_r), I hope before any device was actually probed. Now, because we're using the Device Model for that, we may probe this IO domain device after another Device requires it? e.g. for Puma, we need the IO domains set for PCIe to work. I assume if we were to use PCIe in U-Boot on Puma, we may have this issue (we don't right now use PCIe in U-Boot and I don't think we have any plan of doing so). This all reminds me of the attempts we've made in the Linux kernel to make sure the IO domain devices are probed before the devices that require them to be set up. Maybe we'll need something similar in U-Boot as well. > --- > drivers/misc/rockchip-io-domain.c | 79 +++++++++++++++++++++++++++++-- > 1 file changed, 75 insertions(+), 4 deletions(-) > > diff --git a/drivers/misc/rockchip-io-domain.c b/drivers/misc/rockchip-io-domain.c > index 3f6227f993f9..0ffea32ef07f 100644 > --- a/drivers/misc/rockchip-io-domain.c > +++ b/drivers/misc/rockchip-io-domain.c > @@ -5,7 +5,6 @@ > * Ported from linux drivers/soc/rockchip/io-domain.c > */ > > -#include <common.h> > #include <dm.h> > #include <dm/device_compat.h> > #include <regmap.h> > @@ -28,6 +27,10 @@ > #define MAX_VOLTAGE_1_8 1980000 > #define MAX_VOLTAGE_3_3 3600000 > > +#define RK3399_PMUGRF_CON0 0x180 > +#define RK3399_PMUGRF_CON0_VSEL BIT(8) > +#define RK3399_PMUGRF_VSEL_SUPPLY_NUM 9 > + > #define RK3568_PMU_GRF_IO_VSEL0 0x0140 > #define RK3568_PMU_GRF_IO_VSEL1 0x0144 > #define RK3568_PMU_GRF_IO_VSEL2 0x0148 > @@ -35,10 +38,10 @@ > struct rockchip_iodomain_soc_data { > int grf_offset; > const char *supply_names[MAX_SUPPLIES]; > - int (*write)(struct regmap *grf, int idx, int uV); > + int (*write)(struct regmap *grf, uint offset, int idx, int uV); > }; > > -static int rk3568_iodomain_write(struct regmap *grf, int idx, int uV) > +static int rk3568_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) > { > u32 is_3v3 = uV > MAX_VOLTAGE_1_8; > u32 val0, val1; > @@ -78,6 +81,64 @@ static int rk3568_iodomain_write(struct regmap *grf, int idx, int uV) > return 0; > } > > +static int rockchip_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) > +{ > + u32 val; > + > + /* set value bit */ > + val = (uV > MAX_VOLTAGE_1_8) ? 0 : 1; > + val <<= idx; > + > + /* apply hiword-mask */ > + val |= (BIT(idx) << 16); > + > + return regmap_write(grf, offset, val); You could use: """ if (uV > MAX_VOLTAGE_1_8) { val = RK_CLRBITS(BIT(idx)); } else { val = RK_SETBITS(BIT(idx)); } return regmap_write(grf, offset, val); """ by including asm/rockchip/hardware.h. > +} > + > +static int rk3399_pmu_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) > +{ > + int ret = rockchip_iodomain_write(grf, offset, idx, uV); > + > + if (!ret && idx == RK3399_PMUGRF_VSEL_SUPPLY_NUM) { > + /* > + * set pmu io iodomain to also use this framework > + * instead of a special gpio. > + */ > + u32 val = RK3399_PMUGRF_CON0_VSEL | (RK3399_PMUGRF_CON0_VSEL << 16); > + ret = regmap_write(grf, RK3399_PMUGRF_CON0, val); Same here, but two options :) """ ret = regmap_write(grf, RK3399_PMUGRF_CON0, RK_SETBITS(RK3399_PMUGRF_CON0_VSEL)); """ or """ ret = regmap_write(grf, RK3399_PMUGRF_CON0, FIELD_PREP(RK3399_PMUGRF_CON0_VSEL, 1)); """ Maybe the if check on the offset is actually a bit overkill? This function can only be called for one IO domain since there's only one IO domain in the PMUGRF in RK3399. Therefore.... Maybe just hardcode everything? """ static int rk3399_pmu_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) { int ret = rockchip_iodomain_write(grf, offset, 9, uV); if (ret) return ret; return regmap_write(grf, RK3399_PMUGRF_CON0, FIELD_PREP(RK3399_PMUGRF_CON0_VSEL, 1)); } static const struct rockchip_iodomain_soc_data soc_data_rk3399_pmu = { .grf_offset = 0x180, .supply_names = { "pmu1830-supply", /* PMUIO2_VDD */ }, .write = rk3399_pmu_iodomain_write, }; """ You can also keep the 8 NULL supplies before to not have to hardcode "9" in rk3399_pmu_iodomain_write for example, and still not do the check, adding a comment explaining why. The code looks sound in any case, only issue I have is wrt device probe ordering in U-Boot. Cheers, Quentin
Hi Quentin, On 2024-02-21 19:18, Quentin Schulz wrote: > Hi Jonas, > > On 2/17/24 19:35, Jonas Karlman wrote: >> Port the RK3399 part of the Rockchip IO-domain driver from linux. >> >> This differs from linux version in that pmu io iodomain bit is enabled >> in the write ops instead of in an init ops as in linux, this way we can >> avoid keeping a full state of all supply that have been configured. >> >> Signed-off-by: Jonas Karlman <jonas@kwiboo.se> > > Suggestions below, otherwise I only have one concern: > > This actually postpones the moment the IO domain is properly set. > Before, we knew almost for sure when this was set, as it was pretty > early in the boot process (misc_init_r), I hope before any device was > actually probed. Now, because we're using the Device Model for that, we > may probe this IO domain device after another Device requires it? e.g. > for Puma, we need the IO domains set for PCIe to work. I assume if we > were to use PCIe in U-Boot on Puma, we may have this issue (we don't > right now use PCIe in U-Boot and I don't think we have any plan of doing > so). Because this driver makes the following call in its bind ops, the opposite is actually true and the IO domain is configured earlier than it was previously done with misc_init_r. With this the IO domain driver is probed directly after bind and all regulators that is referenced by io-domain supply nodes will be regulator_autoset() before the uV value is evaluated. In rockchip_iodomain_bind(): dev_or_flags(dev, DM_FLAG_PROBE_AFTER_BIND); On the boards I can test on the GRF got configured exactly as before, just a little bit earlier in the boot process. Prior to the "rockchip: Port IO-domain driver for RK3568 from linux" [1] series the rk8xx driver had some issues and incorrect voltage could be read for some regulators. [1] https://patchwork.ozlabs.org/cover/1823769/ > > This all reminds me of the attempts we've made in the Linux kernel to > make sure the IO domain devices are probed before the devices that > require them to be set up. Maybe we'll need something similar in U-Boot > as well. The main thing missing compared to the linux counterpart is that changes to regulator voltage is not tracked, so there will not be any changes made the initial IO domain voltage configuration made by this driver. > >> --- >> drivers/misc/rockchip-io-domain.c | 79 +++++++++++++++++++++++++++++-- >> 1 file changed, 75 insertions(+), 4 deletions(-) >> >> diff --git a/drivers/misc/rockchip-io-domain.c b/drivers/misc/rockchip-io-domain.c >> index 3f6227f993f9..0ffea32ef07f 100644 >> --- a/drivers/misc/rockchip-io-domain.c >> +++ b/drivers/misc/rockchip-io-domain.c >> @@ -5,7 +5,6 @@ >> * Ported from linux drivers/soc/rockchip/io-domain.c >> */ >> >> -#include <common.h> >> #include <dm.h> >> #include <dm/device_compat.h> >> #include <regmap.h> >> @@ -28,6 +27,10 @@ >> #define MAX_VOLTAGE_1_8 1980000 >> #define MAX_VOLTAGE_3_3 3600000 >> >> +#define RK3399_PMUGRF_CON0 0x180 >> +#define RK3399_PMUGRF_CON0_VSEL BIT(8) >> +#define RK3399_PMUGRF_VSEL_SUPPLY_NUM 9 >> + >> #define RK3568_PMU_GRF_IO_VSEL0 0x0140 >> #define RK3568_PMU_GRF_IO_VSEL1 0x0144 >> #define RK3568_PMU_GRF_IO_VSEL2 0x0148 >> @@ -35,10 +38,10 @@ >> struct rockchip_iodomain_soc_data { >> int grf_offset; >> const char *supply_names[MAX_SUPPLIES]; >> - int (*write)(struct regmap *grf, int idx, int uV); >> + int (*write)(struct regmap *grf, uint offset, int idx, int uV); >> }; >> >> -static int rk3568_iodomain_write(struct regmap *grf, int idx, int uV) >> +static int rk3568_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) >> { >> u32 is_3v3 = uV > MAX_VOLTAGE_1_8; >> u32 val0, val1; >> @@ -78,6 +81,64 @@ static int rk3568_iodomain_write(struct regmap *grf, int idx, int uV) >> return 0; >> } >> >> +static int rockchip_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) >> +{ >> + u32 val; >> + >> + /* set value bit */ >> + val = (uV > MAX_VOLTAGE_1_8) ? 0 : 1; >> + val <<= idx; >> + >> + /* apply hiword-mask */ >> + val |= (BIT(idx) << 16); >> + >> + return regmap_write(grf, offset, val); > > You could use: > > """ > if (uV > MAX_VOLTAGE_1_8) { > val = RK_CLRBITS(BIT(idx)); > } else { > val = RK_SETBITS(BIT(idx)); > } > > return regmap_write(grf, offset, val); > """ > > by including asm/rockchip/hardware.h. > >> +} >> + >> +static int rk3399_pmu_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) >> +{ >> + int ret = rockchip_iodomain_write(grf, offset, idx, uV); >> + >> + if (!ret && idx == RK3399_PMUGRF_VSEL_SUPPLY_NUM) { >> + /* >> + * set pmu io iodomain to also use this framework >> + * instead of a special gpio. >> + */ >> + u32 val = RK3399_PMUGRF_CON0_VSEL | (RK3399_PMUGRF_CON0_VSEL << 16); >> + ret = regmap_write(grf, RK3399_PMUGRF_CON0, val); > > Same here, but two options :) > > """ > ret = regmap_write(grf, RK3399_PMUGRF_CON0, > RK_SETBITS(RK3399_PMUGRF_CON0_VSEL)); > """ > > or > """ > ret = regmap_write(grf, RK3399_PMUGRF_CON0, > FIELD_PREP(RK3399_PMUGRF_CON0_VSEL, 1)); > """ Thanks for the suggestions, I have purposely tried to deviate as little as possible from the linux driver, as I would like to port support for more SoCs. Will take a closer look if there is a need for a v2 or as part of a future follow-up series. > > Maybe the if check on the offset is actually a bit overkill? This > function can only be called for one IO domain since there's only one IO > domain in the PMUGRF in RK3399. > > Therefore.... Maybe just hardcode everything? Hehe, true, I first implemented in this way for RK3328 (patches not sent yet), and just followed using the same pattern for RK3399 without thinking too much :-) Will change if there is a v2, or as part of a future follow-up series that adds RK3328 and RK3308 support. Regards, Jonas > > """ > static int rk3399_pmu_iodomain_write(struct regmap *grf, uint offset, > int idx, int uV) > { > int ret = rockchip_iodomain_write(grf, offset, 9, uV); > if (ret) > return ret; > > return regmap_write(grf, RK3399_PMUGRF_CON0, > FIELD_PREP(RK3399_PMUGRF_CON0_VSEL, 1)); > } > > static const struct rockchip_iodomain_soc_data soc_data_rk3399_pmu = { > .grf_offset = 0x180, > .supply_names = { > "pmu1830-supply", /* PMUIO2_VDD */ > }, > .write = rk3399_pmu_iodomain_write, > }; > """ > > You can also keep the 8 NULL supplies before to not have to hardcode "9" > in rk3399_pmu_iodomain_write for example, and still not do the check, > adding a comment explaining why. > > The code looks sound in any case, only issue I have is wrt device probe > ordering in U-Boot. > > Cheers, > Quentin
Hi Jonas, On 2/21/24 20:05, Jonas Karlman wrote: > Hi Quentin, > > On 2024-02-21 19:18, Quentin Schulz wrote: >> Hi Jonas, >> >> On 2/17/24 19:35, Jonas Karlman wrote: >>> Port the RK3399 part of the Rockchip IO-domain driver from linux. >>> >>> This differs from linux version in that pmu io iodomain bit is enabled >>> in the write ops instead of in an init ops as in linux, this way we can >>> avoid keeping a full state of all supply that have been configured. >>> >>> Signed-off-by: Jonas Karlman <jonas@kwiboo.se> >> >> Suggestions below, otherwise I only have one concern: >> >> This actually postpones the moment the IO domain is properly set. >> Before, we knew almost for sure when this was set, as it was pretty >> early in the boot process (misc_init_r), I hope before any device was >> actually probed. Now, because we're using the Device Model for that, we >> may probe this IO domain device after another Device requires it? e.g. >> for Puma, we need the IO domains set for PCIe to work. I assume if we >> were to use PCIe in U-Boot on Puma, we may have this issue (we don't >> right now use PCIe in U-Boot and I don't think we have any plan of doing >> so). > > Because this driver makes the following call in its bind ops, the > opposite is actually true and the IO domain is configured earlier than > it was previously done with misc_init_r. > > With this the IO domain driver is probed directly after bind and > all regulators that is referenced by io-domain supply nodes will be > regulator_autoset() before the uV value is evaluated. > > In rockchip_iodomain_bind(): > > dev_or_flags(dev, DM_FLAG_PROBE_AFTER_BIND); > > On the boards I can test on the GRF got configured exactly as before, > just a little bit earlier in the boot process. > > Prior to the "rockchip: Port IO-domain driver for RK3568 from linux" [1] > series the rk8xx driver had some issues and incorrect voltage could be > read for some regulators. > > [1] https://patchwork.ozlabs.org/cover/1823769/ > Well, maybe I should read the source code before raising a potential issue :) Thanks for the correction. So in short: common/board_r.c:init_sequence_r calls initr_dm before misc_init_r. initr_dm -> dm_init_and_scan -> dm_scan -> dm_extended_scan which binds the device and because the IO domain driver sets DM_FLAG_PROBE_AFTER_BIND in its bind, dm_probe_devices at the end of dm_scan will probe the device all that before misc_init_r is called. >> >> This all reminds me of the attempts we've made in the Linux kernel to >> make sure the IO domain devices are probed before the devices that >> require them to be set up. Maybe we'll need something similar in U-Boot >> as well. > > The main thing missing compared to the linux counterpart is that changes > to regulator voltage is not tracked, so there will not be any changes > made the initial IO domain voltage configuration made by this driver. > There's a common issue for Linux and U-boot parts is that devices dependent on the IO domain being properly configured is not properly handled. Here in U-Boot, if there are devices which also have DM_FLAG_PROBE_AFTER_BIND set, then I think this is dependent on the order in udevice->sibling_node/child_head. In any case, nothing that is specific to this patch series because it was already the case before. Therefore, Reviewed-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> Thanks, Quentin
On 2024/2/18 02:35, Jonas Karlman wrote: > Port the RK3399 part of the Rockchip IO-domain driver from linux. > > This differs from linux version in that pmu io iodomain bit is enabled > in the write ops instead of in an init ops as in linux, this way we can > avoid keeping a full state of all supply that have been configured. > > Signed-off-by: Jonas Karlman <jonas@kwiboo.se> Reviewed-by: Kever Yang <kever.yang@rock-chips.com> Thanks, - Kever > --- > drivers/misc/rockchip-io-domain.c | 79 +++++++++++++++++++++++++++++-- > 1 file changed, 75 insertions(+), 4 deletions(-) > > diff --git a/drivers/misc/rockchip-io-domain.c b/drivers/misc/rockchip-io-domain.c > index 3f6227f993f9..0ffea32ef07f 100644 > --- a/drivers/misc/rockchip-io-domain.c > +++ b/drivers/misc/rockchip-io-domain.c > @@ -5,7 +5,6 @@ > * Ported from linux drivers/soc/rockchip/io-domain.c > */ > > -#include <common.h> > #include <dm.h> > #include <dm/device_compat.h> > #include <regmap.h> > @@ -28,6 +27,10 @@ > #define MAX_VOLTAGE_1_8 1980000 > #define MAX_VOLTAGE_3_3 3600000 > > +#define RK3399_PMUGRF_CON0 0x180 > +#define RK3399_PMUGRF_CON0_VSEL BIT(8) > +#define RK3399_PMUGRF_VSEL_SUPPLY_NUM 9 > + > #define RK3568_PMU_GRF_IO_VSEL0 0x0140 > #define RK3568_PMU_GRF_IO_VSEL1 0x0144 > #define RK3568_PMU_GRF_IO_VSEL2 0x0148 > @@ -35,10 +38,10 @@ > struct rockchip_iodomain_soc_data { > int grf_offset; > const char *supply_names[MAX_SUPPLIES]; > - int (*write)(struct regmap *grf, int idx, int uV); > + int (*write)(struct regmap *grf, uint offset, int idx, int uV); > }; > > -static int rk3568_iodomain_write(struct regmap *grf, int idx, int uV) > +static int rk3568_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) > { > u32 is_3v3 = uV > MAX_VOLTAGE_1_8; > u32 val0, val1; > @@ -78,6 +81,64 @@ static int rk3568_iodomain_write(struct regmap *grf, int idx, int uV) > return 0; > } > > +static int rockchip_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) > +{ > + u32 val; > + > + /* set value bit */ > + val = (uV > MAX_VOLTAGE_1_8) ? 0 : 1; > + val <<= idx; > + > + /* apply hiword-mask */ > + val |= (BIT(idx) << 16); > + > + return regmap_write(grf, offset, val); > +} > + > +static int rk3399_pmu_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) > +{ > + int ret = rockchip_iodomain_write(grf, offset, idx, uV); > + > + if (!ret && idx == RK3399_PMUGRF_VSEL_SUPPLY_NUM) { > + /* > + * set pmu io iodomain to also use this framework > + * instead of a special gpio. > + */ > + u32 val = RK3399_PMUGRF_CON0_VSEL | (RK3399_PMUGRF_CON0_VSEL << 16); > + ret = regmap_write(grf, RK3399_PMUGRF_CON0, val); > + } > + > + return ret; > +} > + > +static const struct rockchip_iodomain_soc_data soc_data_rk3399 = { > + .grf_offset = 0xe640, > + .supply_names = { > + "bt656-supply", /* APIO2_VDD */ > + "audio-supply", /* APIO5_VDD */ > + "sdmmc-supply", /* SDMMC0_VDD */ > + "gpio1830-supply", /* APIO4_VDD */ > + }, > + .write = rockchip_iodomain_write, > +}; > + > +static const struct rockchip_iodomain_soc_data soc_data_rk3399_pmu = { > + .grf_offset = 0x180, > + .supply_names = { > + NULL, > + NULL, > + NULL, > + NULL, > + NULL, > + NULL, > + NULL, > + NULL, > + NULL, > + "pmu1830-supply", /* PMUIO2_VDD */ > + }, > + .write = rk3399_pmu_iodomain_write, > +}; > + > static const struct rockchip_iodomain_soc_data soc_data_rk3568_pmu = { > .grf_offset = 0x140, > .supply_names = { > @@ -95,6 +156,14 @@ static const struct rockchip_iodomain_soc_data soc_data_rk3568_pmu = { > }; > > static const struct udevice_id rockchip_iodomain_ids[] = { > + { > + .compatible = "rockchip,rk3399-io-voltage-domain", > + .data = (ulong)&soc_data_rk3399, > + }, > + { > + .compatible = "rockchip,rk3399-pmu-io-voltage-domain", > + .data = (ulong)&soc_data_rk3399_pmu, > + }, > { > .compatible = "rockchip,rk3568-pmu-io-voltage-domain", > .data = (ulong)&soc_data_rk3568_pmu, > @@ -152,7 +221,9 @@ static int rockchip_iodomain_probe(struct udevice *dev) > continue; > } > > - soc_data->write(grf, i, uV); > + ret = soc_data->write(grf, soc_data->grf_offset, i, uV); > + if (ret) > + dev_err(dev, "%s: Couldn't write to GRF\n", supply_name); > } > > return 0;
diff --git a/drivers/misc/rockchip-io-domain.c b/drivers/misc/rockchip-io-domain.c index 3f6227f993f9..0ffea32ef07f 100644 --- a/drivers/misc/rockchip-io-domain.c +++ b/drivers/misc/rockchip-io-domain.c @@ -5,7 +5,6 @@ * Ported from linux drivers/soc/rockchip/io-domain.c */ -#include <common.h> #include <dm.h> #include <dm/device_compat.h> #include <regmap.h> @@ -28,6 +27,10 @@ #define MAX_VOLTAGE_1_8 1980000 #define MAX_VOLTAGE_3_3 3600000 +#define RK3399_PMUGRF_CON0 0x180 +#define RK3399_PMUGRF_CON0_VSEL BIT(8) +#define RK3399_PMUGRF_VSEL_SUPPLY_NUM 9 + #define RK3568_PMU_GRF_IO_VSEL0 0x0140 #define RK3568_PMU_GRF_IO_VSEL1 0x0144 #define RK3568_PMU_GRF_IO_VSEL2 0x0148 @@ -35,10 +38,10 @@ struct rockchip_iodomain_soc_data { int grf_offset; const char *supply_names[MAX_SUPPLIES]; - int (*write)(struct regmap *grf, int idx, int uV); + int (*write)(struct regmap *grf, uint offset, int idx, int uV); }; -static int rk3568_iodomain_write(struct regmap *grf, int idx, int uV) +static int rk3568_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) { u32 is_3v3 = uV > MAX_VOLTAGE_1_8; u32 val0, val1; @@ -78,6 +81,64 @@ static int rk3568_iodomain_write(struct regmap *grf, int idx, int uV) return 0; } +static int rockchip_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) +{ + u32 val; + + /* set value bit */ + val = (uV > MAX_VOLTAGE_1_8) ? 0 : 1; + val <<= idx; + + /* apply hiword-mask */ + val |= (BIT(idx) << 16); + + return regmap_write(grf, offset, val); +} + +static int rk3399_pmu_iodomain_write(struct regmap *grf, uint offset, int idx, int uV) +{ + int ret = rockchip_iodomain_write(grf, offset, idx, uV); + + if (!ret && idx == RK3399_PMUGRF_VSEL_SUPPLY_NUM) { + /* + * set pmu io iodomain to also use this framework + * instead of a special gpio. + */ + u32 val = RK3399_PMUGRF_CON0_VSEL | (RK3399_PMUGRF_CON0_VSEL << 16); + ret = regmap_write(grf, RK3399_PMUGRF_CON0, val); + } + + return ret; +} + +static const struct rockchip_iodomain_soc_data soc_data_rk3399 = { + .grf_offset = 0xe640, + .supply_names = { + "bt656-supply", /* APIO2_VDD */ + "audio-supply", /* APIO5_VDD */ + "sdmmc-supply", /* SDMMC0_VDD */ + "gpio1830-supply", /* APIO4_VDD */ + }, + .write = rockchip_iodomain_write, +}; + +static const struct rockchip_iodomain_soc_data soc_data_rk3399_pmu = { + .grf_offset = 0x180, + .supply_names = { + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + "pmu1830-supply", /* PMUIO2_VDD */ + }, + .write = rk3399_pmu_iodomain_write, +}; + static const struct rockchip_iodomain_soc_data soc_data_rk3568_pmu = { .grf_offset = 0x140, .supply_names = { @@ -95,6 +156,14 @@ static const struct rockchip_iodomain_soc_data soc_data_rk3568_pmu = { }; static const struct udevice_id rockchip_iodomain_ids[] = { + { + .compatible = "rockchip,rk3399-io-voltage-domain", + .data = (ulong)&soc_data_rk3399, + }, + { + .compatible = "rockchip,rk3399-pmu-io-voltage-domain", + .data = (ulong)&soc_data_rk3399_pmu, + }, { .compatible = "rockchip,rk3568-pmu-io-voltage-domain", .data = (ulong)&soc_data_rk3568_pmu, @@ -152,7 +221,9 @@ static int rockchip_iodomain_probe(struct udevice *dev) continue; } - soc_data->write(grf, i, uV); + ret = soc_data->write(grf, soc_data->grf_offset, i, uV); + if (ret) + dev_err(dev, "%s: Couldn't write to GRF\n", supply_name); } return 0;
Port the RK3399 part of the Rockchip IO-domain driver from linux. This differs from linux version in that pmu io iodomain bit is enabled in the write ops instead of in an init ops as in linux, this way we can avoid keeping a full state of all supply that have been configured. Signed-off-by: Jonas Karlman <jonas@kwiboo.se> --- drivers/misc/rockchip-io-domain.c | 79 +++++++++++++++++++++++++++++-- 1 file changed, 75 insertions(+), 4 deletions(-)