On 18/05/2023 05:23, zhuyinbo wrote: > > > 在 2023/5/17 下午11:00, Krzysztof Kozlowski 写道: >> On 17/05/2023 09:31, Yinbo Zhu wrote: >>> Add the Loongson-2 SoC Power Management Controller binding with DT >>> schema format using json-schema. >>> >>> Signed-off-by: Yinbo Zhu <zhuyinbo@xxxxxxxxxxx> >> >> ... >> >>> +properties: >>> + compatible: >>> + items: >>> + - enum: >>> + - loongson,ls2k-pmc >>> + - const: syscon >>> + >>> + reg: >>> + maxItems: 1 >>> + >>> + interrupts: >>> + maxItems: 1 >>> + >>> + suspend-address: >>> + $ref: /schemas/types.yaml#/definitions/uint32 >>> + description: >>> + This option indicate this PM suspend address. >> >> This tells me nothing. Drop "This option indicate this" and rephrase >> everything to actually describe this property. Why would the address >> differ on given, specific SoC? It looks like you just miss compatibles. >> Anyway this needs much more explanation so we can judge whether it fits DT. > > Hi Krzysztof, > > I will add following description about "suspend-address", please review. Thanks. > > The "suspend-address" is a ACPI S3 (Suspend To RAM) firmware entry Why do we add properties for ACPI? This does not seem right. Please reword to skip ACPI stuff, e.g. deep sleep states (Suspend to RAM). > address which was jumped from kernel and it's value was dependent on > specific platform firmware code. "entry address which was jumped" <- the address cannot jump. Please explain who is jumping here - boot CPU? each suspended CPU? I guess the first as CPUs are offlined, right? > In addition, the PM driver need > according to it to indicate that current SoC whether support ACPI S3. Skip references to driver. > Best regards, Krzysztof
