On 05/16/2018 11:09 PM, Mark Brown wrote: > On Tue, Apr 24, 2018 at 01:46:21PM -0700, David Collins wrote: >> The RPMh hardware is aware of the parent-child connections between >> regulators as well as minimum headroom to ensure stable LDO voltage output >> for subregulated LDOs. The intention of having the headroom be a >> configurable property for processors is to support usecases in which >> subregulated LDO loads are particularly sensitive to noise and require >> additional headroom. Such usecases are board dependent and beyond the >> baseline configurations set in RPMh hardware. > > So the hardware implementation is some hard coding stuff that doesn't > really adequately reflect reality? This seems unfortunate. However do > we really need to tell the hardware about the fact that we're adding > extra headroom - are there actual interactions with non-Linux things > here? The RPMh hardware is configured by the boot loader. The configuration does reflect reality; however, it cannot handle all configurations at initialization time. Specific headroom management typically comes up in modem usecases for RF supplies that are sensitive to noise. This feature allows RPMh masters (application processor, modem processor, etc) to make requests only for the regulators that they directly care about without having to worry about power grid parent-child details and setting the voltage of parent regulators in order to ensure sufficient headroom. If you really don't like having this feature present in the Linux RPMh regulator driver, then I'd be ok removing it. It is not required for SDM845 which the driver is initially targeting. >>>> XOB managed regulators physically cannot change voltage. Therefore, do >>>> you agree that it is reasonable to use fixed_uV for them? Note that I >>>> removed init_data->constraints.apply_uV manipulation in version 2 of this >>>> patch. > >>> If these regulators can't change voltage then surely we know what >>> voltage they have without needing it to be specified in DT? > >> In the case of XOB managed LDO regulators, the LDOs physically can be >> configured to different voltages by the bootloader. However, the RPMh >> interface provides no mechanism for the application processor to read or >> change that voltage. Therefore, we need a way to specify such voltages in >> a board specific (as opposed to driver specific) manner (i.e. device tree). > > Is the kernel somehow prevented from varying these voltages? Yes. Physically, there exists no RPMh register to read or write the voltage of LDOs managed via XOB. Additionally, the kernel running on the application processor is blocked from configuring the voltage via a direct SPMI writes by access permissions that crash the system when violated. Take care, David -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
