On 2017-05-29 14:47, Mika Westerberg wrote: > On Mon, May 29, 2017 at 01:33:29PM +0200, Jan Kiszka wrote: >> Enhance acpi_load_table to also return the table index. Use that index >> to unload the table again when the corresponding directory in configfs >> gets removed. This allows to change SSDTs without rebooting the system. >> It also allows to destroy devices again that a dynamically loaded SSDT >> created. >> >> This is widely similar to the DT overlay behavior. >> >> Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> >> --- >> >> Can someone explain to me why an unloaded table still sticks around in >> sysfs and why we cannot release its ID and rather have to use a new one >> when loading a modified version? > > IIRC ACPICA relies the fact that SSDTs are never unloaded. Bob (CC'd) > can correct me if I got it wrong. OK... Is that standard-driven or just a limitation of this implementation? Is there an upper limit of tables? I'm thinking of lengthy development sessions that play with tables, loading and unloading modified versions. Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
