2019-04-19 08:58:24 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:56 +03:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2023-04-06 20:18:00 +03:00
|
|
|
|
|
|
|
|
|
2023-07-14 11:49:28 -06:00
|
|
|
|
2023-04-06 20:18:00 +03:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2023-04-06 20:18:00 +03:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2023-04-06 20:18:00 +03:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:55 +03:00
|
|
|
|
|
|
|
|
|
2024-09-10 14:46:30 +08:00
|
|
|
|
2023-04-06 22:41:55 +03:00
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2023-04-06 22:41:55 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
2023-04-06 22:41:55 +03:00
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
2023-04-06 20:18:01 +03:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2021-05-11 17:13:35 -04:00
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-20 10:01:07 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-11 17:13:34 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-06-02 11:29:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-20 10:01:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
2019-11-06 08:12:11 -08:00
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-25 20:40:17 +08:00
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-18 16:11:04 +05:30
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2014-02-18 16:11:04 +05:30
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-12 03:05:56 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
2016-01-12 03:05:56 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
2016-01-12 03:05:56 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-25 20:40:17 +08:00
|
|
|
|
2014-09-16 17:54:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-25 20:40:17 +08:00
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-28 19:32:05 +05:30
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2015-05-26 18:19:45 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-25 20:40:17 +08:00
|
|
|
|
2016-01-12 03:05:56 -08:00
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-25 20:40:16 +08:00
|
|
|
|
|
|
|
|
|
2021-05-25 20:40:17 +08:00
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-20 10:01:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
2016-04-20 10:01:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
2016-04-20 10:01:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-20 10:01:07 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
2021-05-25 20:40:17 +08:00
|
|
|
|
|
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
2014-09-16 17:54:01 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-11-06 08:12:11 -08:00
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
2021-05-25 20:40:17 +08:00
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-11 17:13:35 -04:00
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
2021-05-11 17:13:34 -04:00
|
|
|
|
|
|
|
|
|
2021-06-02 11:29:47 +00:00
|
|
|
|
2021-05-11 17:13:34 -04:00
|
|
|
|
|
|
|
|
|
2021-05-25 20:40:17 +08:00
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
2021-05-11 17:13:34 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2021-05-11 17:13:35 -04:00
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-11 17:13:35 -04:00
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-11 17:13:35 -04:00
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2014-09-18 21:48:48 +08:00
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2014-09-14 21:23:01 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:56 +03:00
|
|
|
|
2021-05-25 20:40:17 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
regulator: fan53555: add enable_time support and soft-start times
The datasheets for all the fan53555 variants (and clones using the same
interface) define so called soft start times, from enabling the regulator
until at least some percentage of the output (i.e. 92% for the rk860x
types) are available.
The regulator framework supports this with the enable_time property
but currently the fan53555 driver does not define enable_times for any
variant.
I ran into a problem with this while testing the new driver for the
Rockchip NPUs (rocket), which does runtime-pm including disabling and
enabling a rk8602 as needed. When reenabling the regulator while running
a load, fatal hangs could be observed while enabling the associated
power-domain, which the regulator supplies.
Experimentally setting the regulator to always-on, made the issue
disappear, leading to the missing delay to let power stabilize.
And as expected, setting the enable-time to a non-zero value
according to the datasheet also resolved the regulator-issue.
The datasheets in nearly all cases only specify "typical" values,
except for the fan53555 type 08. There both a typical and maximum
value are listed - 40uS apart.
For all typical values I've added 100uS to be on the safe side.
Individual details for the relevant regulators below:
- fan53526:
The datasheet for all variants lists a typical value of 150uS, so
make that 250uS with safety margin.
- fan53555:
types 08 and 18 (unsupported) are given a typical enable time of 135uS
but also a maximum of 175uS so use that value. All the other types only
have a typical time in the datasheet of 300uS, so give a bit margin by
setting it to 400uS.
- rk8600 + rk8602:
Datasheet reports a typical value of 260us, so use 360uS to be safe.
- syr82x + syr83x:
All datasheets report typical soft-start values of 300uS for these
regulators, so use 400uS.
- tcs452x:
Datasheet sadly does not report a soft-start time, so I've not set
an enable-time
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patch.msgid.link/20250606190418.478633-1-heiko@sntech.de
Signed-off-by: Mark Brown <broonie@kernel.org>
2025-06-06 21:04:18 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2015-01-05 10:04:19 +01:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
2014-11-10 14:43:53 +01:00
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-10 14:43:53 +01:00
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-08-21 11:13:24 +08:00
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
2021-05-11 17:13:35 -04:00
|
|
|
|
2021-06-02 11:29:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-11-18 23:44:35 +01:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-10 14:43:53 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-30 17:20:47 +09:00
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
2014-11-10 14:43:53 +01:00
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
2023-04-06 22:41:57 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2014-09-18 21:49:38 +08:00
|
|
|
|
2023-08-28 17:47:46 +01:00
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:57 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 17:54:01 +02:00
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
2019-02-24 11:21:46 +08:00
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
2014-09-16 17:54:01 +02:00
|
|
|
|
|
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
2023-04-06 22:41:57 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
2023-04-06 22:41:57 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
2023-04-06 22:41:57 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:57 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-19 08:58:23 +08:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
|
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:57 +03:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2023-04-06 22:41:57 +03:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2019-02-20 16:43:03 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
|
|
|
|
|
2023-04-06 22:41:58 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2017-08-21 13:47:43 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2021-04-21 18:03:38 -03:00
|
|
|
|
|
|
|
|
|
2021-05-11 17:13:35 -04:00
|
|
|
|
2021-06-02 11:29:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-16 21:22:54 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
2015-07-30 18:18:40 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
regulator: Set PROBE_PREFER_ASYNCHRONOUS for drivers that existed in 4.14
Probing of regulators can be a slow operation and can contribute to
slower boot times. This is especially true if a regulator is turned on
at probe time (with regulator-boot-on or regulator-always-on) and the
regulator requires delays (off-on-time, ramp time, etc).
While the overall kernel is not ready to switch to async probe by
default, as per the discussion on the mailing lists [1] it is believed
that the regulator subsystem is in good shape and we can move
regulator drivers over wholesale. There is no way to just magically
opt in all regulators (regulators are just normal drivers like
platform_driver), so we set PROBE_PREFER_ASYNCHRONOUS for all
regulators found in 'drivers/regulator' individually.
Given the number of drivers touched and the impossibility to test this
ahead of time, it wouldn't be shocking at all if this caused a
regression for someone. If there is a regression caused by this patch,
it's likely to be one of the cases talked about in [1]. As a "quick
fix", drivers involved in the regression could be fixed by changing
them to PROBE_FORCE_SYNCHRONOUS. That being said, the correct fix
would be to directly fix the problem that caused the issue with async
probe.
The approach here follows a similar approach that was used for the mmc
subsystem several years ago [2]. In fact, I ran nearly the same python
script to auto-generate the changes. The only thing I changed was to
search for "i2c_driver", "spmi_driver", and "spi_driver" in addition
to "platform_driver".
[1] https://lore.kernel.org/r/06db017f-e985-4434-8d1d-02ca2100cca0@sirena.org.uk
[2] https://lore.kernel.org/r/20200903232441.2694866-1-dianders@chromium.org/
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Link: https://lore.kernel.org/r/20230316125351.1.I2a4677392a38db5758dee0788b2cea5872562a82@changeid
Signed-off-by: Mark Brown <broonie@kernel.org>
2023-03-16 12:54:38 -07:00
|
|
|
|
2014-09-16 21:22:53 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
2023-05-06 00:02:18 +02:00
|
|
|
|
2012-09-08 03:52:18 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|