On 27/02/2026 06:52, Jingyi Wang wrote: > qcom,milos-pas.yaml > qcom,sa8775p-pas.yaml > qcom,sc7180-pas.yaml > qcom,sm8150-pas.yaml > qcom,sm8350-pas.yaml > modifying pas-common means we need to add explicit list in each file, > (also we need to add constraint for smem-state) > > To avoid affecting the existing yaml bindings, we assume below > Option2: have a new common file for soccp yaml with "pong" > interrupt along with 4 corresponding "smem-state" > > the example will be like: > kaanapali-soccp.yaml ref with soccp-common.yaml. and the common yaml > will be very much pas-common.yaml content, while the interrupt and > smem state will be updated. >
I don't understand how many files you want to have. Two new files, so three common files? You need one place for definition of common properties, so all smem-states and smd/glink-edge. The interrupts don't have to be there at all. They were placed because some devices have similar constraints and the lists should be shared. If the list anyway cannot be shared via common file, just move it to individual schemas. The other common bits like clocks and power-domains also make little point in the common file if they are not actually fixed (thus common). Best regards, Krzysztof
