On Sun, Nov 22, 2020 at 11:59:20AM +0100, Krzysztof Kozlowski wrote:
On Fri, Nov 20, 2020 at 08:04:29PM +0000, Mark Brown wrote:
On Fri, Nov 20, 2020 at 08:42:45PM +0100, Krzysztof Kozlowski wrote:
On Fri, Nov 20, 2020 at 04:56:34PM +0000, Mark Brown wrote:
It would be better to fix these by annotating the table as potentially unused, if nothing else it means if someone wants to add ACPI support (or it just works on their ACPI system with the plain old I2C ID) then they don't need to revert this change.
The point is after this patch - removal of of_match_ptr() - they will already support the ACPI matching through the PRP0001.
Keeping of_match_ptr() and maybe_unused will prevent any ACPI re-usage unless explicit ACPI table is added
Surely if that's the desired outcome the fix is to change the definition of of_match_ptr() such that it leaves the reference with CONFIG_ACPI, perhaps hidden behind a config option for PRP0001? That seems better than going through the entire tree like this.
That could be indeed an easier way to achieve this.
...easier and wrong in my opinion. Not all drivers need that. What the point to touch it in the driver which is OF-only? (For IP which will quite unlikely to be present in ACPI world) Or if the device will get the correct ACPI ID?
+Cc Andy, Rafael,
I guess Rafael can correct me or others.
I saw you were doing similar way as I did here [1] for the 698fffc2705c ("rtc: ds1307: Drop of_match_ptr and CONFIG_OF protections") with the same reasoning as mine ("These prevent use of this driver with ACPI via PRP0001.").
The above is a device which can be connected to any system, including ACPI-based one. The patch has been cooked to have some means to make it usable on such systems (because previous patch removes wrong ACPI IDs).
Do you have thoughts on Mark's proposal above (to change the of_match_ptr())?
[1] https://lore.kernel.org/lkml/20201120161653.445521-1-krzk@kernel.org/