mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2025-01-26 02:25:00 -05:00
regulator: of: Don't flag voltage change as possible for exact voltages
Flagging voltage changes as possible for exactly specified voltages appears to be triggering bugs in the SDHCI code (it should be able to handle the case where only one voltage it wants is in the range it is allowed to set) so make sure we only set the flag in cases where there's genuine variability. Signed-off-by: Mark Brown <broonie@kernel.org>
This commit is contained in:
parent
fa93fd4ecc
commit
45fa2038cf
1 changed files with 4 additions and 2 deletions
|
@ -43,10 +43,12 @@ static void of_get_regulation_constraints(struct device_node *np,
|
|||
constraints->max_uV = pval;
|
||||
|
||||
/* Voltage change possible? */
|
||||
if (constraints->min_uV && constraints->max_uV) {
|
||||
if (constraints->min_uV != constraints->max_uV)
|
||||
constraints->valid_ops_mask |= REGULATOR_CHANGE_VOLTAGE;
|
||||
|
||||
/* Do we have a voltage range, if so try to apply it? */
|
||||
if (constraints->min_uV && constraints->max_uV)
|
||||
constraints->apply_uV = true;
|
||||
}
|
||||
|
||||
if (!of_property_read_u32(np, "regulator-microvolt-offset", &pval))
|
||||
constraints->uV_offset = pval;
|
||||
|
|
Loading…
Add table
Reference in a new issue