On Tue, Apr 19, 2022 at 11:09:09AM -0700, Dan Williams wrote: > On Tue, Apr 19, 2022 at 9:48 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > On Tue, Apr 19, 2022 at 09:38:51AM -0700, Tony Luck wrote: > > > The initial implementation of IFS is model specific. Enumeration is > > > via a combination of family-model-stepping and a check for a bit in the > > > CORE_CAPABILITIES MSR. > > > > > > Linux has handled this lack of enumeration before with a code stub to > > > create a device. See arch/x86/kernel/pmem.c. Use the same approach > > > here. > > > > Ick, why? Why not just create a simple virtual device and use that? Do > > you really want to bind a driver to this? Or do you already "know" the > > only driver that you have will bind to this? > > With the realization that there may be multiple instances of an > IFS-like capability going forward, and that ideally those capabilities > would move away from a CPU capability bit to an ACPI description, then > it seemed to me that a simulated platform_device for this is a > reasonable fit. I.e. when / if an ACPI _HID is assigned for this > capability the same platform_driver can be reused for those instances. Don't write code today for stuff you do not have right now, you all know that. We can always revisit it in the future. thanks, greg k-h
