Re: [PATCH 01/12] dt-bindings: i3c: Add mipi-i3c-static-method to support SETAASA
Akhil R <[email protected]>
| Newsgroups | dev.linux.lists.acpica-devel,org.infradead.lists.linux-i3c,org.kernel.vger.linux-acpi,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-hwmon,org.kernel.vger.linux-kernel,org.kernel.vger.linux-tegra |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 19 Mar 2026 18:14:41 +0100, Krzysztof Kozlowski wrote: > On 19/03/2026 18:01, Akhil R wrote: >>> >>>> more than one method. It also cannot represent the vendor extensions (Bit 2) >>>> cleanly. Would this be better if we use macros instead of raw numbers? >>> >>> Hoes does setting bit 2 differ from a string "vendor"? >> >> Okay, a string array would handle those cases. >> >> I am concerned if this can be a string array for the ACPI because the MIPI >> specification defines the property differently. Would it be fine to deviate >> from that specification in the ACPI? Or do you suggest to keep it as bitmap >> for the ACPI and use strings in DT? > > We are not defining here a property for the ACPI. I don't suggest > anything for ACPI. Understood. I will wait for responses in the driver changes to determine what works best. This property is primarily intended for the ACPI and if it does not align with DT, I would prefer to drop this from the binding in the next revision - if you agree. Best Regards, Akhil