On 02/12/2024 15:04, Konrad Dybcio wrote: >>>> > >>>> IP blocks like SE can be shared. Here we are talking about I2C sharing. >>>> In future it can be SPI sharing. But design wise it fits better to add >>>> flag per SE node. Same we shall be adding for SPI too in future. >>> >>> >>> How flag per SE node is relevant? I did not ask to move the property. >>> >>>> >>>> Please let me know your further suggestions. >>> We do not talk about I2C or SPI here only. We talk about entire SoC. >>> Since beginning. Find other patch proposals and align with rest of >>> Qualcomm developers so that you come with only one definition for this >>> feature/characteristic. Or do you want to say that I am free to NAK all >>> further properties duplicating this one? > > I'm not sure a single property name+description can fit all possible > cases here. The hardware being "shared" can mean a number of different Existing property does not explain anything more, either. To recap - this block is SE and property is named "se-shared", so basically it is equal to just "shared". "shared" is indeed quite vague, so I was expecting some wider work here. > things, with some blocks having hardware provisions for that, while > others may have totally none and rely on external mechanisms (e.g. > a shared memory buffer) to indicate whether an external entity > manages power to them. We have properties for that too. Qualcomm SoCs need once per year for such shared properties. BAM has two or three. IPA has two. There are probably even more blocks which I don't remember now. > > Even here, I'm not particularly sure whether dt is the right place. > Maybe we could think about checking for clock_is_enabled()? That's > just an idea, as it may fall apart if CCF gets a .sync_state impl. Best regards, Krzysztof
