65bae54e08
The VCN33_BT and VCN33_WIFI regulators are actually the same regulator, having the same voltage setting and output pin. There are simply two enable bits that are ORed together to enable the regulator. Having two regulators representing the same output pin is misleading from a design matching standpoint, and also error-prone in driver implementations. If consumers try to set different voltages on either regulator, the one set later would override the one set before. There are ways around this, such as chaining them together and having the downstream one act as a switch. But given there's only one output pin, such a workaround doesn't match reality. Remove the VCN33_WIFI regulator. During the probe phase, have the driver sync the enable status of VCN33_WIFI to VCN33_BT. Also drop the suffix so that the regulator name matches the pin name in the datasheet. Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> Link: https://lore.kernel.org/r/20230609083009.2822259-4-wenst@chromium.org Signed-off-by: Mark Brown <broonie@kernel.org> |
||
|---|---|---|
| .. | ||
| act8865.h | ||
| arizona-ldo1.h | ||
| arizona-micsupp.h | ||
| consumer.h | ||
| coupler.h | ||
| da9121.h | ||
| da9211.h | ||
| db8500-prcmu.h | ||
| driver.h | ||
| fan53555.h | ||
| fixed.h | ||
| gpio-regulator.h | ||
| lp872x.h | ||
| lp3971.h | ||
| lp3972.h | ||
| machine.h | ||
| max1586.h | ||
| max8649.h | ||
| max8660.h | ||
| max8952.h | ||
| max8973-regulator.h | ||
| mt6311.h | ||
| mt6315-regulator.h | ||
| mt6323-regulator.h | ||
| mt6331-regulator.h | ||
| mt6332-regulator.h | ||
| mt6357-regulator.h | ||
| mt6358-regulator.h | ||
| mt6359-regulator.h | ||
| mt6380-regulator.h | ||
| mt6397-regulator.h | ||
| of_regulator.h | ||
| pca9450.h | ||
| pfuze100.h | ||
| tps6507x.h | ||
| tps51632-regulator.h | ||
| tps62360.h | ||
| userspace-consumer.h | ||