On 2/26/20 7:27 PM, Tony Lindgren wrote: > * Suman Anna <s-anna@xxxxxx> [200226 20:31]: >> On 2/26/20 12:26 PM, Tony Lindgren wrote: >>> * Suman Anna <s-anna@xxxxxx> [200224 15:22]: >>>> Hi Tony, >>>> >>>> The following patches drop the hwmod data for PRUSS on AM33xx and AM437x >>>> SoCs, and for the IPU and DSP processors on OMAP4 SoC. Patches are based >>>> on 5.6-rc1. Please consider these for the 5.7 merge window. >>>> >>>> I will be submitting another series tomorrow to add the ti-sysc support >>>> for PRUSS. Nevertheless, the PRUSS hwmods will not be used going forward >>>> and can be dropped independently. >>>> >>>> The IPU and DSP hwmods were never added for OMAP5 and DRA7xx/AM57xx SoCs, >>>> and the MMU data was already dropped for 5.6-rc1, as it has all been >>>> converted to ti-sysc and omap-prm. The DT nodes for these will follow >>>> for the next merge window once the current OMAP remoteproc DT support >>>> is accepted [1]. >>> >>> Well we still need the hwmod data until dts data is in place to reset >>> and idle these modules. So I'll wait with this set until we have the >>> dts changes in place. >> >> Not really, you cannot just idle these processors devices by themselves >> without the cores running. The hwmod code actually keeps these in the >> default reset asserted state itself, so no harm done in dropping the >> data. The remoteproc bindings are acked, so for next merge window, we >> can post the dts nodes once those get merged. > > OK if they are in reset from the bootloader.. I'll try to check. OK thanks. FWIW, we have never added the hwmods for IPUs and DSPs on OMAP5 and DRA7xx/AM57xx, and most of them are pseudo hwmods anyway for reset purposes, and do not get exercised until the remoteproc driver would have specifically requested for them. regards Suman
