Refactor fw_devlink to significantly improve boot time
Subsystems (9)
v2 cover Refactor fw_devlink to significantly improve boot time
The current implementation of fw_devlink is very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.
We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by fw_devlink.
So this patch series refactors fw_devlink to be more efficient. The key difference now is the addition of support for fwnode links -- just a few simple APIs. This also allows most of the code to be moved out of firmware specific (DT mostly) code into driver core.
This brings the following benefits:
- Instead of parsing the device tree multiple times (complexity was close to O(N^3) where N in the number of properties) during bootup, fw_devlink parses each fwnode node/property only once and creates fwnode links. The rest of the fw_devlink code then just looks at these fwnode links to do rest of the work.
- Makes it much easier to debug probe issue due to fw_devlink in the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.
- Much easier to add fw_devlink support to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support to fw_devlink. This series gets that done.
Laurent and Grygorii tested the v1 series and they saw boot time improvment of about 12 seconds and 3 seconds, respectively.
Thanks,
Saravana
[1] - https://lore.kernel.org/linux-pm/CAGETcx-aiW251dhEXT1GNb9bi6YcX8W=jLBrro5CnPuEjGL09g@mail.gmail.com/
v1 -> v2:
Patches 1-6:
- Added the "why" to explain the reverts.
Patch 7:
- Fixed white space comment.
Patch 8:
- Reworded commit text and some function doc.
Patch 11:
- Fixed the build warning this patch would cause by removing a "const". Patch 12:
- Added/updated documentation.
- Changed flags from u32 to u8.
Patch 13:
- Squashed with Patch 10. Will use v1 patch number for the rest of the diff descriptions.
Patch 15:
- Removed an unnecessary unlikely()
Patch 17:
- Refactored fw_devlink_create_devlink() to flip the error handling vs successful paths.
Patch 18:
- Squashed into Patch 17 as requested by Greg.
- Added Tested-by: tags from Laurent and Grygorii.
New Patch 17:
- New patch to delete useless input to add_links()
Saravana Kannan (17):
Revert "driver core: Avoid deferred probe due to
fw_devlink_pause/resume()"
Revert "driver core: Rename dev_links_info.defer_sync to defer_hook" Revert "driver core: Don't do deferred probe in parallel with
kernel_init thread"
Revert "driver core: Remove check in
driver_deferred_probe_force_trigger()"
Revert "of: platform: Batch fwnode parsing when adding all top level
devices"
Revert "driver core: fw_devlink: Add support for batching fwnode
parsing"
driver core: Add fwnode_init()
driver core: Add fwnode link support
driver core: Allow only unprobed consumers for SYNC_STATE_ONLY device
links
device property: Add fwnode_is_ancestor_of() and
fwnode_get_next_parent_dev()
driver core: Redefine the meaning of fwnode_operations.add_links() driver core: Add fw_devlink_parse_fwtree()
driver core: Use device's fwnode to check if it is waiting for
suppliers
of: property: Update implementation of add_links() to create fwnode
links
efi: Update implementation of add_links() to create fwnode links driver core: Refactor fw_devlink feature
driver core: Delete pointless parameter in fwnode_operations.add_links
drivers/acpi/property.c | 2 +- drivers/acpi/scan.c | 2 +- drivers/base/core.c | 555 ++++++++++++++++++++------------ drivers/base/property.c | 52 +++ drivers/base/swnode.c | 2 +- drivers/firmware/efi/efi-init.c | 32 +- drivers/of/dynamic.c | 1 + drivers/of/platform.c | 2 - drivers/of/property.c | 149 +++------ include/linux/device.h | 10 +- include/linux/fwnode.h | 73 ++--- include/linux/of.h | 2 +- include/linux/property.h | 3 + kernel/irq/irqdomain.c | 2 +- 14 files changed, 495 insertions(+), 392 deletions(-)
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 1/17 Revert "driver core: Avoid deferred probe due to fw_devlink_pause/resume()"
This reverts commit 2451e746478a6a6e981cfa66b62b791ca93b90c8.
fw_devlink_pause/resume() was an incomplete attempt at boot time optimization. That's going to get replaced by a much better optimization at the end of the series. Since fw_devlink_pause/resume() is going away, changes made for that can also go away.
--- drivers/base/core.c | 21 --------------------- include/linux/device.h | 3 +-- 2 files changed, 1 insertion(+), 23 deletions(-)
drivers/base/core.c +0 -21
@@ -51,7 +51,6 @@ static DEFINE_MUTEX(wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static unsigned int defer_fw_devlink_count; -static LIST_HEAD (deferred_fw_devlink);static DEFINE_MUTEX (defer_fw_devlink_lock);static bool fw_devlink_is_permissive (void );
@@ -1470,12 +1469,6 @@ static void fw_devlink_link_device(struct device *dev) fw_ret = -EAGAIN ; }else { fw_ret = -ENODEV ; -/* -* defer_hook is not used to add device to deferred_sync list -* until device is bound. Since deferred fw devlink also blocks -* probing, same list hook can be used for deferred_fw_devlink. -*/ -list_add_tail (&dev->links.defer_hook, &deferred_fw_devlink); }if (fw_ret == -ENODEV )
@@ -1544,9 +1537,6 @@ void fw_devlink_pause(void)*/ void fw_devlink_resume (void ) { -struct device *dev, *tmp; -LIST_HEAD (probe_list); -mutex_lock (&defer_fw_devlink_lock);if (!defer_fw_devlink_count) {WARN (true,"Unmatched fw_devlink pause/resume!" );
@@ -1558,19 +1548,8 @@ void fw_devlink_resume(void) goto out;device_link_add_missing_supplier_links (); -list_splice_tail_init (&deferred_fw_devlink, &probe_list); out:mutex_unlock (&defer_fw_devlink_lock); - -/* -* bus_probe_device() can cause new devices to get added and they'll -* try to grab defer_fw_devlink_lock. So, this needs to be done outside -* the defer_fw_devlink_lock. -*/ -list_for_each_entry_safe (dev, tmp, &probe_list, links.defer_hook) { -list_del_init (&dev->links.defer_hook); -bus_probe_device (dev); - } }/* Device links support end. */
include/linux/device.h +1 -2
@@ -352,8 +352,7 @@ enum dl_dev_state {* @suppliers: List of links to supplier devices. * @consumers: List of links to consumer devices. * @needs_suppliers: Hook to global list of devices waiting for suppliers. -* @defer_hook: Hook to global list of devices that have deferred sync_state or -* deferred fw_devlink. +* @defer_hook: Hook to global list of devices that have deferred sync_state. * @need_for_probe: If needs_suppliers is on a list, this indicates if the * suppliers are needed for probe or not. * @status: Driver status information.
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 2/17 Revert "driver core: Rename dev_links_info.defer_sync to defer_hook"
In reply to Saravana KannanThis reverts commit ec7bd78498f29680f536451fbdf9464e851273ed.
This field rename was done to reuse defer_syc list head for multiple lists. That's not needed anymore and this list head will only be used for defer sync. So revert this patch to avoid conflicts with the other reverts coming after this.
--- drivers/base/core.c | 22 +++++++++++----------- include/linux/device.h | 4 ++-- 2 files changed, 13 insertions(+), 13 deletions(-)
drivers/base/core.c +11 -11
@@ -959,11 +959,11 @@ static void __device_links_queue_sync_state(struct device *dev,*/ dev->state_synced = true; -if (WARN_ON (!list_empty (&dev->links.defer_hook))) +if (WARN_ON (!list_empty (&dev->links.defer_sync)))return ;get_device (dev); -list_add_tail (&dev->links.defer_hook, list); +list_add_tail (&dev->links.defer_sync, list); }/**
@@ -981,8 +981,8 @@ static void device_links_flush_sync_list(struct list_head *list, {struct device *dev, *tmp; -list_for_each_entry_safe (dev, tmp, list, links.defer_hook) { -list_del_init (&dev->links.defer_hook); +list_for_each_entry_safe (dev, tmp, list, links.defer_sync) { +list_del_init (&dev->links.defer_sync);if (dev != dont_lock_dev)device_lock (dev);
@@ -1020,12 +1020,12 @@ void device_links_supplier_sync_state_resume(void)if (defer_sync_state_count) goto out; -list_for_each_entry_safe (dev, tmp, &deferred_sync, links.defer_hook) { +list_for_each_entry_safe (dev, tmp, &deferred_sync, links.defer_sync) {/* * Delete from deferred_sync list before queuing it to -* sync_list because defer_hook is used for both lists. +* sync_list because defer_sync is used for both lists. */ -list_del_init (&dev->links.defer_hook); +list_del_init (&dev->links.defer_sync);__device_links_queue_sync_state (dev, &sync_list); } out:
@@ -1043,8 +1043,8 @@ late_initcall(sync_state_resume_initcall);static void __device_links_supplier_defer_sync (struct device *sup) { -if (list_empty (&sup->links.defer_hook) &&dev_has_sync_state (sup)) -list_add_tail (&sup->links.defer_hook, &deferred_sync); +if (list_empty (&sup->links.defer_sync) &&dev_has_sync_state (sup)) +list_add_tail (&sup->links.defer_sync, &deferred_sync); }static void device_link_drop_managed (struct device_link *link)
@@ -1274,7 +1274,7 @@ void device_links_driver_cleanup(struct device *dev)WRITE_ONCE (link->status,DL_STATE_DORMANT ); } -list_del_init (&dev->links.defer_hook); +list_del_init (&dev->links.defer_sync);__device_links_no_driver (dev);device_links_write_unlock ();
@@ -2407,7 +2407,7 @@ void device_initialize(struct device *dev)INIT_LIST_HEAD (&dev->links.consumers);INIT_LIST_HEAD (&dev->links.suppliers);INIT_LIST_HEAD (&dev->links.needs_suppliers); -INIT_LIST_HEAD (&dev->links.defer_hook); +INIT_LIST_HEAD (&dev->links.defer_sync); dev->links.status =DL_DEV_NO_DRIVER ; }EXPORT_SYMBOL_GPL (device_initialize);
include/linux/device.h +2 -2
@@ -352,7 +352,7 @@ enum dl_dev_state {* @suppliers: List of links to supplier devices. * @consumers: List of links to consumer devices. * @needs_suppliers: Hook to global list of devices waiting for suppliers. -* @defer_hook: Hook to global list of devices that have deferred sync_state. +* @defer_sync: Hook to global list of devices that have deferred sync_state. * @need_for_probe: If needs_suppliers is on a list, this indicates if the * suppliers are needed for probe or not. * @status: Driver status information.
@@ -361,7 +361,7 @@ struct dev_links_info {struct list_head suppliers;struct list_head consumers;struct list_head needs_suppliers; -struct list_head defer_hook; +struct list_head defer_sync;bool need_for_probe;enum dl_dev_state status; };
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 3/17 Revert "driver core: Don't do deferred probe in parallel with kernel_init thread"
In reply to Saravana KannanThis reverts commit cec72f3efc6272420c2c2c699607f03d09b93e41.
Commit cec72f3efc62 ("driver core: Don't do deferred probe in parallel with kernel_init thread") was fixing a commit 716a7a259690 ("driver
core: fw_devlink: Add support for batching fwnode parsing"). Since the commit being fixed itself is going to be reverted, the fix can also be reverted.
--- drivers/base/base.h | 1 + drivers/base/core.c | 1 + drivers/base/dd.c | 5 +++++ 3 files changed, 7 insertions(+)
drivers/base/base.h +1 -0
@@ -156,6 +156,7 @@ extern char *make_class_name(const char *name, struct kobject *kobj);extern int devres_release_all (struct device *dev);extern void device_block_probing (void );extern void device_unblock_probing (void ); +extern void driver_deferred_probe_force_trigger (void );/* /sys/devices directory */ extern struct kset *devices_kset;
drivers/base/core.c +1 -0
@@ -1548,6 +1548,7 @@ void fw_devlink_resume(void) goto out;device_link_add_missing_supplier_links (); +driver_deferred_probe_force_trigger (); out:mutex_unlock (&defer_fw_devlink_lock); }
drivers/base/dd.c +5 -0
@@ -167,6 +167,11 @@ static void driver_deferred_probe_trigger(void)if (!driver_deferred_probe_enable)return ; +driver_deferred_probe_force_trigger (); +} + +void driver_deferred_probe_force_trigger (void ) +{/* * A successful probe means that all the devices in the pending list * should be triggered to be reprobed. Move all the deferred devices
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 4/17 Revert "driver core: Remove check in driver_deferred_probe_force_trigger()"
In reply to Saravana KannanThis reverts commit fefcfc968723caf93318613a08e1f3ad07a6154f.
The reverted commit is fixing commit 716a7a259690 ("driver core:fw_devlink: Add support for batching fwnode parsing"). Since the original commit will be reverted, the fix can be reverted too.
--- drivers/base/dd.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/base/dd.c +3 -0
@@ -172,6 +172,9 @@ static void driver_deferred_probe_trigger(void)void driver_deferred_probe_force_trigger (void ) { +if (!driver_deferred_probe_enable) +return ; +/* * A successful probe means that all the devices in the pending list * should be triggered to be reprobed. Move all the deferred devices
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 5/17 Revert "of: platform: Batch fwnode parsing when adding all top level devices"
In reply to Saravana KannanThis reverts commit 93d2e4322aa74c1ad1e8c2160608eb9a960d69ff.
The fw_devlink_pause/resume() optimization attempt is getting replaced with a much more robust optimization by the end of this series. So, stop using those APIs.
--- drivers/of/platform.c | 2 -- 1 file changed, 2 deletions(-)
drivers/of/platform.c +0 -2
@@ -538,9 +538,7 @@ static int __init of_platform_default_populate_init(void) }/* Populate everything else. */ -fw_devlink_pause ();of_platform_default_populate (NULL ,NULL ,NULL ); -fw_devlink_resume ();return 0 ; }
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 05/17] Revert "of: platform: Batch fwnode parsing when adding all top level devices"
Quoted 11 lines · Saravana Kannan
This reverts commit
93d2e4322aa74c1ad1e8c2160608eb9a960d69ff.The fw_devlink_pause/resume() optimization attempt is getting replaced with a much more robust optimization by the end of this series. So, stop using those APIs.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 2 -- 1 file changed, 2 deletions(-)
PATCH v2 6/17 Revert "driver core: fw_devlink: Add support for batching fwnode parsing"
In reply to Saravana KannanThis reverts commit 716a7a25969003d82ab738179c3f1068a120ed11.
The fw_devlink_pause/resume() APIs added by the commit being reverted were a first cut attempt at optimizing boot time. But these APIs don't fully solve the problem and are very fragile (can only be used for the top level devices being added). This series replaces them with a much better optimization that works for all device additions and also has the benefit of reducing the complexity of the firmware (DT, EFI) specific code and abstracting out common code to driver core.
--- drivers/base/base.h | 1 - drivers/base/core.c | 116 +++-------------------------------------- drivers/base/dd.c | 8 --- include/linux/fwnode.h | 2 - 4 files changed, 7 insertions(+), 120 deletions(-)
drivers/base/base.h +0 -1
@@ -156,7 +156,6 @@ extern char *make_class_name(const char *name, struct kobject *kobj);extern int devres_release_all (struct device *dev);extern void device_block_probing (void );extern void device_unblock_probing (void ); -extern void driver_deferred_probe_force_trigger (void );/* /sys/devices directory */ extern struct kset *devices_kset;
drivers/base/core.c +7 -109
139 lines not on this page · raw message
drivers/base/dd.c +0 -8
@@ -163,14 +163,6 @@ static bool driver_deferred_probe_enable = false;* again. */ static void driver_deferred_probe_trigger (void ) -{ -if (!driver_deferred_probe_enable) -return ; - -driver_deferred_probe_force_trigger (); -} - -void driver_deferred_probe_force_trigger (void ) {if (!driver_deferred_probe_enable)return ;
include/linux/fwnode.h +0 -2
@@ -171,7 +171,5 @@ struct fwnode_operations {#define get_dev_from_fwnode (fwnode) get_device((fwnode)->dev)extern u32 fw_devlink_get_flags (void ); -void fw_devlink_pause (void ); -void fw_devlink_resume (void );#endif
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 7/17 driver core: Add fwnode_init()
In reply to Saravana KannanThere are multiple locations in the kernel where a struct fwnode_handle is initialized. Add fwnode_init() so that we have one way of initializing a fwnode_handle.
--- drivers/acpi/property.c | 2 +- drivers/acpi/scan.c | 2 +- drivers/base/swnode.c | 2 +- drivers/firmware/efi/efi-init.c | 8 ++++---- include/linux/fwnode.h | 6 ++++++ include/linux/of.h | 2 +- kernel/irq/irqdomain.c | 2 +- 7 files changed, 15 insertions(+), 9 deletions(-)
drivers/acpi/property.c +1 -1
@@ -76,7 +76,7 @@ static bool acpi_nondev_subnode_extract(const union acpi_object *desc,return false; dn->name = link->package.elements[0 ].string.pointer; - dn->fwnode.ops = &acpi_data_fwnode_ops; +fwnode_init (&dn->fwnode, &acpi_data_fwnode_ops); dn->parent = parent;INIT_LIST_HEAD (&dn->data.properties);INIT_LIST_HEAD (&dn->data.subnodes);
drivers/acpi/scan.c +1 -1
@@ -1589,7 +1589,7 @@ void acpi_init_device_object(struct acpi_device *device, acpi_handle handle, device->device_type = type; device->handle = handle; device->parent =acpi_bus_get_parent (handle); - device->fwnode.ops = &acpi_device_fwnode_ops; +fwnode_init (&device->fwnode, &acpi_device_fwnode_ops);acpi_set_device_status (device, sta);acpi_device_get_busid (device);acpi_set_pnp_ids (handle, &device->pnp, type);
drivers/base/swnode.c +1 -1
@@ -653,7 +653,7 @@ swnode_register(const struct software_node *node, struct swnode *parent, swnode->parent = parent; swnode->allocated = allocated; swnode->kobj.kset = swnode_kset; - swnode->fwnode.ops = &software_node_ops; +fwnode_init (&swnode->fwnode, &software_node_ops);ida_init (&swnode->child_ids);INIT_LIST_HEAD (&swnode->entry);
drivers/firmware/efi/efi-init.c +4 -4
@@ -359,9 +359,7 @@ static const struct fwnode_operations efifb_fwnode_ops = { .add_links = efifb_add_links, }; -static struct fwnode_handle efifb_fwnode = { - .ops = &efifb_fwnode_ops, -}; +static struct fwnode_handle efifb_fwnode;static int __init register_gop_device (void ) {
@@ -375,8 +373,10 @@ static int __init register_gop_device(void)if (!pd)return -ENOMEM ; -if (IS_ENABLED (CONFIG_PCI )) +if (IS_ENABLED (CONFIG_PCI )) { +fwnode_init (&efifb_fwnode, &efifb_fwnode_ops); pd->dev.fwnode = &efifb_fwnode; + } err =platform_device_add_data (pd, &screen_info,sizeof (screen_info));if (err)
include/linux/fwnode.h +6 -0
@@ -170,6 +170,12 @@ struct fwnode_operations { } while (false)#define get_dev_from_fwnode (fwnode) get_device((fwnode)->dev) +static inline void fwnode_init (struct fwnode_handle *fwnode, +const struct fwnode_operations *ops) +{ + fwnode->ops = ops; +} +extern u32 fw_devlink_get_flags (void );#endif
include/linux/of.h +1 -1
@@ -108,7 +108,7 @@ static inline void of_node_init(struct device_node *node)#if defined(CONFIG_OF_KOBJ )kobject_init (&node->kobj, &of_node_ktype);#endif - node->fwnode.ops = &of_fwnode_ops; +fwnode_init (&node->fwnode, &of_fwnode_ops); }#if defined(CONFIG_OF_KOBJ )
kernel/irq/irqdomain.c +1 -1
@@ -91,7 +91,7 @@ struct fwnode_handle *__irq_domain_alloc_fwnode(unsigned int type, int id, fwid->type = type; fwid->name = n; fwid->pa = pa; - fwid->fwnode.ops = &irqchip_fwnode_ops; +fwnode_init (&fwid->fwnode, &irqchip_fwnode_ops);return &fwid->fwnode; }EXPORT_SYMBOL_GPL (__irq_domain_alloc_fwnode);
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 07/17] driver core: Add fwnode_init()
Quoted 5 lines · Saravana Kannan
There are multiple locations in the kernel where a struct
fwnode_handleis initialized. Addfwnode_init()so that we have one way of initializing afwnode_handle.Signed-off-by Saravana Kannan <[email protected]>
Quoted 9 lines
--- drivers/acpi/property.c | 2 +- drivers/acpi/scan.c | 2 +- drivers/base/swnode.c | 2 +- drivers/firmware/efi/efi-init.c | 8 ++++---- include/linux/fwnode.h | 6 ++++++ include/linux/of.h | 2 +- kernel/irq/irqdomain.c | 2 +- 7 files changed, 15 insertions(+), 9 deletions(-)
In this series, I didn't find any extension of fwnode_init() to be it more than simple assignment. This change looks to me like unnecessary churn and obfuscation rather than improvement.
"...ops = &...;" is pretty standard in the kernel to initialize ops structures.
Thanks
Re: [PATCH v2 07/17] driver core: Add fwnode_init()
Quoted 17 lines · Leon Romanovsky
Quoted 5 lines · Saravana Kannan
There are multiple locations in the kernel where a struct
fwnode_handleis initialized. Addfwnode_init()so that we have one way of initializing afwnode_handle.Signed-off-by Saravana Kannan <[email protected]>Quoted 9 lines
--- drivers/acpi/property.c | 2 +- drivers/acpi/scan.c | 2 +- drivers/base/swnode.c | 2 +- drivers/firmware/efi/efi-init.c | 8 ++++---- include/linux/fwnode.h | 6 ++++++ include/linux/of.h | 2 +- kernel/irq/irqdomain.c | 2 +- 7 files changed, 15 insertions(+), 9 deletions(-)
Quoted 6 lines
In this series, I didn't find any extension of
fwnode_init()to be it more than simple assignment. This change looks to me like unnecessary churn and obfuscation rather than improvement."...ops = &...;" is pretty standard in the kernel to initialize ops structures.
Subsequent patches make fwnode_init() do more stuff.
-Saravana
Re: [PATCH v2 07/17] driver core: Add fwnode_init()
Quoted 18 lines · Saravana Kannan
Quoted 17 lines · Leon Romanovsky
Quoted 14 lines · Saravana Kannan
There are multiple locations in the kernel where a struct
fwnode_handleis initialized. Addfwnode_init()so that we have one way of initializing afwnode_handle.Signed-off-by Saravana Kannan <[email protected]>--- drivers/acpi/property.c | 2 +- drivers/acpi/scan.c | 2 +- drivers/base/swnode.c | 2 +- drivers/firmware/efi/efi-init.c | 8 ++++---- include/linux/fwnode.h | 6 ++++++ include/linux/of.h | 2 +- kernel/irq/irqdomain.c | 2 +- 7 files changed, 15 insertions(+), 9 deletions(-)
Quoted 8 lines
Quoted 6 lines
In this series, I didn't find any extension of
fwnode_init()to be it more than simple assignment. This change looks to me like unnecessary churn and obfuscation rather than improvement."...ops = &...;" is pretty standard in the kernel to initialize ops structures.
Subsequent patches make
fwnode_init()do more stuff.
But not in this series, right?
Thanks
Quoted 2 lines
-Saravana
Re: [PATCH v2 07/17] driver core: Add fwnode_init()
Quoted 24 lines · Leon Romanovsky
Quoted 22 lines · Saravana Kannan
Quoted 21 lines · Leon Romanovsky
Quoted 5 lines · Saravana Kannan
There are multiple locations in the kernel where a struct
fwnode_handleis initialized. Addfwnode_init()so that we have one way of initializing afwnode_handle.Signed-off-by Saravana Kannan <[email protected]>Quoted 9 lines
--- drivers/acpi/property.c | 2 +- drivers/acpi/scan.c | 2 +- drivers/base/swnode.c | 2 +- drivers/firmware/efi/efi-init.c | 8 ++++---- include/linux/fwnode.h | 6 ++++++ include/linux/of.h | 2 +- kernel/irq/irqdomain.c | 2 +- 7 files changed, 15 insertions(+), 9 deletions(-)In this series, I didn't find any extension of
fwnode_init()to be it more than simple assignment. This change looks to me like unnecessary churn and obfuscation rather than improvement.
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
"...ops = &...;" is pretty standard in the kernel to initialize ops structures.
Subsequent patches make
fwnode_init()do more stuff.But not in this series, right?
In this series. The very next patch - Patch 8/17 :)
-Saravana
Re: [PATCH v2 07/17] driver core: Add fwnode_init()
Quoted 25 lines · Saravana Kannan
Quoted 24 lines · Leon Romanovsky
Quoted 22 lines · Saravana Kannan
Quoted 21 lines · Leon Romanovsky
Quoted 5 lines · Saravana Kannan
There are multiple locations in the kernel where a struct
fwnode_handleis initialized. Addfwnode_init()so that we have one way of initializing afwnode_handle.Signed-off-by Saravana Kannan <[email protected]>Quoted 9 lines
--- drivers/acpi/property.c | 2 +- drivers/acpi/scan.c | 2 +- drivers/base/swnode.c | 2 +- drivers/firmware/efi/efi-init.c | 8 ++++---- include/linux/fwnode.h | 6 ++++++ include/linux/of.h | 2 +- kernel/irq/irqdomain.c | 2 +- 7 files changed, 15 insertions(+), 9 deletions(-)In this series, I didn't find any extension of
fwnode_init()to be it more than simple assignment. This change looks to me like unnecessary churn and obfuscation rather than improvement.
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
"...ops = &...;" is pretty standard in the kernel to initialize ops structures.
Subsequent patches make
fwnode_init()do more stuff.But not in this series, right?
In this series. The very next patch - Patch 8/17 :)
Thanks, sorry for the noise.
Quoted 2 lines
-Saravana
Re: [PATCH v2 07/17] driver core: Add fwnode_init()
In reply to Saravana KannanQuoted 5 lines · Saravana Kannan
There are multiple locations in the kernel where a struct
fwnode_handleis initialized. Addfwnode_init()so that we have one way of initializing afwnode_handle.Signed-off-by Saravana Kannan <[email protected]>
Quoted 10 lines
--- drivers/acpi/property.c | 2 +- drivers/acpi/scan.c | 2 +- drivers/base/swnode.c | 2 +- drivers/firmware/efi/efi-init.c | 8 ++++---- include/linux/fwnode.h | 6 ++++++ include/linux/of.h | 2 +- kernel/irq/irqdomain.c | 2 +- 7 files changed, 15 insertions(+), 9 deletions(-)
PATCH v2 8/17 driver core: Add fwnode link support
In reply to Saravana KannanAdd support for creating supplier-consumer links between fwnodes. It is intended for internal use the driver core and generic firmware support code (eg. Device Tree, ACPI), so it is simple by design and the API provided is limited.
--- drivers/base/core.c | 98 ++++++++++++++++++++++++++++++++++++++++++ drivers/of/dynamic.c | 1 + include/linux/fwnode.h | 14 ++++++ 3 files changed, 113 insertions(+)
drivers/base/core.c +98 -0
@@ -50,6 +50,104 @@ static LIST_HEAD(wait_for_suppliers);static DEFINE_MUTEX (wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ; +static DEFINE_MUTEX (fwnode_link_lock); + +/** +* fwnode_link_add - Create a link between two fwnode_handles. +* @con: Consumer end of the link. +* @sup: Supplier end of the link. +* +* Create a fwnode link between fwnode handles @con and @sup. The fwnode link +* represents the detail that the firmware lists @sup fwnode as supplying a +* resource to @con. +* +* The driver core will use the fwnode link to create a device link between the +* two device objects corresponding to @con and @sup when they are created. The +* driver core will automatically delete the fwnode link between @con and @sup +* after doing that. +* +* Attempts to create duplicate links between the same pair of fwnode handles +* are ignored and there is no reference counting. +*/ +int fwnode_link_add (struct fwnode_handle *con,struct fwnode_handle *sup) +{ +struct fwnode_link *link; +int ret =0 ; + +mutex_lock (&fwnode_link_lock); + +list_for_each_entry (link, &sup->consumers, s_hook) +if (link->consumer == con) + goto out; + + link =kzalloc (sizeof (*link),GFP_KERNEL ); +if (!link) { + ret = -ENOMEM ; + goto out; + } + + link->supplier = sup; +INIT_LIST_HEAD (&link->s_hook); + link->consumer = con; +INIT_LIST_HEAD (&link->c_hook); + +list_add (&link->s_hook, &sup->consumers); +list_add (&link->c_hook, &con->suppliers); +out: +mutex_unlock (&fwnode_link_lock); + +return ret; +} + +/** +* fwnode_links_purge_suppliers - Delete all supplier links of fwnode_handle. +* @fwnode: fwnode whose supplier links need to be deleted +* +* Deletes all supplier links connecting directly to @fwnode. +*/ +static void fwnode_links_purge_suppliers (struct fwnode_handle *fwnode) +{ +struct fwnode_link *link, *tmp; + +mutex_lock (&fwnode_link_lock); +list_for_each_entry_safe (link, tmp, &fwnode->suppliers, c_hook) { +list_del (&link->s_hook); +list_del (&link->c_hook); +kfree (link); + } +mutex_unlock (&fwnode_link_lock); +} + +/** +* fwnode_links_purge_consumers - Delete all consumer links of fwnode_handle. +* @fwnode: fwnode whose consumer links need to be deleted +* +* Deletes all consumer links connecting directly to @fwnode. +*/ +static void fwnode_links_purge_consumers (struct fwnode_handle *fwnode) +{ +struct fwnode_link *link, *tmp; + +mutex_lock (&fwnode_link_lock); +list_for_each_entry_safe (link, tmp, &fwnode->consumers, s_hook) { +list_del (&link->s_hook); +list_del (&link->c_hook); +kfree (link); + } +mutex_unlock (&fwnode_link_lock); +} + +/** +* fwnode_links_purge - Delete all links connected to a fwnode_handle. +* @fwnode: fwnode whose links needs to be deleted +* +* Deletes all links connecting directly to a fwnode. +*/ +void fwnode_links_purge (struct fwnode_handle *fwnode) +{ +fwnode_links_purge_suppliers (fwnode); +fwnode_links_purge_consumers (fwnode); +}#ifdef CONFIG_SRCU static DEFINE_MUTEX (device_links_lock);
drivers/of/dynamic.c +1 -0
@@ -356,6 +356,7 @@ void of_node_release(struct kobject *kobj)property_list_free (node->properties);property_list_free (node->deadprops); +fwnode_links_purge (of_fwnode_handle (node));kfree (node->full_name);kfree (node->data);
include/linux/fwnode.h +14 -0
@@ -10,6 +10,7 @@#define _LINUX_FWNODE_H_#include <linux/types.h> +#include <linux/list.h> struct fwnode_operations ;struct device ;
@@ -18,6 +19,15 @@ struct fwnode_handle {struct fwnode_handle *secondary;const struct fwnode_operations *ops;struct device *dev; +struct list_head suppliers; +struct list_head consumers; +}; + +struct fwnode_link { +struct fwnode_handle *supplier; +struct list_head s_hook; +struct fwnode_handle *consumer; +struct list_head c_hook; };/**
@@ -174,8 +184,12 @@ static inline void fwnode_init(struct fwnode_handle *fwnode, const struct fwnode_operations *ops) { fwnode->ops = ops; +INIT_LIST_HEAD (&fwnode->consumers); +INIT_LIST_HEAD (&fwnode->suppliers); }extern u32 fw_devlink_get_flags (void ); +int fwnode_link_add (struct fwnode_handle *con,struct fwnode_handle *sup); +void fwnode_links_purge (struct fwnode_handle *fwnode);#endif
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 08/17] driver core: Add fwnode link support
Quoted 28 lines · Saravana Kannan
Add support for creating supplier-consumer links between fwnodes. It is intended for internal use the driver core and generic firmware support code (eg. Device Tree, ACPI), so it is simple by design and the API provided is limited.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 98 ++++++++++++++++++++++++++++++++++++++++++ drivers/of/dynamic.c | 1 + include/linux/fwnode.h | 14 ++++++ 3 files changed, 113 insertions(+)drivers/base/core.c +8
-0@@ -50,6 +50,104 @@ static LIST_HEAD(wait_for_suppliers);static DEFINE_MUTEX (wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ; +static DEFINE_MUTEX (fwnode_link_lock); + +/** +* fwnode_link_add - Create a link between two fwnode_handles. +* @con: Consumer end of the link. +* @sup: Supplier end of the link. +* +* Create a fwnode link between fwnode handles @con and @sup. The fwnode link
drivers/base/core.c static LIST_HEAD(wait_for_suppliers); · line 70
Quoted 10 lines
drivers/base/core.c +10
-0+* represents the detail that the firmware lists @sup fwnode as supplying a +* resource to @con. +* +* The driver core will use the fwnode link to create a device link between the +* two device objects corresponding to @con and @sup when they are created. The +* driver core will automatically delete the fwnode link between @con and @sup +* after doing that. +* +* Attempts to create duplicate links between the same pair of fwnode handles +* are ignored and there is no reference counting.
Sorry to ask, but why is that?
Isn't this a programmer error?
Thanks
Re: [PATCH v2 08/17] driver core: Add fwnode link support
Quoted 35 lines · Leon Romanovsky
Quoted 33 lines · Saravana Kannan
Add support for creating supplier-consumer links between fwnodes. It is intended for internal use the driver core and generic firmware support code (eg. Device Tree, ACPI), so it is simple by design and the API provided is limited.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 98 ++++++++++++++++++++++++++++++++++++++++++ drivers/of/dynamic.c | 1 + include/linux/fwnode.h | 14 ++++++ 3 files changed, 113 insertions(+)drivers/base/core.c +13
-0@@ -50,6 +50,104 @@ static LIST_HEAD(wait_for_suppliers);static DEFINE_MUTEX (wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ; +static DEFINE_MUTEX (fwnode_link_lock); + +/** +* fwnode_link_add - Create a link between two fwnode_handles. +* @con: Consumer end of the link. +* @sup: Supplier end of the link. +* +* Create a fwnode link between fwnode handles @con and @sup. The fwnode link +* represents the detail that the firmware lists @sup fwnode as supplying a +* resource to @con. +* +* The driver core will use the fwnode link to create a device link between the +* two device objects corresponding to @con and @sup when they are created. The
Quoted 8 lines
drivers/base/core.c static LIST_HEAD(wait_for_suppliers); · line 70
Quoted 5 lines
drivers/base/core.c +5
-0+* driver core will automatically delete the fwnode link between @con and @sup +* after doing that. +* +* Attempts to create duplicate links between the same pair of fwnode handles +* are ignored and there is no reference counting. Sorry to ask, but why is that?
Isn't this a programmer error?
No, not a programmer error.
One firmware node can point to the same supplier many times. For example, the consumer can be using multiple clocks from the same supplier clock controller. In the context of fw_devlink, there's no reason to keep track of each clock dependency separately because we'll be creating only one device link from fwnode link. So multiple fwnode link attempts between the same two devices are just treated as one instance of dependency. I hope that clarifies things.
-Saravana
Re: [PATCH v2 08/17] driver core: Add fwnode link support
Quoted 47 lines · Saravana Kannan
Quoted 35 lines · Leon Romanovsky
Quoted 33 lines · Saravana Kannan
Add support for creating supplier-consumer links between fwnodes. It is intended for internal use the driver core and generic firmware support code (eg. Device Tree, ACPI), so it is simple by design and the API provided is limited.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 98 ++++++++++++++++++++++++++++++++++++++++++ drivers/of/dynamic.c | 1 + include/linux/fwnode.h | 14 ++++++ 3 files changed, 113 insertions(+)drivers/base/core.c +13
-0@@ -50,6 +50,104 @@ static LIST_HEAD(wait_for_suppliers);static DEFINE_MUTEX (wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ; +static DEFINE_MUTEX (fwnode_link_lock); + +/** +* fwnode_link_add - Create a link between two fwnode_handles. +* @con: Consumer end of the link. +* @sup: Supplier end of the link. +* +* Create a fwnode link between fwnode handles @con and @sup. The fwnode link +* represents the detail that the firmware lists @sup fwnode as supplying a +* resource to @con. +* +* The driver core will use the fwnode link to create a device link between the +* two device objects corresponding to @con and @sup when they are created. The Quoted 8 lines
drivers/base/core.c static LIST_HEAD(wait_for_suppliers); · line 70
Quoted 5 lines
drivers/base/core.c +5
-0+* driver core will automatically delete the fwnode link between @con and @sup +* after doing that. +* +* Attempts to create duplicate links between the same pair of fwnode handles +* are ignored and there is no reference counting. Sorry to ask, but why is that?
Isn't this a programmer error?No, not a programmer error.
Quoted 7 lines
One firmware node can point to the same supplier many times. For example, the consumer can be using multiple clocks from the same supplier clock controller. In the context of
fw_devlink, there's no reason to keep track of each clock dependency separately because we'll be creating only one device link from fwnode link. So multiple fwnode link attempts between the same two devices are just treated as one instance of dependency. I hope that clarifies things.
Yes, thanks.
Quoted 2 lines
-Saravana
Re: [PATCH v2 08/17] driver core: Add fwnode link support
In reply to Saravana KannanQuoted 5 lines · Saravana Kannan
Add support for creating supplier-consumer links between fwnodes. It is intended for internal use the driver core and generic firmware support code (eg. Device Tree, ACPI), so it is simple by design and the API provided is limited.
Quoted 7 lines
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 98 ++++++++++++++++++++++++++++++++++++++++++ drivers/of/dynamic.c | 1 + include/linux/fwnode.h | 14 ++++++ 3 files changed, 113 insertions(+)
PATCH v2 9/17 driver core: Allow only unprobed consumers for SYNC_STATE_ONLY device links
In reply to Saravana KannanSYNC_STATE_ONLY device links only affect the behavior of sync_state() callbacks. Specifically, they prevent sync_state() only callbacks from being called on a device if one or more of its consumers haven't probed.
So, creating a SYNC_STATE_ONLY device link from an already probed consumer is useless. So, don't allow creating such device links.
--- drivers/base/core.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
drivers/base/core.c +11 -0
@@ -649,6 +649,17 @@ struct device_link *device_link_add(struct device *consumer, goto out; } +/* +* SYNC_STATE_ONLY links are useless once a consumer device has probed. +* So, only create it if the consumer hasn't probed yet. +*/ +if (flags &DL_FLAG_SYNC_STATE_ONLY && + consumer->links.status !=DL_DEV_NO_DRIVER && + consumer->links.status !=DL_DEV_PROBING ) { + link =NULL ; + goto out; + } +/* * DL_FLAG_AUTOREMOVE_SUPPLIER indicates that the link will be needed * longer than for DL_FLAG_AUTOREMOVE_CONSUMER and setting them both
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 10/17 device property: Add fwnode_is_ancestor_of() and fwnode_get_next_parent_dev()
In reply to Saravana KannanAdd fwnode_is_ancestor_of() helper function to check if a fwnode is an ancestor of another fwnode.
Add fwnode_get_next_parent_dev() helper function that take as input a fwnode and finds the closest ancestor fwnode that has a corresponding struct device and returns that struct device.
--- drivers/base/property.c | 52 ++++++++++++++++++++++++++++++++++++++++ include/linux/property.h | 3 +++ 2 files changed, 55 insertions(+)
drivers/base/property.c +52 -0
@@ -614,6 +614,31 @@ struct fwnode_handle *fwnode_get_next_parent(struct fwnode_handle *fwnode) }EXPORT_SYMBOL_GPL (fwnode_get_next_parent); +/** +* fwnode_get_next_parent_dev - Find device of closest ancestor fwnode +* @fwnode: firmware node +* +* Given a firmware node (@fwnode), this function finds its closest ancestor +* firmware node that has a corresponding struct device and returns that struct +* device. +* +* The caller of this function is expected to call put_device() on the returned +* device when they are done. +*/ +struct device *fwnode_get_next_parent_dev (struct fwnode_handle *fwnode) +{ +struct device *dev =NULL ; + +fwnode_handle_get (fwnode); +do { + fwnode =fwnode_get_next_parent (fwnode); +if (fwnode) + dev =get_dev_from_fwnode (fwnode); + }while (fwnode && !dev); +fwnode_handle_put (fwnode); +return dev; +} +/** * fwnode_count_parents - Return the number of parents a node has * @fwnode: The node the parents of which are to be counted
@@ -660,6 +685,33 @@ struct fwnode_handle *fwnode_get_nth_parent(struct fwnode_handle *fwnode, }EXPORT_SYMBOL_GPL (fwnode_get_nth_parent); +/** +* fwnode_is_ancestor_of - Test if @test_ancestor is ancestor of @test_child +* @test_ancestor: Firmware which is tested for being an ancestor +* @test_child: Firmware which is tested for being the child +* +* A node is considered an ancestor of itself too. +* +* Returns true if @test_ancestor is an ancestor of @test_child. +* Otherwise, returns false. +*/ +bool fwnode_is_ancestor_of (struct fwnode_handle *test_ancestor, +struct fwnode_handle *test_child) +{ +if (!test_ancestor) +return false; + +fwnode_handle_get (test_child); +while (test_child) { +if (test_child == test_ancestor) { +fwnode_handle_put (test_child); +return true; + } + test_child =fwnode_get_next_parent (test_child); + } +return false; +} +/** * fwnode_get_next_child_node - Return the next child node handle for a node * @fwnode: Firmware node to find the next child node for.
include/linux/property.h +3 -0
@@ -85,9 +85,12 @@ const char *fwnode_get_name_prefix(const struct fwnode_handle *fwnode);struct fwnode_handle *fwnode_get_parent (const struct fwnode_handle *fwnode);struct fwnode_handle *fwnode_get_next_parent (struct fwnode_handle *fwnode); +struct device *fwnode_get_next_parent_dev (struct fwnode_handle *fwnode);unsigned int fwnode_count_parents (const struct fwnode_handle *fwn);struct fwnode_handle *fwnode_get_nth_parent (struct fwnode_handle *fwn,unsigned int depth); +bool fwnode_is_ancestor_of (struct fwnode_handle *test_ancestor, +struct fwnode_handle *test_child);struct fwnode_handle *fwnode_get_next_child_node (const struct fwnode_handle *fwnode,struct fwnode_handle *child); struct fwnode_handle *fwnode_get_next_available_child_node(
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 11/17 driver core: Redefine the meaning of fwnode_operations.add_links()
In reply to Saravana KannanChange the meaning of fwnode_operations.add_links() to just create fwnode links by parsing the properties of a given fwnode.
This patch doesn't actually make any code changes. To keeps things more digestable, the actual functional changes come in later patches in this series.
--- drivers/firmware/efi/efi-init.c | 2 +- include/linux/fwnode.h | 42 +++------------------------------ 2 files changed, 4 insertions(+), 40 deletions(-)
drivers/firmware/efi/efi-init.c +1 -1
@@ -316,7 +316,7 @@ static struct device_node *find_pci_overlap_node(void)* resource reservation conflict on the memory window that the efifb * framebuffer steals from the PCIe host bridge. */ -static int efifb_add_links (const struct fwnode_handle *fwnode, +static int efifb_add_links (struct fwnode_handle *fwnode,struct device *dev) {struct device_node *sup_np;
include/linux/fwnode.h +3 -39
54 lines not on this page · raw message
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 12/17 driver core: Add fw_devlink_parse_fwtree()
In reply to Saravana KannanThis function is a wrapper around fwnode_operations.add_links().
This function parses each node in a fwnode tree and create fwnode links for each of those nodes. The information for creating the fwnode links (the supplier and consumer fwnode) is obtained by parsing the properties in each of the fwnodes.
This function also ensures that no fwnode is parsed more than once by marking the fwnodes as parsed.
--- drivers/base/core.c | 19 +++++++++++++++++++ include/linux/fwnode.h | 8 ++++++++ 2 files changed, 27 insertions(+)
drivers/base/core.c +19 -0
@@ -1544,6 +1544,25 @@ static bool fw_devlink_is_permissive(void)return fw_devlink_flags ==DL_FLAG_SYNC_STATE_ONLY ; } +static void fw_devlink_parse_fwnode (struct fwnode_handle *fwnode) +{ +if (fwnode->flags &FWNODE_FLAG_LINKS_ADDED ) +return ; + +fwnode_call_int_op (fwnode, add_links,NULL ); + fwnode->flags |=FWNODE_FLAG_LINKS_ADDED ; +} + +static void fw_devlink_parse_fwtree (struct fwnode_handle *fwnode) +{ +struct fwnode_handle *child =NULL ; + +fw_devlink_parse_fwnode (fwnode); + +while ((child =fwnode_get_next_available_child_node (fwnode, child))) +fw_devlink_parse_fwtree (child); +} +static void fw_devlink_link_device (struct device *dev) {int fw_ret;
include/linux/fwnode.h +8 -0
@@ -15,12 +15,20 @@struct fwnode_operations ;struct device ; +/* +* fwnode link flags +* +* LINKS_ADDED: The fwnode has already be parsed to add fwnode links. +*/ +#define FWNODE_FLAG_LINKS_ADDED BIT(0) +struct fwnode_handle {struct fwnode_handle *secondary;const struct fwnode_operations *ops;struct device *dev;struct list_head suppliers;struct list_head consumers; +u8 flags; };struct fwnode_link {
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 13/17 driver core: Use device's fwnode to check if it is waiting for suppliers
In reply to Saravana KannanTo check if a device is still waiting for its supplier devices to be added, we used to check if the devices is in a global waiting_for_suppliers list. Since the global list will be deleted in subsequent patches, this patch stops using this check.
Instead, this patch uses a more device specific check. It checks if the device's fwnode has any fwnode links that haven't been converted to device links yet.
--- drivers/base/core.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)
drivers/base/core.c +8 -10
@@ -51,6 +51,7 @@ static DEFINE_MUTEX(wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock); +static bool fw_devlink_is_permissive (void );/** * fwnode_link_add - Create a link between two fwnode_handles.
@@ -995,13 +996,13 @@ int device_links_check_suppliers(struct device *dev)* Device waiting for supplier to become available is not allowed to * probe. */ -mutex_lock (&wfs_lock); -if (!list_empty (&dev->links.needs_suppliers) && - dev->links.need_for_probe) { -mutex_unlock (&wfs_lock); +mutex_lock (&fwnode_link_lock); +if (dev->fwnode && !list_empty (&dev->fwnode->suppliers) && + !fw_devlink_is_permissive ()) { +mutex_unlock (&fwnode_link_lock);return -EPROBE_DEFER ; } -mutex_unlock (&wfs_lock); +mutex_unlock (&fwnode_link_lock);device_links_write_lock ();
@@ -1167,10 +1168,7 @@ static ssize_t waiting_for_supplier_show(struct device *dev,bool val;device_lock (dev); -mutex_lock (&wfs_lock); - val = !list_empty (&dev->links.needs_suppliers) - && dev->links.need_for_probe; -mutex_unlock (&wfs_lock); + val = !list_empty (&dev->fwnode->suppliers);device_unlock (dev);return sysfs_emit (buf,"%u\n" , val); }
@@ -2202,7 +2200,7 @@ static int device_add_attrs(struct device *dev) goto err_remove_dev_groups; } -if (fw_devlink_flags && !fw_devlink_is_permissive ()) { +if (fw_devlink_flags && !fw_devlink_is_permissive () && dev->fwnode) { error =device_create_file (dev, &dev_attr_waiting_for_supplier);if (error) goto err_remove_dev_online;
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 13/17] driver core: Use device's fwnode to check if it is waiting for suppliers
Quoted 28 lines · Saravana Kannan
To check if a device is still waiting for its supplier devices to be added, we used to check if the devices is in a global
waiting_for_supplierslist. Since the global list will be deleted in subsequent patches, this patch stops using this check.Instead, this patch uses a more device specific check. It checks if the device's fwnode has any fwnode links that haven't been converted to device links yet.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)drivers/base/core.c +1
-0@@ -51,6 +51,7 @@ static DEFINE_MUTEX(wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock); +static bool fw_devlink_is_permissive (void );/** * fwnode_link_add - Create a link between two fwnode_handles. @@ -995,13 +996,13 @@ int device_links_check_suppliers(struct device *dev)* Device waiting for supplier to become available is not allowed to
drivers/base/core.c int device_links_check_suppliers(struct device *dev) · line 1002
Quoted 10 lines
drivers/base/core.c +4
-4* probe. */ -mutex_lock (&wfs_lock); -if (!list_empty (&dev->links.needs_suppliers) && - dev->links.need_for_probe) { -mutex_unlock (&wfs_lock); +mutex_lock (&fwnode_link_lock); +if (dev->fwnode && !list_empty (&dev->fwnode->suppliers) && + !fw_devlink_is_permissive ()) { +mutex_unlock (&fwnode_link_lock);
Hi Saravana,
First of, sorry for going back to this.
There is a scenario where this check will not work and probably should work. It goes like this:
A clock controller is not allowed to probe because it uses a clock from a child device of a consumer, like so:
dispcc: clock-controller@af00000 {
clocks = <&dsi0_phy 0>;
};
mdss: mdss@ae00000 {
clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>;
dsi0_phy: dsi-phy@ae94400 {
clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>,
};
};This is a real scenario actually, but I stripped it down to the essentials.
So, the dsi0_phy will be "device_add'ed" (through of_platform_populate) by the mdss probe. The mdss will probe defer waiting for the DISP_CC_MDSS_MDP_CLK, while
the dispcc will probe defer waiting for the dsi0_phy (supplier).
Basically, this 'supplier availability check' does not work when a supplier might be populated by a consumer of the device that is currently trying to probe.
Abel
Quoted 32 lines
drivers/base/core.c +3
-7return -EPROBE_DEFER ; } -mutex_unlock (&wfs_lock); +mutex_unlock (&fwnode_link_lock);device_links_write_lock ();@@ -1167,10 +1168,7 @@ static ssize_t waiting_for_supplier_show(struct device *dev,bool val;device_lock (dev); -mutex_lock (&wfs_lock); - val = !list_empty (&dev->links.needs_suppliers) - && dev->links.need_for_probe; -mutex_unlock (&wfs_lock); + val = !list_empty (&dev->fwnode->suppliers);device_unlock (dev);return sysfs_emit (buf,"%u\n" , val); }@@ -2202,7 +2200,7 @@ static int device_add_attrs(struct device *dev) goto err_remove_dev_groups; } -if (fw_devlink_flags && !fw_devlink_is_permissive ()) { +if (fw_devlink_flags && !fw_devlink_is_permissive () && dev->fwnode) { error =device_create_file (dev, &dev_attr_waiting_for_supplier);if (error) goto err_remove_dev_online; --2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 13/17] driver core: Use device's fwnode to check if it is waiting for suppliers
Quoted 43 lines · Abel Vesa
Quoted 28 lines · Saravana Kannan
To check if a device is still waiting for its supplier devices to be added, we used to check if the devices is in a global
waiting_for_supplierslist. Since the global list will be deleted in subsequent patches, this patch stops using this check.Instead, this patch uses a more device specific check. It checks if the device's fwnode has any fwnode links that haven't been converted to device links yet.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)drivers/base/core.c +1
-0@@ -51,6 +51,7 @@ static DEFINE_MUTEX(wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock); +static bool fw_devlink_is_permissive (void );/** * fwnode_link_add - Create a link between two fwnode_handles. @@ -995,13 +996,13 @@ int device_links_check_suppliers(struct device *dev)* Device waiting for supplier to become available is not allowed to drivers/base/core.c int device_links_check_suppliers(struct device *dev) · line 1002
Quoted 10 lines
drivers/base/core.c +4
-4* probe. */ -mutex_lock (&wfs_lock); -if (!list_empty (&dev->links.needs_suppliers) && - dev->links.need_for_probe) { -mutex_unlock (&wfs_lock); +mutex_lock (&fwnode_link_lock); +if (dev->fwnode && !list_empty (&dev->fwnode->suppliers) && + !fw_devlink_is_permissive ()) { +mutex_unlock (&fwnode_link_lock);Hi Saravana,
Quoted 1 line
First of, sorry for going back to this.
No worries at all. If there's an issue with fw_devlink, I want to have it fixed.
Quoted 18 lines
There is a scenario where this check will not work and probably should work. It goes like this:
A clock controller is not allowed to probe because it uses a clock from a child device of a consumer, like so:
dispcc: clock-controller@af00000 { clocks = <&dsi0_phy 0>; }; mdss: mdss@ae00000 { clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>; dsi0_phy: dsi-phy@ae94400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; };
Quoted 1 line
This is a real scenario actually, but I stripped it down to the essentials.
I'm well aware of this scenario and explicitly wrote code to address this :)
See this comment in fw_devlink_create_devlink()
/*
* If we can't find the supplier device from its fwnode, it might be
* due to a cyclic dependency between fwnodes. Some of these cycles can
* be broken by applying logic. Check for these types of cycles and
* break them so that devices in the cycle probe properly. *
* If the supplier's parent is dependent on the consumer, then the
* consumer and supplier have a cyclic dependency. Since fw_devlink
* can't tell which of the inferred dependencies are incorrect, don't
* enforce probe ordering between any of the devices in this cyclic
* dependency. Do this by relaxing all the fw_devlink device links in
* this cycle and by treating the fwnode link between the consumer and
* the supplier as an invalid dependency.
*/
Applying this comment to your example, dispcc is the "consumer", dsi0_phy is the "supplier" and mdss is the "supplier's parent".
And because we can't guarantee the order of addition of these top level devices is why I also have this piece of recursive call inside __fw_devlink_link_to_suppliers():
/*
* If a device link was successfully created to a supplier, we
* now need to try and link the supplier to all its suppliers. *
* This is needed to detect and delete false dependencies in
* fwnode links that haven't been converted to a device link
* yet. See comments in fw_devlink_create_devlink() for more
* details on the false dependency.
*
* Without deleting these false dependencies, some devices will
* never probe because they'll keep waiting for their false
* dependency fwnode links to be converted to device links. */
sup_dev = get_dev_from_fwnode(sup); __fw_devlink_link_to_suppliers(sup_dev, sup_dev->fwnode); put_device(sup_dev);
So when mdss gets added, we'll link it to dispcc and then check if dispcc has any suppliers it needs to link to. And that's when the logic will catch the cycle and fix it.
Can you tell me why this wouldn't unblock the probing of dispcc? Are you actually hitting this on a device? If so, can you please check why this logic isn't sufficient to catch and undo the cycle?
Thanks,
Saravana
Quoted 43 lines
So, the
dsi0_phywill be "device_add'ed" (throughof_platform_populate) by the mdss probe. The mdss will probe defer waiting for theDISP_CC_MDSS_MDP_CLK, while
the dispcc will probe defer waiting for thedsi0_phy(supplier).Basically, this 'supplier availability check' does not work when a supplier might be populated by a consumer of the device that is currently trying to probe.
Abel
Quoted 32 lines
drivers/base/core.c +3
-7return -EPROBE_DEFER ; } -mutex_unlock (&wfs_lock); +mutex_unlock (&fwnode_link_lock);device_links_write_lock ();@@ -1167,10 +1168,7 @@ static ssize_t waiting_for_supplier_show(struct device *dev,bool val;device_lock (dev); -mutex_lock (&wfs_lock); - val = !list_empty (&dev->links.needs_suppliers) - && dev->links.need_for_probe; -mutex_unlock (&wfs_lock); + val = !list_empty (&dev->fwnode->suppliers);device_unlock (dev);return sysfs_emit (buf,"%u\n" , val); }@@ -2202,7 +2200,7 @@ static int device_add_attrs(struct device *dev) goto err_remove_dev_groups; } -if (fw_devlink_flags && !fw_devlink_is_permissive ()) { +if (fw_devlink_flags && !fw_devlink_is_permissive () && dev->fwnode) { error =device_create_file (dev, &dev_attr_waiting_for_supplier);if (error) goto err_remove_dev_online; --2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 13/17] driver core: Use device's fwnode to check if it is waiting for suppliers
Quoted 61 lines · Saravana Kannan
Quoted 43 lines · Abel Vesa
Quoted 28 lines · Saravana Kannan
To check if a device is still waiting for its supplier devices to be added, we used to check if the devices is in a global
waiting_for_supplierslist. Since the global list will be deleted in subsequent patches, this patch stops using this check.Instead, this patch uses a more device specific check. It checks if the device's fwnode has any fwnode links that haven't been converted to device links yet.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)drivers/base/core.c +1
-0@@ -51,6 +51,7 @@ static DEFINE_MUTEX(wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock); +static bool fw_devlink_is_permissive (void );/** * fwnode_link_add - Create a link between two fwnode_handles. @@ -995,13 +996,13 @@ int device_links_check_suppliers(struct device *dev)* Device waiting for supplier to become available is not allowed to drivers/base/core.c int device_links_check_suppliers(struct device *dev) · line 1002
Quoted 10 lines
drivers/base/core.c +4
-4* probe. */ -mutex_lock (&wfs_lock); -if (!list_empty (&dev->links.needs_suppliers) && - dev->links.need_for_probe) { -mutex_unlock (&wfs_lock); +mutex_lock (&fwnode_link_lock); +if (dev->fwnode && !list_empty (&dev->fwnode->suppliers) && + !fw_devlink_is_permissive ()) { +mutex_unlock (&fwnode_link_lock);Hi Saravana,
Quoted 1 line
First of, sorry for going back to this.
No worries at all. If there's an issue with
fw_devlink, I want to have it fixed.Quoted 13 lines
There is a scenario where this check will not work and probably should work. It goes like this:
A clock controller is not allowed to probe because it uses a clock from a child device of a consumer, like so:
dispcc: clock-controller@af00000 { clocks = <&dsi0_phy 0>; }; mdss: mdss@ae00000 { clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>;
Quoted 9 lines
Quoted 6 lines
dsi0_phy: dsi-phy@ae94400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; };This is a real scenario actually, but I stripped it down to the essentials.
I'm well aware of this scenario and explicitly wrote code to address this :)
Actually, the problem seems to be when you have two dsi phys. Like so:
dispcc: clock-controller@af00000 {
clocks = <&dsi0_phy 0>;
clocks = <&dsi1_phy 0>;
};
mdss: mdss@ae00000 {
clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>;
dsi0_phy: dsi-phy@ae94400 {
clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>,
};
dsi1_phy: dsi-phy@ae64400 {
clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>,
};
};And from what I've seen happening so far is that the device_is_dependent check for the parent of the supplier (if it also a consumer) seems to return false on second pass of the same link due to the DL_FLAG_SYNC_STATE_ONLY being set this time around.
Quoted 17 lines
See this comment in
fw_devlink_create_devlink()/*
* If we can't find the supplier device from its fwnode, it might be
* due to a cyclic dependency between fwnodes. Some of these cycles can
* be broken by applying logic. Check for these types of cycles and
* break them so that devices in the cycle probe properly. *
* If the supplier's parent is dependent on the consumer, then the
* consumer and supplier have a cyclic dependency. Sincefw_devlink
* can't tell which of the inferred dependencies are incorrect, don't
* enforce probe ordering between any of the devices in this cyclic
* dependency. Do this by relaxing all thefw_devlinkdevice links in
* this cycle and by treating the fwnode link between the consumer and
* the supplier as an invalid dependency.
*/
So when this thing you mentioned above is happening for the second dsi phy (order doesn't matter), since the dsi phy itself cannot be found, the device_is_dependent is run for the same link: dispcc -> mdss (supplier -> consumer), but again, since it has the DL_FLAG_SYNC_STATE_ONLY this time around, it will skip that specific link.
Quoted 24 lines
Applying this comment to your example, dispcc is the "consumer",
dsi0_phyis the "supplier" and mdss is the "supplier's parent".And because we can't guarantee the order of addition of these top level devices is why I also have this piece of recursive call inside
__fw_devlink_link_to_suppliers():/*
* If a device link was successfully created to a supplier, we
* now need to try and link the supplier to all its suppliers. *
* This is needed to detect and delete false dependencies in
* fwnode links that haven't been converted to a device link
* yet. See comments infw_devlink_create_devlink()for more
* details on the false dependency.
*
* Without deleting these false dependencies, some devices will
* never probe because they'll keep waiting for their false
* dependency fwnode links to be converted to device links. */
sup_dev=get_dev_from_fwnode(sup);__fw_devlink_link_to_suppliers(sup_dev, sup_dev->fwnode);put_device(sup_dev);
Quoted 8 lines
So when mdss gets added, we'll link it to dispcc and then check if dispcc has any suppliers it needs to link to. And that's when the logic will catch the cycle and fix it.
Can you tell me why this wouldn't unblock the probing of dispcc? Are you actually hitting this on a device? If so, can you please check why this logic isn't sufficient to catch and undo the cycle?
This is happening on Qualcomm SDM845 with Linus's tree.
Quoted 47 lines
Thanks,
SaravanaQuoted 43 lines
So, the
dsi0_phywill be "device_add'ed" (throughof_platform_populate) by the mdss probe. The mdss will probe defer waiting for theDISP_CC_MDSS_MDP_CLK, while
the dispcc will probe defer waiting for thedsi0_phy(supplier).Basically, this 'supplier availability check' does not work when a supplier might be populated by a consumer of the device that is currently trying to probe.
Abel
Quoted 32 lines
drivers/base/core.c +3
-7return -EPROBE_DEFER ; } -mutex_unlock (&wfs_lock); +mutex_unlock (&fwnode_link_lock);device_links_write_lock ();@@ -1167,10 +1168,7 @@ static ssize_t waiting_for_supplier_show(struct device *dev,bool val;device_lock (dev); -mutex_lock (&wfs_lock); - val = !list_empty (&dev->links.needs_suppliers) - && dev->links.need_for_probe; -mutex_unlock (&wfs_lock); + val = !list_empty (&dev->fwnode->suppliers);device_unlock (dev);return sysfs_emit (buf,"%u\n" , val); }@@ -2202,7 +2200,7 @@ static int device_add_attrs(struct device *dev) goto err_remove_dev_groups; } -if (fw_devlink_flags && !fw_devlink_is_permissive ()) { +if (fw_devlink_flags && !fw_devlink_is_permissive () && dev->fwnode) { error =device_create_file (dev, &dev_attr_waiting_for_supplier);if (error) goto err_remove_dev_online; --2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 13/17] driver core: Use device's fwnode to check if it is waiting for suppliers
Quoted 3 lines · Abel Vesa
Quoted 2 lines · Saravana Kannan
Quoted 1 line · Abel Vesa
Oups, forget this reply since it not to the right message-id.
Will do it properly right now.
Quoted 201 lines
Quoted 59 lines
Quoted 42 lines · Saravana Kannan
Quoted 28 lines
To check if a device is still waiting for its supplier devices to be added, we used to check if the devices is in a global
waiting_for_supplierslist. Since the global list will be deleted in subsequent patches, this patch stops using this check.Instead, this patch uses a more device specific check. It checks if the device's fwnode has any fwnode links that haven't been converted to device links yet.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)drivers/base/core.c +1
-0@@ -51,6 +51,7 @@ static DEFINE_MUTEX(wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock); +static bool fw_devlink_is_permissive (void );/** * fwnode_link_add - Create a link between two fwnode_handles. @@ -995,13 +996,13 @@ int device_links_check_suppliers(struct device *dev)* Device waiting for supplier to become available is not allowed to drivers/base/core.c int device_links_check_suppliers(struct device *dev) · line 1002
Quoted 10 lines
drivers/base/core.c +4
-4* probe. */ -mutex_lock (&wfs_lock); -if (!list_empty (&dev->links.needs_suppliers) && - dev->links.need_for_probe) { -mutex_unlock (&wfs_lock); +mutex_lock (&fwnode_link_lock); +if (dev->fwnode && !list_empty (&dev->fwnode->suppliers) && + !fw_devlink_is_permissive ()) { +mutex_unlock (&fwnode_link_lock);Hi Saravana,
Quoted 1 line
First of, sorry for going back to this.
No worries at all. If there's an issue with
fw_devlink, I want to have it fixed.Quoted 13 lines
There is a scenario where this check will not work and probably should work. It goes like this:
A clock controller is not allowed to probe because it uses a clock from a child device of a consumer, like so:
dispcc: clock-controller@af00000 { clocks = <&dsi0_phy 0>; }; mdss: mdss@ae00000 { clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>;Quoted 9 lines
Quoted 6 lines
dsi0_phy: dsi-phy@ae94400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; };This is a real scenario actually, but I stripped it down to the essentials.
I'm well aware of this scenario and explicitly wrote code to address this :)
Actually, the problem seems to be when you have two dsi phys. Like so:
dispcc: clock-controller@af00000 { clocks = <&dsi0_phy 0>; clocks = <&dsi1_phy 0>; }; mdss: mdss@ae00000 { clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>; dsi0_phy: dsi-phy@ae94400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; dsi1_phy: dsi-phy@ae64400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; };And from what I've seen happening so far is that the
device_is_dependentcheck for the parent of the supplier (if it also a consumer) seems to return false on second pass of the same link due to theDL_FLAG_SYNC_STATE_ONLYbeing set this time around.Quoted 17 lines
See this comment in
fw_devlink_create_devlink()/*
* If we can't find the supplier device from its fwnode, it might be
* due to a cyclic dependency between fwnodes. Some of these cycles can
* be broken by applying logic. Check for these types of cycles and
* break them so that devices in the cycle probe properly. *
* If the supplier's parent is dependent on the consumer, then the
* consumer and supplier have a cyclic dependency. Sincefw_devlink
* can't tell which of the inferred dependencies are incorrect, don't
* enforce probe ordering between any of the devices in this cyclic
* dependency. Do this by relaxing all thefw_devlinkdevice links in
* this cycle and by treating the fwnode link between the consumer and
* the supplier as an invalid dependency.
*/So when this thing you mentioned above is happening for the second dsi phy (order doesn't matter), since the dsi phy itself cannot be found, the
device_is_dependentis run for the same link: dispcc -> mdss (supplier -> consumer), but again, since it has theDL_FLAG_SYNC_STATE_ONLYthis time around, it will skip that specific link.Quoted 24 lines
Applying this comment to your example, dispcc is the "consumer",
dsi0_phyis the "supplier" and mdss is the "supplier's parent".And because we can't guarantee the order of addition of these top level devices is why I also have this piece of recursive call inside
__fw_devlink_link_to_suppliers():/*
* If a device link was successfully created to a supplier, we
* now need to try and link the supplier to all its suppliers. *
* This is needed to detect and delete false dependencies in
* fwnode links that haven't been converted to a device link
* yet. See comments infw_devlink_create_devlink()for more
* details on the false dependency.
*
* Without deleting these false dependencies, some devices will
* never probe because they'll keep waiting for their false
* dependency fwnode links to be converted to device links. */
sup_dev=get_dev_from_fwnode(sup);__fw_devlink_link_to_suppliers(sup_dev, sup_dev->fwnode);put_device(sup_dev);Quoted 8 lines
So when mdss gets added, we'll link it to dispcc and then check if dispcc has any suppliers it needs to link to. And that's when the logic will catch the cycle and fix it.
Can you tell me why this wouldn't unblock the probing of dispcc? Are you actually hitting this on a device? If so, can you please check why this logic isn't sufficient to catch and undo the cycle?
This is happening on Qualcomm SDM845 with Linus's tree.
Quoted 47 lines
Thanks,
SaravanaQuoted 43 lines
So, the
dsi0_phywill be "device_add'ed" (throughof_platform_populate) by the mdss probe. The mdss will probe defer waiting for theDISP_CC_MDSS_MDP_CLK, while
the dispcc will probe defer waiting for thedsi0_phy(supplier).Basically, this 'supplier availability check' does not work when a supplier might be populated by a consumer of the device that is currently trying to probe.
Abel
Quoted 32 lines
drivers/base/core.c +3
-7return -EPROBE_DEFER ; } -mutex_unlock (&wfs_lock); +mutex_unlock (&fwnode_link_lock);device_links_write_lock ();@@ -1167,10 +1168,7 @@ static ssize_t waiting_for_supplier_show(struct device *dev,bool val;device_lock (dev); -mutex_lock (&wfs_lock); - val = !list_empty (&dev->links.needs_suppliers) - && dev->links.need_for_probe; -mutex_unlock (&wfs_lock); + val = !list_empty (&dev->fwnode->suppliers);device_unlock (dev);return sysfs_emit (buf,"%u\n" , val); }@@ -2202,7 +2200,7 @@ static int device_add_attrs(struct device *dev) goto err_remove_dev_groups; } -if (fw_devlink_flags && !fw_devlink_is_permissive ()) { +if (fw_devlink_flags && !fw_devlink_is_permissive () && dev->fwnode) { error =device_create_file (dev, &dev_attr_waiting_for_supplier);if (error) goto err_remove_dev_online; --2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 13/17] driver core: Use device's fwnode to check if it is waiting for suppliers
In reply to Saravana KannanQuoted 61 lines · Saravana Kannan
Quoted 43 lines · Abel Vesa
Quoted 28 lines · Saravana Kannan
To check if a device is still waiting for its supplier devices to be added, we used to check if the devices is in a global
waiting_for_supplierslist. Since the global list will be deleted in subsequent patches, this patch stops using this check.Instead, this patch uses a more device specific check. It checks if the device's fwnode has any fwnode links that haven't been converted to device links yet.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)drivers/base/core.c +1
-0@@ -51,6 +51,7 @@ static DEFINE_MUTEX(wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock); +static bool fw_devlink_is_permissive (void );/** * fwnode_link_add - Create a link between two fwnode_handles. @@ -995,13 +996,13 @@ int device_links_check_suppliers(struct device *dev)* Device waiting for supplier to become available is not allowed to drivers/base/core.c int device_links_check_suppliers(struct device *dev) · line 1002
Quoted 10 lines
drivers/base/core.c +4
-4* probe. */ -mutex_lock (&wfs_lock); -if (!list_empty (&dev->links.needs_suppliers) && - dev->links.need_for_probe) { -mutex_unlock (&wfs_lock); +mutex_lock (&fwnode_link_lock); +if (dev->fwnode && !list_empty (&dev->fwnode->suppliers) && + !fw_devlink_is_permissive ()) { +mutex_unlock (&fwnode_link_lock);Hi Saravana,
Quoted 1 line
First of, sorry for going back to this.
No worries at all. If there's an issue with
fw_devlink, I want to have it fixed.Quoted 13 lines
There is a scenario where this check will not work and probably should work. It goes like this:
A clock controller is not allowed to probe because it uses a clock from a child device of a consumer, like so:
dispcc: clock-controller@af00000 { clocks = <&dsi0_phy 0>; }; mdss: mdss@ae00000 { clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>;
Quoted 9 lines
Quoted 6 lines
dsi0_phy: dsi-phy@ae94400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; };This is a real scenario actually, but I stripped it down to the essentials.
I'm well aware of this scenario and explicitly wrote code to address this :)
Actually, the problem seems to be when you have two dsi phys. Like so:
dispcc: clock-controller@af00000 {
clocks = <&dsi0_phy 0>;
clocks = <&dsi1_phy 0>;
};
mdss: mdss@ae00000 {
clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>;
dsi0_phy: dsi-phy@ae94400 {
clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>,
};
dsi1_phy: dsi-phy@ae64400 {
clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>,
};
};And from what I've seen happening so far is that the device_is_dependent check for the parent of the supplier (if it also a consumer) seems to return false on second pass of the same link due to the DL_FLAG_SYNC_STATE_ONLY being set this time around.
Quoted 17 lines
See this comment in
fw_devlink_create_devlink()/*
* If we can't find the supplier device from its fwnode, it might be
* due to a cyclic dependency between fwnodes. Some of these cycles can
* be broken by applying logic. Check for these types of cycles and
* break them so that devices in the cycle probe properly. *
* If the supplier's parent is dependent on the consumer, then the
* consumer and supplier have a cyclic dependency. Sincefw_devlink
* can't tell which of the inferred dependencies are incorrect, don't
* enforce probe ordering between any of the devices in this cyclic
* dependency. Do this by relaxing all thefw_devlinkdevice links in
* this cycle and by treating the fwnode link between the consumer and
* the supplier as an invalid dependency.
*/
So when this thing you mentioned above is happening for the second dsi phy (order doesn't matter), since the dsi phy itself cannot be found, the device_is_dependent is run for the same link: dispcc -> mdss (supplier -> consumer), but again, since it has the DL_FLAG_SYNC_STATE_ONLY this time around, it will skip that specific link.
Quoted 24 lines
Applying this comment to your example, dispcc is the "consumer",
dsi0_phyis the "supplier" and mdss is the "supplier's parent".And because we can't guarantee the order of addition of these top level devices is why I also have this piece of recursive call inside
__fw_devlink_link_to_suppliers():/*
* If a device link was successfully created to a supplier, we
* now need to try and link the supplier to all its suppliers. *
* This is needed to detect and delete false dependencies in
* fwnode links that haven't been converted to a device link
* yet. See comments infw_devlink_create_devlink()for more
* details on the false dependency.
*
* Without deleting these false dependencies, some devices will
* never probe because they'll keep waiting for their false
* dependency fwnode links to be converted to device links. */
sup_dev=get_dev_from_fwnode(sup);__fw_devlink_link_to_suppliers(sup_dev, sup_dev->fwnode);put_device(sup_dev);
Quoted 8 lines
So when mdss gets added, we'll link it to dispcc and then check if dispcc has any suppliers it needs to link to. And that's when the logic will catch the cycle and fix it.
Can you tell me why this wouldn't unblock the probing of dispcc? Are you actually hitting this on a device? If so, can you please check why this logic isn't sufficient to catch and undo the cycle?
This is happening on Qualcomm SDM845 with Linus's tree.
Quoted 47 lines
Thanks,
SaravanaQuoted 43 lines
So, the
dsi0_phywill be "device_add'ed" (throughof_platform_populate) by the mdss probe. The mdss will probe defer waiting for theDISP_CC_MDSS_MDP_CLK, while
the dispcc will probe defer waiting for thedsi0_phy(supplier).Basically, this 'supplier availability check' does not work when a supplier might be populated by a consumer of the device that is currently trying to probe.
Abel
Quoted 32 lines
drivers/base/core.c +3
-7return -EPROBE_DEFER ; } -mutex_unlock (&wfs_lock); +mutex_unlock (&fwnode_link_lock);device_links_write_lock ();@@ -1167,10 +1168,7 @@ static ssize_t waiting_for_supplier_show(struct device *dev,bool val;device_lock (dev); -mutex_lock (&wfs_lock); - val = !list_empty (&dev->links.needs_suppliers) - && dev->links.need_for_probe; -mutex_unlock (&wfs_lock); + val = !list_empty (&dev->fwnode->suppliers);device_unlock (dev);return sysfs_emit (buf,"%u\n" , val); }@@ -2202,7 +2200,7 @@ static int device_add_attrs(struct device *dev) goto err_remove_dev_groups; } -if (fw_devlink_flags && !fw_devlink_is_permissive ()) { +if (fw_devlink_flags && !fw_devlink_is_permissive () && dev->fwnode) { error =device_create_file (dev, &dev_attr_waiting_for_supplier);if (error) goto err_remove_dev_online; --2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 13/17] driver core: Use device's fwnode to check if it is waiting for suppliers
Quoted 116 lines · Abel Vesa
Quoted 61 lines · Saravana Kannan
Quoted 43 lines · Abel Vesa
Quoted 28 lines · Saravana Kannan
To check if a device is still waiting for its supplier devices to be added, we used to check if the devices is in a global
waiting_for_supplierslist. Since the global list will be deleted in subsequent patches, this patch stops using this check.Instead, this patch uses a more device specific check. It checks if the device's fwnode has any fwnode links that haven't been converted to device links yet.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)drivers/base/core.c +1
-0@@ -51,6 +51,7 @@ static DEFINE_MUTEX(wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock); +static bool fw_devlink_is_permissive (void );/** * fwnode_link_add - Create a link between two fwnode_handles. @@ -995,13 +996,13 @@ int device_links_check_suppliers(struct device *dev)* Device waiting for supplier to become available is not allowed to drivers/base/core.c int device_links_check_suppliers(struct device *dev) · line 1002
Quoted 10 lines
drivers/base/core.c +4
-4* probe. */ -mutex_lock (&wfs_lock); -if (!list_empty (&dev->links.needs_suppliers) && - dev->links.need_for_probe) { -mutex_unlock (&wfs_lock); +mutex_lock (&fwnode_link_lock); +if (dev->fwnode && !list_empty (&dev->fwnode->suppliers) && + !fw_devlink_is_permissive ()) { +mutex_unlock (&fwnode_link_lock);Hi Saravana,
Quoted 1 line
First of, sorry for going back to this.
No worries at all. If there's an issue with
fw_devlink, I want to have it fixed.Quoted 13 lines
There is a scenario where this check will not work and probably should work. It goes like this:
A clock controller is not allowed to probe because it uses a clock from a child device of a consumer, like so:
dispcc: clock-controller@af00000 { clocks = <&dsi0_phy 0>; }; mdss: mdss@ae00000 { clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>;Quoted 9 lines
Quoted 6 lines
dsi0_phy: dsi-phy@ae94400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; };This is a real scenario actually, but I stripped it down to the essentials.
I'm well aware of this scenario and explicitly wrote code to address this :)
Actually, the problem seems to be when you have two dsi phys. Like so:
dispcc: clock-controller@af00000 { clocks = <&dsi0_phy 0>; clocks = <&dsi1_phy 0>; }; mdss: mdss@ae00000 { clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>; dsi0_phy: dsi-phy@ae94400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; dsi1_phy: dsi-phy@ae64400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; };And from what I've seen happening so far is that the
device_is_dependentcheck for the parent of the supplier (if it also a consumer) seems to return false on second pass of the same link due to theDL_FLAG_SYNC_STATE_ONLYbeing set this time around.Quoted 17 lines
See this comment in
fw_devlink_create_devlink()/*
* If we can't find the supplier device from its fwnode, it might be
* due to a cyclic dependency between fwnodes. Some of these cycles can
* be broken by applying logic. Check for these types of cycles and
* break them so that devices in the cycle probe properly. *
* If the supplier's parent is dependent on the consumer, then the
* consumer and supplier have a cyclic dependency. Sincefw_devlink
* can't tell which of the inferred dependencies are incorrect, don't
* enforce probe ordering between any of the devices in this cyclic
* dependency. Do this by relaxing all thefw_devlinkdevice links in
* this cycle and by treating the fwnode link between the consumer and
* the supplier as an invalid dependency.
*/
Quoted 6 lines
So when this thing you mentioned above is happening for the second dsi phy (order doesn't matter), since the dsi phy itself cannot be found, the
device_is_dependentis run for the same link: dispcc -> mdss (supplier -> consumer), but again, since it has theDL_FLAG_SYNC_STATE_ONLYthis time around, it will skip that specific link.
Ugh... I knew there was this gap, but didn't expect it to be a real world issue.
There are different ways of addressing this and they all fall somewhere within a spectrum of:
"stop enforcing very specific edges of the dependency graph when you find a cycles"
To
"just don't enforce any dependency for devices in a cycle and let the drivers figure out when to -EPROBE_DEFER".
And each of those are of varying complexity. Ideally I'd prefer to relax specific edges, but I need to balance it out with the code complexity. Let me soak this for a few weeks to decide on what option to take.
Thanks for the report.
-Saravana
Quoted 83 lines
Quoted 25 lines
Applying this comment to your example, dispcc is the "consumer",
dsi0_phyis the "supplier" and mdss is the "supplier's parent".And because we can't guarantee the order of addition of these top level devices is why I also have this piece of recursive call inside
__fw_devlink_link_to_suppliers():/*
* If a device link was successfully created to a supplier, we
* now need to try and link the supplier to all its suppliers. *
* This is needed to detect and delete false dependencies in
* fwnode links that haven't been converted to a device link
* yet. See comments infw_devlink_create_devlink()for more
* details on the false dependency.
*
* Without deleting these false dependencies, some devices will
* never probe because they'll keep waiting for their false
* dependency fwnode links to be converted to device links. */
sup_dev=get_dev_from_fwnode(sup);__fw_devlink_link_to_suppliers(sup_dev, sup_dev->fwnode);put_device(sup_dev);Quoted 8 lines
So when mdss gets added, we'll link it to dispcc and then check if dispcc has any suppliers it needs to link to. And that's when the logic will catch the cycle and fix it.
Can you tell me why this wouldn't unblock the probing of dispcc? Are you actually hitting this on a device? If so, can you please check why this logic isn't sufficient to catch and undo the cycle?
This is happening on Qualcomm SDM845 with Linus's tree.
Quoted 47 lines
Thanks,
SaravanaQuoted 43 lines
So, the
dsi0_phywill be "device_add'ed" (throughof_platform_populate) by the mdss probe. The mdss will probe defer waiting for theDISP_CC_MDSS_MDP_CLK, while
the dispcc will probe defer waiting for thedsi0_phy(supplier).Basically, this 'supplier availability check' does not work when a supplier might be populated by a consumer of the device that is currently trying to probe.
Abel
Quoted 32 lines
drivers/base/core.c +3
-7return -EPROBE_DEFER ; } -mutex_unlock (&wfs_lock); +mutex_unlock (&fwnode_link_lock);device_links_write_lock ();@@ -1167,10 +1168,7 @@ static ssize_t waiting_for_supplier_show(struct device *dev,bool val;device_lock (dev); -mutex_lock (&wfs_lock); - val = !list_empty (&dev->links.needs_suppliers) - && dev->links.need_for_probe; -mutex_unlock (&wfs_lock); + val = !list_empty (&dev->fwnode->suppliers);device_unlock (dev);return sysfs_emit (buf,"%u\n" , val); }@@ -2202,7 +2200,7 @@ static int device_add_attrs(struct device *dev) goto err_remove_dev_groups; } -if (fw_devlink_flags && !fw_devlink_is_permissive ()) { +if (fw_devlink_flags && !fw_devlink_is_permissive () && dev->fwnode) { error =device_create_file (dev, &dev_attr_waiting_for_supplier);if (error) goto err_remove_dev_online; --2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 13/17] driver core: Use device's fwnode to check if it is waiting for suppliers
Hi,
Quoted 134 lines · Saravana Kannan
Quoted 116 lines · Abel Vesa
Quoted 61 lines · Saravana Kannan
Quoted 43 lines · Abel Vesa
Quoted 28 lines · Saravana Kannan
To check if a device is still waiting for its supplier devices to be added, we used to check if the devices is in a global
waiting_for_supplierslist. Since the global list will be deleted in subsequent patches, this patch stops using this check.Instead, this patch uses a more device specific check. It checks if the device's fwnode has any fwnode links that haven't been converted to device links yet.
Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)drivers/base/core.c +1
-0@@ -51,6 +51,7 @@ static DEFINE_MUTEX(wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock); +static bool fw_devlink_is_permissive (void );/** * fwnode_link_add - Create a link between two fwnode_handles. @@ -995,13 +996,13 @@ int device_links_check_suppliers(struct device *dev)* Device waiting for supplier to become available is not allowed to drivers/base/core.c int device_links_check_suppliers(struct device *dev) · line 1002
Quoted 10 lines
drivers/base/core.c +4
-4* probe. */ -mutex_lock (&wfs_lock); -if (!list_empty (&dev->links.needs_suppliers) && - dev->links.need_for_probe) { -mutex_unlock (&wfs_lock); +mutex_lock (&fwnode_link_lock); +if (dev->fwnode && !list_empty (&dev->fwnode->suppliers) && + !fw_devlink_is_permissive ()) { +mutex_unlock (&fwnode_link_lock);Hi Saravana,
Quoted 1 line
First of, sorry for going back to this.
No worries at all. If there's an issue with
fw_devlink, I want to have it fixed.Quoted 13 lines
There is a scenario where this check will not work and probably should work. It goes like this:
A clock controller is not allowed to probe because it uses a clock from a child device of a consumer, like so:
dispcc: clock-controller@af00000 { clocks = <&dsi0_phy 0>; }; mdss: mdss@ae00000 { clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>;Quoted 9 lines
Quoted 6 lines
dsi0_phy: dsi-phy@ae94400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; };This is a real scenario actually, but I stripped it down to the essentials.
I'm well aware of this scenario and explicitly wrote code to address this :)
Actually, the problem seems to be when you have two dsi phys. Like so:
dispcc: clock-controller@af00000 { clocks = <&dsi0_phy 0>; clocks = <&dsi1_phy 0>; }; mdss: mdss@ae00000 { clocks = <&dispcc DISP_CC_MDSS_MDP_CLK>; dsi0_phy: dsi-phy@ae94400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; dsi1_phy: dsi-phy@ae64400 { clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, }; };And from what I've seen happening so far is that the
device_is_dependentcheck for the parent of the supplier (if it also a consumer) seems to return false on second pass of the same link due to theDL_FLAG_SYNC_STATE_ONLYbeing set this time around.Quoted 17 lines
See this comment in
fw_devlink_create_devlink()/*
* If we can't find the supplier device from its fwnode, it might be
* due to a cyclic dependency between fwnodes. Some of these cycles can
* be broken by applying logic. Check for these types of cycles and
* break them so that devices in the cycle probe properly. *
* If the supplier's parent is dependent on the consumer, then the
* consumer and supplier have a cyclic dependency. Sincefw_devlink
* can't tell which of the inferred dependencies are incorrect, don't
* enforce probe ordering between any of the devices in this cyclic
* dependency. Do this by relaxing all thefw_devlinkdevice links in
* this cycle and by treating the fwnode link between the consumer and
* the supplier as an invalid dependency.
*/Quoted 6 lines
So when this thing you mentioned above is happening for the second dsi phy (order doesn't matter), since the dsi phy itself cannot be found, the
device_is_dependentis run for the same link: dispcc -> mdss (supplier -> consumer), but again, since it has theDL_FLAG_SYNC_STATE_ONLYthis time around, it will skip that specific link.Ugh... I knew there was this gap, but didn't expect it to be a real world issue.
There are different ways of addressing this and they all fall somewhere within a spectrum of:
"stop enforcing very specific edges of the dependency graph when you find a cycles"
To
"just don't enforce any dependency for devices in a cycle and let the drivers figure out when to -EPROBE_DEFER".
Quoted 4 lines
And each of those are of varying complexity. Ideally I'd prefer to relax specific edges, but I need to balance it out with the code complexity. Let me soak this for a few weeks to decide on what option to take.
I wanted to check if there is any progress on this topic? It appears that few weeks turned into few months already and the issue is still present. If not, can we please re-consider applying [1] while Saravana is working on a better fix?
[1] https://lore.kernel.org/all/[email protected]/
Quoted 88 lines
Thanks for the report.
-Saravana
Quoted 83 lines
Quoted 25 lines
Applying this comment to your example, dispcc is the "consumer",
dsi0_phyis the "supplier" and mdss is the "supplier's parent".And because we can't guarantee the order of addition of these top level devices is why I also have this piece of recursive call inside
__fw_devlink_link_to_suppliers():/*
* If a device link was successfully created to a supplier, we
* now need to try and link the supplier to all its suppliers. *
* This is needed to detect and delete false dependencies in
* fwnode links that haven't been converted to a device link
* yet. See comments infw_devlink_create_devlink()for more
* details on the false dependency.
*
* Without deleting these false dependencies, some devices will
* never probe because they'll keep waiting for their false
* dependency fwnode links to be converted to device links. */
sup_dev=get_dev_from_fwnode(sup);__fw_devlink_link_to_suppliers(sup_dev, sup_dev->fwnode);put_device(sup_dev);Quoted 8 lines
So when mdss gets added, we'll link it to dispcc and then check if dispcc has any suppliers it needs to link to. And that's when the logic will catch the cycle and fix it.
Can you tell me why this wouldn't unblock the probing of dispcc? Are you actually hitting this on a device? If so, can you please check why this logic isn't sufficient to catch and undo the cycle?
This is happening on Qualcomm SDM845 with Linus's tree.
Quoted 47 lines
Thanks,
SaravanaQuoted 43 lines
So, the
dsi0_phywill be "device_add'ed" (throughof_platform_populate) by the mdss probe. The mdss will probe defer waiting for theDISP_CC_MDSS_MDP_CLK, while
the dispcc will probe defer waiting for thedsi0_phy(supplier).Basically, this 'supplier availability check' does not work when a supplier might be populated by a consumer of the device that is currently trying to probe.
Abel
Quoted 32 lines
drivers/base/core.c +3
-7return -EPROBE_DEFER ; } -mutex_unlock (&wfs_lock); +mutex_unlock (&fwnode_link_lock);device_links_write_lock ();@@ -1167,10 +1168,7 @@ static ssize_t waiting_for_supplier_show(struct device *dev,bool val;device_lock (dev); -mutex_lock (&wfs_lock); - val = !list_empty (&dev->links.needs_suppliers) - && dev->links.need_for_probe; -mutex_unlock (&wfs_lock); + val = !list_empty (&dev->fwnode->suppliers);device_unlock (dev);return sysfs_emit (buf,"%u\n" , val); }@@ -2202,7 +2200,7 @@ static int device_add_attrs(struct device *dev) goto err_remove_dev_groups; } -if (fw_devlink_flags && !fw_devlink_is_permissive ()) { +if (fw_devlink_flags && !fw_devlink_is_permissive () && dev->fwnode) { error =device_create_file (dev, &dev_attr_waiting_for_supplier);if (error) goto err_remove_dev_online; --2.29.2.454.gaff20da3a2-goog
Signature · 2 lines
With best wishes Dmitry
PATCH v2 14/17 of: property: Update implementation of add_links() to create fwnode links
In reply to Saravana KannanThe semantics of add_links() has changed from creating device link between devices to creating fwnode links between fwnodes. So, update the implementation of add_links() to match the new semantics.
--- drivers/of/property.c | 150 ++++++++++++------------------------------ 1 file changed, 41 insertions(+), 109 deletions(-)
drivers/of/property.c +41 -109
@@ -1038,33 +1038,9 @@ static bool of_is_ancestor_of(struct device_node *test_ancestor, }/** -* of_get_next_parent_dev - Add device link to supplier from supplier phandle -* @np: device tree node -* -* Given a device tree node (@np), this function finds its closest ancestor -* device tree node that has a corresponding struct device. -* -* The caller of this function is expected to call put_device() on the returned -* device when they are done. -*/ -static struct device *of_get_next_parent_dev (struct device_node *np) -{ -struct device *dev =NULL ; - -of_node_get (np); -do { - np =of_get_next_parent (np); -if (np) - dev =get_dev_from_fwnode (&np->fwnode); - }while (np && !dev); -of_node_put (np); -return dev; -} - -/** -* of_link_to_phandle - Add device link to supplier from supplier phandle -* @dev: consumer device -* @sup_np: phandle to supplier device tree node +* of_link_to_phandle - Add fwnode link to supplier from supplier phandle +* @con_np: consumer device tree node +* @sup_np: supplier device tree node * * Given a phandle to a supplier device tree node (@sup_np), this function * finds the device that owns the supplier device tree node and creates a
@@ -1074,16 +1050,14 @@ static struct device *of_get_next_parent_dev(struct device_node *np)* cases, it returns an error. * * Returns: -* - 0 if link successfully created to supplier -* - -EAGAIN if linking to the supplier should be reattempted +* - 0 if fwnode link successfully created to supplier * - -EINVAL if the supplier link is invalid and should not be created -* - -ENODEV if there is no device that corresponds to the supplier phandle +* - -ENODEV if struct device will never be create for supplier */ -static int of_link_to_phandle (struct device *dev,struct device_node *sup_np, -u32 dl_flags) +static int of_link_to_phandle (struct device_node *con_np, +struct device_node *sup_np) { -struct device *sup_dev, *sup_par_dev; -int ret =0 ; +struct device *sup_dev;struct device_node *tmp_np = sup_np;of_node_get (sup_np);
@@ -1106,7 +1080,8 @@ static int of_link_to_phandle(struct device *dev, struct device_node *sup_np, }if (!sup_np) { -dev_dbg (dev,"Not linking to %pOFP - No device\n" , tmp_np); +pr_debug ("Not linking %pOFP to %pOFP - No device\n" , + con_np, tmp_np);return -ENODEV ; }
@@ -1115,53 +1090,30 @@ static int of_link_to_phandle(struct device *dev, struct device_node *sup_np,* descendant nodes. By definition, a child node can't be a functional * dependency for the parent node. */ -if (of_is_ancestor_of (dev->of_node, sup_np)) { -dev_dbg (dev,"Not linking to %pOFP - is descendant\n" , sup_np); +if (of_is_ancestor_of (con_np, sup_np)) { +pr_debug ("Not linking %pOFP to %pOFP - is descendant\n" , + con_np, sup_np);of_node_put (sup_np);return -EINVAL ; } + +/* +* Don't create links to "early devices" that won't have struct devices +* created for them. +*/ sup_dev =get_dev_from_fwnode (&sup_np->fwnode);if (!sup_dev &&of_node_check_flag (sup_np,OF_POPULATED )) { -/* Early device without struct device. */ -dev_dbg (dev,"Not linking to %pOFP - No struct device\n" , - sup_np); +pr_debug ("Not linking %pOFP to %pOFP - No struct device\n" , + con_np, sup_np);of_node_put (sup_np);return -ENODEV ; - }else if (!sup_dev) { -/* -* DL_FLAG_SYNC_STATE_ONLY doesn't block probing and supports -* cycles. So cycle detection isn't necessary and shouldn't be -* done. -*/ -if (dl_flags &DL_FLAG_SYNC_STATE_ONLY ) { -of_node_put (sup_np); -return -EAGAIN ; - } - - sup_par_dev =of_get_next_parent_dev (sup_np); - -if (sup_par_dev &&device_is_dependent (dev, sup_par_dev)) { -/* Cyclic dependency detected, don't try to link */ -dev_dbg (dev,"Not linking to %pOFP - cycle detected\n" , - sup_np); - ret = -EINVAL ; - }else { -/* -* Can't check for cycles or no cycles. So let's try -* again later. -*/ - ret = -EAGAIN ; - } - -of_node_put (sup_np); -put_device (sup_par_dev); -return ret; } -of_node_put (sup_np); -if (!device_link_add (dev, sup_dev, dl_flags)) - ret = -EINVAL ;put_device (sup_dev); -return ret; + +fwnode_link_add (of_fwnode_handle (con_np),of_fwnode_handle (sup_np)); +of_node_put (sup_np); + +return 0 ; }/**
@@ -1361,37 +1313,29 @@ static const struct supplier_bindings of_supplier_bindings[] = {* that list phandles to suppliers. If @prop_name isn't one, this function * doesn't do anything. * -* If @prop_name is one, this function attempts to create device links from the -* consumer device @dev to all the devices of the suppliers listed in -* @prop_name. +* If @prop_name is one, this function attempts to create fwnode links from the +* consumer device tree node @con_np to all the suppliers device tree nodes +* listed in @prop_name. * -* Any failed attempt to create a device link will NOT result in an immediate +* Any failed attempt to create a fwnode link will NOT result in an immediate * return. of_link_property() must create links to all the available supplier -* devices even when attempts to create a link to one or more suppliers fail. +* device tree nodes even when attempts to create a link to one or more +* suppliers fail. */ -static int of_link_property (struct device *dev,struct device_node *con_np, -const char *prop_name) +static int of_link_property (struct device_node *con_np,const char *prop_name) {struct device_node *phandle;const struct supplier_bindings *s = of_supplier_bindings;unsigned int i =0 ;bool matched = false;int ret =0 ; -u32 dl_flags; - -if (dev->of_node == con_np) - dl_flags =fw_devlink_get_flags (); -else - dl_flags =DL_FLAG_SYNC_STATE_ONLY ;/* Do not stop at first failed link, link all available suppliers. */ while (!matched && s->parse_prop) {while ((phandle = s->parse_prop (con_np, prop_name, i))) { matched = true; i++; -if (of_link_to_phandle (dev, phandle, dl_flags) - == -EAGAIN ) - ret = -EAGAIN ; +of_link_to_phandle (con_np, phandle);of_node_put (phandle); } s++;
@@ -1399,31 +1343,19 @@ static int of_link_property(struct device *dev, struct device_node *con_np,return ret; } -static int of_link_to_suppliers (struct device *dev, -struct device_node *con_np) +static int of_fwnode_add_links (struct fwnode_handle *fwnode, +struct device *dev) { -struct device_node *child;struct property *p; -int ret =0 ; +struct device_node *con_np =to_of_node (fwnode); -for_each_property_of_node (con_np, p) -if (of_link_property (dev, con_np, p->name)) - ret = -ENODEV ; - -for_each_available_child_of_node (con_np, child) -if (of_link_to_suppliers (dev, child) && !ret) - ret = -EAGAIN ; - -return ret; -} +if (!con_np) +return -EINVAL ; -static int of_fwnode_add_links (const struct fwnode_handle *fwnode, -struct device *dev) -{ -if (unlikely (!is_of_node (fwnode))) -return 0 ; +for_each_property_of_node (con_np, p) +of_link_property (con_np, p->name); -return of_link_to_suppliers (dev,to_of_node (fwnode)); +return 0 ; }const struct fwnode_operations of_fwnode_ops = {
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 14/17] of: property: Update implementation of add_links() to create fwnode links
Quoted 9 lines · Saravana Kannan
The semantics of
add_links()has changed from creating device link between devices to creating fwnode links between fwnodes. So, update the implementation ofadd_links()to match the new semantics.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/property.c | 150 ++++++++++++------------------------------ 1 file changed, 41 insertions(+), 109 deletions(-)
PATCH v2 15/17 efi: Update implementation of add_links() to create fwnode links
In reply to Saravana KannanThe semantics of add_links() has changed from creating device link between devices to creating fwnode links between fwnodes. So, update the implementation of add_links() to match the new semantics.
--- drivers/firmware/efi/efi-init.c | 21 +-------------------- 1 file changed, 1 insertion(+), 20 deletions(-)
drivers/firmware/efi/efi-init.c +1 -20
@@ -320,7 +320,6 @@ static int efifb_add_links(struct fwnode_handle *fwnode, struct device *dev) {struct device_node *sup_np; -struct device *sup_dev; sup_np =find_pci_overlap_node ();
@@ -331,27 +330,9 @@ static int efifb_add_links(struct fwnode_handle *fwnode,if (!sup_np)return 0 ; - sup_dev =get_dev_from_fwnode (&sup_np->fwnode); +fwnode_link_add (fwnode,of_fwnode_handle (sup_np));of_node_put (sup_np); -/* -* Return -ENODEV if the PCI graphics controller device hasn't been -* registered yet. This ensures that efifb isn't allowed to probe -* and this function is retried again when new devices are -* registered. -*/ -if (!sup_dev) -return -ENODEV ; - -/* -* If this fails, retrying this function at a later point won't -* change anything. So, don't return an error after this. -*/ -if (!device_link_add (dev, sup_dev,fw_devlink_get_flags ())) -dev_warn (dev,"device_link_add() failed\n" ); - -put_device (sup_dev); -return 0 ; }
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
PATCH v2 16/17 driver core: Refactor fw_devlink feature
In reply to Saravana KannanThe current implementation of fw_devlink is very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.
We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by fw_devlink.
So this patch uses all the setup done by the previous patches in this series to refactor fw_devlink to be more efficient. Most of the code has been moved out of firmware specific (DT mostly) code into driver core.
This brings the following benefits:
- Instead of parsing the device tree multiple times during bootup, fw_devlink parses each fwnode node/property only once and creates fwnode links. The rest of the fw_devlink code then just looks at these fwnode links to do rest of the work.
- Makes it much easier to debug probe issue due to fw_devlink in the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.
- Much easier to add fw_devlink support to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support to fw_devlink. This series gets that done.
[1] - https://lore.kernel.org/linux-omap/[email protected]/
--- drivers/base/core.c | 325 ++++++++++++++++++++++++++++++----------- include/linux/device.h | 5 - 2 files changed, 238 insertions(+), 92 deletions(-)
drivers/base/core.c +238 -87
@@ -46,8 +46,6 @@ early_param("sysfs.deprecated", sysfs_deprecated_setup);#endif /* Device links support. */ -static LIST_HEAD (wait_for_suppliers); -static DEFINE_MUTEX (wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock);
@@ -803,74 +801,6 @@ struct device_link *device_link_add(struct device *consumer, }EXPORT_SYMBOL_GPL (device_link_add); -/** -* device_link_wait_for_supplier - Add device to wait_for_suppliers list -* @consumer: Consumer device -* -* Marks the @consumer device as waiting for suppliers to become available by -* adding it to the wait_for_suppliers list. The consumer device will never be -* probed until it's removed from the wait_for_suppliers list. -* -* The caller is responsible for adding the links to the supplier devices once -* they are available and removing the @consumer device from the -* wait_for_suppliers list once links to all the suppliers have been created. -* -* This function is NOT meant to be called from the probe function of the -* consumer but rather from code that creates/adds the consumer device. -*/ -static void device_link_wait_for_supplier (struct device *consumer, -bool need_for_probe) -{ -mutex_lock (&wfs_lock); -list_add_tail (&consumer->links.needs_suppliers, &wait_for_suppliers); - consumer->links.need_for_probe = need_for_probe; -mutex_unlock (&wfs_lock); -} - -static void device_link_wait_for_mandatory_supplier (struct device *consumer) -{ -device_link_wait_for_supplier (consumer, true); -} - -static void device_link_wait_for_optional_supplier (struct device *consumer) -{ -device_link_wait_for_supplier (consumer, false); -} - -/** -* device_link_add_missing_supplier_links - Add links from consumer devices to -* supplier devices, leaving any -* consumer with inactive suppliers on -* the wait_for_suppliers list -* -* Loops through all consumers waiting on suppliers and tries to add all their -* supplier links. If that succeeds, the consumer device is removed from -* wait_for_suppliers list. Otherwise, they are left in the wait_for_suppliers -* list. Devices left on the wait_for_suppliers list will not be probed. -* -* The fwnode add_links callback is expected to return 0 if it has found and -* added all the supplier links for the consumer device. It should return an -* error if it isn't able to do so. -* -* The caller of device_link_wait_for_supplier() is expected to call this once -* it's aware of potential suppliers becoming available. -*/ -static void device_link_add_missing_supplier_links (void ) -{ -struct device *dev, *tmp; - -mutex_lock (&wfs_lock); -list_for_each_entry_safe (dev, tmp, &wait_for_suppliers, - links.needs_suppliers) { -int ret =fwnode_call_int_op (dev->fwnode, add_links, dev); -if (!ret) -list_del_init (&dev->links.needs_suppliers); -else if (ret != -ENODEV ) - dev->links.need_for_probe = false; - } -mutex_unlock (&wfs_lock); -} -#ifdef CONFIG_SRCU static void __device_link_del (struct kref *kref) {
@@ -1195,9 +1125,8 @@ void device_links_driver_bound(struct device *dev)* the device links it needs to or make new device links as it needs * them. So, it no longer needs to wait on any suppliers. */ -mutex_lock (&wfs_lock); -list_del_init (&dev->links.needs_suppliers); -mutex_unlock (&wfs_lock); +if (dev->fwnode && dev->fwnode->dev == dev) +fwnode_links_purge_suppliers (dev->fwnode);device_remove_file (dev, &dev_attr_waiting_for_supplier);device_links_write_lock ();
@@ -1488,10 +1417,6 @@ static void device_links_purge(struct device *dev)if (dev->class == &devlink_class)return ; -mutex_lock (&wfs_lock); -list_del (&dev->links.needs_suppliers); -mutex_unlock (&wfs_lock); -/* * Delete all of the remaining links from this device to any other * devices (either consumers or suppliers).
@@ -1561,19 +1486,246 @@ static void fw_devlink_parse_fwtree(struct fwnode_handle *fwnode)fw_devlink_parse_fwtree (child); } -static void fw_devlink_link_device (struct device *dev) +/** +* fw_devlink_create_devlink - Create a device link from a consumer to fwnode +* @con - Consumer device for the device link +* @sup_handle - fwnode handle of supplier +* +* This function will try to create a device link between the consumer device +* @con and the supplier device represented by @sup_handle. +* +* The supplier has to be provided as a fwnode because incorrect cycles in +* fwnode links can sometimes cause the supplier device to never be created. +* This function detects such cases and returns an error if it cannot create a +* device link from the consumer to a missing supplier. +* +* Returns, +* 0 on successfully creating a device link +* -EINVAL if the device link cannot be created as expected +* -EAGAIN if the device link cannot be created right now, but it may be +* possible to do that in the future +*/ +static int fw_devlink_create_devlink (struct device *con, +struct fwnode_handle *sup_handle,u32 flags) +{ +struct device *sup_dev; +int ret =0 ; + + sup_dev =get_dev_from_fwnode (sup_handle); +if (sup_dev) { +/* +* If this fails, it is due to cycles in device links. Just +* give up on this link and treat it as invalid. +*/ +if (!device_link_add (con, sup_dev, flags)) + ret = -EINVAL ; + + goto out; + } + +/* +* DL_FLAG_SYNC_STATE_ONLY doesn't block probing and supports +* cycles. So cycle detection isn't necessary and shouldn't be +* done. +*/ +if (flags &DL_FLAG_SYNC_STATE_ONLY ) +return -EAGAIN ; + +/* +* If we can't find the supplier device from its fwnode, it might be +* due to a cyclic dependency between fwnodes. Some of these cycles can +* be broken by applying logic. Check for these types of cycles and +* break them so that devices in the cycle probe properly. +* +* If the supplier's parent is dependent on the consumer, then +* the consumer-supplier dependency is a false dependency. So, +* treat it as an invalid link. +*/ + sup_dev =fwnode_get_next_parent_dev (sup_handle); +if (sup_dev &&device_is_dependent (con, sup_dev)) { +dev_dbg (con,"Not linking to %pfwP - False link\n" , + sup_handle); + ret = -EINVAL ; + }else { +/* +* Can't check for cycles or no cycles. So let's try +* again later. +*/ + ret = -EAGAIN ; + } + +out: +put_device (sup_dev); +return ret; +} + +/** +* __fw_devlink_link_to_consumers - Create device links to consumers of a device +* @dev - Device that needs to be linked to its consumers +* +* This function looks at all the consumer fwnodes of @dev and creates device +* links between the consumer device and @dev (supplier). +* +* If the consumer device has not been added yet, then this function creates a +* SYNC_STATE_ONLY link between @dev (supplier) and the closest ancestor device +* of the consumer fwnode. This is necessary to make sure @dev doesn't get a +* sync_state() callback before the real consumer device gets to be added and +* then probed. +* +* Once device links are created from the real consumer to @dev (supplier), the +* fwnode links are deleted. +*/ +static void __fw_devlink_link_to_consumers (struct device *dev) +{ +struct fwnode_handle *fwnode = dev->fwnode; +struct fwnode_link *link, *tmp; + +list_for_each_entry_safe (link, tmp, &fwnode->consumers, s_hook) { +u32 dl_flags =fw_devlink_get_flags (); +struct device *con_dev; +bool own_link = true; +int ret; + + con_dev =get_dev_from_fwnode (link->consumer); +/* +* If consumer device is not available yet, make a "proxy" +* SYNC_STATE_ONLY link from the consumer's parent device to +* the supplier device. This is necessary to make sure the +* supplier doesn't get a sync_state() callback before the real +* consumer can create a device link to the supplier. +* +* This proxy link step is needed to handle the case where the +* consumer's parent device is added before the supplier. +*/ +if (!con_dev) { + con_dev =fwnode_get_next_parent_dev (link->consumer); +/* +* However, if the consumer's parent device is also the +* parent of the supplier, don't create a +* consumer-supplier link from the parent to its child +* device. Such a dependency is impossible. +*/ +if (con_dev && +fwnode_is_ancestor_of (con_dev->fwnode, fwnode)) { +put_device (con_dev); + con_dev =NULL ; + }else { + own_link = false; + dl_flags =DL_FLAG_SYNC_STATE_ONLY ; + } + } + +if (!con_dev) +continue ; + + ret =fw_devlink_create_devlink (con_dev, fwnode, dl_flags); +put_device (con_dev); +if (!own_link || ret == -EAGAIN ) +continue ; + +list_del (&link->s_hook); +list_del (&link->c_hook); +kfree (link); + } +} + +/** +* __fw_devlink_link_to_suppliers - Create device links to suppliers of a device +* @dev - The consumer device that needs to be linked to its suppliers +* @fwnode - Root of the fwnode tree that is used to create device links +* +* This function looks at all the supplier fwnodes of fwnode tree rooted at +* @fwnode and creates device links between @dev (consumer) and all the +* supplier devices of the entire fwnode tree at @fwnode. +* +* The function creates normal (non-SYNC_STATE_ONLY) device links between @dev +* and the real suppliers of @dev. Once these device links are created, the +* fwnode links are deleted. When such device links are successfully created, +* this function is called recursively on those supplier devices. This is +* needed to detect and break some invalid cycles in fwnode links. See +* fw_devlink_create_devlink() for more details. +* +* In addition, it also looks at all the suppliers of the entire fwnode tree +* because some of the child devices of @dev that have not been added yet +* (because @dev hasn't probed) might already have their suppliers added to +* driver core. So, this function creates SYNC_STATE_ONLY device links between +* @dev (consumer) and these suppliers to make sure they don't execute their +* sync_state() callbacks before these child devices have a chance to create +* their device links. The fwnode links that correspond to the child devices +* aren't delete because they are needed later to create the device links +* between the real consumer and supplier devices. +*/ +static void __fw_devlink_link_to_suppliers (struct device *dev, +struct fwnode_handle *fwnode) { -int fw_ret; +bool own_link = (dev->fwnode == fwnode); +struct fwnode_link *link, *tmp; +struct fwnode_handle *child =NULL ; +u32 dl_flags; + +if (own_link) + dl_flags =fw_devlink_get_flags (); +else + dl_flags =DL_FLAG_SYNC_STATE_ONLY ; -device_link_add_missing_supplier_links (); +list_for_each_entry_safe (link, tmp, &fwnode->suppliers, c_hook) { +int ret; +struct device *sup_dev; +struct fwnode_handle *sup = link->supplier; + + ret =fw_devlink_create_devlink (dev, sup, dl_flags); +if (!own_link || ret == -EAGAIN ) +continue ; -if (fw_devlink_flags &&fwnode_has_op (dev->fwnode, add_links)) { - fw_ret =fwnode_call_int_op (dev->fwnode, add_links, dev); -if (fw_ret == -ENODEV && !fw_devlink_is_permissive ()) -device_link_wait_for_mandatory_supplier (dev); -else if (fw_ret) -device_link_wait_for_optional_supplier (dev); +list_del (&link->s_hook); +list_del (&link->c_hook); +kfree (link); + +/* If no device link was created, nothing more to do. */ +if (ret) +continue ; + +/* +* If a device link was successfully created to a supplier, we +* now need to try and link the supplier to all its suppliers. +* +* This is needed to detect and delete false dependencies in +* fwnode links that haven't been converted to a device link +* yet. See comments in fw_devlink_create_devlink() for more +* details on the false dependency. +* +* Without deleting these false dependencies, some devices will +* never probe because they'll keep waiting for their false +* dependency fwnode links to be converted to device links. +*/ + sup_dev =get_dev_from_fwnode (sup); +__fw_devlink_link_to_suppliers (sup_dev, sup_dev->fwnode); +put_device (sup_dev); } + +/* +* Make "proxy" SYNC_STATE_ONLY device links to represent the needs of +* all the descendants. This proxy link step is needed to handle the +* case where the supplier is added before the consumer's parent device +* (@dev). +*/ +while ((child =fwnode_get_next_available_child_node (fwnode, child))) +__fw_devlink_link_to_suppliers (dev, child); +} + +static void fw_devlink_link_device (struct device *dev) +{ +struct fwnode_handle *fwnode = dev->fwnode; + +if (!fw_devlink_flags) +return ; + +fw_devlink_parse_fwtree (fwnode); + +mutex_lock (&fwnode_link_lock); +__fw_devlink_link_to_consumers (dev); +__fw_devlink_link_to_suppliers (dev, fwnode); +mutex_unlock (&fwnode_link_lock); }/* Device links support end. */
@@ -2431,7 +2583,6 @@ void device_initialize(struct device *dev)#endif INIT_LIST_HEAD (&dev->links.consumers);INIT_LIST_HEAD (&dev->links.suppliers); -INIT_LIST_HEAD (&dev->links.needs_suppliers);INIT_LIST_HEAD (&dev->links.defer_sync); dev->links.status =DL_DEV_NO_DRIVER ; }
include/linux/device.h +0 -5
@@ -351,18 +351,13 @@ enum dl_dev_state {* struct dev_links_info - Device data related to device links. * @suppliers: List of links to supplier devices. * @consumers: List of links to consumer devices. -* @needs_suppliers: Hook to global list of devices waiting for suppliers. * @defer_sync: Hook to global list of devices that have deferred sync_state. -* @need_for_probe: If needs_suppliers is on a list, this indicates if the -* suppliers are needed for probe or not. * @status: Driver status information. */ struct dev_links_info {struct list_head suppliers;struct list_head consumers; -struct list_head needs_suppliers;struct list_head defer_sync; -bool need_for_probe;enum dl_dev_state status; };
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
kernel test robot
build bot[driver core] 95f755a4ef: will-it-scale.per_process_ops 2.2% improvement
FYI, we noticed a 2.2% improvement of will-it-scale.per_process_ops due to commit:
Greeting,
FYI, we noticed a 2.2% improvement of will-it-scale.per_process_ops due to commit:
commit: 95f755a4ef7b9ccbedf6012b4112a990120b6a6c ("[PATCH v2 16/17] driver core: Refactor fw_devlink feature")
url: https://github.com/0day-ci/linux/commits/Saravana-Kannan/Refactor-fw_devlink-to-significantly-improve-boot-time/20201121-100850
base: https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git linux-next
in testcase: will-it-scale
on test machine: 192 threads Intel(R) Xeon(R) Platinum 9242 CPU @ 2.30GHz with 192G memory with following parameters:
nr_task: 50% mode: process test: futex3 cpufreq_governor: performance ucode: 0x5003003
test-description: Will It Scale takes a testcase and runs it from 1 through to n parallel copies to see if the testcase will scale. It builds both a process and threads based test in order to see any differences between the two.
test-url: https://github.com/antonblanchard/will-it-scale
In addition to that, the commit also has significant impact on the following tests:
+------------------+---------------------------------------------------------------------------+ | testcase: change | will-it-scale: will-it-scale.per_process_ops 5.2% improvement | | test machine | 192 threads Intel(R) Xeon(R) Platinum 9242 CPU @ 2.30GHz with 192G memory | | test parameters | cpufreq_governor=performance | | | mode=process | | | nr_task=50% | | | test=dup1 | | | ucode=0x5003003 | +------------------+---------------------------------------------------------------------------+
Details are as below:
-------------------------------------------------------------------------------------------------->
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
=========================================================================================
compiler/cpufreq_governor/kconfig/mode/nr_task/rootfs/tbox_group/test/testcase/ucode:
gcc-9/performance/x86_64-rhel-8.3/process/50%/debian-10.4-x86_64-20200603.cgz/lkp-csl-2ap2/futex3/will-it-scale/0x5003003
commit:
03b7843215 ("efi: Update implementation of add_links() to create fwnode links") 95f755a4ef ("driver core: Refactor fw_devlink feature")
03b7843215575338 95f755a4ef7b9ccbedf6012b411
---------------- ---------------------------
%stddev %change %stddev
\ | \
10181734 +2.2% 10402895 will-it-scale.per_process_ops
9.774e+08 +2.2% 9.987e+08 will-it-scale.workload
13832427 ± 6% -10.8% 12342804 ± 4% meminfo.DirectMap2M
2454 -5.0% 2332 ± 2% vmstat.system.cs
16233 ± 29% +172.3% 44205 ± 33% numa-vmstat.node0.nr_anon_pages
17076 ± 33% +162.3% 44793 ± 35% numa-vmstat.node0.nr_inactive_anon
17076 ± 33% +162.3% 44793 ± 35% numa-vmstat.node0.nr_zone_inactive_anon
23545 ± 69% +388.7% 115074 ± 36% numa-meminfo.node0.AnonHugePages
64841 ± 29% +172.6% 176742 ± 33% numa-meminfo.node0.AnonPages
68213 ± 33% +162.6% 179095 ± 35% numa-meminfo.node0.Inactive
68213 ± 33% +162.6% 179095 ± 35% numa-meminfo.node0.Inactive(anon)
4.38 ± 10% -2.5 1.87 ± 8% perf-profile.calltrace.cycles-pp.syscall_enter_from_user_mode.do_syscall_64.entry_SYSCALL_64_after_hwframe.syscall
4.61 ± 9% -2.7 1.88 ± 8% perf-profile.children.cycles-pp.syscall_enter_from_user_mode
0.46 ± 11% -0.2 0.24 ± 9% perf-profile.children.cycles-pp.__x86_indirect_thunk_rax
4.44 ± 10% -2.7 1.71 ± 8% perf-profile.self.cycles-pp.syscall_enter_from_user_mode
2.00 ± 9% +0.6 2.63 ± 8% perf-profile.self.cycles-pp.do_futex
2.52 ± 10% +0.8 3.37 ± 9% perf-profile.self.cycles-pp.__x64_sys_futex
70868 ± 13% +21.5% 86124 sched_debug.cfs_rq:/.exec_clock.avg
125411 ± 10% +17.9% 147892 sched_debug.cfs_rq:/.exec_clock.max
7286186 ± 12% +21.3% 8840402 sched_debug.cfs_rq:/.min_vruntime.avg
12873032 ± 10% +17.7% 15149207 sched_debug.cfs_rq:/.min_vruntime.max
0.80 ± 13% +29.9% 1.04 ± 9% sched_debug.cfs_rq:/.nr_spread_over.avg
-828241 +84.1% -1524980 sched_debug.cfs_rq:/.spread0.min
7478 ± 5% +9.6% 8199 sched_debug.cpu.curr->pid.max
21364 ± 19% +41.9% 30320 ± 23% sched_debug.cpu.ttwu_count.max
1997 ± 14% +27.8% 2552 ± 15% sched_debug.cpu.ttwu_count.stddev
6.451e+10 +2.3% 6.597e+10 perf-stat.i.branch-instructions
4.942e+08 +2.3% 5.054e+08 perf-stat.i.branch-misses
13.97 ± 2% -1.0 13.00 ± 3% perf-stat.i.cache-miss-rate%
1429864 ± 3% -8.8% 1303388 ± 4% perf-stat.i.cache-misses
2410 -5.2% 2285 ± 3% perf-stat.i.context-switches
0.71 -2.6% 0.69 perf-stat.i.cpi
229727 ± 2% +9.8% 252139 ± 4% perf-stat.i.cycles-between-cache-misses
1.062e+11 +2.3% 1.087e+11 perf-stat.i.dTLB-loads
127892 +1.6% 129886 perf-stat.i.dTLB-store-misses
8.09e+10 +2.2% 8.272e+10 perf-stat.i.dTLB-stores
4259891 ± 2% -4.0% 4089092 perf-stat.i.iTLB-loads
4.208e+11 +2.3% 4.303e+11 perf-stat.i.instructions
1.42 +2.2% 1.45 perf-stat.i.ipc
0.65 +3.1% 0.67 perf-stat.i.major-faults
1.33 +3.6% 1.38 perf-stat.i.metric.K/sec
1310 +2.3% 1340 perf-stat.i.metric.M/sec
14.08 ± 2% -1.2 12.92 ± 3% perf-stat.overall.cache-miss-rate%
0.70 -2.1% 0.69 perf-stat.overall.cpi
205608 ± 3% +10.0% 226168 ± 4% perf-stat.overall.cycles-between-cache-misses
1.42 +2.2% 1.45 perf-stat.overall.ipc
6.429e+10 +2.3% 6.574e+10 perf-stat.ps.branch-instructions
4.925e+08 +2.3% 5.037e+08 perf-stat.ps.branch-misses
1439249 ± 3% -8.9% 1310558 ± 4% perf-stat.ps.cache-misses
2401 -5.3% 2274 ± 3% perf-stat.ps.context-switches
1.059e+11 +2.3% 1.083e+11 perf-stat.ps.dTLB-loads
127806 +1.7% 129943 perf-stat.ps.dTLB-store-misses
8.062e+10 +2.2% 8.243e+10 perf-stat.ps.dTLB-stores
4246454 ± 2% -4.1% 4074221 perf-stat.ps.iTLB-loads
4.193e+11 +2.3% 4.288e+11 perf-stat.ps.instructions
32095 ± 2% -6.6% 29971 ± 5% perf-stat.ps.node-loads
1.27e+14 +2.1% 1.297e+14 perf-stat.total.instructions
2251 ± 13% -25.6% 1674 ± 16% interrupts.CPU100.CAL:Function_call_interrupts
4823 ± 46% +34.3% 6475 ± 35% interrupts.CPU105.NMI:Non-maskable_interrupts
4823 ± 46% +34.3% 6475 ± 35% interrupts.CPU105.PMI:Performance_monitoring_interrupts
7063 ± 15% -47.6% 3704 ± 47% interrupts.CPU11.NMI:Non-maskable_interrupts
7063 ± 15% -47.6% 3704 ± 47% interrupts.CPU11.PMI:Performance_monitoring_interrupts
1743 ± 6% +29.0% 2249 ± 22% interrupts.CPU126.CAL:Function_call_interrupts
6249 ± 6% -41.3% 3670 ± 14% interrupts.CPU130.NMI:Non-maskable_interrupts
6249 ± 6% -41.3% 3670 ± 14% interrupts.CPU130.PMI:Performance_monitoring_interrupts
7215 ± 17% -42.5% 4148 ± 60% interrupts.CPU137.NMI:Non-maskable_interrupts
7215 ± 17% -42.5% 4148 ± 60% interrupts.CPU137.PMI:Performance_monitoring_interrupts
235.50 ± 19% -77.8% 52.25 ± 91% interrupts.CPU144.RES:Rescheduling_interrupts
5653 ± 37% -50.4% 2803 ± 33% interrupts.CPU146.NMI:Non-maskable_interrupts
5653 ± 37% -50.4% 2803 ± 33% interrupts.CPU146.PMI:Performance_monitoring_interrupts
6894 ± 16% -50.3% 3426 ± 22% interrupts.CPU147.NMI:Non-maskable_interrupts
6894 ± 16% -50.3% 3426 ± 22% interrupts.CPU147.PMI:Performance_monitoring_interrupts
6768 ± 20% -57.4% 2886 ± 36% interrupts.CPU149.NMI:Non-maskable_interrupts
6768 ± 20% -57.4% 2886 ± 36% interrupts.CPU149.PMI:Performance_monitoring_interrupts
6750 ± 19% -36.7% 4274 ± 24% interrupts.CPU15.NMI:Non-maskable_interrupts
6750 ± 19% -36.7% 4274 ± 24% interrupts.CPU15.PMI:Performance_monitoring_interrupts
74.75 ± 95% +181.6% 210.50 ± 32% interrupts.CPU157.RES:Rescheduling_interrupts
3955 ± 41% +114.3% 8474 ± 5% interrupts.CPU159.NMI:Non-maskable_interrupts
3955 ± 41% +114.3% 8474 ± 5% interrupts.CPU159.PMI:Performance_monitoring_interrupts
157.00 ± 50% -82.0% 28.25 ± 83% interrupts.CPU161.RES:Rescheduling_interrupts
6259 ± 11% -42.8% 3579 ± 34% interrupts.CPU183.NMI:Non-maskable_interrupts
6259 ± 11% -42.8% 3579 ± 34% interrupts.CPU183.PMI:Performance_monitoring_interrupts
354.50 ± 77% -87.2% 45.50 ±120% interrupts.CPU2.RES:Rescheduling_interrupts
5070 ± 35% +54.3% 7821 ± 14% interrupts.CPU26.NMI:Non-maskable_interrupts
5070 ± 35% +54.3% 7821 ± 14% interrupts.CPU26.PMI:Performance_monitoring_interrupts
158.75 ± 38% +74.3% 276.75 ± 15% interrupts.CPU35.RES:Rescheduling_interrupts
7163 ± 21% -49.6% 3608 ± 35% interrupts.CPU44.NMI:Non-maskable_interrupts
7163 ± 21% -49.6% 3608 ± 35% interrupts.CPU44.PMI:Performance_monitoring_interrupts
57.75 ± 74% +329.4% 248.00 ± 16% interrupts.CPU48.RES:Rescheduling_interrupts
5295 ± 16% +61.1% 8529 ± 3% interrupts.CPU5.NMI:Non-maskable_interrupts
5295 ± 16% +61.1% 8529 ± 3% interrupts.CPU5.PMI:Performance_monitoring_interrupts
7999 ± 16% -53.7% 3703 ± 47% interrupts.CPU60.NMI:Non-maskable_interrupts
7999 ± 16% -53.7% 3703 ± 47% interrupts.CPU60.PMI:Performance_monitoring_interrupts
6556 ± 23% -47.6% 3432 ± 10% interrupts.CPU61.NMI:Non-maskable_interrupts
6556 ± 23% -47.6% 3432 ± 10% interrupts.CPU61.PMI:Performance_monitoring_interrupts
238.00 ± 27% -63.0% 88.00 ± 80% interrupts.CPU61.RES:Rescheduling_interrupts
7585 ± 10% -49.1% 3863 ± 30% interrupts.CPU63.NMI:Non-maskable_interrupts
7585 ± 10% -49.1% 3863 ± 30% interrupts.CPU63.PMI:Performance_monitoring_interrupts
216.25 ± 21% -73.6% 57.00 ±133% interrupts.CPU63.RES:Rescheduling_interrupts
138.25 ± 56% +90.2% 263.00 ± 10% interrupts.CPU65.RES:Rescheduling_interrupts
241.25 ± 31% -56.7% 104.50 ± 96% interrupts.CPU66.RES:Rescheduling_interrupts
7553 ± 15% -47.0% 4004 ± 40% interrupts.CPU76.NMI:Non-maskable_interrupts
7553 ± 15% -47.0% 4004 ± 40% interrupts.CPU76.PMI:Performance_monitoring_interrupts
4934 ± 52% +71.1% 8442 ± 2% interrupts.CPU92.NMI:Non-maskable_interrupts
4934 ± 52% +71.1% 8442 ± 2% interrupts.CPU92.PMI:Performance_monitoring_interrupts
194.00 ± 30% +47.9% 287.00 interrupts.CPU92.RES:Rescheduling_interrupts
23725 ± 8% -27.8% 17131 ± 18% softirqs.CPU1.RCU
23137 ± 12% -31.2% 15917 ± 24% softirqs.CPU101.RCU
21338 ± 16% -28.2% 15329 ± 22% softirqs.CPU104.RCU
18202 ± 7% -17.2% 15064 ± 18% softirqs.CPU112.RCU
21059 ± 18% -26.8% 15417 ± 10% softirqs.CPU113.RCU
21006 ± 17% -30.8% 14529 ± 14% softirqs.CPU115.RCU
27815 ± 36% -33.3% 18546 ± 57% softirqs.CPU121.SCHED
20978 ± 19% -22.2% 16329 ± 27% softirqs.CPU124.RCU
19729 ± 12% -23.7% 15060 ± 14% softirqs.CPU125.RCU
22706 ± 15% -27.8% 16382 ± 12% softirqs.CPU126.RCU
22705 ± 12% -25.4% 16931 ± 27% softirqs.CPU127.RCU
20037 ± 19% -28.2% 14387 ± 12% softirqs.CPU128.RCU
19573 ± 12% -22.8% 15111 ± 4% softirqs.CPU129.RCU
20596 ± 10% -30.9% 14242 ± 14% softirqs.CPU131.RCU
23440 ± 33% +46.3% 34297 ± 9% softirqs.CPU131.SCHED
19106 ± 16% -23.1% 14700 ± 15% softirqs.CPU132.RCU
22821 ± 11% -26.4% 16795 ± 8% softirqs.CPU138.RCU
23505 ± 11% -32.3% 15917 ± 20% softirqs.CPU14.RCU
22836 ± 9% -16.7% 19023 ± 14% softirqs.CPU141.RCU
21767 ± 14% -30.6% 15105 ± 19% softirqs.CPU143.RCU
19267 ± 46% +67.2% 32223 ± 14% softirqs.CPU143.SCHED
24861 ± 4% -41.0% 14660 ± 11% softirqs.CPU144.RCU
11831 ± 47% +177.8% 32871 ± 15% softirqs.CPU144.SCHED
23297 ± 9% -27.0% 17004 ± 6% softirqs.CPU147.RCU
22685 ± 13% -31.4% 15567 ± 18% softirqs.CPU149.RCU
23209 ± 10% -25.8% 17228 ± 8% softirqs.CPU15.RCU
33035 ± 24% -54.6% 15002 ± 56% softirqs.CPU157.SCHED
28385 ± 25% -63.2% 10448 ± 79% softirqs.CPU159.SCHED
20067 ± 7% -12.1% 17638 ± 9% softirqs.CPU160.RCU
22261 ± 14% -35.7% 14306 ± 6% softirqs.CPU161.RCU
20998 ± 43% +67.5% 35179 ± 11% softirqs.CPU161.SCHED
32659 ± 28% -51.0% 16004 ± 66% softirqs.CPU162.SCHED
23692 ± 12% -19.1% 19177 ± 7% softirqs.CPU166.RCU
23350 ± 7% -26.6% 17139 ± 22% softirqs.CPU170.RCU
21357 ± 8% -35.5% 13779 ± 10% softirqs.CPU174.RCU
21886 ± 5% -33.4% 14582 ± 11% softirqs.CPU175.RCU
26609 ± 3% -27.8% 19208 ± 24% softirqs.CPU18.RCU
19898 ± 12% -27.4% 14443 ± 9% softirqs.CPU180.RCU
23109 ± 9% -32.2% 15658 ± 23% softirqs.CPU186.RCU
19719 ± 18% -36.6% 12500 ± 11% softirqs.CPU188.RCU
21919 ± 16% -33.2% 14647 ± 17% softirqs.CPU2.RCU
25187 ± 11% -23.3% 19313 ± 26% softirqs.CPU20.RCU
23983 ± 15% -20.6% 19041 ± 17% softirqs.CPU21.RCU
24148 ± 14% -17.8% 19849 ± 21% softirqs.CPU22.RCU
24732 ± 9% -25.8% 18348 ± 24% softirqs.CPU24.RCU
23282 ± 14% -27.6% 16851 ± 15% softirqs.CPU25.RCU
20694 ± 34% -54.3% 9460 ± 29% softirqs.CPU35.SCHED
25058 ± 13% -27.9% 18059 ± 18% softirqs.CPU4.RCU
20413 ± 18% -28.2% 14659 ± 8% softirqs.CPU43.RCU
23803 ± 17% -32.8% 15994 ± 19% softirqs.CPU44.RCU
24249 ± 11% -22.1% 18886 ± 22% softirqs.CPU46.RCU
32235 ± 14% -65.5% 11106 ± 51% softirqs.CPU48.SCHED
28803 ± 16% -39.1% 17536 ± 30% softirqs.CPU60.RCU
26565 ± 10% -34.4% 17436 ± 22% softirqs.CPU61.RCU
11142 ± 68% +156.3% 28562 ± 24% softirqs.CPU61.SCHED
25175 ± 12% -37.0% 15853 ± 9% softirqs.CPU63.RCU
14961 ± 56% +120.3% 32955 ± 26% softirqs.CPU63.SCHED
23043 ± 39% -62.7% 8602 ± 36% softirqs.CPU65.SCHED
26792 ± 12% -35.8% 17210 ± 14% softirqs.CPU66.RCU
19766 ± 18% -29.6% 13906 ± 9% softirqs.CPU7.RCU
22073 ± 13% -24.4% 16678 ± 23% softirqs.CPU70.RCU
24267 ± 4% -25.3% 18121 ± 19% softirqs.CPU75.RCU
27057 ± 23% -56.9% 11669 ± 75% softirqs.CPU78.SCHED
23392 ± 9% -32.1% 15885 ± 3% softirqs.CPU81.RCU
21645 ± 11% -26.5% 15910 ± 11% softirqs.CPU83.RCU
23556 ± 8% -30.1% 16475 ± 8% softirqs.CPU85.RCU
10105 ± 53% +102.5% 20466 ± 28% softirqs.CPU85.SCHED
24799 ± 15% -27.3% 18022 ± 9% softirqs.CPU88.RCU
19697 ± 58% -71.0% 5715 ± 7% softirqs.CPU92.SCHED
22778 ± 6% -24.3% 17235 ± 15% softirqs.CPU93.RCU
18189 ± 13% -24.4% 13760 ± 10% softirqs.CPU95.RCU
26156 ± 2% -21.7% 20485 ± 13% softirqs.CPU96.RCU
21904 ± 45% -56.8% 9452 ± 57% softirqs.CPU98.SCHED
22162 ± 11% -27.8% 15992 ± 9% softirqs.CPU99.RCU
38457 ± 10% -32.2% 26084 ± 35% softirqs.NET_RX
4109730 -18.0% 3370902 ± 12% softirqs.RCU
47247 ± 4% -20.1% 37765 ± 15% softirqs.TIMER
will-it-scale.per_process_ops 1.045e+07 +---------------------------------------------------------------+
| O O O |
1.04e+07 |-+ O O O O O O O O O O O O O O O |
| O O O O O O O O O O O O |
1.035e+07 |-+ |
| |
1.03e+07 |-+ |
| |
1.025e+07 |-+ |
| |
1.02e+07 |-+ +.+..+.+ .+. |
| + + .+.+..+.+.+.+ +.+.|
1.015e+07 |.+.+.+.+.+ +. .+.+.+.+.+. .+.+.+.+ |
| + + + |
1.01e+07 +---------------------------------------------------------------+ will-it-scale.workload
1.005e+09 +---------------------------------------------------------------+
| |
1e+09 |-O O O O O O O O O O |
| O O O O O O O O O O O O O O O O |
9.95e+08 |-+ O O O O |
| |
9.9e+08 |-+ |
| |
9.85e+08 |-+ |
| |
9.8e+08 |-+ +. .+.+ |
| : +. + +.+..+.+.+.+.+.+.+.|
9.75e+08 |.+.+.+.+. : +. .+.+.+. .+. .+.+.+. + |
| + + + + + + |
9.7e+08 +---------------------------------------------------------------+ [*] bisect-good sample
[O] bisect-bad sample
***************************************************************************************************
lkp-csl-2ap2: 192 threads Intel(R) Xeon(R) Platinum 9242 CPU @ 2.30GHz with 192G memory
=========================================================================================
compiler/cpufreq_governor/kconfig/mode/nr_task/rootfs/tbox_group/test/testcase/ucode:
gcc-9/performance/x86_64-rhel-8.3/process/50%/debian-10.4-x86_64-20200603.cgz/lkp-csl-2ap2/dup1/will-it-scale/0x5003003
commit:
03b7843215 ("efi: Update implementation of add_links() to create fwnode links") 95f755a4ef ("driver core: Refactor fw_devlink feature")
03b7843215575338 95f755a4ef7b9ccbedf6012b411
---------------- ---------------------------
%stddev %change %stddev
\ | \
4681240 +5.2% 4925857 will-it-scale.per_process_ops
4.494e+08 +5.2% 4.729e+08 will-it-scale.workload
84205 ± 3% -6.6% 78620 ± 2% cpuidle.POLL.time
12.74 +1.4 14.10 mpstat.cpu.all.usr%
38.69 ± 9% +593.5% 268.33 ±101% sched_debug.cfs_rq:/.exec_clock.min
12.00 +8.3% 13.00 vmstat.cpu.us
2342 -1.8% 2299 vmstat.system.cs
1416 ± 4% -9.2% 1287 ± 4% slabinfo.dmaengine-unmap-16.active_objs
1416 ± 4% -9.2% 1287 ± 4% slabinfo.dmaengine-unmap-16.num_objs
6896 ± 4% -10.3% 6185 ± 4% slabinfo.kmalloc-rcl-64.active_objs
6896 ± 4% -10.3% 6185 ± 4% slabinfo.kmalloc-rcl-64.num_objs
2118 ± 2% -13.9% 1824 ± 6% slabinfo.kmalloc-rcl-96.active_objs
2118 ± 2% -13.9% 1824 ± 6% slabinfo.kmalloc-rcl-96.num_objs
13476 ± 4% -12.9% 11741 ± 3% slabinfo.pde_opener.active_objs
13476 ± 4% -12.9% 11741 ± 3% slabinfo.pde_opener.num_objs
2637 ± 63% -81.3% 492.50 ±142% numa-meminfo.node0.Active
2637 ± 63% -81.3% 492.50 ±142% numa-meminfo.node0.Active(anon)
2915 ± 16% -47.8% 1520 ± 19% numa-meminfo.node0.PageTables
87880 ± 10% -20.2% 70124 ± 9% numa-meminfo.node0.SUnreclaim
2153 ± 42% +215.9% 6802 ± 64% numa-meminfo.node2.Shmem
39060 ± 53% +306.7% 158860 ± 45% numa-meminfo.node3.AnonPages
46215 ± 44% +256.0% 164519 ± 42% numa-meminfo.node3.Inactive
46215 ± 44% +256.0% 164519 ± 42% numa-meminfo.node3.Inactive(anon)
750282 ± 10% +20.7% 905405 ± 13% numa-meminfo.node3.MemUsed
658.50 ± 63% -81.4% 122.75 ±142% numa-vmstat.node0.nr_active_anon
728.00 ± 15% -47.9% 379.50 ± 19% numa-vmstat.node0.nr_page_table_pages
21969 ± 10% -20.2% 17530 ± 9% numa-vmstat.node0.nr_slab_unreclaimable
658.50 ± 63% -81.4% 122.75 ±142% numa-vmstat.node0.nr_zone_active_anon
621492 ± 13% -26.7% 455253 ± 16% numa-vmstat.node0.numa_hit
572512 ± 17% -31.5% 391888 ± 15% numa-vmstat.node0.numa_local
538.00 ± 42% +216.0% 1700 ± 64% numa-vmstat.node2.nr_shmem
9760 ± 53% +307.2% 39747 ± 45% numa-vmstat.node3.nr_anon_pages
11513 ± 43% +257.5% 41166 ± 42% numa-vmstat.node3.nr_inactive_anon
11513 ± 43% +257.5% 41166 ± 42% numa-vmstat.node3.nr_zone_inactive_anon
548959 ± 19% +33.0% 730071 ± 31% numa-vmstat.node3.numa_hit
427995 ± 25% +47.7% 632173 ± 36% numa-vmstat.node3.numa_local
2.37 ± 8% -1.5 0.88 ± 8% perf-profile.calltrace.cycles-pp.syscall_enter_from_user_mode.do_syscall_64.entry_SYSCALL_64_after_hwframe.__close
2.33 ± 8% -1.5 0.88 ± 8% perf-profile.calltrace.cycles-pp.syscall_enter_from_user_mode.do_syscall_64.entry_SYSCALL_64_after_hwframe.dup
0.47 ± 57% +0.3 0.74 ± 7% perf-profile.calltrace.cycles-pp.locks_remove_posix.filp_close.__x64_sys_close.do_syscall_64.entry_SYSCALL_64_after_hwframe
1.27 ± 7% +0.7 1.96 ± 8% perf-profile.calltrace.cycles-pp.syscall_return_via_sysret.__close
4.94 ± 8% -3.2 1.77 ± 8% perf-profile.children.cycles-pp.syscall_enter_from_user_mode
0.44 ± 8% -0.2 0.23 ± 8% perf-profile.children.cycles-pp.__x86_indirect_thunk_rax
0.12 ± 18% -0.0 0.08 ± 13% perf-profile.children.cycles-pp.clockevents_program_event
0.11 ± 18% -0.0 0.07 ± 15% perf-profile.children.cycles-pp.ktime_get
0.27 ± 4% +0.1 0.33 ± 18% perf-profile.children.cycles-pp.start_kernel
4.76 ± 8% -3.1 1.62 ± 8% perf-profile.self.cycles-pp.syscall_enter_from_user_mode
1.15 ± 7% -0.5 0.67 ± 8% perf-profile.self.cycles-pp.__x64_sys_close
1.44 ± 9% -0.4 1.05 ± 9% perf-profile.self.cycles-pp.__x64_sys_dup
0.11 ± 21% -0.0 0.07 ± 13% perf-profile.self.cycles-pp.ktime_get
0.09 ± 8% +0.0 0.11 ± 4% perf-profile.self.cycles-pp.rcu_read_unlock_strict
9492 ± 72% -65.5% 3272 ±142% softirqs.CPU10.NET_RX
11789 ± 6% +25.7% 14823 ± 11% softirqs.CPU100.RCU
13884 ± 12% +26.5% 17565 ± 9% softirqs.CPU124.RCU
31918 ± 27% -65.9% 10876 ± 41% softirqs.CPU124.SCHED
15884 ± 11% +22.0% 19382 ± 11% softirqs.CPU13.RCU
30930 ± 28% -48.0% 16070 ± 72% softirqs.CPU132.SCHED
17573 ± 6% +77.1% 31116 ± 23% softirqs.CPU170.SCHED
16544 ± 4% -11.4% 14650 ± 10% softirqs.CPU185.RCU
17192 ± 8% -18.7% 13986 ± 16% softirqs.CPU186.RCU
10342 ± 45% +148.7% 25727 ± 27% softirqs.CPU186.SCHED
18559 ± 11% -22.9% 14300 ± 8% softirqs.CPU2.RCU
11714 ± 45% +150.5% 29341 ± 30% softirqs.CPU2.SCHED
21025 ± 46% -47.9% 10949 ± 77% softirqs.CPU21.SCHED
17639 ± 6% -20.2% 14081 ± 9% softirqs.CPU28.RCU
12427 ± 76% +146.2% 30597 ± 22% softirqs.CPU28.SCHED
5236 ± 6% +242.8% 17948 ± 41% softirqs.CPU4.SCHED
12934 ± 56% +139.0% 30910 ± 17% softirqs.CPU57.SCHED
14047 ± 6% +24.2% 17447 ± 8% softirqs.CPU74.RCU
27112 ± 3% -57.2% 11605 ± 70% softirqs.CPU74.SCHED
14231 ± 13% +15.8% 16478 ± 7% softirqs.CPU79.RCU
12191 ± 4% +28.2% 15634 ± 6% softirqs.CPU90.RCU
33498 ± 11% -47.3% 17657 ± 47% softirqs.CPU90.SCHED
13451 ± 5% +27.0% 17079 ± 13% softirqs.CPU98.RCU
33555 ± 15% -59.5% 13587 ± 56% softirqs.CPU98.SCHED
6.427e+10 +5.1% 6.752e+10 perf-stat.i.branch-instructions
0.90 -0.0 0.88 perf-stat.i.branch-miss-rate%
5.739e+08 +3.4% 5.933e+08 perf-stat.i.branch-misses
2298 -1.8% 2257 perf-stat.i.context-switches
0.88 -5.2% 0.84 perf-stat.i.cpi
1.067e+11 +5.1% 1.121e+11 perf-stat.i.dTLB-loads
110648 +8.9% 120538 perf-stat.i.dTLB-store-misses
7.223e+10 +5.1% 7.591e+10 perf-stat.i.dTLB-stores
6.072e+08 +5.4% 6.401e+08 ± 4% perf-stat.i.iTLB-load-misses
3.356e+11 +5.1% 3.526e+11 perf-stat.i.instructions
1.13 +5.5% 1.19 perf-stat.i.ipc
1.24 ± 2% +7.5% 1.34 ± 3% perf-stat.i.metric.K/sec
1266 +5.1% 1331 perf-stat.i.metric.M/sec
0.03 -3.5% 0.03 perf-stat.overall.MPKI
0.89 -0.0 0.88 perf-stat.overall.branch-miss-rate%
0.88 -5.2% 0.84 perf-stat.overall.cpi
0.00 +0.0 0.00 perf-stat.overall.dTLB-store-miss-rate%
1.13 +5.5% 1.19 perf-stat.overall.ipc
6.405e+10 +5.1% 6.729e+10 perf-stat.ps.branch-instructions
5.719e+08 +3.4% 5.913e+08 perf-stat.ps.branch-misses
2287 -1.8% 2247 perf-stat.ps.context-switches
1.063e+11 +5.1% 1.117e+11 perf-stat.ps.dTLB-loads
110749 +8.7% 120431 perf-stat.ps.dTLB-store-misses
7.199e+10 +5.1% 7.565e+10 perf-stat.ps.dTLB-stores
6.049e+08 +5.4% 6.376e+08 ± 4% perf-stat.ps.iTLB-load-misses
3.345e+11 +5.1% 3.514e+11 perf-stat.ps.instructions
1.013e+14 +5.2% 1.065e+14 perf-stat.total.instructions
18582 ± 74% -66.5% 6229 ±146% interrupts.31:PCI-MSI.524289-edge.eth0-TxRx-0
18582 ± 74% -66.5% 6229 ±146% interrupts.CPU10.31:PCI-MSI.524289-edge.eth0-TxRx-0
2285 ± 40% -27.5% 1655 ± 5% interrupts.CPU103.CAL:Function_call_interrupts
150.00 ± 56% -67.2% 49.25 ±138% interrupts.CPU117.RES:Rescheduling_interrupts
2.00 ± 86% +8587.5% 173.75 ±168% interrupts.CPU123.TLB:TLB_shootdowns
73.00 ±101% +229.5% 240.50 ± 19% interrupts.CPU124.RES:Rescheduling_interrupts
3375 ± 23% +112.2% 7163 ± 20% interrupts.CPU129.NMI:Non-maskable_interrupts
3375 ± 23% +112.2% 7163 ± 20% interrupts.CPU129.PMI:Performance_monitoring_interrupts
2570 ± 19% +131.1% 5940 ± 34% interrupts.CPU132.NMI:Non-maskable_interrupts
2570 ± 19% +131.1% 5940 ± 34% interrupts.CPU132.PMI:Performance_monitoring_interrupts
382.50 ± 68% -78.6% 82.00 ±136% interrupts.CPU15.RES:Rescheduling_interrupts
8363 ± 5% -33.8% 5539 ± 25% interrupts.CPU161.NMI:Non-maskable_interrupts
8363 ± 5% -33.8% 5539 ± 25% interrupts.CPU161.PMI:Performance_monitoring_interrupts
253.00 ± 15% -54.0% 116.50 ± 57% interrupts.CPU186.RES:Rescheduling_interrupts
249.50 ± 16% -64.7% 88.00 ± 64% interrupts.CPU2.RES:Rescheduling_interrupts
4404 ± 25% +89.1% 8327 ± 6% interrupts.CPU21.NMI:Non-maskable_interrupts
4404 ± 25% +89.1% 8327 ± 6% interrupts.CPU21.PMI:Performance_monitoring_interrupts
3516 ± 52% -52.8% 1659 ± 5% interrupts.CPU30.CAL:Function_call_interrupts
8180 ± 9% -42.4% 4710 ± 59% interrupts.CPU33.NMI:Non-maskable_interrupts
8180 ± 9% -42.4% 4710 ± 59% interrupts.CPU33.PMI:Performance_monitoring_interrupts
8601 ± 2% -39.4% 5208 ± 39% interrupts.CPU36.NMI:Non-maskable_interrupts
8601 ± 2% -39.4% 5208 ± 39% interrupts.CPU36.PMI:Performance_monitoring_interrupts
222.75 ± 31% -55.4% 99.25 ±109% interrupts.CPU36.RES:Rescheduling_interrupts
291.75 -40.1% 174.75 ± 38% interrupts.CPU4.RES:Rescheduling_interrupts
7518 ± 17% -30.1% 5251 ± 42% interrupts.CPU66.NMI:Non-maskable_interrupts
7518 ± 17% -30.1% 5251 ± 42% interrupts.CPU66.PMI:Performance_monitoring_interrupts
8034 ± 12% -41.4% 4711 ± 26% interrupts.CPU75.NMI:Non-maskable_interrupts
8034 ± 12% -41.4% 4711 ± 26% interrupts.CPU75.PMI:Performance_monitoring_interrupts
52.50 ± 70% +263.8% 191.00 ± 37% interrupts.CPU90.RES:Rescheduling_interrupts
63.25 ± 65% +243.1% 217.00 ± 34% interrupts.CPU98.RES:Rescheduling_interruptsDisclaimer:
Results have been estimated based on internal Intel analysis and are provided for informational purposes only. Any difference in system hardware or software design or configuration may affect actual performance.
Thanks,
Oliver Sang
#
# Automatically generated file; DO NOT EDIT. # Linux/x86_64 5.10.0-rc4 Kernel Configuration #CONFIG_CC_VERSION_TEXT="gcc-9 (Debian 9.3.0-15) 9.3.0" CONFIG_CC_IS_GCC=yCONFIG_GCC_VERSION=90300 CONFIG_LD_VERSION=235000000 CONFIG_CLANG_VERSION=0CONFIG_CC_CAN_LINK=y CONFIG_CC_CAN_LINK_STATIC=y CONFIG_CC_HAS_ASM_GOTO=y CONFIG_CC_HAS_ASM_INLINE=yCONFIG_IRQ_WORK=y CONFIG_BUILDTIME_TABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y
#
# General setup
#CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not setCONFIG_LOCALVERSION=""CONFIG_LOCALVERSION_AUTO=yCONFIG_BUILD_SALT=""CONFIG_HAVE_KERNEL_GZIP=yCONFIG_HAVE_KERNEL_BZIP2=yCONFIG_HAVE_KERNEL_LZMA=yCONFIG_HAVE_KERNEL_XZ=yCONFIG_HAVE_KERNEL_LZO=yCONFIG_HAVE_KERNEL_LZ4=yCONFIG_HAVE_KERNEL_ZSTD=yCONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
# CONFIG_KERNEL_ZSTD is not setCONFIG_DEFAULT_INIT=""CONFIG_DEFAULT_HOSTNAME="(none)"CONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=yCONFIG_POSIX_MQUEUE=yCONFIG_POSIX_MQUEUE_SYSCTL=y
# CONFIG_WATCH_QUEUE is not setCONFIG_CROSS_MEMORY_ATTACH=y
# CONFIG_USELIB is not setCONFIG_AUDIT=yCONFIG_HAVE_ARCH_AUDITSYSCALL=yCONFIG_AUDITSYSCALL=y
#
# IRQ subsystem
#CONFIG_GENERIC_IRQ_PROBE=yCONFIG_GENERIC_IRQ_SHOW=yCONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=yCONFIG_GENERIC_PENDING_IRQ=yCONFIG_GENERIC_IRQ_MIGRATION=yCONFIG_GENERIC_IRQ_INJECTION=yCONFIG_HARDIRQS_SW_RESEND=yCONFIG_IRQ_DOMAIN=yCONFIG_IRQ_DOMAIN_HIERARCHY=yCONFIG_GENERIC_MSI_IRQ=yCONFIG_GENERIC_MSI_IRQ_DOMAIN=yCONFIG_IRQ_MSI_IOMMU=yCONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=yCONFIG_GENERIC_IRQ_RESERVATION_MODE=yCONFIG_IRQ_FORCED_THREADING=yCONFIG_SPARSE_IRQ=y
# CONFIG_GENERIC_IRQ_DEBUGFS is not set
# end of IRQ subsystem
CONFIG_CLOCKSOURCE_WATCHDOG=yCONFIG_ARCH_CLOCKSOURCE_INIT=yCONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=yCONFIG_GENERIC_TIME_VSYSCALL=yCONFIG_GENERIC_CLOCKEVENTS=yCONFIG_GENERIC_CLOCKEVENTS_BROADCAST=yCONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=yCONFIG_GENERIC_CMOS_UPDATE=yCONFIG_HAVE_POSIX_CPU_TIMERS_TASK_WORK=yCONFIG_POSIX_CPU_TIMERS_TASK_WORK=y
#
# Timers subsystem
#CONFIG_TICK_ONESHOT=yCONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
# CONFIG_NO_HZ_IDLE is not setCONFIG_NO_HZ_FULL=yCONFIG_CONTEXT_TRACKING=y
# CONFIG_CONTEXT_TRACKING_FORCE is not setCONFIG_NO_HZ=yCONFIG_HIGH_RES_TIMERS=y
# end of Timers subsystem
# CONFIG_PREEMPT_NONE is not setCONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not setCONFIG_PREEMPT_COUNT=y
#
# CPU/Task time and stats accounting
#CONFIG_VIRT_CPU_ACCOUNTING=yCONFIG_VIRT_CPU_ACCOUNTING_GEN=yCONFIG_IRQ_TIME_ACCOUNTING=yCONFIG_HAVE_SCHED_AVG_IRQ=yCONFIG_BSD_PROCESS_ACCT=yCONFIG_BSD_PROCESS_ACCT_V3=yCONFIG_TASKSTATS=yCONFIG_TASK_DELAY_ACCT=yCONFIG_TASK_XACCT=yCONFIG_TASK_IO_ACCOUNTING=y
# CONFIG_PSI is not set
# end of CPU/Task time and stats accounting
CONFIG_CPU_ISOLATION=y
#
# RCU Subsystem
#CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not setCONFIG_SRCU=yCONFIG_TREE_SRCU=yCONFIG_TASKS_RCU_GENERIC=yCONFIG_TASKS_RCU=yCONFIG_TASKS_RUDE_RCU=yCONFIG_TASKS_TRACE_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_NEED_SEGCBLIST=yCONFIG_RCU_NOCB_CPU=y
# end of RCU Subsystem
CONFIG_BUILD_BIN2C=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=y
# CONFIG_IKHEADERS is not setCONFIG_LOG_BUF_SHIFT=20CONFIG_LOG_CPU_MAX_BUF_SHIFT=12CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
#
# Scheduler features
#
# CONFIG_UCLAMP_TASK is not set
# end of Scheduler features
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=yCONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=yCONFIG_CC_HAS_INT128=yCONFIG_ARCH_SUPPORTS_INT128=yCONFIG_NUMA_BALANCING=yCONFIG_NUMA_BALANCING_DEFAULT_ENABLED=yCONFIG_CGROUPS=yCONFIG_PAGE_COUNTER=yCONFIG_MEMCG=yCONFIG_MEMCG_SWAP=yCONFIG_MEMCG_KMEM=yCONFIG_BLK_CGROUP=yCONFIG_CGROUP_WRITEBACK=yCONFIG_CGROUP_SCHED=yCONFIG_FAIR_GROUP_SCHED=yCONFIG_CFS_BANDWIDTH=yCONFIG_RT_GROUP_SCHED=yCONFIG_CGROUP_PIDS=yCONFIG_CGROUP_RDMA=yCONFIG_CGROUP_FREEZER=yCONFIG_CGROUP_HUGETLB=yCONFIG_CPUSETS=yCONFIG_PROC_PID_CPUSET=yCONFIG_CGROUP_DEVICE=yCONFIG_CGROUP_CPUACCT=yCONFIG_CGROUP_PERF=yCONFIG_CGROUP_BPF=y
# CONFIG_CGROUP_DEBUG is not setCONFIG_SOCK_CGROUP_DATA=yCONFIG_NAMESPACES=yCONFIG_UTS_NS=yCONFIG_TIME_NS=yCONFIG_IPC_NS=yCONFIG_USER_NS=yCONFIG_PID_NS=yCONFIG_NET_NS=y
# CONFIG_CHECKPOINT_RESTORE is not setCONFIG_SCHED_AUTOGROUP=y
# CONFIG_SYSFS_DEPRECATED is not setCONFIG_RELAY=yCONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=yCONFIG_RD_LZMA=yCONFIG_RD_XZ=yCONFIG_RD_LZO=yCONFIG_RD_LZ4=yCONFIG_RD_ZSTD=y
# CONFIG_BOOT_CONFIG is not setCONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not setCONFIG_SYSCTL=yCONFIG_HAVE_UID16=yCONFIG_SYSCTL_EXCEPTION_TRACE=yCONFIG_HAVE_PCSPKR_PLATFORM=yCONFIG_BPF=y
# CONFIG_EXPERT is not setCONFIG_UID16=yCONFIG_MULTIUSER=yCONFIG_SGETMASK_SYSCALL=yCONFIG_SYSFS_SYSCALL=yCONFIG_FHANDLE=yCONFIG_POSIX_TIMERS=yCONFIG_PRINTK=yCONFIG_PRINTK_NMI=yCONFIG_BUG=yCONFIG_ELF_CORE=yCONFIG_PCSPKR_PLATFORM=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_FUTEX_PI=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_AIO=yCONFIG_IO_URING=yCONFIG_ADVISE_SYSCALLS=yCONFIG_HAVE_ARCH_USERFAULTFD_WP=yCONFIG_MEMBARRIER=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=yCONFIG_KALLSYMS_ABSOLUTE_PERCPU=yCONFIG_KALLSYMS_BASE_RELATIVE=y
# CONFIG_BPF_LSM is not setCONFIG_BPF_SYSCALL=yCONFIG_ARCH_WANT_DEFAULT_BPF_JIT=yCONFIG_BPF_JIT_ALWAYS_ON=yCONFIG_BPF_JIT_DEFAULT_ON=y
# CONFIG_BPF_PRELOAD is not setCONFIG_USERFAULTFD=yCONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=yCONFIG_RSEQ=y
# CONFIG_EMBEDDED is not setCONFIG_HAVE_PERF_EVENTS=y
#
# Kernel Performance Events And Counters
#CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
# end of Kernel Performance Events And Counters
CONFIG_VM_EVENT_COUNTERS=yCONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not setCONFIG_SLUB=yCONFIG_SLAB_MERGE_DEFAULT=yCONFIG_SLAB_FREELIST_RANDOM=y
# CONFIG_SLAB_FREELIST_HARDENED is not setCONFIG_SHUFFLE_PAGE_ALLOCATOR=yCONFIG_SLUB_CPU_PARTIAL=yCONFIG_SYSTEM_DATA_VERIFICATION=yCONFIG_PROFILING=yCONFIG_TRACEPOINTS=y
# end of General setup
CONFIG_64BIT=yCONFIG_X86_64=yCONFIG_X86=yCONFIG_INSTRUCTION_DECODER=yCONFIG_OUTPUT_FORMAT="elf64-x86-64"CONFIG_LOCKDEP_SUPPORT=yCONFIG_STACKTRACE_SUPPORT=yCONFIG_MMU=yCONFIG_ARCH_MMAP_RND_BITS_MIN=28CONFIG_ARCH_MMAP_RND_BITS_MAX=32CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16CONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_BUG=yCONFIG_GENERIC_BUG_RELATIVE_POINTERS=yCONFIG_ARCH_MAY_HAVE_PC_FDC=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_ARCH_HAS_CPU_RELAX=yCONFIG_ARCH_HAS_CACHE_LINE_SIZE=yCONFIG_ARCH_HAS_FILTER_PGPROT=yCONFIG_HAVE_SETUP_PER_CPU_AREA=yCONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=yCONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=yCONFIG_ARCH_HIBERNATION_POSSIBLE=yCONFIG_ARCH_SUSPEND_POSSIBLE=yCONFIG_ARCH_WANT_GENERAL_HUGETLB=yCONFIG_ZONE_DMA32=yCONFIG_AUDIT_ARCH=yCONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=yCONFIG_HAVE_INTEL_TXT=yCONFIG_X86_64_SMP=yCONFIG_ARCH_SUPPORTS_UPROBES=yCONFIG_FIX_EARLYCON_MEM=yCONFIG_DYNAMIC_PHYSICAL_MASK=yCONFIG_PGTABLE_LEVELS=5CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
#
# Processor type and features
#CONFIG_ZONE_DMA=yCONFIG_SMP=yCONFIG_X86_FEATURE_NAMES=yCONFIG_X86_X2APIC=yCONFIG_X86_MPPARSE=y
# CONFIG_GOLDFISH is not setCONFIG_RETPOLINE=yCONFIG_X86_CPU_RESCTRL=yCONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_NUMACHIP is not set
# CONFIG_X86_VSMP is not setCONFIG_X86_UV=y
# CONFIG_X86_GOLDFISH is not set
# CONFIG_X86_INTEL_MID is not setCONFIG_X86_INTEL_LPSS=yCONFIG_X86_AMD_PLATFORM_DEVICE=yCONFIG_IOSF_MBI=y
# CONFIG_IOSF_MBI_DEBUG is not setCONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_SCHED_OMIT_FRAME_POINTER is not setCONFIG_HYPERVISOR_GUEST=yCONFIG_PARAVIRT=y
# CONFIG_PARAVIRT_DEBUG is not setCONFIG_PARAVIRT_SPINLOCKS=yCONFIG_X86_HV_CALLBACK_VECTOR=yCONFIG_XEN=y
# CONFIG_XEN_PV is not setCONFIG_XEN_PVHVM=yCONFIG_XEN_PVHVM_SMP=yCONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
# CONFIG_XEN_PVH is not setCONFIG_KVM_GUEST=yCONFIG_ARCH_CPUIDLE_HALTPOLL=y
# CONFIG_PVH is not setCONFIG_PARAVIRT_TIME_ACCOUNTING=yCONFIG_PARAVIRT_CLOCK=y
# CONFIG_JAILHOUSE_GUEST is not set
# CONFIG_ACRN_GUEST is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not setCONFIG_GENERIC_CPU=yCONFIG_X86_INTERNODE_CACHE_SHIFT=6CONFIG_X86_L1_CACHE_SHIFT=6CONFIG_X86_TSC=yCONFIG_X86_CMPXCHG64=yCONFIG_X86_CMOV=yCONFIG_X86_MINIMUM_CPU_FAMILY=64CONFIG_X86_DEBUGCTLMSR=yCONFIG_IA32_FEAT_CTL=yCONFIG_X86_VMX_FEATURE_NAMES=yCONFIG_CPU_SUP_INTEL=yCONFIG_CPU_SUP_AMD=yCONFIG_CPU_SUP_HYGON=yCONFIG_CPU_SUP_CENTAUR=yCONFIG_CPU_SUP_ZHAOXIN=yCONFIG_HPET_TIMER=yCONFIG_HPET_EMULATE_RTC=yCONFIG_DMI=y
# CONFIG_GART_IOMMU is not setCONFIG_MAXSMP=yCONFIG_NR_CPUS_RANGE_BEGIN=8192CONFIG_NR_CPUS_RANGE_END=8192CONFIG_NR_CPUS_DEFAULT=8192CONFIG_NR_CPUS=8192CONFIG_SCHED_SMT=yCONFIG_SCHED_MC=yCONFIG_SCHED_MC_PRIO=yCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=yCONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=yCONFIG_X86_MCE=yCONFIG_X86_MCELOG_LEGACY=yCONFIG_X86_MCE_INTEL=yCONFIG_X86_MCE_AMD=yCONFIG_X86_MCE_THRESHOLD=yCONFIG_X86_MCE_INJECT=mCONFIG_X86_THERMAL_VECTOR=y
#
# Performance monitoring
#CONFIG_PERF_EVENTS_INTEL_UNCORE=mCONFIG_PERF_EVENTS_INTEL_RAPL=mCONFIG_PERF_EVENTS_INTEL_CSTATE=mCONFIG_PERF_EVENTS_AMD_POWER=m
# end of Performance monitoring
CONFIG_X86_16BIT=yCONFIG_X86_ESPFIX64=y CONFIG_X86_VSYSCALL_EMULATION=y CONFIG_X86_IOPL_IOPERM=yCONFIG_I8K=mCONFIG_MICROCODE=yCONFIG_MICROCODE_INTEL=yCONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=yCONFIG_X86_CPUID=yCONFIG_X86_5LEVEL=yCONFIG_X86_DIRECT_GBPAGES=y
# CONFIG_X86_CPA_STATISTICS is not set CONFIG_AMD_MEM_ENCRYPT=y
# CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is not set CONFIG_NUMA=yCONFIG_AMD_NUMA=yCONFIG_X86_64_ACPI_NUMA=yCONFIG_NUMA_EMU=yCONFIG_NODES_SHIFT=10 CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y
# CONFIG_ARCH_MEMORY_PROBE is not set CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_X86_PMEM_LEGACY_DEVICE=y CONFIG_X86_PMEM_LEGACY=m CONFIG_X86_CHECK_BIOS_CORRUPTION=y
# CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set CONFIG_X86_RESERVE_LOW=64CONFIG_MTRR=yCONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=yCONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_ARCH_RANDOM=yCONFIG_X86_SMAP=yCONFIG_X86_UMIP=y CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS=y CONFIG_X86_INTEL_TSX_MODE_OFF=y
# CONFIG_X86_INTEL_TSX_MODE_ON is not set
# CONFIG_X86_INTEL_TSX_MODE_AUTO is not set CONFIG_EFI=yCONFIG_EFI_STUB=yCONFIG_EFI_MIXED=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not setCONFIG_HZ_1000=yCONFIG_HZ=1000CONFIG_SCHED_HRTICK=yCONFIG_KEXEC=yCONFIG_KEXEC_FILE=y CONFIG_ARCH_HAS_KEXEC_PURGATORY=y
# CONFIG_KEXEC_SIG is not set CONFIG_CRASH_DUMP=yCONFIG_KEXEC_JUMP=y CONFIG_PHYSICAL_START=0x1000000 CONFIG_RELOCATABLE=yCONFIG_RANDOMIZE_BASE=yCONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_DYNAMIC_MEMORY_LAYOUT=y CONFIG_RANDOMIZE_MEMORY=y CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING=0xa CONFIG_HOTPLUG_CPU=y CONFIG_BOOTPARAM_HOTPLUG_CPU0=y
# CONFIG_DEBUG_HOTPLUG_CPU0 is not set
# CONFIG_COMPAT_VDSO is not set CONFIG_LEGACY_VSYSCALL_EMULATE=y
# CONFIG_LEGACY_VSYSCALL_XONLY is not set
# CONFIG_LEGACY_VSYSCALL_NONE is not set
# CONFIG_CMDLINE_BOOL is not set CONFIG_MODIFY_LDT_SYSCALL=y CONFIG_HAVE_LIVEPATCH=yCONFIG_LIVEPATCH=y
# end of Processor type and features
CONFIG_ARCH_HAS_ADD_PAGES=yCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=yCONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=yCONFIG_USE_PERCPU_NUMA_NODE_ID=yCONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=yCONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=yCONFIG_ARCH_ENABLE_THP_MIGRATION=y
#
# Power management and ACPI options
#CONFIG_ARCH_HIBERNATION_HEADER=yCONFIG_SUSPEND=yCONFIG_SUSPEND_FREEZER=yCONFIG_HIBERNATE_CALLBACKS=yCONFIG_HIBERNATION=yCONFIG_HIBERNATION_SNAPSHOT_DEV=yCONFIG_PM_STD_PARTITION=""CONFIG_PM_SLEEP=yCONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not setCONFIG_PM=yCONFIG_PM_DEBUG=y
# CONFIG_PM_ADVANCED_DEBUG is not set
# CONFIG_PM_TEST_SUSPEND is not setCONFIG_PM_SLEEP_DEBUG=y
# CONFIG_PM_TRACE_RTC is not setCONFIG_PM_CLK=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
# CONFIG_ENERGY_MODEL is not setCONFIG_ARCH_SUPPORTS_ACPI=yCONFIG_ACPI=yCONFIG_ACPI_LEGACY_TABLES_LOOKUP=yCONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=yCONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y
# CONFIG_ACPI_DEBUGGER is not setCONFIG_ACPI_SPCR_TABLE=yCONFIG_ACPI_LPIT=yCONFIG_ACPI_SLEEP=yCONFIG_ACPI_REV_OVERRIDE_POSSIBLE=yCONFIG_ACPI_EC_DEBUGFS=mCONFIG_ACPI_AC=yCONFIG_ACPI_BATTERY=yCONFIG_ACPI_BUTTON=yCONFIG_ACPI_VIDEO=mCONFIG_ACPI_FAN=yCONFIG_ACPI_TAD=mCONFIG_ACPI_DOCK=yCONFIG_ACPI_CPU_FREQ_PSS=yCONFIG_ACPI_PROCESSOR_CSTATE=yCONFIG_ACPI_PROCESSOR_IDLE=yCONFIG_ACPI_CPPC_LIB=yCONFIG_ACPI_PROCESSOR=yCONFIG_ACPI_IPMI=mCONFIG_ACPI_HOTPLUG_CPU=yCONFIG_ACPI_PROCESSOR_AGGREGATOR=mCONFIG_ACPI_THERMAL=yCONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=yCONFIG_ACPI_TABLE_UPGRADE=y
# CONFIG_ACPI_DEBUG is not setCONFIG_ACPI_PCI_SLOT=yCONFIG_ACPI_CONTAINER=yCONFIG_ACPI_HOTPLUG_MEMORY=yCONFIG_ACPI_HOTPLUG_IOAPIC=yCONFIG_ACPI_SBS=mCONFIG_ACPI_HED=y
# CONFIG_ACPI_CUSTOM_METHOD is not setCONFIG_ACPI_BGRT=yCONFIG_ACPI_NFIT=m
# CONFIG_NFIT_SECURITY_DEBUG is not setCONFIG_ACPI_NUMA=y
# CONFIG_ACPI_HMAT is not setCONFIG_HAVE_ACPI_APEI=yCONFIG_HAVE_ACPI_APEI_NMI=yCONFIG_ACPI_APEI=yCONFIG_ACPI_APEI_GHES=yCONFIG_ACPI_APEI_PCIEAER=yCONFIG_ACPI_APEI_MEMORY_FAILURE=yCONFIG_ACPI_APEI_EINJ=mCONFIG_ACPI_APEI_ERST_DEBUG=y
# CONFIG_ACPI_DPTF is not setCONFIG_ACPI_WATCHDOG=yCONFIG_ACPI_EXTLOG=mCONFIG_ACPI_ADXL=y
# CONFIG_ACPI_CONFIGFS is not setCONFIG_PMIC_OPREGION=yCONFIG_X86_PM_TIMER=yCONFIG_SFI=y
#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_ATTR_SET=y CONFIG_CPU_FREQ_GOV_COMMON=y CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
#
# CPU frequency scaling drivers
#CONFIG_X86_INTEL_PSTATE=y
# CONFIG_X86_PCC_CPUFREQ is not setCONFIG_X86_ACPI_CPUFREQ=mCONFIG_X86_ACPI_CPUFREQ_CPB=yCONFIG_X86_POWERNOW_K8=mCONFIG_X86_AMD_FREQ_SENSITIVITY=m
# CONFIG_X86_SPEEDSTEP_CENTRINO is not setCONFIG_X86_P4_CLOCKMOD=m
#
# shared options # CONFIG_X86_SPEEDSTEP_LIB=m # end of CPU Frequency scaling
#
# CPU Idle
#CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_GOV_LADDER is not setCONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_CPU_IDLE_GOV_TEO is not set
# CONFIG_CPU_IDLE_GOV_HALTPOLL is not setCONFIG_HALTPOLL_CPUIDLE=y
# end of CPU Idle
CONFIG_INTEL_IDLE=y
# end of Power management and ACPI options
#
# Bus options (PCI etc.)
#CONFIG_PCI_DIRECT=yCONFIG_PCI_MMCONFIG=yCONFIG_PCI_XEN=yCONFIG_MMCONF_FAM10H=yCONFIG_ISA_DMA_API=yCONFIG_AMD_NB=y
# CONFIG_X86_SYSFB is not set
# end of Bus options (PCI etc.)
#
# Binary Emulations
#CONFIG_IA32_EMULATION=y
# CONFIG_X86_X32 is not setCONFIG_COMPAT_32=yCONFIG_COMPAT=yCONFIG_COMPAT_FOR_U64_ALIGNMENT=yCONFIG_SYSVIPC_COMPAT=y
# end of Binary Emulations
#
# Firmware Drivers
#CONFIG_EDD=m
# CONFIG_EDD_OFF is not setCONFIG_FIRMWARE_MEMMAP=yCONFIG_DMIID=yCONFIG_DMI_SYSFS=yCONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y
# CONFIG_ISCSI_IBFT is not setCONFIG_FW_CFG_SYSFS=y
# CONFIG_FW_CFG_SYSFS_CMDLINE is not set
# CONFIG_GOOGLE_FIRMWARE is not set
#
# EFI (Extensible Firmware Interface) Support
#CONFIG_EFI_VARS=yCONFIG_EFI_ESRT=yCONFIG_EFI_VARS_PSTORE=yCONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=yCONFIG_EFI_RUNTIME_MAP=y
# CONFIG_EFI_FAKE_MEMMAP is not setCONFIG_EFI_RUNTIME_WRAPPERS=yCONFIG_EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER=y
# CONFIG_EFI_BOOTLOADER_CONTROL is not set
# CONFIG_EFI_CAPSULE_LOADER is not set
# CONFIG_EFI_TEST is not setCONFIG_APPLE_PROPERTIES=y
# CONFIG_RESET_ATTACK_MITIGATION is not set
# CONFIG_EFI_RCI2_TABLE is not set
# CONFIG_EFI_DISABLE_PCI_DMA is not set
# end of EFI (Extensible Firmware Interface) Support
CONFIG_UEFI_CPER=yCONFIG_UEFI_CPER_X86=yCONFIG_EFI_DEV_PATH_PARSER=yCONFIG_EFI_EARLYCON=yCONFIG_EFI_CUSTOM_SSDT_OVERLAYS=y
#
# Tegra firmware driver
#
# end of Tegra firmware driver # end of Firmware Drivers
CONFIG_HAVE_KVM=yCONFIG_HAVE_KVM_IRQCHIP=yCONFIG_HAVE_KVM_IRQFD=yCONFIG_HAVE_KVM_IRQ_ROUTING=yCONFIG_HAVE_KVM_EVENTFD=yCONFIG_KVM_MMIO=yCONFIG_KVM_ASYNC_PF=yCONFIG_HAVE_KVM_MSI=yCONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=yCONFIG_KVM_VFIO=yCONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=yCONFIG_KVM_COMPAT=yCONFIG_HAVE_KVM_IRQ_BYPASS=yCONFIG_HAVE_KVM_NO_POLL=yCONFIG_KVM_XFER_TO_GUEST_WORK=yCONFIG_VIRTUALIZATION=yCONFIG_KVM=mCONFIG_KVM_INTEL=m
# CONFIG_KVM_AMD is not setCONFIG_KVM_MMU_AUDIT=yCONFIG_AS_AVX512=yCONFIG_AS_SHA1_NI=yCONFIG_AS_SHA256_NI=yCONFIG_AS_TPAUSE=y
#
# General architecture-dependent options
#CONFIG_CRASH_CORE=yCONFIG_KEXEC_CORE=yCONFIG_HOTPLUG_SMT=yCONFIG_GENERIC_ENTRY=yCONFIG_OPROFILE=mCONFIG_OPROFILE_EVENT_MULTIPLEX=yCONFIG_HAVE_OPROFILE=yCONFIG_OPROFILE_NMI_TIMER=yCONFIG_KPROBES=yCONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not set
# CONFIG_STATIC_CALL_SELFTEST is not setCONFIG_OPTPROBES=yCONFIG_KPROBES_ON_FTRACE=yCONFIG_UPROBES=yCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_ARCH_USE_BUILTIN_BSWAP=yCONFIG_KRETPROBES=yCONFIG_USER_RETURN_NOTIFIER=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_OPTPROBES=yCONFIG_HAVE_KPROBES_ON_FTRACE=yCONFIG_HAVE_FUNCTION_ERROR_INJECTION=yCONFIG_HAVE_NMI=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_DMA_CONTIGUOUS=yCONFIG_GENERIC_SMP_IDLE_THREAD=yCONFIG_ARCH_HAS_FORTIFY_SOURCE=yCONFIG_ARCH_HAS_SET_MEMORY=yCONFIG_ARCH_HAS_SET_DIRECT_MAP=yCONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=yCONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT=yCONFIG_HAVE_ASM_MODVERSIONS=yCONFIG_HAVE_REGS_AND_STACK_ACCESS_API=yCONFIG_HAVE_RSEQ=yCONFIG_HAVE_FUNCTION_ARG_ACCESS_API=yCONFIG_HAVE_HW_BREAKPOINT=yCONFIG_HAVE_MIXED_BREAKPOINTS_REGS=yCONFIG_HAVE_USER_RETURN_NOTIFIER=yCONFIG_HAVE_PERF_EVENTS_NMI=yCONFIG_HAVE_HARDLOCKUP_DETECTOR_PERF=yCONFIG_HAVE_PERF_REGS=yCONFIG_HAVE_PERF_USER_STACK_DUMP=yCONFIG_HAVE_ARCH_JUMP_LABEL=yCONFIG_HAVE_ARCH_JUMP_LABEL_RELATIVE=yCONFIG_MMU_GATHER_TABLE_FREE=yCONFIG_MMU_GATHER_RCU_TABLE_FREE=yCONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=yCONFIG_HAVE_ALIGNED_STRUCT_PAGE=yCONFIG_HAVE_CMPXCHG_LOCAL=yCONFIG_HAVE_CMPXCHG_DOUBLE=yCONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=yCONFIG_ARCH_WANT_OLD_COMPAT_IPC=yCONFIG_HAVE_ARCH_SECCOMP=yCONFIG_HAVE_ARCH_SECCOMP_FILTER=yCONFIG_SECCOMP=yCONFIG_SECCOMP_FILTER=yCONFIG_HAVE_ARCH_STACKLEAK=yCONFIG_HAVE_STACKPROTECTOR=yCONFIG_STACKPROTECTOR=yCONFIG_STACKPROTECTOR_STRONG=yCONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=yCONFIG_HAVE_CONTEXT_TRACKING=yCONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=yCONFIG_HAVE_IRQ_TIME_ACCOUNTING=yCONFIG_HAVE_MOVE_PMD=yCONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=yCONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD=yCONFIG_HAVE_ARCH_HUGE_VMAP=yCONFIG_ARCH_WANT_HUGE_PMD_SHARE=yCONFIG_HAVE_ARCH_SOFT_DIRTY=yCONFIG_HAVE_MOD_ARCH_SPECIFIC=yCONFIG_MODULES_USE_ELF_RELA=yCONFIG_ARCH_HAS_ELF_RANDOMIZE=yCONFIG_HAVE_ARCH_MMAP_RND_BITS=yCONFIG_HAVE_EXIT_THREAD=yCONFIG_ARCH_MMAP_RND_BITS=28CONFIG_HAVE_ARCH_MMAP_RND_COMPAT_BITS=yCONFIG_ARCH_MMAP_RND_COMPAT_BITS=8CONFIG_HAVE_ARCH_COMPAT_MMAP_BASES=yCONFIG_HAVE_STACK_VALIDATION=yCONFIG_HAVE_RELIABLE_STACKTRACE=yCONFIG_OLD_SIGSUSPEND3=yCONFIG_COMPAT_OLD_SIGACTION=yCONFIG_COMPAT_32BIT_TIME=yCONFIG_HAVE_ARCH_VMAP_STACK=yCONFIG_VMAP_STACK=yCONFIG_ARCH_HAS_STRICT_KERNEL_RWX=yCONFIG_STRICT_KERNEL_RWX=yCONFIG_ARCH_HAS_STRICT_MODULE_RWX=yCONFIG_STRICT_MODULE_RWX=yCONFIG_HAVE_ARCH_PREL32_RELOCATIONS=yCONFIG_ARCH_USE_MEMREMAP_PROT=y
# CONFIG_LOCK_EVENT_COUNTS is not setCONFIG_ARCH_HAS_MEM_ENCRYPT=yCONFIG_HAVE_STATIC_CALL=yCONFIG_HAVE_STATIC_CALL_INLINE=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not setCONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# end of GCOV-based kernel profiling
CONFIG_HAVE_GCC_PLUGINS=y
# end of General architecture-dependent options
CONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0CONFIG_MODULE_SIG_FORMAT=yCONFIG_MODULES=yCONFIG_MODULE_FORCE_LOAD=yCONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set CONFIG_MODULE_SIG_ALL=y
# CONFIG_MODULE_SIG_SHA1 is not set
# CONFIG_MODULE_SIG_SHA224 is not set CONFIG_MODULE_SIG_SHA256=y
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not set CONFIG_MODULE_SIG_HASH="sha256"
# CONFIG_MODULE_COMPRESS is not set
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set # CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_TRIM_UNUSED_KSYMS is not set CONFIG_MODULES_TREE_LOOKUP=yCONFIG_BLOCK=yCONFIG_BLK_SCSI_REQUEST=y CONFIG_BLK_CGROUP_RWSTAT=yCONFIG_BLK_DEV_BSG=yCONFIG_BLK_DEV_BSGLIB=y CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLK_DEV_INTEGRITY_T10=m CONFIG_BLK_DEV_ZONED=y CONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_DEV_THROTTLING_LOW is not set
# CONFIG_BLK_CMDLINE_PARSER is not set CONFIG_BLK_WBT=y
# CONFIG_BLK_CGROUP_IOLATENCY is not set
# CONFIG_BLK_CGROUP_IOCOST is not set CONFIG_BLK_WBT_MQ=yCONFIG_BLK_DEBUG_FS=yCONFIG_BLK_DEBUG_FS_ZONED=y
# CONFIG_BLK_SED_OPAL is not set
# CONFIG_BLK_INLINE_ENCRYPTION is not set
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_AIX_PARTITION is not setCONFIG_OSF_PARTITION=yCONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not setCONFIG_MAC_PARTITION=yCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not setCONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not setCONFIG_SUN_PARTITION=yCONFIG_KARMA_PARTITION=yCONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
# CONFIG_CMDLINE_PARTITION is not set
# end of Partition Types
CONFIG_BLOCK_COMPAT=yCONFIG_BLK_MQ_PCI=yCONFIG_BLK_MQ_VIRTIO=yCONFIG_BLK_MQ_RDMA=yCONFIG_BLK_PM=y
#
# IO Schedulers
#CONFIG_MQ_IOSCHED_DEADLINE=yCONFIG_MQ_IOSCHED_KYBER=yCONFIG_IOSCHED_BFQ=yCONFIG_BFQ_GROUP_IOSCHED=y
# CONFIG_BFQ_CGROUP_DEBUG is not set
# end of IO Schedulers
CONFIG_PREEMPT_NOTIFIERS=yCONFIG_PADATA=yCONFIG_ASN1=yCONFIG_INLINE_SPIN_UNLOCK_IRQ=yCONFIG_INLINE_READ_UNLOCK=yCONFIG_INLINE_READ_UNLOCK_IRQ=yCONFIG_INLINE_WRITE_UNLOCK=yCONFIG_INLINE_WRITE_UNLOCK_IRQ=yCONFIG_ARCH_SUPPORTS_ATOMIC_RMW=yCONFIG_MUTEX_SPIN_ON_OWNER=yCONFIG_RWSEM_SPIN_ON_OWNER=yCONFIG_LOCK_SPIN_ON_OWNER=yCONFIG_ARCH_USE_QUEUED_SPINLOCKS=yCONFIG_QUEUED_SPINLOCKS=yCONFIG_ARCH_USE_QUEUED_RWLOCKS=yCONFIG_QUEUED_RWLOCKS=yCONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE=yCONFIG_ARCH_HAS_SYNC_CORE_BEFORE_USERMODE=yCONFIG_ARCH_HAS_SYSCALL_WRAPPER=yCONFIG_FREEZER=y
#
# Executable file formats
#CONFIG_BINFMT_ELF=yCONFIG_COMPAT_BINFMT_ELF=yCONFIG_ELFCORE=yCONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=yCONFIG_BINFMT_SCRIPT=yCONFIG_BINFMT_MISC=mCONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#CONFIG_SELECT_MEMORY_MODEL=y CONFIG_SPARSEMEM_MANUAL=yCONFIG_SPARSEMEM=y CONFIG_NEED_MULTIPLE_NODES=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y CONFIG_HAVE_FAST_GUP=y CONFIG_NUMA_KEEP_MEMINFO=y CONFIG_MEMORY_ISOLATION=y CONFIG_HAVE_BOOTMEM_INFO_NODE=y CONFIG_MEMORY_HOTPLUG=y CONFIG_MEMORY_HOTPLUG_SPARSE=y
# CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is not set CONFIG_MEMORY_HOTREMOVE=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_MEMORY_BALLOON=y CONFIG_BALLOON_COMPACTION=y CONFIG_COMPACTION=yCONFIG_PAGE_REPORTING=yCONFIG_MIGRATION=yCONFIG_CONTIG_ALLOC=y CONFIG_PHYS_ADDR_T_64BIT=yCONFIG_BOUNCE=yCONFIG_VIRT_TO_BUS=yCONFIG_MMU_NOTIFIER=yCONFIG_KSM=y CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y CONFIG_MEMORY_FAILURE=y CONFIG_HWPOISON_INJECT=m CONFIG_TRANSPARENT_HUGEPAGE=y CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set CONFIG_ARCH_WANTS_THP_SWAP=y CONFIG_THP_SWAP=yCONFIG_CLEANCACHE=yCONFIG_FRONTSWAP=yCONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not set CONFIG_CMA_AREAS=19CONFIG_ZSWAP=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_DEFLATE is not set CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZO=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_842 is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4 is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4HC is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_ZSTD is not set CONFIG_ZSWAP_COMPRESSOR_DEFAULT="lzo" CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD=y
# CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD is not set # CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC is not set CONFIG_ZSWAP_ZPOOL_DEFAULT="zbud"
# CONFIG_ZSWAP_DEFAULT_ON is not set CONFIG_ZPOOL=yCONFIG_ZBUD=y
# CONFIG_Z3FOLD is not setCONFIG_ZSMALLOC=y
# CONFIG_ZSMALLOC_PGTABLE_MAPPING is not set CONFIG_ZSMALLOC_STAT=y CONFIG_GENERIC_EARLY_IOREMAP=y CONFIG_DEFERRED_STRUCT_PAGE_INIT=y CONFIG_IDLE_PAGE_TRACKING=y CONFIG_ARCH_HAS_PTE_DEVMAP=y CONFIG_ZONE_DEVICE=y CONFIG_DEV_PAGEMAP_OPS=yCONFIG_HMM_MIRROR=yCONFIG_DEVICE_PRIVATE=yCONFIG_VMAP_PFN=yCONFIG_FRAME_VECTOR=y CONFIG_ARCH_USES_HIGH_VMA_FLAGS=y CONFIG_ARCH_HAS_PKEYS=y
# CONFIG_PERCPU_STATS is not set
# CONFIG_GUP_BENCHMARK is not set
# CONFIG_READ_ONLY_THP_FOR_FS is not set CONFIG_ARCH_HAS_PTE_SPECIAL=y CONFIG_MAPPING_DIRTY_HELPERS=y
# end of Memory Management options
CONFIG_NET=yCONFIG_COMPAT_NETLINK_MESSAGES=yCONFIG_NET_INGRESS=yCONFIG_NET_EGRESS=yCONFIG_SKB_EXTENSIONS=y
#
# Networking options
#CONFIG_PACKET=yCONFIG_PACKET_DIAG=mCONFIG_UNIX=yCONFIG_UNIX_SCM=yCONFIG_UNIX_DIAG=mCONFIG_TLS=mCONFIG_TLS_DEVICE=y
# CONFIG_TLS_TOE is not setCONFIG_XFRM=yCONFIG_XFRM_OFFLOAD=yCONFIG_XFRM_ALGO=yCONFIG_XFRM_USER=y
# CONFIG_XFRM_USER_COMPAT is not set
# CONFIG_XFRM_INTERFACE is not setCONFIG_XFRM_SUB_POLICY=yCONFIG_XFRM_MIGRATE=yCONFIG_XFRM_STATISTICS=yCONFIG_XFRM_AH=mCONFIG_XFRM_ESP=mCONFIG_XFRM_IPCOMP=mCONFIG_NET_KEY=mCONFIG_NET_KEY_MIGRATE=y
# CONFIG_SMC is not setCONFIG_XDP_SOCKETS=y
# CONFIG_XDP_SOCKETS_DIAG is not setCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_ADVANCED_ROUTER=yCONFIG_IP_FIB_TRIE_STATS=yCONFIG_IP_MULTIPLE_TABLES=yCONFIG_IP_ROUTE_MULTIPATH=yCONFIG_IP_ROUTE_VERBOSE=yCONFIG_IP_ROUTE_CLASSID=yCONFIG_IP_PNP=yCONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not setCONFIG_NET_IPIP=mCONFIG_NET_IPGRE_DEMUX=mCONFIG_NET_IP_TUNNEL=mCONFIG_NET_IPGRE=mCONFIG_NET_IPGRE_BROADCAST=yCONFIG_IP_MROUTE_COMMON=yCONFIG_IP_MROUTE=yCONFIG_IP_MROUTE_MULTIPLE_TABLES=yCONFIG_IP_PIMSM_V1=yCONFIG_IP_PIMSM_V2=yCONFIG_SYN_COOKIES=yCONFIG_NET_IPVTI=mCONFIG_NET_UDP_TUNNEL=m
# CONFIG_NET_FOU is not set
# CONFIG_NET_FOU_IP_TUNNELS is not setCONFIG_INET_AH=mCONFIG_INET_ESP=mCONFIG_INET_ESP_OFFLOAD=m
# CONFIG_INET_ESPINTCP is not setCONFIG_INET_IPCOMP=mCONFIG_INET_XFRM_TUNNEL=mCONFIG_INET_TUNNEL=mCONFIG_INET_DIAG=mCONFIG_INET_TCP_DIAG=mCONFIG_INET_UDP_DIAG=mCONFIG_INET_RAW_DIAG=m
# CONFIG_INET_DIAG_DESTROY is not setCONFIG_TCP_CONG_ADVANCED=yCONFIG_TCP_CONG_BIC=mCONFIG_TCP_CONG_CUBIC=yCONFIG_TCP_CONG_WESTWOOD=mCONFIG_TCP_CONG_HTCP=mCONFIG_TCP_CONG_HSTCP=mCONFIG_TCP_CONG_HYBLA=mCONFIG_TCP_CONG_VEGAS=mCONFIG_TCP_CONG_NV=mCONFIG_TCP_CONG_SCALABLE=mCONFIG_TCP_CONG_LP=mCONFIG_TCP_CONG_VENO=mCONFIG_TCP_CONG_YEAH=mCONFIG_TCP_CONG_ILLINOIS=mCONFIG_TCP_CONG_DCTCP=m
# CONFIG_TCP_CONG_CDG is not setCONFIG_TCP_CONG_BBR=mCONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not setCONFIG_DEFAULT_TCP_CONG="cubic"CONFIG_TCP_MD5SIG=yCONFIG_IPV6=yCONFIG_IPV6_ROUTER_PREF=yCONFIG_IPV6_ROUTE_INFO=yCONFIG_IPV6_OPTIMISTIC_DAD=yCONFIG_INET6_AH=mCONFIG_INET6_ESP=mCONFIG_INET6_ESP_OFFLOAD=m
# CONFIG_INET6_ESPINTCP is not setCONFIG_INET6_IPCOMP=mCONFIG_IPV6_MIP6=m
# CONFIG_IPV6_ILA is not setCONFIG_INET6_XFRM_TUNNEL=mCONFIG_INET6_TUNNEL=mCONFIG_IPV6_VTI=mCONFIG_IPV6_SIT=mCONFIG_IPV6_SIT_6RD=yCONFIG_IPV6_NDISC_NODETYPE=yCONFIG_IPV6_TUNNEL=mCONFIG_IPV6_GRE=mCONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not setCONFIG_IPV6_MROUTE=yCONFIG_IPV6_MROUTE_MULTIPLE_TABLES=yCONFIG_IPV6_PIMSM_V2=y
# CONFIG_IPV6_SEG6_LWTUNNEL is not set
# CONFIG_IPV6_SEG6_HMAC is not set
# CONFIG_IPV6_RPL_LWTUNNEL is not setCONFIG_NETLABEL=y
# CONFIG_MPTCP is not setCONFIG_NETWORK_SECMARK=yCONFIG_NET_PTP_CLASSIFY=yCONFIG_NETWORK_PHY_TIMESTAMPING=yCONFIG_NETFILTER=yCONFIG_NETFILTER_ADVANCED=yCONFIG_BRIDGE_NETFILTER=m
#
# Core Netfilter Configuration
#CONFIG_NETFILTER_INGRESS=yCONFIG_NETFILTER_NETLINK=mCONFIG_NETFILTER_FAMILY_BRIDGE=yCONFIG_NETFILTER_FAMILY_ARP=y
# CONFIG_NETFILTER_NETLINK_ACCT is not setCONFIG_NETFILTER_NETLINK_QUEUE=mCONFIG_NETFILTER_NETLINK_LOG=mCONFIG_NETFILTER_NETLINK_OSF=mCONFIG_NF_CONNTRACK=mCONFIG_NF_LOG_COMMON=mCONFIG_NF_LOG_NETDEV=mCONFIG_NETFILTER_CONNCOUNT=mCONFIG_NF_CONNTRACK_MARK=yCONFIG_NF_CONNTRACK_SECMARK=yCONFIG_NF_CONNTRACK_ZONES=yCONFIG_NF_CONNTRACK_PROCFS=yCONFIG_NF_CONNTRACK_EVENTS=yCONFIG_NF_CONNTRACK_TIMEOUT=yCONFIG_NF_CONNTRACK_TIMESTAMP=yCONFIG_NF_CONNTRACK_LABELS=yCONFIG_NF_CT_PROTO_DCCP=yCONFIG_NF_CT_PROTO_GRE=yCONFIG_NF_CT_PROTO_SCTP=yCONFIG_NF_CT_PROTO_UDPLITE=yCONFIG_NF_CONNTRACK_AMANDA=mCONFIG_NF_CONNTRACK_FTP=mCONFIG_NF_CONNTRACK_H323=mCONFIG_NF_CONNTRACK_IRC=mCONFIG_NF_CONNTRACK_BROADCAST=mCONFIG_NF_CONNTRACK_NETBIOS_NS=mCONFIG_NF_CONNTRACK_SNMP=mCONFIG_NF_CONNTRACK_PPTP=mCONFIG_NF_CONNTRACK_SANE=mCONFIG_NF_CONNTRACK_SIP=mCONFIG_NF_CONNTRACK_TFTP=mCONFIG_NF_CT_NETLINK=mCONFIG_NF_CT_NETLINK_TIMEOUT=mCONFIG_NF_CT_NETLINK_HELPER=mCONFIG_NETFILTER_NETLINK_GLUE_CT=yCONFIG_NF_NAT=mCONFIG_NF_NAT_AMANDA=mCONFIG_NF_NAT_FTP=mCONFIG_NF_NAT_IRC=mCONFIG_NF_NAT_SIP=mCONFIG_NF_NAT_TFTP=mCONFIG_NF_NAT_REDIRECT=yCONFIG_NF_NAT_MASQUERADE=yCONFIG_NETFILTER_SYNPROXY=mCONFIG_NF_TABLES=mCONFIG_NF_TABLES_INET=yCONFIG_NF_TABLES_NETDEV=yCONFIG_NFT_NUMGEN=mCONFIG_NFT_CT=mCONFIG_NFT_COUNTER=mCONFIG_NFT_CONNLIMIT=mCONFIG_NFT_LOG=mCONFIG_NFT_LIMIT=mCONFIG_NFT_MASQ=mCONFIG_NFT_REDIR=mCONFIG_NFT_NAT=m
# CONFIG_NFT_TUNNEL is not setCONFIG_NFT_OBJREF=mCONFIG_NFT_QUEUE=mCONFIG_NFT_QUOTA=mCONFIG_NFT_REJECT=mCONFIG_NFT_REJECT_INET=mCONFIG_NFT_COMPAT=mCONFIG_NFT_HASH=mCONFIG_NFT_FIB=mCONFIG_NFT_FIB_INET=m
# CONFIG_NFT_XFRM is not setCONFIG_NFT_SOCKET=m
# CONFIG_NFT_OSF is not set
# CONFIG_NFT_TPROXY is not set
# CONFIG_NFT_SYNPROXY is not setCONFIG_NF_DUP_NETDEV=mCONFIG_NFT_DUP_NETDEV=mCONFIG_NFT_FWD_NETDEV=mCONFIG_NFT_FIB_NETDEV=m
# CONFIG_NF_FLOW_TABLE is not setCONFIG_NETFILTER_XTABLES=y
#
# Xtables combined modules
#CONFIG_NETFILTER_XT_MARK=mCONFIG_NETFILTER_XT_CONNMARK=mCONFIG_NETFILTER_XT_SET=m
#
# Xtables targets
#CONFIG_NETFILTER_XT_TARGET_AUDIT=mCONFIG_NETFILTER_XT_TARGET_CHECKSUM=mCONFIG_NETFILTER_XT_TARGET_CLASSIFY=mCONFIG_NETFILTER_XT_TARGET_CONNMARK=mCONFIG_NETFILTER_XT_TARGET_CONNSECMARK=mCONFIG_NETFILTER_XT_TARGET_CT=mCONFIG_NETFILTER_XT_TARGET_DSCP=mCONFIG_NETFILTER_XT_TARGET_HL=mCONFIG_NETFILTER_XT_TARGET_HMARK=mCONFIG_NETFILTER_XT_TARGET_IDLETIMER=m
# CONFIG_NETFILTER_XT_TARGET_LED is not setCONFIG_NETFILTER_XT_TARGET_LOG=mCONFIG_NETFILTER_XT_TARGET_MARK=mCONFIG_NETFILTER_XT_NAT=mCONFIG_NETFILTER_XT_TARGET_NETMAP=mCONFIG_NETFILTER_XT_TARGET_NFLOG=mCONFIG_NETFILTER_XT_TARGET_NFQUEUE=mCONFIG_NETFILTER_XT_TARGET_NOTRACK=mCONFIG_NETFILTER_XT_TARGET_RATEEST=mCONFIG_NETFILTER_XT_TARGET_REDIRECT=mCONFIG_NETFILTER_XT_TARGET_MASQUERADE=mCONFIG_NETFILTER_XT_TARGET_TEE=mCONFIG_NETFILTER_XT_TARGET_TPROXY=mCONFIG_NETFILTER_XT_TARGET_TRACE=mCONFIG_NETFILTER_XT_TARGET_SECMARK=mCONFIG_NETFILTER_XT_TARGET_TCPMSS=mCONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
#
# Xtables matches
#CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=mCONFIG_NETFILTER_XT_MATCH_BPF=mCONFIG_NETFILTER_XT_MATCH_CGROUP=mCONFIG_NETFILTER_XT_MATCH_CLUSTER=mCONFIG_NETFILTER_XT_MATCH_COMMENT=mCONFIG_NETFILTER_XT_MATCH_CONNBYTES=mCONFIG_NETFILTER_XT_MATCH_CONNLABEL=mCONFIG_NETFILTER_XT_MATCH_CONNLIMIT=mCONFIG_NETFILTER_XT_MATCH_CONNMARK=mCONFIG_NETFILTER_XT_MATCH_CONNTRACK=mCONFIG_NETFILTER_XT_MATCH_CPU=mCONFIG_NETFILTER_XT_MATCH_DCCP=mCONFIG_NETFILTER_XT_MATCH_DEVGROUP=mCONFIG_NETFILTER_XT_MATCH_DSCP=mCONFIG_NETFILTER_XT_MATCH_ECN=mCONFIG_NETFILTER_XT_MATCH_ESP=mCONFIG_NETFILTER_XT_MATCH_HASHLIMIT=mCONFIG_NETFILTER_XT_MATCH_HELPER=mCONFIG_NETFILTER_XT_MATCH_HL=m
# CONFIG_NETFILTER_XT_MATCH_IPCOMP is not setCONFIG_NETFILTER_XT_MATCH_IPRANGE=mCONFIG_NETFILTER_XT_MATCH_IPVS=m
# CONFIG_NETFILTER_XT_MATCH_L2TP is not setCONFIG_NETFILTER_XT_MATCH_LENGTH=mCONFIG_NETFILTER_XT_MATCH_LIMIT=mCONFIG_NETFILTER_XT_MATCH_MAC=mCONFIG_NETFILTER_XT_MATCH_MARK=mCONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
# CONFIG_NETFILTER_XT_MATCH_NFACCT is not setCONFIG_NETFILTER_XT_MATCH_OSF=mCONFIG_NETFILTER_XT_MATCH_OWNER=mCONFIG_NETFILTER_XT_MATCH_POLICY=mCONFIG_NETFILTER_XT_MATCH_PHYSDEV=mCONFIG_NETFILTER_XT_MATCH_PKTTYPE=mCONFIG_NETFILTER_XT_MATCH_QUOTA=mCONFIG_NETFILTER_XT_MATCH_RATEEST=mCONFIG_NETFILTER_XT_MATCH_REALM=mCONFIG_NETFILTER_XT_MATCH_RECENT=mCONFIG_NETFILTER_XT_MATCH_SCTP=mCONFIG_NETFILTER_XT_MATCH_SOCKET=mCONFIG_NETFILTER_XT_MATCH_STATE=mCONFIG_NETFILTER_XT_MATCH_STATISTIC=mCONFIG_NETFILTER_XT_MATCH_STRING=mCONFIG_NETFILTER_XT_MATCH_TCPMSS=m
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
# end of Core Netfilter Configuration
CONFIG_IP_SET=mCONFIG_IP_SET_MAX=256CONFIG_IP_SET_BITMAP_IP=mCONFIG_IP_SET_BITMAP_IPMAC=mCONFIG_IP_SET_BITMAP_PORT=mCONFIG_IP_SET_HASH_IP=mCONFIG_IP_SET_HASH_IPMARK=mCONFIG_IP_SET_HASH_IPPORT=mCONFIG_IP_SET_HASH_IPPORTIP=mCONFIG_IP_SET_HASH_IPPORTNET=mCONFIG_IP_SET_HASH_IPMAC=mCONFIG_IP_SET_HASH_MAC=mCONFIG_IP_SET_HASH_NETPORTNET=mCONFIG_IP_SET_HASH_NET=mCONFIG_IP_SET_HASH_NETNET=mCONFIG_IP_SET_HASH_NETPORT=mCONFIG_IP_SET_HASH_NETIFACE=mCONFIG_IP_SET_LIST_SET=mCONFIG_IP_VS=mCONFIG_IP_VS_IPV6=y
# CONFIG_IP_VS_DEBUG is not setCONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#CONFIG_IP_VS_PROTO_TCP=yCONFIG_IP_VS_PROTO_UDP=yCONFIG_IP_VS_PROTO_AH_ESP=yCONFIG_IP_VS_PROTO_ESP=yCONFIG_IP_VS_PROTO_AH=yCONFIG_IP_VS_PROTO_SCTP=y
#
# IPVS scheduler
#CONFIG_IP_VS_RR=mCONFIG_IP_VS_WRR=mCONFIG_IP_VS_LC=mCONFIG_IP_VS_WLC=mCONFIG_IP_VS_FO=mCONFIG_IP_VS_OVF=mCONFIG_IP_VS_LBLC=mCONFIG_IP_VS_LBLCR=mCONFIG_IP_VS_DH=mCONFIG_IP_VS_SH=m
# CONFIG_IP_VS_MH is not setCONFIG_IP_VS_SED=mCONFIG_IP_VS_NQ=m
#
# IPVS SH scheduler
#CONFIG_IP_VS_SH_TAB_BITS=8
#
# IPVS MH scheduler
#CONFIG_IP_VS_MH_TAB_INDEX=12
#
# IPVS application helper
#CONFIG_IP_VS_FTP=mCONFIG_IP_VS_NFCT=yCONFIG_IP_VS_PE_SIP=m
#
# IP: Netfilter Configuration
#CONFIG_NF_DEFRAG_IPV4=mCONFIG_NF_SOCKET_IPV4=mCONFIG_NF_TPROXY_IPV4=mCONFIG_NF_TABLES_IPV4=yCONFIG_NFT_REJECT_IPV4=mCONFIG_NFT_DUP_IPV4=mCONFIG_NFT_FIB_IPV4=mCONFIG_NF_TABLES_ARP=yCONFIG_NF_DUP_IPV4=mCONFIG_NF_LOG_ARP=mCONFIG_NF_LOG_IPV4=mCONFIG_NF_REJECT_IPV4=mCONFIG_NF_NAT_SNMP_BASIC=mCONFIG_NF_NAT_PPTP=mCONFIG_NF_NAT_H323=mCONFIG_IP_NF_IPTABLES=mCONFIG_IP_NF_MATCH_AH=mCONFIG_IP_NF_MATCH_ECN=mCONFIG_IP_NF_MATCH_RPFILTER=mCONFIG_IP_NF_MATCH_TTL=mCONFIG_IP_NF_FILTER=mCONFIG_IP_NF_TARGET_REJECT=mCONFIG_IP_NF_TARGET_SYNPROXY=mCONFIG_IP_NF_NAT=mCONFIG_IP_NF_TARGET_MASQUERADE=mCONFIG_IP_NF_TARGET_NETMAP=mCONFIG_IP_NF_TARGET_REDIRECT=mCONFIG_IP_NF_MANGLE=m
# CONFIG_IP_NF_TARGET_CLUSTERIP is not setCONFIG_IP_NF_TARGET_ECN=mCONFIG_IP_NF_TARGET_TTL=mCONFIG_IP_NF_RAW=mCONFIG_IP_NF_SECURITY=mCONFIG_IP_NF_ARPTABLES=mCONFIG_IP_NF_ARPFILTER=mCONFIG_IP_NF_ARP_MANGLE=m
# end of IP: Netfilter Configuration
#
# IPv6: Netfilter Configuration
#CONFIG_NF_SOCKET_IPV6=mCONFIG_NF_TPROXY_IPV6=mCONFIG_NF_TABLES_IPV6=yCONFIG_NFT_REJECT_IPV6=mCONFIG_NFT_DUP_IPV6=mCONFIG_NFT_FIB_IPV6=mCONFIG_NF_DUP_IPV6=mCONFIG_NF_REJECT_IPV6=mCONFIG_NF_LOG_IPV6=mCONFIG_IP6_NF_IPTABLES=mCONFIG_IP6_NF_MATCH_AH=mCONFIG_IP6_NF_MATCH_EUI64=mCONFIG_IP6_NF_MATCH_FRAG=mCONFIG_IP6_NF_MATCH_OPTS=mCONFIG_IP6_NF_MATCH_HL=mCONFIG_IP6_NF_MATCH_IPV6HEADER=mCONFIG_IP6_NF_MATCH_MH=mCONFIG_IP6_NF_MATCH_RPFILTER=mCONFIG_IP6_NF_MATCH_RT=m
# CONFIG_IP6_NF_MATCH_SRH is not set
# CONFIG_IP6_NF_TARGET_HL is not setCONFIG_IP6_NF_FILTER=mCONFIG_IP6_NF_TARGET_REJECT=mCONFIG_IP6_NF_TARGET_SYNPROXY=mCONFIG_IP6_NF_MANGLE=mCONFIG_IP6_NF_RAW=mCONFIG_IP6_NF_SECURITY=mCONFIG_IP6_NF_NAT=mCONFIG_IP6_NF_TARGET_MASQUERADE=mCONFIG_IP6_NF_TARGET_NPT=m
# end of IPv6: Netfilter Configuration
CONFIG_NF_DEFRAG_IPV6=m CONFIG_NF_TABLES_BRIDGE=m
# CONFIG_NFT_BRIDGE_META is not set CONFIG_NFT_BRIDGE_REJECT=m CONFIG_NF_LOG_BRIDGE=m
# CONFIG_NF_CONNTRACK_BRIDGE is not set CONFIG_BRIDGE_NF_EBTABLES=m CONFIG_BRIDGE_EBT_BROUTE=m CONFIG_BRIDGE_EBT_T_FILTER=m CONFIG_BRIDGE_EBT_T_NAT=m CONFIG_BRIDGE_EBT_802_3=m CONFIG_BRIDGE_EBT_AMONG=m CONFIG_BRIDGE_EBT_ARP=m CONFIG_BRIDGE_EBT_IP=m CONFIG_BRIDGE_EBT_IP6=m CONFIG_BRIDGE_EBT_LIMIT=m CONFIG_BRIDGE_EBT_MARK=m CONFIG_BRIDGE_EBT_PKTTYPE=m CONFIG_BRIDGE_EBT_STP=m CONFIG_BRIDGE_EBT_VLAN=m CONFIG_BRIDGE_EBT_ARPREPLY=m CONFIG_BRIDGE_EBT_DNAT=m CONFIG_BRIDGE_EBT_MARK_T=m CONFIG_BRIDGE_EBT_REDIRECT=m CONFIG_BRIDGE_EBT_SNAT=m CONFIG_BRIDGE_EBT_LOG=m CONFIG_BRIDGE_EBT_NFLOG=m
# CONFIG_BPFILTER is not set
# CONFIG_IP_DCCP is not setCONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5 is not set CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1=y
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not set CONFIG_SCTP_COOKIE_HMAC_MD5=y CONFIG_SCTP_COOKIE_HMAC_SHA1=y CONFIG_INET_SCTP_DIAG=m
# CONFIG_RDS is not setCONFIG_TIPC=m
# CONFIG_TIPC_MEDIA_IB is not set CONFIG_TIPC_MEDIA_UDP=yCONFIG_TIPC_CRYPTO=yCONFIG_TIPC_DIAG=mCONFIG_ATM=mCONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_L2TP=mCONFIG_L2TP_DEBUGFS=mCONFIG_L2TP_V3=yCONFIG_L2TP_IP=mCONFIG_L2TP_ETH=mCONFIG_STP=mCONFIG_GARP=mCONFIG_MRP=mCONFIG_BRIDGE=m CONFIG_BRIDGE_IGMP_SNOOPING=y CONFIG_BRIDGE_VLAN_FILTERING=y
# CONFIG_BRIDGE_MRP is not set CONFIG_HAVE_NET_DSA=y
# CONFIG_NET_DSA is not set CONFIG_VLAN_8021Q=mCONFIG_VLAN_8021Q_GVRP=y CONFIG_VLAN_8021Q_MVRP=y
# CONFIG_DECNET is not setCONFIG_LLC=m
# CONFIG_LLC2 is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not setCONFIG_6LOWPAN=m
# CONFIG_6LOWPAN_DEBUGFS is not set
# CONFIG_6LOWPAN_NHC is not set CONFIG_IEEE802154=m
# CONFIG_IEEE802154_NL802154_EXPERIMENTAL is not set CONFIG_IEEE802154_SOCKET=m CONFIG_IEEE802154_6LOWPAN=m CONFIG_MAC802154=mCONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#CONFIG_NET_SCH_CBQ=mCONFIG_NET_SCH_HTB=mCONFIG_NET_SCH_HFSC=mCONFIG_NET_SCH_ATM=mCONFIG_NET_SCH_PRIO=mCONFIG_NET_SCH_MULTIQ=mCONFIG_NET_SCH_RED=mCONFIG_NET_SCH_SFB=mCONFIG_NET_SCH_SFQ=mCONFIG_NET_SCH_TEQL=mCONFIG_NET_SCH_TBF=m
# CONFIG_NET_SCH_CBS is not set
# CONFIG_NET_SCH_ETF is not set
# CONFIG_NET_SCH_TAPRIO is not setCONFIG_NET_SCH_GRED=mCONFIG_NET_SCH_DSMARK=mCONFIG_NET_SCH_NETEM=mCONFIG_NET_SCH_DRR=mCONFIG_NET_SCH_MQPRIO=m
# CONFIG_NET_SCH_SKBPRIO is not setCONFIG_NET_SCH_CHOKE=mCONFIG_NET_SCH_QFQ=mCONFIG_NET_SCH_CODEL=mCONFIG_NET_SCH_FQ_CODEL=y
# CONFIG_NET_SCH_CAKE is not setCONFIG_NET_SCH_FQ=mCONFIG_NET_SCH_HHF=mCONFIG_NET_SCH_PIE=m
# CONFIG_NET_SCH_FQ_PIE is not setCONFIG_NET_SCH_INGRESS=mCONFIG_NET_SCH_PLUG=m
# CONFIG_NET_SCH_ETS is not setCONFIG_NET_SCH_DEFAULT=y
# CONFIG_DEFAULT_FQ is not set
# CONFIG_DEFAULT_CODEL is not setCONFIG_DEFAULT_FQ_CODEL=y
# CONFIG_DEFAULT_SFQ is not set
# CONFIG_DEFAULT_PFIFO_FAST is not setCONFIG_DEFAULT_NET_SCH="fq_codel"
#
# Classification
#CONFIG_NET_CLS=yCONFIG_NET_CLS_BASIC=mCONFIG_NET_CLS_TCINDEX=mCONFIG_NET_CLS_ROUTE4=mCONFIG_NET_CLS_FW=mCONFIG_NET_CLS_U32=mCONFIG_CLS_U32_PERF=yCONFIG_CLS_U32_MARK=yCONFIG_NET_CLS_RSVP=mCONFIG_NET_CLS_RSVP6=mCONFIG_NET_CLS_FLOW=mCONFIG_NET_CLS_CGROUP=yCONFIG_NET_CLS_BPF=mCONFIG_NET_CLS_FLOWER=mCONFIG_NET_CLS_MATCHALL=mCONFIG_NET_EMATCH=yCONFIG_NET_EMATCH_STACK=32CONFIG_NET_EMATCH_CMP=mCONFIG_NET_EMATCH_NBYTE=mCONFIG_NET_EMATCH_U32=mCONFIG_NET_EMATCH_META=mCONFIG_NET_EMATCH_TEXT=m
# CONFIG_NET_EMATCH_CANID is not setCONFIG_NET_EMATCH_IPSET=m
# CONFIG_NET_EMATCH_IPT is not setCONFIG_NET_CLS_ACT=yCONFIG_NET_ACT_POLICE=mCONFIG_NET_ACT_GACT=mCONFIG_GACT_PROB=yCONFIG_NET_ACT_MIRRED=mCONFIG_NET_ACT_SAMPLE=m
# CONFIG_NET_ACT_IPT is not setCONFIG_NET_ACT_NAT=mCONFIG_NET_ACT_PEDIT=mCONFIG_NET_ACT_SIMP=mCONFIG_NET_ACT_SKBEDIT=mCONFIG_NET_ACT_CSUM=m
# CONFIG_NET_ACT_MPLS is not setCONFIG_NET_ACT_VLAN=mCONFIG_NET_ACT_BPF=m
# CONFIG_NET_ACT_CONNMARK is not set
# CONFIG_NET_ACT_CTINFO is not setCONFIG_NET_ACT_SKBMOD=m
# CONFIG_NET_ACT_IFE is not setCONFIG_NET_ACT_TUNNEL_KEY=m
# CONFIG_NET_ACT_GATE is not set
# CONFIG_NET_TC_SKB_EXT is not setCONFIG_NET_SCH_FIFO=yCONFIG_DCB=yCONFIG_DNS_RESOLVER=m
# CONFIG_BATMAN_ADV is not setCONFIG_OPENVSWITCH=mCONFIG_OPENVSWITCH_GRE=mCONFIG_VSOCKETS=mCONFIG_VSOCKETS_DIAG=mCONFIG_VSOCKETS_LOOPBACK=mCONFIG_VMWARE_VMCI_VSOCKETS=mCONFIG_VIRTIO_VSOCKETS=mCONFIG_VIRTIO_VSOCKETS_COMMON=mCONFIG_HYPERV_VSOCKETS=mCONFIG_NETLINK_DIAG=mCONFIG_MPLS=yCONFIG_NET_MPLS_GSO=yCONFIG_MPLS_ROUTING=mCONFIG_MPLS_IPTUNNEL=mCONFIG_NET_NSH=y
# CONFIG_HSR is not setCONFIG_NET_SWITCHDEV=yCONFIG_NET_L3_MASTER_DEV=y
# CONFIG_QRTR is not set
# CONFIG_NET_NCSI is not setCONFIG_RPS=yCONFIG_RFS_ACCEL=yCONFIG_XPS=yCONFIG_CGROUP_NET_PRIO=yCONFIG_CGROUP_NET_CLASSID=yCONFIG_NET_RX_BUSY_POLL=yCONFIG_BQL=yCONFIG_BPF_JIT=yCONFIG_BPF_STREAM_PARSER=yCONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#CONFIG_NET_PKTGEN=mCONFIG_NET_DROP_MONITOR=y
# end of Network testing # end of Networking options
# CONFIG_HAMRADIO is not setCONFIG_CAN=mCONFIG_CAN_RAW=mCONFIG_CAN_BCM=mCONFIG_CAN_GW=m
# CONFIG_CAN_J1939 is not set
# CONFIG_CAN_ISOTP is not set
#
# CAN Device Drivers
#CONFIG_CAN_VCAN=m
# CONFIG_CAN_VXCAN is not setCONFIG_CAN_SLCAN=mCONFIG_CAN_DEV=mCONFIG_CAN_CALC_BITTIMING=y
# CONFIG_CAN_KVASER_PCIEFD is not setCONFIG_CAN_C_CAN=mCONFIG_CAN_C_CAN_PLATFORM=mCONFIG_CAN_C_CAN_PCI=mCONFIG_CAN_CC770=m
# CONFIG_CAN_CC770_ISA is not setCONFIG_CAN_CC770_PLATFORM=m
# CONFIG_CAN_IFI_CANFD is not set
# CONFIG_CAN_M_CAN is not set
# CONFIG_CAN_PEAK_PCIEFD is not setCONFIG_CAN_SJA1000=mCONFIG_CAN_EMS_PCI=m
# CONFIG_CAN_F81601 is not setCONFIG_CAN_KVASER_PCI=mCONFIG_CAN_PEAK_PCI=mCONFIG_CAN_PEAK_PCIEC=yCONFIG_CAN_PLX_PCI=m
# CONFIG_CAN_SJA1000_ISA is not setCONFIG_CAN_SJA1000_PLATFORM=mCONFIG_CAN_SOFTING=m
#
# CAN SPI interfaces
#
# CONFIG_CAN_HI311X is not set
# CONFIG_CAN_MCP251X is not set
# CONFIG_CAN_MCP251XFD is not set
# end of CAN SPI interfaces
#
# CAN USB interfaces
#
# CONFIG_CAN_8DEV_USB is not set
# CONFIG_CAN_EMS_USB is not set
# CONFIG_CAN_ESD_USB2 is not set
# CONFIG_CAN_GS_USB is not set
# CONFIG_CAN_KVASER_USB is not set
# CONFIG_CAN_MCBA_USB is not set
# CONFIG_CAN_PEAK_USB is not set
# CONFIG_CAN_UCAN is not set
# end of CAN USB interfaces
# CONFIG_CAN_DEBUG_DEVICES is not set
# end of CAN Device Drivers
CONFIG_BT=mCONFIG_BT_BREDR=yCONFIG_BT_RFCOMM=mCONFIG_BT_RFCOMM_TTY=yCONFIG_BT_BNEP=mCONFIG_BT_BNEP_MC_FILTER=yCONFIG_BT_BNEP_PROTO_FILTER=yCONFIG_BT_HIDP=mCONFIG_BT_HS=yCONFIG_BT_LE=y
# CONFIG_BT_6LOWPAN is not set
# CONFIG_BT_LEDS is not set
# CONFIG_BT_MSFTEXT is not setCONFIG_BT_DEBUGFS=y
# CONFIG_BT_SELFTEST is not set
#
# Bluetooth device drivers
#
# CONFIG_BT_HCIBTUSB is not set
# CONFIG_BT_HCIBTSDIO is not setCONFIG_BT_HCIUART=mCONFIG_BT_HCIUART_H4=yCONFIG_BT_HCIUART_BCSP=yCONFIG_BT_HCIUART_ATH3K=y
# CONFIG_BT_HCIUART_INTEL is not set
# CONFIG_BT_HCIUART_AG6XX is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not setCONFIG_BT_HCIVHCI=mCONFIG_BT_MRVL=m
# CONFIG_BT_MRVL_SDIO is not set
# CONFIG_BT_MTKSDIO is not set
# end of Bluetooth device drivers
# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not setCONFIG_STREAM_PARSER=yCONFIG_FIB_RULES=yCONFIG_WIRELESS=yCONFIG_WEXT_CORE=yCONFIG_WEXT_PROC=yCONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not setCONFIG_CFG80211_REQUIRE_SIGNED_REGDB=yCONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=yCONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not setCONFIG_CFG80211_CRDA_SUPPORT=yCONFIG_CFG80211_WEXT=yCONFIG_MAC80211=mCONFIG_MAC80211_HAS_RC=yCONFIG_MAC80211_RC_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT="minstrel_ht"CONFIG_MAC80211_MESH=yCONFIG_MAC80211_LEDS=yCONFIG_MAC80211_DEBUGFS=y
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not setCONFIG_MAC80211_STA_HASH_MAX_SIZE=0
# CONFIG_WIMAX is not setCONFIG_RFKILL=mCONFIG_RFKILL_LEDS=yCONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_GPIO is not setCONFIG_NET_9P=yCONFIG_NET_9P_VIRTIO=y
# CONFIG_NET_9P_XEN is not set
# CONFIG_NET_9P_RDMA is not set
# CONFIG_NET_9P_DEBUG is not set
# CONFIG_CAIF is not setCONFIG_CEPH_LIB=m
# CONFIG_CEPH_LIB_PRETTYDEBUG is not setCONFIG_CEPH_LIB_USE_DNS_RESOLVER=y
# CONFIG_NFC is not setCONFIG_PSAMPLE=m
# CONFIG_NET_IFE is not setCONFIG_LWTUNNEL=yCONFIG_LWTUNNEL_BPF=yCONFIG_DST_CACHE=yCONFIG_GRO_CELLS=yCONFIG_SOCK_VALIDATE_XMIT=yCONFIG_NET_SOCK_MSG=yCONFIG_NET_DEVLINK=yCONFIG_PAGE_POOL=yCONFIG_FAILOVER=mCONFIG_ETHTOOL_NETLINK=yCONFIG_HAVE_EBPF_JIT=y
#
# Device Drivers
#CONFIG_HAVE_EISA=y
# CONFIG_EISA is not setCONFIG_HAVE_PCI=yCONFIG_PCI=yCONFIG_PCI_DOMAINS=yCONFIG_PCIEPORTBUS=yCONFIG_HOTPLUG_PCI_PCIE=yCONFIG_PCIEAER=yCONFIG_PCIEAER_INJECT=mCONFIG_PCIE_ECRC=yCONFIG_PCIEASPM=yCONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not setCONFIG_PCIE_PME=yCONFIG_PCIE_DPC=y
# CONFIG_PCIE_PTM is not set
# CONFIG_PCIE_BW is not set
# CONFIG_PCIE_EDR is not setCONFIG_PCI_MSI=yCONFIG_PCI_MSI_IRQ_DOMAIN=yCONFIG_PCI_QUIRKS=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_REALLOC_ENABLE_AUTO is not setCONFIG_PCI_STUB=yCONFIG_PCI_PF_STUB=m
# CONFIG_XEN_PCIDEV_FRONTEND is not setCONFIG_PCI_ATS=yCONFIG_PCI_LOCKLESS_CONFIG=yCONFIG_PCI_IOV=yCONFIG_PCI_PRI=yCONFIG_PCI_PASID=y
# CONFIG_PCI_P2PDMA is not setCONFIG_PCI_LABEL=yCONFIG_PCI_HYPERV=mCONFIG_HOTPLUG_PCI=yCONFIG_HOTPLUG_PCI_ACPI=yCONFIG_HOTPLUG_PCI_ACPI_IBM=m
# CONFIG_HOTPLUG_PCI_CPCI is not setCONFIG_HOTPLUG_PCI_SHPC=y
#
# PCI controller drivers
#CONFIG_VMD=yCONFIG_PCI_HYPERV_INTERFACE=m
#
# DesignWare PCI Core Support
#
# CONFIG_PCIE_DW_PLAT_HOST is not set
# CONFIG_PCI_MESON is not set
# end of DesignWare PCI Core Support
#
# Mobiveil PCIe Core Support
#
# end of Mobiveil PCIe Core Support
#
# Cadence PCIe controllers support
#
# end of Cadence PCIe controllers support # end of PCI controller drivers
#
# PCI Endpoint
#
# CONFIG_PCI_ENDPOINT is not set
# end of PCI Endpoint
#
# PCI switch controller drivers
#
# CONFIG_PCI_SW_SWITCHTEC is not set
# end of PCI switch controller drivers
# CONFIG_PCCARD is not set
# CONFIG_RAPIDIO is not set
#
# Generic Driver Options
#
# CONFIG_UEVENT_HELPER is not setCONFIG_DEVTMPFS=yCONFIG_DEVTMPFS_MOUNT=yCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#CONFIG_FW_LOADER=y CONFIG_FW_LOADER_PAGED_BUF=y CONFIG_EXTRA_FIRMWARE="" CONFIG_FW_LOADER_USER_HELPER=y
# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set # CONFIG_FW_LOADER_COMPRESS is not set CONFIG_FW_CACHE=y
# end of Firmware loader
CONFIG_ALLOW_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
# CONFIG_PM_QOS_KUNIT_TEST is not set
# CONFIG_TEST_ASYNC_DRIVER_PROBE is not setCONFIG_KUNIT_DRIVER_PE_TEST=yCONFIG_SYS_HYPERVISOR=yCONFIG_GENERIC_CPU_AUTOPROBE=yCONFIG_GENERIC_CPU_VULNERABILITIES=yCONFIG_REGMAP=yCONFIG_REGMAP_I2C=mCONFIG_REGMAP_SPI=mCONFIG_DMA_SHARED_BUFFER=y
# CONFIG_DMA_FENCE_TRACE is not set
# end of Generic Driver Options
#
# Bus devices
#
# CONFIG_MHI_BUS is not set
# end of Bus devices
CONFIG_CONNECTOR=yCONFIG_PROC_EVENTS=y
# CONFIG_GNSS is not set
# CONFIG_MTD is not set
# CONFIG_OF is not setCONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=yCONFIG_PARPORT=mCONFIG_PARPORT_PC=mCONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AX88796 is not setCONFIG_PARPORT_1284=yCONFIG_PNP=y
# CONFIG_PNP_DEBUG_MESSAGES is not set
#
# Protocols
#CONFIG_PNPACPI=yCONFIG_BLK_DEV=yCONFIG_BLK_DEV_NULL_BLK=mCONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION=y
# CONFIG_BLK_DEV_FD is not setCONFIG_CDROM=m
# CONFIG_PARIDE is not set
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
# CONFIG_ZRAM is not set
# CONFIG_BLK_DEV_UMEM is not setCONFIG_BLK_DEV_LOOP=mCONFIG_BLK_DEV_LOOP_MIN_COUNT=0
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not setCONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SKD is not set
# CONFIG_BLK_DEV_SX8 is not setCONFIG_BLK_DEV_RAM=mCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=16384CONFIG_CDROM_PKTCDVD=mCONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not setCONFIG_XEN_BLKDEV_FRONTEND=mCONFIG_VIRTIO_BLK=mCONFIG_BLK_DEV_RBD=m
# CONFIG_BLK_DEV_RSXX is not set
#
# NVME Support
#CONFIG_NVME_CORE=mCONFIG_BLK_DEV_NVME=mCONFIG_NVME_MULTIPATH=y
# CONFIG_NVME_HWMON is not setCONFIG_NVME_FABRICS=m
# CONFIG_NVME_RDMA is not setCONFIG_NVME_FC=m
# CONFIG_NVME_TCP is not setCONFIG_NVME_TARGET=m
# CONFIG_NVME_TARGET_PASSTHRU is not setCONFIG_NVME_TARGET_LOOP=m
# CONFIG_NVME_TARGET_RDMA is not setCONFIG_NVME_TARGET_FC=mCONFIG_NVME_TARGET_FCLOOP=m
# CONFIG_NVME_TARGET_TCP is not set
# end of NVME Support
#
# Misc devices
#CONFIG_SENSORS_LIS3LV02D=m
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not setCONFIG_TIFM_CORE=mCONFIG_TIFM_7XX1=m
# CONFIG_ICS932S401 is not setCONFIG_ENCLOSURE_SERVICES=mCONFIG_SGI_XP=mCONFIG_HP_ILO=mCONFIG_SGI_GRU=m
# CONFIG_SGI_GRU_DEBUG is not setCONFIG_APDS9802ALS=mCONFIG_ISL29003=mCONFIG_ISL29020=mCONFIG_SENSORS_TSL2550=mCONFIG_SENSORS_BH1770=mCONFIG_SENSORS_APDS990X=m
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not setCONFIG_VMWARE_BALLOON=m
# CONFIG_LATTICE_ECP3_CONFIG is not set
# CONFIG_SRAM is not set
# CONFIG_PCI_ENDPOINT_TEST is not set
# CONFIG_XILINX_SDFEC is not setCONFIG_MISC_RTSX=mCONFIG_PVPANIC=y
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_AT25 is not setCONFIG_EEPROM_LEGACY=mCONFIG_EEPROM_MAX6875=mCONFIG_EEPROM_93CX6=m
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_EEPROM_IDT_89HPESX is not set
# CONFIG_EEPROM_EE1004 is not set
# end of EEPROM support
CONFIG_CB710_CORE=m
# CONFIG_CB710_DEBUG is not setCONFIG_CB710_DEBUG_ASSUMPTIONS=y
#
# Texas Instruments shared transport line discipline #
# CONFIG_TI_ST is not set
# end of Texas Instruments shared transport line discipline
CONFIG_SENSORS_LIS3_I2C=mCONFIG_ALTERA_STAPL=mCONFIG_INTEL_MEI=mCONFIG_INTEL_MEI_ME=m
# CONFIG_INTEL_MEI_TXE is not set
# CONFIG_INTEL_MEI_VIRTIO is not set
# CONFIG_INTEL_MEI_HDCP is not setCONFIG_VMWARE_VMCI=m
# CONFIG_GENWQE is not set
# CONFIG_ECHO is not set
# CONFIG_MISC_ALCOR_PCI is not setCONFIG_MISC_RTSX_PCI=m
# CONFIG_MISC_RTSX_USB is not set
# CONFIG_HABANA_AI is not set
# CONFIG_UACCE is not set
# end of Misc devices
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#CONFIG_SCSI_MOD=yCONFIG_RAID_ATTRS=mCONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_NETLINK=yCONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=mCONFIG_CHR_DEV_ST=mCONFIG_BLK_DEV_SR=mCONFIG_CHR_DEV_SG=mCONFIG_CHR_DEV_SCH=mCONFIG_SCSI_ENCLOSURE=mCONFIG_SCSI_CONSTANTS=yCONFIG_SCSI_LOGGING=yCONFIG_SCSI_SCAN_ASYNC=y
#
# SCSI Transports
#CONFIG_SCSI_SPI_ATTRS=mCONFIG_SCSI_FC_ATTRS=mCONFIG_SCSI_ISCSI_ATTRS=mCONFIG_SCSI_SAS_ATTRS=mCONFIG_SCSI_SAS_LIBSAS=mCONFIG_SCSI_SAS_ATA=yCONFIG_SCSI_SAS_HOST_SMP=yCONFIG_SCSI_SRP_ATTRS=m
# end of SCSI Transports
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_CXGB4_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_MVUMI is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not setCONFIG_SCSI_MPT3SAS=mCONFIG_SCSI_MPT2SAS_MAX_SGE=128CONFIG_SCSI_MPT3SAS_MAX_SGE=128
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_SMARTPQI is not set
# CONFIG_SCSI_UFSHCD is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_MYRB is not set
# CONFIG_SCSI_MYRS is not set
# CONFIG_VMWARE_PVSCSI is not set
# CONFIG_XEN_SCSI_FRONTEND is not setCONFIG_HYPERV_STORAGE=m
# CONFIG_LIBFC is not set
# CONFIG_SCSI_SNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_FDOMAIN_PCI is not set
# CONFIG_SCSI_GDTH is not setCONFIG_SCSI_ISCI=m
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_WD719X is not setCONFIG_SCSI_DEBUG=m
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
# CONFIG_SCSI_BFA_FC is not set
# CONFIG_SCSI_VIRTIO is not set
# CONFIG_SCSI_CHELSIO_FCOE is not setCONFIG_SCSI_DH=yCONFIG_SCSI_DH_RDAC=yCONFIG_SCSI_DH_HP_SW=yCONFIG_SCSI_DH_EMC=yCONFIG_SCSI_DH_ALUA=y
# end of SCSI device support
CONFIG_ATA=mCONFIG_SATA_HOST=yCONFIG_PATA_TIMINGS=yCONFIG_ATA_VERBOSE_ERROR=yCONFIG_ATA_FORCE=yCONFIG_ATA_ACPI=y
# CONFIG_SATA_ZPODD is not setCONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#CONFIG_SATA_AHCI=mCONFIG_SATA_MOBILE_LPM_POLICY=0CONFIG_SATA_AHCI_PLATFORM=m
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_SATA_SIL24 is not setCONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not setCONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#CONFIG_ATA_PIIX=m
# CONFIG_SATA_DWC is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SCH is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#
# CONFIG_PATA_ACPI is not set CONFIG_ATA_GENERIC=m
# CONFIG_PATA_LEGACY is not set CONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_AUTODETECT=yCONFIG_MD_LINEAR=mCONFIG_MD_RAID0=mCONFIG_MD_RAID1=mCONFIG_MD_RAID10=mCONFIG_MD_RAID456=mCONFIG_MD_MULTIPATH=mCONFIG_MD_FAULTY=mCONFIG_MD_CLUSTER=m
# CONFIG_BCACHE is not set CONFIG_BLK_DEV_DM_BUILTIN=y CONFIG_BLK_DEV_DM=mCONFIG_DM_DEBUG=yCONFIG_DM_BUFIO=m
# CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING is not set CONFIG_DM_BIO_PRISON=m CONFIG_DM_PERSISTENT_DATA=m
# CONFIG_DM_UNSTRIPED is not set CONFIG_DM_CRYPT=mCONFIG_DM_SNAPSHOT=m CONFIG_DM_THIN_PROVISIONING=m CONFIG_DM_CACHE=mCONFIG_DM_CACHE_SMQ=m CONFIG_DM_WRITECACHE=m
# CONFIG_DM_EBS is not setCONFIG_DM_ERA=m
# CONFIG_DM_CLONE is not set CONFIG_DM_MIRROR=m CONFIG_DM_LOG_USERSPACE=mCONFIG_DM_RAID=mCONFIG_DM_ZERO=mCONFIG_DM_MULTIPATH=m CONFIG_DM_MULTIPATH_QL=m CONFIG_DM_MULTIPATH_ST=m
# CONFIG_DM_MULTIPATH_HST is not set CONFIG_DM_DELAY=m
# CONFIG_DM_DUST is not set CONFIG_DM_UEVENT=yCONFIG_DM_FLAKEY=mCONFIG_DM_VERITY=m
# CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG is not set # CONFIG_DM_VERITY_FEC is not set CONFIG_DM_SWITCH=mCONFIG_DM_LOG_WRITES=m CONFIG_DM_INTEGRITY=m
# CONFIG_DM_ZONED is not set CONFIG_TARGET_CORE=mCONFIG_TCM_IBLOCK=mCONFIG_TCM_FILEIO=mCONFIG_TCM_PSCSI=mCONFIG_TCM_USER2=m CONFIG_LOOPBACK_TARGET=m CONFIG_ISCSI_TARGET=m
# CONFIG_SBP_TARGET is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#CONFIG_FIREWIRE=mCONFIG_FIREWIRE_OHCI=mCONFIG_FIREWIRE_SBP2=mCONFIG_FIREWIRE_NET=m
# CONFIG_FIREWIRE_NOSY is not set
# end of IEEE 1394 (FireWire) support
CONFIG_MACINTOSH_DRIVERS=yCONFIG_MAC_EMUMOUSEBTN=yCONFIG_NETDEVICES=yCONFIG_MII=mCONFIG_NET_CORE=y
# CONFIG_BONDING is not set
# CONFIG_DUMMY is not set
# CONFIG_WIREGUARD is not set
# CONFIG_EQUALIZER is not set
# CONFIG_NET_FC is not set
# CONFIG_IFB is not set
# CONFIG_NET_TEAM is not set
# CONFIG_MACVLAN is not set
# CONFIG_IPVLAN is not set
# CONFIG_VXLAN is not set
# CONFIG_GENEVE is not set
# CONFIG_BAREUDP is not set
# CONFIG_GTP is not set
# CONFIG_MACSEC is not setCONFIG_NETCONSOLE=mCONFIG_NETCONSOLE_DYNAMIC=yCONFIG_NETPOLL=yCONFIG_NET_POLL_CONTROLLER=yCONFIG_TUN=m
# CONFIG_TUN_VNET_CROSS_LE is not setCONFIG_VETH=m
# CONFIG_VIRTIO_NET is not set
# CONFIG_NLMON is not set
# CONFIG_NET_VRF is not set
# CONFIG_VSOCKMON is not set
# CONFIG_ARCNET is not setCONFIG_ATM_DRIVERS=y
# CONFIG_ATM_DUMMY is not set
# CONFIG_ATM_TCP is not set
# CONFIG_ATM_LANAI is not set
# CONFIG_ATM_ENI is not set
# CONFIG_ATM_FIRESTREAM is not set
# CONFIG_ATM_ZATM is not set
# CONFIG_ATM_NICSTAR is not set
# CONFIG_ATM_IDT77252 is not set
# CONFIG_ATM_AMBASSADOR is not set
# CONFIG_ATM_HORIZON is not set
# CONFIG_ATM_IA is not set
# CONFIG_ATM_FORE200E is not set
# CONFIG_ATM_HE is not set
# CONFIG_ATM_SOLOS is not set
#
# Distributed Switch Architecture drivers
#
# end of Distributed Switch Architecture drivers
CONFIG_ETHERNET=yCONFIG_MDIO=yCONFIG_NET_VENDOR_3COM=y
# CONFIG_VORTEX is not set
# CONFIG_TYPHOON is not setCONFIG_NET_VENDOR_ADAPTEC=y
# CONFIG_ADAPTEC_STARFIRE is not setCONFIG_NET_VENDOR_AGERE=y
# CONFIG_ET131X is not setCONFIG_NET_VENDOR_ALACRITECH=y
# CONFIG_SLICOSS is not setCONFIG_NET_VENDOR_ALTEON=y
# CONFIG_ACENIC is not set
# CONFIG_ALTERA_TSE is not setCONFIG_NET_VENDOR_AMAZON=y
# CONFIG_ENA_ETHERNET is not setCONFIG_NET_VENDOR_AMD=y
# CONFIG_AMD8111_ETH is not set
# CONFIG_PCNET32 is not set
# CONFIG_AMD_XGBE is not setCONFIG_NET_VENDOR_AQUANTIA=y
# CONFIG_AQTION is not setCONFIG_NET_VENDOR_ARC=yCONFIG_NET_VENDOR_ATHEROS=y
# CONFIG_ATL2 is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
# CONFIG_ALX is not set
# CONFIG_NET_VENDOR_AURORA is not setCONFIG_NET_VENDOR_BROADCOM=y
# CONFIG_B44 is not set
# CONFIG_BCMGENET is not set
# CONFIG_BNX2 is not set
# CONFIG_CNIC is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2X is not set
# CONFIG_SYSTEMPORT is not set
# CONFIG_BNXT is not setCONFIG_NET_VENDOR_BROCADE=y
# CONFIG_BNA is not setCONFIG_NET_VENDOR_CADENCE=y
# CONFIG_MACB is not setCONFIG_NET_VENDOR_CAVIUM=y
# CONFIG_THUNDER_NIC_PF is not set
# CONFIG_THUNDER_NIC_VF is not set
# CONFIG_THUNDER_NIC_BGX is not set
# CONFIG_THUNDER_NIC_RGX is not setCONFIG_CAVIUM_PTP=y
# CONFIG_LIQUIDIO is not set
# CONFIG_LIQUIDIO_VF is not setCONFIG_NET_VENDOR_CHELSIO=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_CHELSIO_T4 is not set
# CONFIG_CHELSIO_T4VF is not setCONFIG_NET_VENDOR_CISCO=y
# CONFIG_ENIC is not setCONFIG_NET_VENDOR_CORTINA=y
# CONFIG_CX_ECAT is not set
# CONFIG_DNET is not setCONFIG_NET_VENDOR_DEC=y
# CONFIG_NET_TULIP is not setCONFIG_NET_VENDOR_DLINK=y
# CONFIG_DL2K is not set
# CONFIG_SUNDANCE is not setCONFIG_NET_VENDOR_EMULEX=y
# CONFIG_BE2NET is not setCONFIG_NET_VENDOR_EZCHIP=yCONFIG_NET_VENDOR_GOOGLE=y
# CONFIG_GVE is not setCONFIG_NET_VENDOR_HUAWEI=y
# CONFIG_HINIC is not setCONFIG_NET_VENDOR_I825XX=yCONFIG_NET_VENDOR_INTEL=y
# CONFIG_E100 is not setCONFIG_E1000=yCONFIG_E1000E=yCONFIG_E1000E_HWTS=yCONFIG_IGB=yCONFIG_IGB_HWMON=y
# CONFIG_IGBVF is not set
# CONFIG_IXGB is not setCONFIG_IXGBE=yCONFIG_IXGBE_HWMON=y
# CONFIG_IXGBE_DCB is not setCONFIG_IXGBE_IPSEC=y
# CONFIG_IXGBEVF is not setCONFIG_I40E=y
# CONFIG_I40E_DCB is not set
# CONFIG_I40EVF is not set
# CONFIG_ICE is not set
# CONFIG_FM10K is not set
# CONFIG_IGC is not set
# CONFIG_JME is not setCONFIG_NET_VENDOR_MARVELL=y
# CONFIG_MVMDIO is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_PRESTERA is not setCONFIG_NET_VENDOR_MELLANOX=y
# CONFIG_MLX4_EN is not set
# CONFIG_MLX5_CORE is not set
# CONFIG_MLXSW_CORE is not set
# CONFIG_MLXFW is not setCONFIG_NET_VENDOR_MICREL=y
# CONFIG_KS8842 is not set
# CONFIG_KS8851 is not set
# CONFIG_KS8851_MLL is not set
# CONFIG_KSZ884X_PCI is not setCONFIG_NET_VENDOR_MICROCHIP=y
# CONFIG_ENC28J60 is not set
# CONFIG_ENCX24J600 is not set
# CONFIG_LAN743X is not setCONFIG_NET_VENDOR_MICROSEMI=yCONFIG_NET_VENDOR_MYRI=y
# CONFIG_MYRI10GE is not set
# CONFIG_FEALNX is not setCONFIG_NET_VENDOR_NATSEMI=y
# CONFIG_NATSEMI is not set
# CONFIG_NS83820 is not setCONFIG_NET_VENDOR_NETERION=y
# CONFIG_S2IO is not set
# CONFIG_VXGE is not setCONFIG_NET_VENDOR_NETRONOME=y
# CONFIG_NFP is not setCONFIG_NET_VENDOR_NI=y
# CONFIG_NI_XGE_MANAGEMENT_ENET is not setCONFIG_NET_VENDOR_8390=y
# CONFIG_NE2K_PCI is not setCONFIG_NET_VENDOR_NVIDIA=y
# CONFIG_FORCEDETH is not setCONFIG_NET_VENDOR_OKI=y
# CONFIG_ETHOC is not setCONFIG_NET_VENDOR_PACKET_ENGINES=y
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not setCONFIG_NET_VENDOR_PENSANDO=y
# CONFIG_IONIC is not setCONFIG_NET_VENDOR_QLOGIC=y
# CONFIG_QLA3XXX is not set
# CONFIG_QLCNIC is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_QED is not setCONFIG_NET_VENDOR_QUALCOMM=y
# CONFIG_QCOM_EMAC is not set
# CONFIG_RMNET is not setCONFIG_NET_VENDOR_RDC=y
# CONFIG_R6040 is not setCONFIG_NET_VENDOR_REALTEK=y
# CONFIG_ATP is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not setCONFIG_R8169=yCONFIG_NET_VENDOR_RENESAS=yCONFIG_NET_VENDOR_ROCKER=y
# CONFIG_ROCKER is not setCONFIG_NET_VENDOR_SAMSUNG=y
# CONFIG_SXGBE_ETH is not setCONFIG_NET_VENDOR_SEEQ=yCONFIG_NET_VENDOR_SOLARFLARE=y
# CONFIG_SFC is not set
# CONFIG_SFC_FALCON is not setCONFIG_NET_VENDOR_SILAN=y
# CONFIG_SC92031 is not setCONFIG_NET_VENDOR_SIS=y
# CONFIG_SIS900 is not set
# CONFIG_SIS190 is not setCONFIG_NET_VENDOR_SMSC=y
# CONFIG_EPIC100 is not set
# CONFIG_SMSC911X is not set
# CONFIG_SMSC9420 is not setCONFIG_NET_VENDOR_SOCIONEXT=yCONFIG_NET_VENDOR_STMICRO=y
# CONFIG_STMMAC_ETH is not setCONFIG_NET_VENDOR_SUN=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NIU is not setCONFIG_NET_VENDOR_SYNOPSYS=y
# CONFIG_DWC_XLGMAC is not setCONFIG_NET_VENDOR_TEHUTI=y
# CONFIG_TEHUTI is not setCONFIG_NET_VENDOR_TI=y
# CONFIG_TI_CPSW_PHY_SEL is not set
# CONFIG_TLAN is not setCONFIG_NET_VENDOR_VIA=y
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not setCONFIG_NET_VENDOR_WIZNET=y
# CONFIG_WIZNET_W5100 is not set
# CONFIG_WIZNET_W5300 is not setCONFIG_NET_VENDOR_XILINX=y
# CONFIG_XILINX_AXI_EMAC is not set
# CONFIG_XILINX_LL_TEMAC is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_NET_SB1000 is not setCONFIG_PHYLIB=y
# CONFIG_LED_TRIGGER_PHY is not set
# CONFIG_FIXED_PHY is not set
#
# MII PHY device drivers
#
# CONFIG_AMD_PHY is not set
# CONFIG_ADIN_PHY is not set
# CONFIG_AQUANTIA_PHY is not set
# CONFIG_AX88796B_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_BCM54140_PHY is not set
# CONFIG_BCM7XXX_PHY is not set
# CONFIG_BCM84881_PHY is not set
# CONFIG_BCM87XX_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_CORTINA_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_INTEL_XWAY_PHY is not set
# CONFIG_LSI_ET1011C_PHY is not set
# CONFIG_MARVELL_PHY is not set
# CONFIG_MARVELL_10G_PHY is not set
# CONFIG_MICREL_PHY is not set
# CONFIG_MICROCHIP_PHY is not set
# CONFIG_MICROCHIP_T1_PHY is not set
# CONFIG_MICROSEMI_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_NXP_TJA11XX_PHY is not set
# CONFIG_QSEMI_PHY is not setCONFIG_REALTEK_PHY=y
# CONFIG_RENESAS_PHY is not set
# CONFIG_ROCKCHIP_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_TERANETICS_PHY is not set
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
# CONFIG_DP83848_PHY is not set
# CONFIG_DP83867_PHY is not set
# CONFIG_DP83869_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_XILINX_GMII2RGMII is not set
# CONFIG_MICREL_KS8995MA is not setCONFIG_MDIO_DEVICE=yCONFIG_MDIO_BUS=yCONFIG_MDIO_DEVRES=y
# CONFIG_MDIO_BITBANG is not set
# CONFIG_MDIO_BCM_UNIMAC is not set
# CONFIG_MDIO_MVUSB is not set
# CONFIG_MDIO_MSCC_MIIM is not set
# CONFIG_MDIO_THUNDER is not set
#
# MDIO Multiplexers
#
#
# PCS device drivers
#
# CONFIG_PCS_XPCS is not set
# end of PCS device drivers
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not setCONFIG_USB_NET_DRIVERS=y
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not setCONFIG_USB_RTL8152=m
# CONFIG_USB_LAN78XX is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_HSO is not set
# CONFIG_USB_IPHETH is not setCONFIG_WLAN=yCONFIG_WLAN_VENDOR_ADMTEK=y
# CONFIG_ADM8211 is not setCONFIG_WLAN_VENDOR_ATH=y
# CONFIG_ATH_DEBUG is not set
# CONFIG_ATH5K is not set
# CONFIG_ATH5K_PCI is not set
# CONFIG_ATH9K is not set
# CONFIG_ATH9K_HTC is not set
# CONFIG_CARL9170 is not set
# CONFIG_ATH6KL is not set
# CONFIG_AR5523 is not set
# CONFIG_WIL6210 is not set
# CONFIG_ATH10K is not set
# CONFIG_WCN36XX is not set
# CONFIG_ATH11K is not setCONFIG_WLAN_VENDOR_ATMEL=y
# CONFIG_ATMEL is not set
# CONFIG_AT76C50X_USB is not setCONFIG_WLAN_VENDOR_BROADCOM=y
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
# CONFIG_BRCMSMAC is not set
# CONFIG_BRCMFMAC is not setCONFIG_WLAN_VENDOR_CISCO=y
# CONFIG_AIRO is not setCONFIG_WLAN_VENDOR_INTEL=y
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_IWL4965 is not set
# CONFIG_IWL3945 is not set
# CONFIG_IWLWIFI is not setCONFIG_WLAN_VENDOR_INTERSIL=y
# CONFIG_HOSTAP is not set
# CONFIG_HERMES is not set
# CONFIG_P54_COMMON is not set
# CONFIG_PRISM54 is not setCONFIG_WLAN_VENDOR_MARVELL=y
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
# CONFIG_MWIFIEX is not set
# CONFIG_MWL8K is not setCONFIG_WLAN_VENDOR_MEDIATEK=y
# CONFIG_MT7601U is not set
# CONFIG_MT76x0U is not set
# CONFIG_MT76x0E is not set
# CONFIG_MT76x2E is not set
# CONFIG_MT76x2U is not set
# CONFIG_MT7603E is not set
# CONFIG_MT7615E is not set
# CONFIG_MT7663U is not set
# CONFIG_MT7663S is not set
# CONFIG_MT7915E is not setCONFIG_WLAN_VENDOR_MICROCHIP=y
# CONFIG_WILC1000_SDIO is not set
# CONFIG_WILC1000_SPI is not setCONFIG_WLAN_VENDOR_RALINK=y
# CONFIG_RT2X00 is not setCONFIG_WLAN_VENDOR_REALTEK=y
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not setCONFIG_RTL_CARDS=m
# CONFIG_RTL8192CE is not set
# CONFIG_RTL8192SE is not set
# CONFIG_RTL8192DE is not set
# CONFIG_RTL8723AE is not set
# CONFIG_RTL8723BE is not set
# CONFIG_RTL8188EE is not set
# CONFIG_RTL8192EE is not set
# CONFIG_RTL8821AE is not set
# CONFIG_RTL8192CU is not set
# CONFIG_RTL8XXXU is not set
# CONFIG_RTW88 is not setCONFIG_WLAN_VENDOR_RSI=y
# CONFIG_RSI_91X is not setCONFIG_WLAN_VENDOR_ST=y
# CONFIG_CW1200 is not setCONFIG_WLAN_VENDOR_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not setCONFIG_WLAN_VENDOR_ZYDAS=y
# CONFIG_USB_ZD1201 is not set
# CONFIG_ZD1211RW is not setCONFIG_WLAN_VENDOR_QUANTENNA=y
# CONFIG_QTNFMAC_PCIE is not setCONFIG_MAC80211_HWSIM=m
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_VIRT_WIFI is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers #
# CONFIG_WAN is not set CONFIG_IEEE802154_DRIVERS=m
# CONFIG_IEEE802154_FAKELB is not set
# CONFIG_IEEE802154_AT86RF230 is not set
# CONFIG_IEEE802154_MRF24J40 is not set
# CONFIG_IEEE802154_CC2520 is not set
# CONFIG_IEEE802154_ATUSB is not set
# CONFIG_IEEE802154_ADF7242 is not set
# CONFIG_IEEE802154_CA8210 is not set
# CONFIG_IEEE802154_MCR20A is not set
# CONFIG_IEEE802154_HWSIM is not set CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_VMXNET3 is not set
# CONFIG_FUJITSU_ES is not set
# CONFIG_HYPERV_NET is not setCONFIG_NETDEVSIM=m
# CONFIG_NET_FAILOVER is not set
# CONFIG_ISDN is not set
# CONFIG_NVM is not set
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_LEDS=yCONFIG_INPUT_FF_MEMLESS=mCONFIG_INPUT_POLLDEV=mCONFIG_INPUT_SPARSEKMAP=m
# CONFIG_INPUT_MATRIXKMAP is not set
#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not setCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_JOYDEV=mCONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
# CONFIG_KEYBOARD_APPLESPI is not setCONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1050 is not set
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_DLINK_DIR685 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_SAMSUNG is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_TM2_TOUCHKEY is not set
# CONFIG_KEYBOARD_XTKBD is not setCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_MOUSE_PS2_ALPS=yCONFIG_MOUSE_PS2_BYD=yCONFIG_MOUSE_PS2_LOGIPS2PP=yCONFIG_MOUSE_PS2_SYNAPTICS=yCONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=yCONFIG_MOUSE_PS2_CYPRESS=yCONFIG_MOUSE_PS2_LIFEBOOK=yCONFIG_MOUSE_PS2_TRACKPOINT=yCONFIG_MOUSE_PS2_ELANTECH=yCONFIG_MOUSE_PS2_ELANTECH_SMBUS=yCONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not setCONFIG_MOUSE_PS2_FOCALTECH=yCONFIG_MOUSE_PS2_VMMOUSE=yCONFIG_MOUSE_PS2_SMBUS=yCONFIG_MOUSE_SERIAL=m
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not setCONFIG_MOUSE_CYAPA=mCONFIG_MOUSE_ELAN_I2C=mCONFIG_MOUSE_ELAN_I2C_I2C=yCONFIG_MOUSE_ELAN_I2C_SMBUS=yCONFIG_MOUSE_VSXXXAA=m
# CONFIG_MOUSE_GPIO is not setCONFIG_MOUSE_SYNAPTICS_I2C=m
# CONFIG_MOUSE_SYNAPTICS_USB is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not setCONFIG_RMI4_CORE=mCONFIG_RMI4_I2C=mCONFIG_RMI4_SPI=mCONFIG_RMI4_SMB=mCONFIG_RMI4_F03=yCONFIG_RMI4_F03_SERIO=mCONFIG_RMI4_2D_SENSOR=yCONFIG_RMI4_F11=yCONFIG_RMI4_F12=yCONFIG_RMI4_F30=yCONFIG_RMI4_F34=y
# CONFIG_RMI4_F3A is not set
# CONFIG_RMI4_F54 is not setCONFIG_RMI4_F55=y
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_ARCH_MIGHT_HAVE_PC_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not setCONFIG_SERIO_LIBPS2=yCONFIG_SERIO_RAW=mCONFIG_SERIO_ALTERA_PS2=m
# CONFIG_SERIO_PS2MULT is not setCONFIG_SERIO_ARC_PS2=mCONFIG_HYPERV_KEYBOARD=m
# CONFIG_SERIO_GPIO_PS2 is not set
# CONFIG_USERIO is not set
# CONFIG_GAMEPORT is not set
# end of Hardware I/O ports # end of Input device support
#
# Character devices
#CONFIG_TTY=yCONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_VT_CONSOLE_SLEEP=yCONFIG_HW_CONSOLE=yCONFIG_VT_HW_CONSOLE_BINDING=yCONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not setCONFIG_LDISC_AUTOLOAD=y
#
# Serial drivers
#CONFIG_SERIAL_EARLYCON=y CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_16550A_VARIANTS is not set # CONFIG_SERIAL_8250_FINTEK is not set CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_DMA=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_EXAR=y CONFIG_SERIAL_8250_NR_UARTS=64 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set CONFIG_SERIAL_8250_RSA=y CONFIG_SERIAL_8250_DWLIB=y CONFIG_SERIAL_8250_DW=y
# CONFIG_SERIAL_8250_RT288X is not set CONFIG_SERIAL_8250_LPSS=y CONFIG_SERIAL_8250_MID=y
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_UARTLITE is not setCONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=yCONFIG_SERIAL_JSM=m
# CONFIG_SERIAL_LANTIQ is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not setCONFIG_SERIAL_ARC=mCONFIG_SERIAL_ARC_NR_PORTS=1
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_SERIAL_FSL_LINFLEXUART is not set
# CONFIG_SERIAL_SPRD is not set
# end of Serial drivers
CONFIG_SERIAL_MCTRL_GPIO=yCONFIG_SERIAL_NONSTANDARD=y
# CONFIG_ROCKETPORT is not setCONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not setCONFIG_SYNCLINK=mCONFIG_SYNCLINKMP=mCONFIG_SYNCLINK_GT=m
# CONFIG_ISI is not setCONFIG_N_HDLC=mCONFIG_N_GSM=mCONFIG_NOZOMI=m
# CONFIG_NULL_TTY is not set
# CONFIG_TRACE_SINK is not setCONFIG_HVC_DRIVER=yCONFIG_HVC_IRQ=yCONFIG_HVC_XEN=yCONFIG_HVC_XEN_FRONTEND=y
# CONFIG_SERIAL_DEV_BUS is not setCONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not setCONFIG_PPDEV=mCONFIG_VIRTIO_CONSOLE=mCONFIG_IPMI_HANDLER=mCONFIG_IPMI_DMI_DECODE=yCONFIG_IPMI_PLAT_DATA=yCONFIG_IPMI_PANIC_EVENT=yCONFIG_IPMI_PANIC_STRING=yCONFIG_IPMI_DEVICE_INTERFACE=mCONFIG_IPMI_SI=mCONFIG_IPMI_SSIF=mCONFIG_IPMI_WATCHDOG=mCONFIG_IPMI_POWEROFF=mCONFIG_HW_RANDOM=yCONFIG_HW_RANDOM_TIMERIOMEM=mCONFIG_HW_RANDOM_INTEL=mCONFIG_HW_RANDOM_AMD=m
# CONFIG_HW_RANDOM_BA431 is not setCONFIG_HW_RANDOM_VIA=mCONFIG_HW_RANDOM_VIRTIO=y
# CONFIG_HW_RANDOM_XIPHERA is not set
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not setCONFIG_DEVMEM=y
# CONFIG_DEVKMEM is not setCONFIG_NVRAM=yCONFIG_RAW_DRIVER=yCONFIG_MAX_RAW_DEVS=8192CONFIG_DEVPORT=yCONFIG_HPET=yCONFIG_HPET_MMAP=y
# CONFIG_HPET_MMAP_DEFAULT is not setCONFIG_HANGCHECK_TIMER=mCONFIG_UV_MMTIMER=mCONFIG_TCG_TPM=yCONFIG_HW_RANDOM_TPM=yCONFIG_TCG_TIS_CORE=yCONFIG_TCG_TIS=y
# CONFIG_TCG_TIS_SPI is not setCONFIG_TCG_TIS_I2C_ATMEL=mCONFIG_TCG_TIS_I2C_INFINEON=mCONFIG_TCG_TIS_I2C_NUVOTON=mCONFIG_TCG_NSC=mCONFIG_TCG_ATMEL=mCONFIG_TCG_INFINEON=m
# CONFIG_TCG_XEN is not setCONFIG_TCG_CRB=y
# CONFIG_TCG_VTPM_PROXY is not setCONFIG_TCG_TIS_ST33ZP24=mCONFIG_TCG_TIS_ST33ZP24_I2C=m
# CONFIG_TCG_TIS_ST33ZP24_SPI is not setCONFIG_TELCLOCK=m
# CONFIG_XILLYBUS is not set
# end of Character devices
# CONFIG_RANDOM_TRUST_CPU is not set
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set
#
# I2C support
#CONFIG_I2C=yCONFIG_ACPI_I2C_OPREGION=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_COMPAT=yCONFIG_I2C_CHARDEV=mCONFIG_I2C_MUX=m
#
# Multiplexer I2C Chip support
#
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_LTC4306 is not set
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
# CONFIG_I2C_MUX_REG is not setCONFIG_I2C_MUX_MLXCPLD=m
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_SMBUS=yCONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not setCONFIG_I2C_AMD756=mCONFIG_I2C_AMD756_S4882=mCONFIG_I2C_AMD8111=m
# CONFIG_I2C_AMD_MP2 is not setCONFIG_I2C_I801=yCONFIG_I2C_ISCH=mCONFIG_I2C_ISMT=mCONFIG_I2C_PIIX4=mCONFIG_I2C_NFORCE2=mCONFIG_I2C_NFORCE2_S4985=m
# CONFIG_I2C_NVIDIA_GPU is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not setCONFIG_I2C_SIS96X=mCONFIG_I2C_VIA=mCONFIG_I2C_VIAPRO=m
#
# ACPI drivers
#CONFIG_I2C_SCMI=m
#
# I2C system bus drivers (mostly embedded / system-on-chip) #
# CONFIG_I2C_CBUS_GPIO is not set CONFIG_I2C_DESIGNWARE_CORE=m
# CONFIG_I2C_DESIGNWARE_SLAVE is not set CONFIG_I2C_DESIGNWARE_PLATFORM=m CONFIG_I2C_DESIGNWARE_BAYTRAIL=y
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_EMEV2 is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set CONFIG_I2C_PCA_PLATFORM=mCONFIG_I2C_SIMTEC=m
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not setCONFIG_I2C_PARPORT=m
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#CONFIG_I2C_MLXCPLD=m
# end of I2C Hardware Bus support
CONFIG_I2C_STUB=m
# CONFIG_I2C_SLAVE is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# end of I2C support
# CONFIG_I3C is not setCONFIG_SPI=y
# CONFIG_SPI_DEBUG is not setCONFIG_SPI_MASTER=y
# CONFIG_SPI_MEM is not set
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_AXI_SPI_ENGINE is not set
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_BUTTERFLY is not set
# CONFIG_SPI_CADENCE is not set
# CONFIG_SPI_DESIGNWARE is not set
# CONFIG_SPI_NXP_FLEXSPI is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_LM70_LLP is not set
# CONFIG_SPI_LANTIQ_SSC is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PXA2XX is not set
# CONFIG_SPI_ROCKCHIP is not set
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_SIFIVE is not set
# CONFIG_SPI_MXIC is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_ZYNQMP_GQSPI is not set
# CONFIG_SPI_AMD is not set
#
# SPI Multiplexer support
#
# CONFIG_SPI_MUX is not set
#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_LOOPBACK_TEST is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_SPI_SLAVE is not setCONFIG_SPI_DYNAMIC=y
# CONFIG_SPMI is not set
# CONFIG_HSI is not setCONFIG_PPS=y
# CONFIG_PPS_DEBUG is not set
#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not setCONFIG_PPS_CLIENT_LDISC=mCONFIG_PPS_CLIENT_PARPORT=mCONFIG_PPS_CLIENT_GPIO=m
#
# PPS generators support
#
#
# PTP clock support
#CONFIG_PTP_1588_CLOCK=y
# CONFIG_DP83640_PHY is not set
# CONFIG_PTP_1588_CLOCK_INES is not setCONFIG_PTP_1588_CLOCK_KVM=m
# CONFIG_PTP_1588_CLOCK_IDT82P33 is not set
# CONFIG_PTP_1588_CLOCK_IDTCM is not set
# CONFIG_PTP_1588_CLOCK_VMW is not set
# end of PTP clock support
CONFIG_PINCTRL=yCONFIG_PINMUX=yCONFIG_PINCONF=yCONFIG_GENERIC_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not setCONFIG_PINCTRL_AMD=m
# CONFIG_PINCTRL_MCP23S08 is not set
# CONFIG_PINCTRL_SX150X is not setCONFIG_PINCTRL_BAYTRAIL=y
# CONFIG_PINCTRL_CHERRYVIEW is not set
# CONFIG_PINCTRL_LYNXPOINT is not setCONFIG_PINCTRL_INTEL=yCONFIG_PINCTRL_BROXTON=mCONFIG_PINCTRL_CANNONLAKE=mCONFIG_PINCTRL_CEDARFORK=mCONFIG_PINCTRL_DENVERTON=m
# CONFIG_PINCTRL_EMMITSBURG is not setCONFIG_PINCTRL_GEMINILAKE=m
# CONFIG_PINCTRL_ICELAKE is not set
# CONFIG_PINCTRL_JASPERLAKE is not setCONFIG_PINCTRL_LEWISBURG=mCONFIG_PINCTRL_SUNRISEPOINT=m
# CONFIG_PINCTRL_TIGERLAKE is not set
#
# Renesas pinctrl drivers
#
# end of Renesas pinctrl drivers
CONFIG_GPIOLIB=yCONFIG_GPIOLIB_FASTPATH_LIMIT=512CONFIG_GPIO_ACPI=yCONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not setCONFIG_GPIO_SYSFS=yCONFIG_GPIO_CDEV=yCONFIG_GPIO_CDEV_V1=yCONFIG_GPIO_GENERIC=m
#
# Memory mapped GPIO drivers
#CONFIG_GPIO_AMDPT=m
# CONFIG_GPIO_DWAPB is not set
# CONFIG_GPIO_EXAR is not set
# CONFIG_GPIO_GENERIC_PLATFORM is not setCONFIG_GPIO_ICH=m
# CONFIG_GPIO_MB86S7X is not set
# CONFIG_GPIO_VX855 is not set
# CONFIG_GPIO_XILINX is not set
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers
#
# Port-mapped I/O GPIO drivers
#
# CONFIG_GPIO_F7188X is not set
# CONFIG_GPIO_IT87 is not set
# CONFIG_GPIO_SCH is not set
# CONFIG_GPIO_SCH311X is not set
# CONFIG_GPIO_WINBOND is not set
# CONFIG_GPIO_WS16C48 is not set
# end of Port-mapped I/O GPIO drivers
#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCA9570 is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_TPIC2810 is not set
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#
# end of MFD GPIO expanders
#
# PCI GPIO expanders
#
# CONFIG_GPIO_AMD8111 is not set
# CONFIG_GPIO_BT8XX is not set
# CONFIG_GPIO_ML_IOH is not set
# CONFIG_GPIO_PCI_IDIO_16 is not set
# CONFIG_GPIO_PCIE_IDIO_24 is not set
# CONFIG_GPIO_RDC321X is not set
# end of PCI GPIO expanders
#
# SPI GPIO expanders
#
# CONFIG_GPIO_MAX3191X is not set
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_PISOSR is not set
# CONFIG_GPIO_XRA1403 is not set
# end of SPI GPIO expanders
#
# USB GPIO expanders
#
# end of USB GPIO expanders
# CONFIG_GPIO_AGGREGATOR is not set
# CONFIG_GPIO_MOCKUP is not set
# CONFIG_W1 is not setCONFIG_POWER_RESET=y
# CONFIG_POWER_RESET_RESTART is not setCONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not setCONFIG_POWER_SUPPLY_HWMON=y
# CONFIG_PDA_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_CHARGER_ADP5061 is not set
# CONFIG_BATTERY_CW2015 is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_CHARGER_SBS is not set
# CONFIG_MANAGER_SBS is not set
# CONFIG_BATTERY_BQ27XXX is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_LT3651 is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ2515X is not set
# CONFIG_CHARGER_BQ25890 is not set
# CONFIG_CHARGER_BQ25980 is not setCONFIG_CHARGER_SMB347=m
# CONFIG_BATTERY_GAUGE_LTC2941 is not set
# CONFIG_CHARGER_RT9455 is not set
# CONFIG_CHARGER_BD99954 is not setCONFIG_HWMON=yCONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#CONFIG_SENSORS_ABITUGURU=mCONFIG_SENSORS_ABITUGURU3=m
# CONFIG_SENSORS_AD7314 is not setCONFIG_SENSORS_AD7414=mCONFIG_SENSORS_AD7418=mCONFIG_SENSORS_ADM1021=mCONFIG_SENSORS_ADM1025=mCONFIG_SENSORS_ADM1026=mCONFIG_SENSORS_ADM1029=mCONFIG_SENSORS_ADM1031=m
# CONFIG_SENSORS_ADM1177 is not setCONFIG_SENSORS_ADM9240=mCONFIG_SENSORS_ADT7X10=m
# CONFIG_SENSORS_ADT7310 is not setCONFIG_SENSORS_ADT7410=mCONFIG_SENSORS_ADT7411=mCONFIG_SENSORS_ADT7462=mCONFIG_SENSORS_ADT7470=mCONFIG_SENSORS_ADT7475=m
# CONFIG_SENSORS_AS370 is not setCONFIG_SENSORS_ASC7621=m
# CONFIG_SENSORS_AXI_FAN_CONTROL is not setCONFIG_SENSORS_K8TEMP=mCONFIG_SENSORS_K10TEMP=mCONFIG_SENSORS_FAM15H_POWER=m
# CONFIG_SENSORS_AMD_ENERGY is not setCONFIG_SENSORS_APPLESMC=mCONFIG_SENSORS_ASB100=m
# CONFIG_SENSORS_ASPEED is not setCONFIG_SENSORS_ATXP1=m
# CONFIG_SENSORS_CORSAIR_CPRO is not set
# CONFIG_SENSORS_DRIVETEMP is not setCONFIG_SENSORS_DS620=mCONFIG_SENSORS_DS1621=mCONFIG_SENSORS_DELL_SMM=mCONFIG_SENSORS_I5K_AMB=mCONFIG_SENSORS_F71805F=mCONFIG_SENSORS_F71882FG=mCONFIG_SENSORS_F75375S=mCONFIG_SENSORS_FSCHMD=m
# CONFIG_SENSORS_FTSTEUTATES is not setCONFIG_SENSORS_GL518SM=mCONFIG_SENSORS_GL520SM=mCONFIG_SENSORS_G760A=m
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_HIH6130 is not setCONFIG_SENSORS_IBMAEM=mCONFIG_SENSORS_IBMPEX=mCONFIG_SENSORS_I5500=mCONFIG_SENSORS_CORETEMP=mCONFIG_SENSORS_IT87=mCONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_POWR1220 is not setCONFIG_SENSORS_LINEAGE=m
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2947_I2C is not set
# CONFIG_SENSORS_LTC2947_SPI is not set
# CONFIG_SENSORS_LTC2990 is not setCONFIG_SENSORS_LTC4151=mCONFIG_SENSORS_LTC4215=m
# CONFIG_SENSORS_LTC4222 is not setCONFIG_SENSORS_LTC4245=m
# CONFIG_SENSORS_LTC4260 is not setCONFIG_SENSORS_LTC4261=m
# CONFIG_SENSORS_MAX1111 is not setCONFIG_SENSORS_MAX16065=mCONFIG_SENSORS_MAX1619=mCONFIG_SENSORS_MAX1668=mCONFIG_SENSORS_MAX197=m
# CONFIG_SENSORS_MAX31722 is not set
# CONFIG_SENSORS_MAX31730 is not set
# CONFIG_SENSORS_MAX6621 is not setCONFIG_SENSORS_MAX6639=mCONFIG_SENSORS_MAX6642=mCONFIG_SENSORS_MAX6650=mCONFIG_SENSORS_MAX6697=m
# CONFIG_SENSORS_MAX31790 is not setCONFIG_SENSORS_MCP3021=m
# CONFIG_SENSORS_MLXREG_FAN is not set
# CONFIG_SENSORS_TC654 is not set
# CONFIG_SENSORS_MR75203 is not set
# CONFIG_SENSORS_ADCXX is not setCONFIG_SENSORS_LM63=m
# CONFIG_SENSORS_LM70 is not setCONFIG_SENSORS_LM73=mCONFIG_SENSORS_LM75=mCONFIG_SENSORS_LM77=mCONFIG_SENSORS_LM78=mCONFIG_SENSORS_LM80=mCONFIG_SENSORS_LM83=mCONFIG_SENSORS_LM85=mCONFIG_SENSORS_LM87=mCONFIG_SENSORS_LM90=mCONFIG_SENSORS_LM92=mCONFIG_SENSORS_LM93=mCONFIG_SENSORS_LM95234=mCONFIG_SENSORS_LM95241=mCONFIG_SENSORS_LM95245=mCONFIG_SENSORS_PC87360=mCONFIG_SENSORS_PC87427=mCONFIG_SENSORS_NTC_THERMISTOR=m
# CONFIG_SENSORS_NCT6683 is not setCONFIG_SENSORS_NCT6775=m
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_NPCM7XX is not setCONFIG_SENSORS_PCF8591=mCONFIG_PMBUS=mCONFIG_SENSORS_PMBUS=m
# CONFIG_SENSORS_ADM1266 is not setCONFIG_SENSORS_ADM1275=m
# CONFIG_SENSORS_BEL_PFE is not set
# CONFIG_SENSORS_IBM_CFFPS is not set
# CONFIG_SENSORS_INSPUR_IPSPS is not set
# CONFIG_SENSORS_IR35221 is not set
# CONFIG_SENSORS_IR38064 is not set
# CONFIG_SENSORS_IRPS5401 is not set
# CONFIG_SENSORS_ISL68137 is not setCONFIG_SENSORS_LM25066=mCONFIG_SENSORS_LTC2978=m
# CONFIG_SENSORS_LTC3815 is not setCONFIG_SENSORS_MAX16064=m
# CONFIG_SENSORS_MAX16601 is not set
# CONFIG_SENSORS_MAX20730 is not set
# CONFIG_SENSORS_MAX20751 is not set
# CONFIG_SENSORS_MAX31785 is not setCONFIG_SENSORS_MAX34440=mCONFIG_SENSORS_MAX8688=m
# CONFIG_SENSORS_MP2975 is not set
# CONFIG_SENSORS_PXE1610 is not set
# CONFIG_SENSORS_TPS40422 is not set
# CONFIG_SENSORS_TPS53679 is not setCONFIG_SENSORS_UCD9000=mCONFIG_SENSORS_UCD9200=m
# CONFIG_SENSORS_XDPE122 is not setCONFIG_SENSORS_ZL6100=mCONFIG_SENSORS_SHT15=mCONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHTC1 is not setCONFIG_SENSORS_SIS5595=mCONFIG_SENSORS_DME1737=mCONFIG_SENSORS_EMC1403=m
# CONFIG_SENSORS_EMC2103 is not setCONFIG_SENSORS_EMC6W201=mCONFIG_SENSORS_SMSC47M1=mCONFIG_SENSORS_SMSC47M192=mCONFIG_SENSORS_SMSC47B397=mCONFIG_SENSORS_SCH56XX_COMMON=mCONFIG_SENSORS_SCH5627=mCONFIG_SENSORS_SCH5636=m
# CONFIG_SENSORS_STTS751 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_ADC128D818 is not setCONFIG_SENSORS_ADS7828=m
# CONFIG_SENSORS_ADS7871 is not setCONFIG_SENSORS_AMC6821=mCONFIG_SENSORS_INA209=mCONFIG_SENSORS_INA2XX=m
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not setCONFIG_SENSORS_THMC50=mCONFIG_SENSORS_TMP102=m
# CONFIG_SENSORS_TMP103 is not set
# CONFIG_SENSORS_TMP108 is not setCONFIG_SENSORS_TMP401=mCONFIG_SENSORS_TMP421=m
# CONFIG_SENSORS_TMP513 is not setCONFIG_SENSORS_VIA_CPUTEMP=mCONFIG_SENSORS_VIA686A=mCONFIG_SENSORS_VT1211=mCONFIG_SENSORS_VT8231=m
# CONFIG_SENSORS_W83773G is not setCONFIG_SENSORS_W83781D=mCONFIG_SENSORS_W83791D=mCONFIG_SENSORS_W83792D=mCONFIG_SENSORS_W83793=mCONFIG_SENSORS_W83795=m
# CONFIG_SENSORS_W83795_FANCTRL is not setCONFIG_SENSORS_W83L785TS=mCONFIG_SENSORS_W83L786NG=mCONFIG_SENSORS_W83627HF=mCONFIG_SENSORS_W83627EHF=m
# CONFIG_SENSORS_XGENE is not set
#
# ACPI drivers
#CONFIG_SENSORS_ACPI_POWER=m CONFIG_SENSORS_ATK0110=mCONFIG_THERMAL=y
# CONFIG_THERMAL_NETLINK is not set
# CONFIG_THERMAL_STATISTICS is not set CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0 CONFIG_THERMAL_HWMON=y CONFIG_THERMAL_WRITABLE_TRIPS=y CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set CONFIG_THERMAL_GOV_FAIR_SHARE=y CONFIG_THERMAL_GOV_STEP_WISE=y CONFIG_THERMAL_GOV_BANG_BANG=y CONFIG_THERMAL_GOV_USER_SPACE=y
# CONFIG_THERMAL_EMULATION is not set
#
# Intel thermal drivers
#CONFIG_INTEL_POWERCLAMP=mCONFIG_X86_PKG_TEMP_THERMAL=mCONFIG_INTEL_SOC_DTS_IOSF_CORE=m
# CONFIG_INTEL_SOC_DTS_THERMAL is not set
#
# ACPI INT340X thermal drivers
#CONFIG_INT340X_THERMAL=mCONFIG_ACPI_THERMAL_REL=m
# CONFIG_INT3406_THERMAL is not setCONFIG_PROC_THERMAL_MMIO_RAPL=y
# end of ACPI INT340X thermal drivers
CONFIG_INTEL_PCH_THERMAL=m
# end of Intel thermal drivers
CONFIG_WATCHDOG=yCONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not setCONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=yCONFIG_WATCHDOG_OPEN_TIMEOUT=0CONFIG_WATCHDOG_SYSFS=y
#
# Watchdog Pretimeout Governors
#
# CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set
#
# Watchdog Device Drivers
#CONFIG_SOFT_WATCHDOG=mCONFIG_WDAT_WDT=m
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_MLX_WDT is not set
# CONFIG_CADENCE_WATCHDOG is not set
# CONFIG_DW_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not setCONFIG_ALIM1535_WDT=mCONFIG_ALIM7101_WDT=m
# CONFIG_EBC_C384_WDT is not setCONFIG_F71808E_WDT=mCONFIG_SP5100_TCO=mCONFIG_SBC_FITPC2_WATCHDOG=m
# CONFIG_EUROTECH_WDT is not setCONFIG_IB700_WDT=mCONFIG_IBMASR=m
# CONFIG_WAFER_WDT is not setCONFIG_I6300ESB_WDT=yCONFIG_IE6XX_WDT=mCONFIG_ITCO_WDT=yCONFIG_ITCO_VENDOR_SUPPORT=yCONFIG_IT8712F_WDT=mCONFIG_IT87_WDT=mCONFIG_HP_WATCHDOG=mCONFIG_HPWDT_NMI_DECODING=y
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not setCONFIG_NV_TCO=m
# CONFIG_60XX_WDT is not set
# CONFIG_CPU5_WDT is not setCONFIG_SMSC_SCH311X_WDT=m
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_TQMX86_WDT is not setCONFIG_VIA_WDT=mCONFIG_W83627HF_WDT=mCONFIG_W83877F_WDT=mCONFIG_W83977F_WDT=mCONFIG_MACHZ_WDT=m
# CONFIG_SBC_EPX_C3_WATCHDOG is not setCONFIG_INTEL_MEI_WDT=m
# CONFIG_NI903X_WDT is not set
# CONFIG_NIC7018_WDT is not set
# CONFIG_MEN_A21_WDT is not setCONFIG_XEN_WDT=m
#
# PCI-based Watchdog Cards
#CONFIG_PCIPCWATCHDOG=mCONFIG_WDTPCI=m
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not setCONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not setCONFIG_BCMA_POSSIBLE=yCONFIG_BCMA=mCONFIG_BCMA_HOST_PCI_POSSIBLE=yCONFIG_BCMA_HOST_PCI=y
# CONFIG_BCMA_HOST_SOC is not setCONFIG_BCMA_DRIVER_PCI=yCONFIG_BCMA_DRIVER_GMAC_CMN=yCONFIG_BCMA_DRIVER_GPIO=y
# CONFIG_BCMA_DEBUG is not set
#
# Multifunction device drivers
#CONFIG_MFD_CORE=y
# CONFIG_MFD_AS3711 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_BD9571MWV is not set
# CONFIG_MFD_AXP20X_I2C is not set
# CONFIG_MFD_MADERA is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_DLN2 is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_MFD_MP2629 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_MFD_INTEL_QUARK_I2C_GPIO is not setCONFIG_LPC_ICH=yCONFIG_LPC_SCH=m
# CONFIG_INTEL_SOC_PMIC_CHTDC_TI is not setCONFIG_MFD_INTEL_LPSS=yCONFIG_MFD_INTEL_LPSS_ACPI=yCONFIG_MFD_INTEL_LPSS_PCI=y
# CONFIG_MFD_INTEL_PMC_BXT is not set
# CONFIG_MFD_IQS62X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_MAX14577 is not set
# CONFIG_MFD_MAX77693 is not set
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MT6360 is not set
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not set
# CONFIG_MFD_VIPERBOARD is not set
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_SEC_CORE is not set
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SL28CPLD is not setCONFIG_MFD_SM501=mCONFIG_MFD_SM501_GPIO=y
# CONFIG_MFD_SKY81452 is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_MFD_SYSCON is not set
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_TI_LMU is not set
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS80031 is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TQMX86 is not setCONFIG_MFD_VX855=m
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_INTEL_M10_BMC is not set
# end of Multifunction device drivers
# CONFIG_REGULATOR is not setCONFIG_RC_CORE=mCONFIG_RC_MAP=mCONFIG_LIRC=yCONFIG_RC_DECODERS=yCONFIG_IR_NEC_DECODER=mCONFIG_IR_RC5_DECODER=mCONFIG_IR_RC6_DECODER=mCONFIG_IR_JVC_DECODER=mCONFIG_IR_SONY_DECODER=mCONFIG_IR_SANYO_DECODER=m
# CONFIG_IR_SHARP_DECODER is not setCONFIG_IR_MCE_KBD_DECODER=m
# CONFIG_IR_XMP_DECODER is not setCONFIG_IR_IMON_DECODER=m
# CONFIG_IR_RCMM_DECODER is not setCONFIG_RC_DEVICES=y
# CONFIG_RC_ATI_REMOTE is not setCONFIG_IR_ENE=m
# CONFIG_IR_IMON is not set
# CONFIG_IR_IMON_RAW is not set
# CONFIG_IR_MCEUSB is not setCONFIG_IR_ITE_CIR=mCONFIG_IR_FINTEK=mCONFIG_IR_NUVOTON=m
# CONFIG_IR_REDRAT3 is not set
# CONFIG_IR_STREAMZAP is not setCONFIG_IR_WINBOND_CIR=m
# CONFIG_IR_IGORPLUGUSB is not set
# CONFIG_IR_IGUANA is not set
# CONFIG_IR_TTUSBIR is not set
# CONFIG_RC_LOOPBACK is not setCONFIG_IR_SERIAL=mCONFIG_IR_SERIAL_TRANSMITTER=yCONFIG_IR_SIR=m
# CONFIG_RC_XBOX_DVD is not set
# CONFIG_IR_TOY is not setCONFIG_MEDIA_CEC_SUPPORT=y
# CONFIG_CEC_CH7322 is not set
# CONFIG_CEC_SECO is not set
# CONFIG_USB_PULSE8_CEC is not set
# CONFIG_USB_RAINSHADOW_CEC is not setCONFIG_MEDIA_SUPPORT=m
# CONFIG_MEDIA_SUPPORT_FILTER is not set
# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set
#
# Media device types
#CONFIG_MEDIA_CAMERA_SUPPORT=yCONFIG_MEDIA_ANALOG_TV_SUPPORT=yCONFIG_MEDIA_DIGITAL_TV_SUPPORT=yCONFIG_MEDIA_RADIO_SUPPORT=yCONFIG_MEDIA_SDR_SUPPORT=yCONFIG_MEDIA_PLATFORM_SUPPORT=yCONFIG_MEDIA_TEST_SUPPORT=y
# end of Media device types
#
# Media core support
#CONFIG_VIDEO_DEV=mCONFIG_MEDIA_CONTROLLER=yCONFIG_DVB_CORE=m
# end of Media core support
#
# Video4Linux options
#CONFIG_VIDEO_V4L2=mCONFIG_VIDEO_V4L2_I2C=yCONFIG_VIDEO_V4L2_SUBDEV_API=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
# end of Video4Linux options
#
# Media controller options
#
# CONFIG_MEDIA_CONTROLLER_DVB is not set
# end of Media controller options
#
# Digital TV options
#
# CONFIG_DVB_MMAP is not setCONFIG_DVB_NET=yCONFIG_DVB_MAX_ADAPTERS=16CONFIG_DVB_DYNAMIC_MINORS=y
# CONFIG_DVB_DEMUX_SECTION_LOSS_LOG is not set
# CONFIG_DVB_ULE_DEBUG is not set
# end of Digital TV options
#
# Media drivers
#
# CONFIG_MEDIA_USB_SUPPORT is not set
# CONFIG_MEDIA_PCI_SUPPORT is not setCONFIG_RADIO_ADAPTERS=y
# CONFIG_RADIO_SI470X is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_MR800 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_SHARK is not set
# CONFIG_RADIO_SHARK2 is not set
# CONFIG_USB_KEENE is not set
# CONFIG_USB_RAREMONO is not set
# CONFIG_USB_MA901 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_RADIO_SAA7706H is not set
# CONFIG_RADIO_TEF6862 is not set
# CONFIG_RADIO_WL1273 is not setCONFIG_VIDEOBUF2_CORE=mCONFIG_VIDEOBUF2_V4L2=mCONFIG_VIDEOBUF2_MEMOPS=mCONFIG_VIDEOBUF2_VMALLOC=m
# CONFIG_V4L_PLATFORM_DRIVERS is not set
# CONFIG_V4L_MEM2MEM_DRIVERS is not set
# CONFIG_DVB_PLATFORM_DRIVERS is not set
# CONFIG_SDR_PLATFORM_DRIVERS is not set
#
# MMC/SDIO DVB adapters
#
# CONFIG_SMS_SDIO_DRV is not set
# CONFIG_V4L_TEST_DRIVERS is not set
# CONFIG_DVB_TEST_DRIVERS is not set
#
# FireWire (IEEE 1394) Adapters
#
# CONFIG_DVB_FIREDTV is not set
# end of Media drivers
#
# Media ancillary drivers
#CONFIG_MEDIA_ATTACH=yCONFIG_VIDEO_IR_I2C=m
#
# Audio decoders, processors and mixers
#
# CONFIG_VIDEO_TVAUDIO is not set
# CONFIG_VIDEO_TDA7432 is not set
# CONFIG_VIDEO_TDA9840 is not set
# CONFIG_VIDEO_TEA6415C is not set
# CONFIG_VIDEO_TEA6420 is not set
# CONFIG_VIDEO_MSP3400 is not set
# CONFIG_VIDEO_CS3308 is not set
# CONFIG_VIDEO_CS5345 is not set
# CONFIG_VIDEO_CS53L32A is not set
# CONFIG_VIDEO_TLV320AIC23B is not set
# CONFIG_VIDEO_UDA1342 is not set
# CONFIG_VIDEO_WM8775 is not set
# CONFIG_VIDEO_WM8739 is not set
# CONFIG_VIDEO_VP27SMPX is not set
# CONFIG_VIDEO_SONY_BTF_MPX is not set
# end of Audio decoders, processors and mixers
#
# RDS decoders
#
# CONFIG_VIDEO_SAA6588 is not set
# end of RDS decoders
#
# Video decoders
#
# CONFIG_VIDEO_ADV7180 is not set
# CONFIG_VIDEO_ADV7183 is not set
# CONFIG_VIDEO_ADV7604 is not set
# CONFIG_VIDEO_ADV7842 is not set
# CONFIG_VIDEO_BT819 is not set
# CONFIG_VIDEO_BT856 is not set
# CONFIG_VIDEO_BT866 is not set
# CONFIG_VIDEO_KS0127 is not set
# CONFIG_VIDEO_ML86V7667 is not set
# CONFIG_VIDEO_SAA7110 is not set
# CONFIG_VIDEO_SAA711X is not set
# CONFIG_VIDEO_TC358743 is not set
# CONFIG_VIDEO_TVP514X is not set
# CONFIG_VIDEO_TVP5150 is not set
# CONFIG_VIDEO_TVP7002 is not set
# CONFIG_VIDEO_TW2804 is not set
# CONFIG_VIDEO_TW9903 is not set
# CONFIG_VIDEO_TW9906 is not set
# CONFIG_VIDEO_TW9910 is not set
# CONFIG_VIDEO_VPX3220 is not set
#
# Video and audio decoders
#
# CONFIG_VIDEO_SAA717X is not set
# CONFIG_VIDEO_CX25840 is not set
# end of Video decoders
#
# Video encoders
#
# CONFIG_VIDEO_SAA7127 is not set
# CONFIG_VIDEO_SAA7185 is not set
# CONFIG_VIDEO_ADV7170 is not set
# CONFIG_VIDEO_ADV7175 is not set
# CONFIG_VIDEO_ADV7343 is not set
# CONFIG_VIDEO_ADV7393 is not set
# CONFIG_VIDEO_ADV7511 is not set
# CONFIG_VIDEO_AD9389B is not set
# CONFIG_VIDEO_AK881X is not set
# CONFIG_VIDEO_THS8200 is not set
# end of Video encoders
#
# Video improvement chips
#
# CONFIG_VIDEO_UPD64031A is not set
# CONFIG_VIDEO_UPD64083 is not set
# end of Video improvement chips
#
# Audio/Video compression chips
#
# CONFIG_VIDEO_SAA6752HS is not set
# end of Audio/Video compression chips
#
# SDR tuner chips
#
# CONFIG_SDR_MAX2175 is not set
# end of SDR tuner chips
#
# Miscellaneous helper chips
#
# CONFIG_VIDEO_THS7303 is not set
# CONFIG_VIDEO_M52790 is not set
# CONFIG_VIDEO_I2C is not set
# CONFIG_VIDEO_ST_MIPID02 is not set
# end of Miscellaneous helper chips
#
# Camera sensor devices
#
# CONFIG_VIDEO_HI556 is not set
# CONFIG_VIDEO_IMX214 is not set
# CONFIG_VIDEO_IMX219 is not set
# CONFIG_VIDEO_IMX258 is not set
# CONFIG_VIDEO_IMX274 is not set
# CONFIG_VIDEO_IMX290 is not set
# CONFIG_VIDEO_IMX319 is not set
# CONFIG_VIDEO_IMX355 is not set
# CONFIG_VIDEO_OV2640 is not set
# CONFIG_VIDEO_OV2659 is not set
# CONFIG_VIDEO_OV2680 is not set
# CONFIG_VIDEO_OV2685 is not set
# CONFIG_VIDEO_OV2740 is not set
# CONFIG_VIDEO_OV5647 is not set
# CONFIG_VIDEO_OV6650 is not set
# CONFIG_VIDEO_OV5670 is not set
# CONFIG_VIDEO_OV5675 is not set
# CONFIG_VIDEO_OV5695 is not set
# CONFIG_VIDEO_OV7251 is not set
# CONFIG_VIDEO_OV772X is not set
# CONFIG_VIDEO_OV7640 is not set
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_OV7740 is not set
# CONFIG_VIDEO_OV8856 is not set
# CONFIG_VIDEO_OV9640 is not set
# CONFIG_VIDEO_OV9650 is not set
# CONFIG_VIDEO_OV13858 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M001 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9M111 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9T112 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_MT9V111 is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
# CONFIG_VIDEO_M5MOLS is not set
# CONFIG_VIDEO_RDACM20 is not set
# CONFIG_VIDEO_RJ54N1 is not set
# CONFIG_VIDEO_S5K6AA is not set
# CONFIG_VIDEO_S5K6A3 is not set
# CONFIG_VIDEO_S5K4ECGX is not set
# CONFIG_VIDEO_S5K5BAF is not set
# CONFIG_VIDEO_SMIAPP is not set
# CONFIG_VIDEO_ET8EK8 is not set
# CONFIG_VIDEO_S5C73M3 is not set
# end of Camera sensor devices
#
# Lens drivers
#
# CONFIG_VIDEO_AD5820 is not set
# CONFIG_VIDEO_AK7375 is not set
# CONFIG_VIDEO_DW9714 is not set
# CONFIG_VIDEO_DW9768 is not set
# CONFIG_VIDEO_DW9807_VCM is not set
# end of Lens drivers
#
# Flash devices
#
# CONFIG_VIDEO_ADP1653 is not set
# CONFIG_VIDEO_LM3560 is not set
# CONFIG_VIDEO_LM3646 is not set
# end of Flash devices
#
# SPI helper chips
#
# CONFIG_VIDEO_GS1662 is not set
# end of SPI helper chips
#
# Media SPI Adapters
#CONFIG_CXD2880_SPI_DRV=m
# end of Media SPI Adapters
CONFIG_MEDIA_TUNER=m
#
# Customize TV tuners
#CONFIG_MEDIA_TUNER_SIMPLE=mCONFIG_MEDIA_TUNER_TDA18250=mCONFIG_MEDIA_TUNER_TDA8290=mCONFIG_MEDIA_TUNER_TDA827X=mCONFIG_MEDIA_TUNER_TDA18271=mCONFIG_MEDIA_TUNER_TDA9887=mCONFIG_MEDIA_TUNER_TEA5761=mCONFIG_MEDIA_TUNER_TEA5767=mCONFIG_MEDIA_TUNER_MSI001=mCONFIG_MEDIA_TUNER_MT20XX=mCONFIG_MEDIA_TUNER_MT2060=mCONFIG_MEDIA_TUNER_MT2063=mCONFIG_MEDIA_TUNER_MT2266=mCONFIG_MEDIA_TUNER_MT2131=mCONFIG_MEDIA_TUNER_QT1010=mCONFIG_MEDIA_TUNER_XC2028=mCONFIG_MEDIA_TUNER_XC5000=mCONFIG_MEDIA_TUNER_XC4000=mCONFIG_MEDIA_TUNER_MXL5005S=mCONFIG_MEDIA_TUNER_MXL5007T=mCONFIG_MEDIA_TUNER_MC44S803=mCONFIG_MEDIA_TUNER_MAX2165=mCONFIG_MEDIA_TUNER_TDA18218=mCONFIG_MEDIA_TUNER_FC0011=mCONFIG_MEDIA_TUNER_FC0012=mCONFIG_MEDIA_TUNER_FC0013=mCONFIG_MEDIA_TUNER_TDA18212=mCONFIG_MEDIA_TUNER_E4000=mCONFIG_MEDIA_TUNER_FC2580=mCONFIG_MEDIA_TUNER_M88RS6000T=mCONFIG_MEDIA_TUNER_TUA9001=mCONFIG_MEDIA_TUNER_SI2157=mCONFIG_MEDIA_TUNER_IT913X=mCONFIG_MEDIA_TUNER_R820T=mCONFIG_MEDIA_TUNER_MXL301RF=mCONFIG_MEDIA_TUNER_QM1D1C0042=mCONFIG_MEDIA_TUNER_QM1D1B0004=m
# end of Customize TV tuners
#
# Customise DVB Frontends
#
#
# Multistandard (satellite) frontends
#CONFIG_DVB_STB0899=mCONFIG_DVB_STB6100=m
CONFIG_DVB_STV090x=mCONFIG_DVB_STV0910=m
CONFIG_DVB_STV6110x=mCONFIG_DVB_STV6111=mCONFIG_DVB_MXL5XX=mCONFIG_DVB_M88DS3103=m
#
# Multistandard (cable + terrestrial) frontends
#CONFIG_DVB_DRXK=mCONFIG_DVB_TDA18271C2DD=mCONFIG_DVB_SI2165=mCONFIG_DVB_MN88472=mCONFIG_DVB_MN88473=m
#
# DVB-S (satellite) frontends
#CONFIG_DVB_CX24110=mCONFIG_DVB_CX24123=mCONFIG_DVB_MT312=mCONFIG_DVB_ZL10036=mCONFIG_DVB_ZL10039=mCONFIG_DVB_S5H1420=mCONFIG_DVB_STV0288=mCONFIG_DVB_STB6000=mCONFIG_DVB_STV0299=mCONFIG_DVB_STV6110=mCONFIG_DVB_STV0900=mCONFIG_DVB_TDA8083=mCONFIG_DVB_TDA10086=mCONFIG_DVB_TDA8261=mCONFIG_DVB_VES1X93=mCONFIG_DVB_TUNER_ITD1000=mCONFIG_DVB_TUNER_CX24113=mCONFIG_DVB_TDA826X=mCONFIG_DVB_TUA6100=mCONFIG_DVB_CX24116=mCONFIG_DVB_CX24117=mCONFIG_DVB_CX24120=mCONFIG_DVB_SI21XX=mCONFIG_DVB_TS2020=mCONFIG_DVB_DS3000=mCONFIG_DVB_MB86A16=mCONFIG_DVB_TDA10071=m
#
# DVB-T (terrestrial) frontends
#CONFIG_DVB_SP8870=mCONFIG_DVB_SP887X=mCONFIG_DVB_CX22700=mCONFIG_DVB_CX22702=mCONFIG_DVB_S5H1432=mCONFIG_DVB_DRXD=mCONFIG_DVB_L64781=mCONFIG_DVB_TDA1004X=mCONFIG_DVB_NXT6000=mCONFIG_DVB_MT352=mCONFIG_DVB_ZL10353=mCONFIG_DVB_DIB3000MB=mCONFIG_DVB_DIB3000MC=mCONFIG_DVB_DIB7000M=mCONFIG_DVB_DIB7000P=mCONFIG_DVB_DIB9000=mCONFIG_DVB_TDA10048=mCONFIG_DVB_AF9013=mCONFIG_DVB_EC100=mCONFIG_DVB_STV0367=mCONFIG_DVB_CXD2820R=mCONFIG_DVB_CXD2841ER=mCONFIG_DVB_RTL2830=mCONFIG_DVB_RTL2832=mCONFIG_DVB_RTL2832_SDR=mCONFIG_DVB_SI2168=mCONFIG_DVB_ZD1301_DEMOD=mCONFIG_DVB_CXD2880=m
#
# DVB-C (cable) frontends
#CONFIG_DVB_VES1820=mCONFIG_DVB_TDA10021=mCONFIG_DVB_TDA10023=mCONFIG_DVB_STV0297=m
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends #CONFIG_DVB_NXT200X=mCONFIG_DVB_OR51211=mCONFIG_DVB_OR51132=mCONFIG_DVB_BCM3510=mCONFIG_DVB_LGDT330X=mCONFIG_DVB_LGDT3305=mCONFIG_DVB_LGDT3306A=mCONFIG_DVB_LG2160=mCONFIG_DVB_S5H1409=mCONFIG_DVB_AU8522=mCONFIG_DVB_AU8522_DTV=mCONFIG_DVB_AU8522_V4L=mCONFIG_DVB_S5H1411=m
#
# ISDB-T (terrestrial) frontends
#CONFIG_DVB_S921=mCONFIG_DVB_DIB8000=mCONFIG_DVB_MB86A20S=m
#
# ISDB-S (satellite) & ISDB-T (terrestrial) frontends #CONFIG_DVB_TC90522=mCONFIG_DVB_MN88443X=m
#
# Digital terrestrial only tuners/PLL
#CONFIG_DVB_PLL=mCONFIG_DVB_TUNER_DIB0070=mCONFIG_DVB_TUNER_DIB0090=m
#
# SEC control devices for DVB-S
#CONFIG_DVB_DRX39XYJ=mCONFIG_DVB_LNBH25=mCONFIG_DVB_LNBH29=mCONFIG_DVB_LNBP21=mCONFIG_DVB_LNBP22=mCONFIG_DVB_ISL6405=mCONFIG_DVB_ISL6421=mCONFIG_DVB_ISL6423=mCONFIG_DVB_A8293=mCONFIG_DVB_LGS8GL5=mCONFIG_DVB_LGS8GXX=mCONFIG_DVB_ATBM8830=m
CONFIG_DVB_TDA665x=mCONFIG_DVB_IX2505V=mCONFIG_DVB_M88RS2000=mCONFIG_DVB_AF9033=mCONFIG_DVB_HORUS3A=mCONFIG_DVB_ASCOT2E=mCONFIG_DVB_HELENE=m
#
# Common Interface (EN50221) controller drivers
#CONFIG_DVB_CXD2099=mCONFIG_DVB_SP2=m
# end of Customise DVB Frontends
#
# Tools to develop new frontends
#
# CONFIG_DVB_DUMMY_FE is not set
# end of Media ancillary drivers
#
# Graphics support
#
# CONFIG_AGP is not setCONFIG_INTEL_GTT=mCONFIG_VGA_ARB=yCONFIG_VGA_ARB_MAX_GPUS=64CONFIG_VGA_SWITCHEROO=yCONFIG_DRM=mCONFIG_DRM_MIPI_DSI=yCONFIG_DRM_DP_AUX_CHARDEV=y
# CONFIG_DRM_DEBUG_SELFTEST is not setCONFIG_DRM_KMS_HELPER=mCONFIG_DRM_KMS_FB_HELPER=yCONFIG_DRM_FBDEV_EMULATION=yCONFIG_DRM_FBDEV_OVERALLOC=100CONFIG_DRM_LOAD_EDID_FIRMWARE=y
# CONFIG_DRM_DP_CEC is not setCONFIG_DRM_TTM=mCONFIG_DRM_TTM_DMA_PAGE_POOL=yCONFIG_DRM_VRAM_HELPER=mCONFIG_DRM_TTM_HELPER=mCONFIG_DRM_GEM_SHMEM_HELPER=y
#
# I2C encoder or helper chips
#CONFIG_DRM_I2C_CH7006=mCONFIG_DRM_I2C_SIL164=m
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_I2C_NXP_TDA9950 is not set
# end of I2C encoder or helper chips
#
# ARM devices
#
# end of ARM devices
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_AMDGPU is not set
# CONFIG_DRM_NOUVEAU is not setCONFIG_DRM_I915=mCONFIG_DRM_I915_FORCE_PROBE=""CONFIG_DRM_I915_CAPTURE_ERROR=yCONFIG_DRM_I915_COMPRESS_ERROR=yCONFIG_DRM_I915_USERPTR=yCONFIG_DRM_I915_GVT=yCONFIG_DRM_I915_GVT_KVMGT=mCONFIG_DRM_I915_FENCE_TIMEOUT=10000CONFIG_DRM_I915_USERFAULT_AUTOSUSPEND=250CONFIG_DRM_I915_HEARTBEAT_INTERVAL=2500CONFIG_DRM_I915_PREEMPT_TIMEOUT=640CONFIG_DRM_I915_MAX_REQUEST_BUSYWAIT=8000CONFIG_DRM_I915_STOP_TIMEOUT=100CONFIG_DRM_I915_TIMESLICE_DURATION=1
# CONFIG_DRM_VGEM is not set
# CONFIG_DRM_VKMS is not setCONFIG_DRM_VMWGFX=mCONFIG_DRM_VMWGFX_FBCON=yCONFIG_DRM_GMA500=mCONFIG_DRM_GMA600=yCONFIG_DRM_GMA3600=y
# CONFIG_DRM_UDL is not setCONFIG_DRM_AST=mCONFIG_DRM_MGAG200=mCONFIG_DRM_QXL=mCONFIG_DRM_BOCHS=mCONFIG_DRM_VIRTIO_GPU=mCONFIG_DRM_PANEL=y
#
# Display Panels
#
# CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set
# end of Display Panels
CONFIG_DRM_BRIDGE=yCONFIG_DRM_PANEL_BRIDGE=y
#
# Display Interface Bridges
#
# CONFIG_DRM_ANALOGIX_ANX78XX is not set
# end of Display Interface Bridges
# CONFIG_DRM_ETNAVIV is not setCONFIG_DRM_CIRRUS_QEMU=m
# CONFIG_DRM_GM12U320 is not set
# CONFIG_TINYDRM_HX8357D is not set
# CONFIG_TINYDRM_ILI9225 is not set
# CONFIG_TINYDRM_ILI9341 is not set
# CONFIG_TINYDRM_ILI9486 is not set
# CONFIG_TINYDRM_MI0283QT is not set
# CONFIG_TINYDRM_REPAPER is not set
# CONFIG_TINYDRM_ST7586 is not set
# CONFIG_TINYDRM_ST7735R is not set
# CONFIG_DRM_XEN is not set
# CONFIG_DRM_VBOXVIDEO is not set
# CONFIG_DRM_LEGACY is not setCONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y
#
# Frame buffer Devices
#CONFIG_FB_CMDLINE=yCONFIG_FB_NOTIFY=yCONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not setCONFIG_FB_BOOT_VESA_SUPPORT=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=yCONFIG_FB_SYS_FILLRECT=mCONFIG_FB_SYS_COPYAREA=mCONFIG_FB_SYS_IMAGEBLIT=m
# CONFIG_FB_FOREIGN_ENDIAN is not setCONFIG_FB_SYS_FOPS=mCONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_MODE_HELPERS is not setCONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not setCONFIG_FB_VESA=yCONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_SM501 is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_IBM_GXT4500 is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_XEN_FBDEV_FRONTEND is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not setCONFIG_FB_HYPERV=m
# CONFIG_FB_SIMPLE is not set
# CONFIG_FB_SM712 is not set
# end of Frame buffer Devices
#
# Backlight & LCD device support
#CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_LCD_L4F00242T03 is not set
# CONFIG_LCD_LMS283GF05 is not set
# CONFIG_LCD_LTV350QV is not set
# CONFIG_LCD_ILI922X is not set
# CONFIG_LCD_ILI9320 is not set
# CONFIG_LCD_TDO24M is not set
# CONFIG_LCD_VGG2432A4 is not setCONFIG_LCD_PLATFORM=m
# CONFIG_LCD_AMS369FG06 is not set
# CONFIG_LCD_LMS501KF03 is not set
# CONFIG_LCD_HX8357 is not set
# CONFIG_LCD_OTM3225A is not setCONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_KTD253 is not set
# CONFIG_BACKLIGHT_PWM is not setCONFIG_BACKLIGHT_APPLE=m
# CONFIG_BACKLIGHT_QCOM_WLED is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not setCONFIG_BACKLIGHT_LP855X=m
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_BACKLIGHT_ARCXCNN is not set
# end of Backlight & LCD device support
CONFIG_HDMI=y
#
# Console display driver support
#CONFIG_VGA_CONSOLE=yCONFIG_DUMMY_CONSOLE=y CONFIG_DUMMY_CONSOLE_COLUMNS=80 CONFIG_DUMMY_CONSOLE_ROWS=25 CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set
# end of Console display driver support
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not setCONFIG_LOGO_LINUX_CLUT224=y
# end of Graphics support
# CONFIG_SOUND is not set
#
# HID support
#CONFIG_HID=yCONFIG_HID_BATTERY_STRENGTH=yCONFIG_HIDRAW=yCONFIG_UHID=mCONFIG_HID_GENERIC=y
#
# Special HID drivers
#CONFIG_HID_A4TECH=m
# CONFIG_HID_ACCUTOUCH is not setCONFIG_HID_ACRUX=m
# CONFIG_HID_ACRUX_FF is not setCONFIG_HID_APPLE=m
# CONFIG_HID_APPLEIR is not setCONFIG_HID_ASUS=mCONFIG_HID_AUREAL=mCONFIG_HID_BELKIN=m
# CONFIG_HID_BETOP_FF is not set
# CONFIG_HID_BIGBEN_FF is not setCONFIG_HID_CHERRY=mCONFIG_HID_CHICONY=m
# CONFIG_HID_CORSAIR is not set
# CONFIG_HID_COUGAR is not set
# CONFIG_HID_MACALLY is not setCONFIG_HID_CMEDIA=m
# CONFIG_HID_CP2112 is not set
# CONFIG_HID_CREATIVE_SB0540 is not setCONFIG_HID_CYPRESS=mCONFIG_HID_DRAGONRISE=m
# CONFIG_DRAGONRISE_FF is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELAN is not setCONFIG_HID_ELECOM=m
# CONFIG_HID_ELO is not setCONFIG_HID_EZKEY=mCONFIG_HID_GEMBIRD=mCONFIG_HID_GFRM=m
# CONFIG_HID_GLORIOUS is not set
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_VIVALDI is not set
# CONFIG_HID_GT683R is not setCONFIG_HID_KEYTOUCH=mCONFIG_HID_KYE=m
# CONFIG_HID_UCLOGIC is not setCONFIG_HID_WALTOP=m
# CONFIG_HID_VIEWSONIC is not setCONFIG_HID_GYRATION=mCONFIG_HID_ICADE=mCONFIG_HID_ITE=mCONFIG_HID_JABRA=mCONFIG_HID_TWINHAN=mCONFIG_HID_KENSINGTON=mCONFIG_HID_LCPOWER=mCONFIG_HID_LED=mCONFIG_HID_LENOVO=mCONFIG_HID_LOGITECH=mCONFIG_HID_LOGITECH_DJ=mCONFIG_HID_LOGITECH_HIDPP=m
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
# CONFIG_LOGIWHEELS_FF is not setCONFIG_HID_MAGICMOUSE=y
# CONFIG_HID_MALTRON is not set
# CONFIG_HID_MAYFLASH is not set
# CONFIG_HID_REDRAGON is not setCONFIG_HID_MICROSOFT=mCONFIG_HID_MONTEREY=mCONFIG_HID_MULTITOUCH=mCONFIG_HID_NTI=m
# CONFIG_HID_NTRIG is not setCONFIG_HID_ORTEK=mCONFIG_HID_PANTHERLORD=m
# CONFIG_PANTHERLORD_FF is not set
# CONFIG_HID_PENMOUNT is not setCONFIG_HID_PETALYNX=mCONFIG_HID_PICOLCD=mCONFIG_HID_PICOLCD_FB=yCONFIG_HID_PICOLCD_BACKLIGHT=yCONFIG_HID_PICOLCD_LCD=yCONFIG_HID_PICOLCD_LEDS=yCONFIG_HID_PICOLCD_CIR=yCONFIG_HID_PLANTRONICS=mCONFIG_HID_PRIMAX=m
# CONFIG_HID_RETRODE is not set
# CONFIG_HID_ROCCAT is not setCONFIG_HID_SAITEK=mCONFIG_HID_SAMSUNG=m
# CONFIG_HID_SONY is not setCONFIG_HID_SPEEDLINK=m
# CONFIG_HID_STEAM is not setCONFIG_HID_STEELSERIES=mCONFIG_HID_SUNPLUS=mCONFIG_HID_RMI=mCONFIG_HID_GREENASIA=m
# CONFIG_GREENASIA_FF is not setCONFIG_HID_HYPERV_MOUSE=mCONFIG_HID_SMARTJOYPLUS=m
# CONFIG_SMARTJOYPLUS_FF is not setCONFIG_HID_TIVO=mCONFIG_HID_TOPSEED=mCONFIG_HID_THINGM=mCONFIG_HID_THRUSTMASTER=m
# CONFIG_THRUSTMASTER_FF is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_U2FZERO is not set
# CONFIG_HID_WACOM is not setCONFIG_HID_WIIMOTE=mCONFIG_HID_XINMO=mCONFIG_HID_ZEROPLUS=m
# CONFIG_ZEROPLUS_FF is not setCONFIG_HID_ZYDACRON=mCONFIG_HID_SENSOR_HUB=yCONFIG_HID_SENSOR_CUSTOM_SENSOR=mCONFIG_HID_ALPS=m
# CONFIG_HID_MCP2221 is not set
# end of Special HID drivers
#
# USB HID support
#CONFIG_USB_HID=y
# CONFIG_HID_PID is not set
# CONFIG_USB_HIDDEV is not set
# end of USB HID support
#
# I2C HID support
#CONFIG_I2C_HID=m
# end of I2C HID support
#
# Intel ISH HID support
#CONFIG_INTEL_ISH_HID=m
# CONFIG_INTEL_ISH_FIRMWARE_DOWNLOADER is not set
# end of Intel ISH HID support # end of HID support
CONFIG_USB_OHCI_LITTLE_ENDIAN=yCONFIG_USB_SUPPORT=yCONFIG_USB_COMMON=y
# CONFIG_USB_LED_TRIG is not set
# CONFIG_USB_ULPI_BUS is not set
# CONFIG_USB_CONN_GPIO is not setCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB=yCONFIG_USB_PCI=yCONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_FEW_INIT_RETRIES is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_PRODUCTLIST is not setCONFIG_USB_LEDS_TRIGGER_USBPORT=yCONFIG_USB_AUTOSUSPEND_DELAY=2CONFIG_USB_MON=y
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not setCONFIG_USB_XHCI_HCD=y
# CONFIG_USB_XHCI_DBGCAP is not setCONFIG_USB_XHCI_PCI=y
# CONFIG_USB_XHCI_PCI_RENESAS is not set
# CONFIG_USB_XHCI_PLATFORM is not setCONFIG_USB_EHCI_HCD=yCONFIG_USB_EHCI_ROOT_HUB_TT=yCONFIG_USB_EHCI_TT_NEWSCHED=yCONFIG_USB_EHCI_PCI=y
# CONFIG_USB_EHCI_FSL is not set
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
# CONFIG_USB_MAX3421_HCD is not setCONFIG_USB_OHCI_HCD=yCONFIG_USB_OHCI_HCD_PCI=y
# CONFIG_USB_OHCI_HCD_PLATFORM is not setCONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HCD_BCMA is not set
# CONFIG_USB_HCD_TEST_MODE is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may #
#
# also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_REALTEK is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_STORAGE_ALAUDA is not set # CONFIG_USB_STORAGE_ONETOUCH is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_STORAGE_ENE_UB6250 is not set # CONFIG_USB_UAS is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USBIP_CORE is not set
# CONFIG_USB_CDNS3 is not set
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_DWC3 is not set
# CONFIG_USB_DWC2 is not set
# CONFIG_USB_CHIPIDEA is not set
# CONFIG_USB_ISP1760 is not set
#
# USB port drivers
#
# CONFIG_USB_USS720 is not setCONFIG_USB_SERIAL=mCONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_SIMPLE is not set
# CONFIG_USB_SERIAL_AIRCABLE is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_CH341 is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP210X is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_F81232 is not set
# CONFIG_USB_SERIAL_F8153X is not set
# CONFIG_USB_SERIAL_GARMIN is not set
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_IUU is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_METRO is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_MXUPORT is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_OTI6858 is not set
# CONFIG_USB_SERIAL_QCAUX is not set
# CONFIG_USB_SERIAL_QUALCOMM is not set
# CONFIG_USB_SERIAL_SPCP8X5 is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
# CONFIG_USB_SERIAL_SYMBOL is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_SERIAL_OPTICON is not set
# CONFIG_USB_SERIAL_XSENS_MT is not set
# CONFIG_USB_SERIAL_WISHBONE is not set
# CONFIG_USB_SERIAL_SSU100 is not set
# CONFIG_USB_SERIAL_QT2 is not set
# CONFIG_USB_SERIAL_UPD78F0730 is not setCONFIG_USB_SERIAL_DEBUG=m
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_APPLE_MFI_FASTCHARGE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
# CONFIG_USB_EZUSB_FX2 is not set
# CONFIG_USB_HUB_USB251XB is not set
# CONFIG_USB_HSIC_USB3503 is not set
# CONFIG_USB_HSIC_USB4604 is not set
# CONFIG_USB_LINK_LAYER_TEST is not set
# CONFIG_USB_CHAOSKEY is not set
# CONFIG_USB_ATM is not set
#
# USB Physical Layer drivers
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ISP1301 is not set
# end of USB Physical Layer drivers
# CONFIG_USB_GADGET is not setCONFIG_TYPEC=y
# CONFIG_TYPEC_TCPM is not setCONFIG_TYPEC_UCSI=y
# CONFIG_UCSI_CCG is not setCONFIG_UCSI_ACPI=y
# CONFIG_TYPEC_TPS6598X is not set
# CONFIG_TYPEC_STUSB160X is not set
#
# USB Type-C Multiplexer/DeMultiplexer Switch support #
# CONFIG_TYPEC_MUX_PI3USB30532 is not set
# end of USB Type-C Multiplexer/DeMultiplexer Switch support
#
# USB Type-C Alternate Mode drivers
#
# CONFIG_TYPEC_DP_ALTMODE is not set
# end of USB Type-C Alternate Mode drivers
# CONFIG_USB_ROLE_SWITCH is not setCONFIG_MMC=mCONFIG_MMC_BLOCK=mCONFIG_MMC_BLOCK_MINORS=8CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_DEBUG is not setCONFIG_MMC_SDHCI=mCONFIG_MMC_SDHCI_IO_ACCESSORS=yCONFIG_MMC_SDHCI_PCI=mCONFIG_MMC_RICOH_MMC=yCONFIG_MMC_SDHCI_ACPI=mCONFIG_MMC_SDHCI_PLTFM=m
# CONFIG_MMC_SDHCI_F_SDH30 is not set
# CONFIG_MMC_WBSD is not set
# CONFIG_MMC_TIFM_SD is not set
# CONFIG_MMC_SPI is not set
# CONFIG_MMC_CB710 is not set
# CONFIG_MMC_VIA_SDMMC is not set
# CONFIG_MMC_VUB300 is not set
# CONFIG_MMC_USHC is not set
# CONFIG_MMC_USDHI6ROL0 is not set
# CONFIG_MMC_REALTEK_PCI is not setCONFIG_MMC_CQHCI=m
# CONFIG_MMC_HSQ is not set
# CONFIG_MMC_TOSHIBA_PCI is not set
# CONFIG_MMC_MTK is not set
# CONFIG_MMC_SDHCI_XENON is not set
# CONFIG_MEMSTICK is not setCONFIG_NEW_LEDS=yCONFIG_LEDS_CLASS=y
# CONFIG_LEDS_CLASS_FLASH is not set
# CONFIG_LEDS_CLASS_MULTICOLOR is not set
# CONFIG_LEDS_BRIGHTNESS_HW_CHANGED is not set
#
# LED drivers
#
# CONFIG_LEDS_APU is not setCONFIG_LEDS_LM3530=m
# CONFIG_LEDS_LM3532 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_GPIO is not setCONFIG_LEDS_LP3944=m
# CONFIG_LEDS_LP3952 is not set
# CONFIG_LEDS_LP50XX is not setCONFIG_LEDS_CLEVO_MAIL=m
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_PWM is not set
# CONFIG_LEDS_BD2802 is not setCONFIG_LEDS_INTEL_SS4200=m
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
# CONFIG_LEDS_LM355x is not set
#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM) #CONFIG_LEDS_BLINKM=mCONFIG_LEDS_MLXCPLD=m
# CONFIG_LEDS_MLXREG is not set
# CONFIG_LEDS_USER is not set
# CONFIG_LEDS_NIC78BX is not set
# CONFIG_LEDS_TI_LMU_COMMON is not set
#
# LED Triggers
#CONFIG_LEDS_TRIGGERS=yCONFIG_LEDS_TRIGGER_TIMER=mCONFIG_LEDS_TRIGGER_ONESHOT=m
# CONFIG_LEDS_TRIGGER_DISK is not setCONFIG_LEDS_TRIGGER_HEARTBEAT=mCONFIG_LEDS_TRIGGER_BACKLIGHT=m
# CONFIG_LEDS_TRIGGER_CPU is not set
# CONFIG_LEDS_TRIGGER_ACTIVITY is not setCONFIG_LEDS_TRIGGER_GPIO=mCONFIG_LEDS_TRIGGER_DEFAULT_ON=m
#
# iptables trigger is under Netfilter config (LED target) # CONFIG_LEDS_TRIGGER_TRANSIENT=m CONFIG_LEDS_TRIGGER_CAMERA=m # CONFIG_LEDS_TRIGGER_PANIC is not set # CONFIG_LEDS_TRIGGER_NETDEV is not set # CONFIG_LEDS_TRIGGER_PATTERN is not set CONFIG_LEDS_TRIGGER_AUDIO=m # CONFIG_ACCESSIBILITY is not set CONFIG_INFINIBAND=m CONFIG_INFINIBAND_USER_MAD=m CONFIG_INFINIBAND_USER_ACCESS=m CONFIG_INFINIBAND_USER_MEM=y CONFIG_INFINIBAND_ON_DEMAND_PAGING=y CONFIG_INFINIBAND_ADDR_TRANS=y CONFIG_INFINIBAND_ADDR_TRANS_CONFIGFS=y # CONFIG_INFINIBAND_MTHCA is not set # CONFIG_INFINIBAND_EFA is not set # CONFIG_INFINIBAND_I40IW is not set # CONFIG_MLX4_INFINIBAND is not set # CONFIG_INFINIBAND_OCRDMA is not set # CONFIG_INFINIBAND_USNIC is not set # CONFIG_INFINIBAND_BNXT_RE is not set # CONFIG_INFINIBAND_RDMAVT is not set CONFIG_RDMA_RXE=m CONFIG_RDMA_SIW=m CONFIG_INFINIBAND_IPOIB=m # CONFIG_INFINIBAND_IPOIB_CM is not set CONFIG_INFINIBAND_IPOIB_DEBUG=y # CONFIG_INFINIBAND_IPOIB_DEBUG_DATA is not set CONFIG_INFINIBAND_SRP=m CONFIG_INFINIBAND_SRPT=m # CONFIG_INFINIBAND_ISER is not set # CONFIG_INFINIBAND_ISERT is not set # CONFIG_INFINIBAND_RTRS_CLIENT is not set # CONFIG_INFINIBAND_RTRS_SERVER is not set # CONFIG_INFINIBAND_OPA_VNIC is not set CONFIG_EDAC_ATOMIC_SCRUB=y CONFIG_EDAC_SUPPORT=y CONFIG_EDAC=y CONFIG_EDAC_LEGACY_SYSFS=y # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_DECODE_MCE=m CONFIG_EDAC_GHES=y CONFIG_EDAC_AMD64=m # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set CONFIG_EDAC_E752X=m CONFIG_EDAC_I82975X=m CONFIG_EDAC_I3000=m CONFIG_EDAC_I3200=m CONFIG_EDAC_IE31200=m CONFIG_EDAC_X38=m CONFIG_EDAC_I5400=m CONFIG_EDAC_I7CORE=m CONFIG_EDAC_I5000=m CONFIG_EDAC_I5100=m CONFIG_EDAC_I7300=m CONFIG_EDAC_SBRIDGE=m CONFIG_EDAC_SKX=m # CONFIG_EDAC_I10NM is not set CONFIG_EDAC_PND2=m CONFIG_RTC_LIB=y CONFIG_RTC_MC146818_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_SYSTOHC is not set # CONFIG_RTC_DEBUG is not set CONFIG_RTC_NVMEM=y
#
# RTC interfaces
#CONFIG_RTC_INTF_SYSFS=yCONFIG_RTC_INTF_PROC=yCONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_ABB5ZES3 is not set
# CONFIG_RTC_DRV_ABEOZ9 is not set
# CONFIG_RTC_DRV_ABX80X is not setCONFIG_RTC_DRV_DS1307=m
# CONFIG_RTC_DRV_DS1307_CENTURY is not setCONFIG_RTC_DRV_DS1374=m
# CONFIG_RTC_DRV_DS1374_WDT is not setCONFIG_RTC_DRV_DS1672=mCONFIG_RTC_DRV_MAX6900=mCONFIG_RTC_DRV_RS5C372=mCONFIG_RTC_DRV_ISL1208=mCONFIG_RTC_DRV_ISL12022=mCONFIG_RTC_DRV_X1205=mCONFIG_RTC_DRV_PCF8523=m
# CONFIG_RTC_DRV_PCF85063 is not set
# CONFIG_RTC_DRV_PCF85363 is not setCONFIG_RTC_DRV_PCF8563=mCONFIG_RTC_DRV_PCF8583=mCONFIG_RTC_DRV_M41T80=mCONFIG_RTC_DRV_M41T80_WDT=yCONFIG_RTC_DRV_BQ32K=m
# CONFIG_RTC_DRV_S35390A is not setCONFIG_RTC_DRV_FM3130=m
# CONFIG_RTC_DRV_RX8010 is not setCONFIG_RTC_DRV_RX8581=mCONFIG_RTC_DRV_RX8025=mCONFIG_RTC_DRV_EM3027=m
# CONFIG_RTC_DRV_RV3028 is not set
# CONFIG_RTC_DRV_RV3032 is not set
# CONFIG_RTC_DRV_RV8803 is not set
# CONFIG_RTC_DRV_SD3078 is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1302 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1343 is not set
# CONFIG_RTC_DRV_DS1347 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6916 is not set
# CONFIG_RTC_DRV_R9701 is not setCONFIG_RTC_DRV_RX4581=m
# CONFIG_RTC_DRV_RX6110 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_MCP795 is not setCONFIG_RTC_I2C_AND_SPI=y
#
# SPI and I2C RTC drivers
#CONFIG_RTC_DRV_DS3232=mCONFIG_RTC_DRV_DS3232_HWMON=y
# CONFIG_RTC_DRV_PCF2127 is not setCONFIG_RTC_DRV_RV3029C2=m
# CONFIG_RTC_DRV_RV3029_HWMON is not set
#
# Platform RTC drivers
#CONFIG_RTC_DRV_CMOS=yCONFIG_RTC_DRV_DS1286=mCONFIG_RTC_DRV_DS1511=mCONFIG_RTC_DRV_DS1553=m
# CONFIG_RTC_DRV_DS1685_FAMILY is not setCONFIG_RTC_DRV_DS1742=mCONFIG_RTC_DRV_DS2404=mCONFIG_RTC_DRV_STK17TA8=m
# CONFIG_RTC_DRV_M48T86 is not setCONFIG_RTC_DRV_M48T35=mCONFIG_RTC_DRV_M48T59=mCONFIG_RTC_DRV_MSM6242=mCONFIG_RTC_DRV_BQ4802=mCONFIG_RTC_DRV_RP5C01=mCONFIG_RTC_DRV_V3020=m
#
# on-CPU RTC drivers
#
# CONFIG_RTC_DRV_FTRTC010 is not set
#
# HID Sensor RTC drivers
#CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#CONFIG_DMA_ENGINE=yCONFIG_DMA_VIRTUAL_CHANNELS=yCONFIG_DMA_ACPI=y
# CONFIG_ALTERA_MSGDMA is not setCONFIG_INTEL_IDMA64=m
# CONFIG_INTEL_IDXD is not setCONFIG_INTEL_IOATDMA=m
# CONFIG_PLX_DMA is not set
# CONFIG_XILINX_ZYNQMP_DPDMA is not set
# CONFIG_QCOM_HIDMA_MGMT is not set
# CONFIG_QCOM_HIDMA is not setCONFIG_DW_DMAC_CORE=yCONFIG_DW_DMAC=mCONFIG_DW_DMAC_PCI=y
# CONFIG_DW_EDMA is not set
# CONFIG_DW_EDMA_PCIE is not setCONFIG_HSU_DMA=y
# CONFIG_SF_PDMA is not set
#
# DMA Clients
#CONFIG_ASYNC_TX_DMA=yCONFIG_DMATEST=mCONFIG_DMA_ENGINE_RAID=y
#
# DMABUF options
#CONFIG_SYNC_FILE=y
# CONFIG_SW_SYNC is not set
# CONFIG_UDMABUF is not set
# CONFIG_DMABUF_MOVE_NOTIFY is not set
# CONFIG_DMABUF_SELFTESTS is not set
# CONFIG_DMABUF_HEAPS is not set
# end of DMABUF options
CONFIG_DCA=m
# CONFIG_AUXDISPLAY is not set
# CONFIG_PANEL is not setCONFIG_UIO=mCONFIG_UIO_CIF=mCONFIG_UIO_PDRV_GENIRQ=m
# CONFIG_UIO_DMEM_GENIRQ is not setCONFIG_UIO_AEC=mCONFIG_UIO_SERCOS3=mCONFIG_UIO_PCI_GENERIC=m
# CONFIG_UIO_NETX is not set
# CONFIG_UIO_PRUSS is not set
# CONFIG_UIO_MF624 is not setCONFIG_UIO_HV_GENERIC=mCONFIG_VFIO_IOMMU_TYPE1=mCONFIG_VFIO_VIRQFD=mCONFIG_VFIO=mCONFIG_VFIO_NOIOMMU=yCONFIG_VFIO_PCI=m
# CONFIG_VFIO_PCI_VGA is not setCONFIG_VFIO_PCI_MMAP=yCONFIG_VFIO_PCI_INTX=y
# CONFIG_VFIO_PCI_IGD is not setCONFIG_VFIO_MDEV=mCONFIG_VFIO_MDEV_DEVICE=mCONFIG_IRQ_BYPASS_MANAGER=m
# CONFIG_VIRT_DRIVERS is not setCONFIG_VIRTIO=yCONFIG_VIRTIO_MENU=yCONFIG_VIRTIO_PCI=yCONFIG_VIRTIO_PCI_LEGACY=y
# CONFIG_VIRTIO_PMEM is not setCONFIG_VIRTIO_BALLOON=mCONFIG_VIRTIO_MEM=mCONFIG_VIRTIO_INPUT=m
# CONFIG_VIRTIO_MMIO is not setCONFIG_VIRTIO_DMA_SHARED_BUFFER=m
# CONFIG_VDPA is not setCONFIG_VHOST_IOTLB=mCONFIG_VHOST=mCONFIG_VHOST_MENU=yCONFIG_VHOST_NET=m
# CONFIG_VHOST_SCSI is not setCONFIG_VHOST_VSOCK=m
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set
#
# Microsoft Hyper-V guest support
#CONFIG_HYPERV=mCONFIG_HYPERV_TIMER=yCONFIG_HYPERV_UTILS=mCONFIG_HYPERV_BALLOON=m
# end of Microsoft Hyper-V guest support
#
# Xen driver support
#
# CONFIG_XEN_BALLOON is not setCONFIG_XEN_DEV_EVTCHN=m
# CONFIG_XEN_BACKEND is not setCONFIG_XENFS=mCONFIG_XEN_COMPAT_XENFS=yCONFIG_XEN_SYS_HYPERVISOR=yCONFIG_XEN_XENBUS_FRONTEND=y
# CONFIG_XEN_GNTDEV is not set
# CONFIG_XEN_GRANT_DEV_ALLOC is not set
# CONFIG_XEN_GRANT_DMA_ALLOC is not setCONFIG_SWIOTLB_XEN=y
# CONFIG_XEN_PVCALLS_FRONTEND is not setCONFIG_XEN_PRIVCMD=mCONFIG_XEN_EFI=yCONFIG_XEN_AUTO_XLATE=yCONFIG_XEN_ACPI=y
# CONFIG_XEN_UNPOPULATED_ALLOC is not set
# end of Xen driver support
# CONFIG_GREYBUS is not set
# CONFIG_STAGING is not setCONFIG_X86_PLATFORM_DEVICES=yCONFIG_ACPI_WMI=mCONFIG_WMI_BMOF=m
# CONFIG_ALIENWARE_WMI is not set
# CONFIG_HUAWEI_WMI is not set
# CONFIG_INTEL_WMI_SBL_FW_UPDATE is not setCONFIG_INTEL_WMI_THUNDERBOLT=mCONFIG_MXM_WMI=m
# CONFIG_PEAQ_WMI is not set
# CONFIG_XIAOMI_WMI is not setCONFIG_ACERHDF=m
# CONFIG_ACER_WIRELESS is not setCONFIG_ACER_WMI=mCONFIG_APPLE_GMUX=mCONFIG_ASUS_LAPTOP=m
# CONFIG_ASUS_WIRELESS is not setCONFIG_ASUS_WMI=mCONFIG_ASUS_NB_WMI=mCONFIG_EEEPC_LAPTOP=mCONFIG_EEEPC_WMI=mCONFIG_DCDBAS=mCONFIG_DELL_SMBIOS=mCONFIG_DELL_SMBIOS_WMI=y
# CONFIG_DELL_SMBIOS_SMM is not setCONFIG_DELL_LAPTOP=mCONFIG_DELL_RBTN=mCONFIG_DELL_RBU=mCONFIG_DELL_SMO8800=mCONFIG_DELL_WMI=mCONFIG_DELL_WMI_DESCRIPTOR=mCONFIG_DELL_WMI_AIO=mCONFIG_DELL_WMI_LED=mCONFIG_AMILO_RFKILL=mCONFIG_FUJITSU_LAPTOP=mCONFIG_FUJITSU_TABLET=m
# CONFIG_GPD_POCKET_FAN is not setCONFIG_HP_ACCEL=mCONFIG_HP_WIRELESS=mCONFIG_HP_WMI=m
# CONFIG_IBM_RTL is not setCONFIG_IDEAPAD_LAPTOP=mCONFIG_SENSORS_HDAPS=mCONFIG_THINKPAD_ACPI=m
# CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set
# CONFIG_THINKPAD_ACPI_DEBUG is not set
# CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not setCONFIG_THINKPAD_ACPI_VIDEO=yCONFIG_THINKPAD_ACPI_HOTKEY_POLL=y
# CONFIG_INTEL_ATOMISP2_PM is not setCONFIG_INTEL_HID_EVENT=m
# CONFIG_INTEL_INT0002_VGPIO is not set
# CONFIG_INTEL_MENLOW is not setCONFIG_INTEL_OAKTRAIL=mCONFIG_INTEL_VBTN=m
# CONFIG_SURFACE3_WMI is not set
# CONFIG_SURFACE_3_POWER_OPREGION is not set
# CONFIG_SURFACE_PRO3_BUTTON is not setCONFIG_MSI_LAPTOP=mCONFIG_MSI_WMI=m
# CONFIG_PCENGINES_APU2 is not setCONFIG_SAMSUNG_LAPTOP=mCONFIG_SAMSUNG_Q10=mCONFIG_TOSHIBA_BT_RFKILL=m
# CONFIG_TOSHIBA_HAPS is not set
# CONFIG_TOSHIBA_WMI is not setCONFIG_ACPI_CMPC=mCONFIG_COMPAL_LAPTOP=m
# CONFIG_LG_LAPTOP is not setCONFIG_PANASONIC_LAPTOP=mCONFIG_SONY_LAPTOP=mCONFIG_SONYPI_COMPAT=y
# CONFIG_SYSTEM76_ACPI is not setCONFIG_TOPSTAR_LAPTOP=m
# CONFIG_I2C_MULTI_INSTANTIATE is not setCONFIG_MLX_PLATFORM=mCONFIG_INTEL_IPS=mCONFIG_INTEL_RST=m
# CONFIG_INTEL_SMARTCONNECT is not set
#
# Intel Speed Select Technology interface support
#
# CONFIG_INTEL_SPEED_SELECT_INTERFACE is not set
# end of Intel Speed Select Technology interface support
CONFIG_INTEL_TURBO_MAX_3=y
# CONFIG_INTEL_UNCORE_FREQ_CONTROL is not setCONFIG_INTEL_PMC_CORE=m
# CONFIG_INTEL_PUNIT_IPC is not set
# CONFIG_INTEL_SCU_PCI is not set
# CONFIG_INTEL_SCU_PLATFORM is not setCONFIG_PMC_ATOM=y
# CONFIG_CHROME_PLATFORMS is not setCONFIG_MELLANOX_PLATFORM=yCONFIG_MLXREG_HOTPLUG=m
# CONFIG_MLXREG_IO is not setCONFIG_HAVE_CLK=yCONFIG_CLKDEV_LOOKUP=yCONFIG_HAVE_CLK_PREPARE=yCONFIG_COMMON_CLK=y
# CONFIG_COMMON_CLK_MAX9485 is not set
# CONFIG_COMMON_CLK_SI5341 is not set
# CONFIG_COMMON_CLK_SI5351 is not set
# CONFIG_COMMON_CLK_SI544 is not set
# CONFIG_COMMON_CLK_CDCE706 is not set
# CONFIG_COMMON_CLK_CS2000_CP is not set
# CONFIG_COMMON_CLK_PWM is not setCONFIG_HWSPINLOCK=y
#
# Clock Source drivers
#CONFIG_CLKEVT_I8253=yCONFIG_I8253_LOCK=yCONFIG_CLKBLD_I8253=y
# end of Clock Source drivers
CONFIG_MAILBOX=yCONFIG_PCC=y
# CONFIG_ALTERA_MBOX is not setCONFIG_IOMMU_IOVA=yCONFIG_IOASID=yCONFIG_IOMMU_API=yCONFIG_IOMMU_SUPPORT=y
#
# Generic IOMMU Pagetable Support
#
# end of Generic IOMMU Pagetable Support
# CONFIG_IOMMU_DEBUGFS is not set
# CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not set CONFIG_IOMMU_DMA=yCONFIG_AMD_IOMMU=yCONFIG_AMD_IOMMU_V2=mCONFIG_DMAR_TABLE=yCONFIG_INTEL_IOMMU=y
# CONFIG_INTEL_IOMMU_SVM is not set
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set CONFIG_INTEL_IOMMU_FLOPPY_WA=y
# CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON is not set CONFIG_IRQ_REMAP=yCONFIG_HYPERV_IOMMU=y
#
# Remoteproc drivers
#
# CONFIG_REMOTEPROC is not set
# end of Remoteproc drivers
#
# Rpmsg drivers
#
# CONFIG_RPMSG_QCOM_GLINK_RPM is not set
# CONFIG_RPMSG_VIRTIO is not set
# end of Rpmsg drivers
# CONFIG_SOUNDWIRE is not set
#
# SOC (System On Chip) specific Drivers
#
#
# Amlogic SoC drivers
#
# end of Amlogic SoC drivers
#
# Aspeed SoC drivers
#
# end of Aspeed SoC drivers
#
# Broadcom SoC drivers
#
# end of Broadcom SoC drivers
#
# NXP/Freescale QorIQ SoC drivers
#
# end of NXP/Freescale QorIQ SoC drivers
#
# i.MX SoC drivers
#
# end of i.MX SoC drivers
#
# Qualcomm SoC drivers
#
# end of Qualcomm SoC drivers
# CONFIG_SOC_TI is not set
#
# Xilinx SoC drivers
#
# CONFIG_XILINX_VCU is not set
# end of Xilinx SoC drivers # end of SOC (System On Chip) specific Drivers
# CONFIG_PM_DEVFREQ is not set
# CONFIG_EXTCON is not set
# CONFIG_MEMORY is not set
# CONFIG_IIO is not setCONFIG_NTB=m
# CONFIG_NTB_MSI is not set
# CONFIG_NTB_AMD is not set
# CONFIG_NTB_IDT is not set
# CONFIG_NTB_INTEL is not set
# CONFIG_NTB_SWITCHTEC is not set
# CONFIG_NTB_PINGPONG is not set
# CONFIG_NTB_TOOL is not set
# CONFIG_NTB_PERF is not set
# CONFIG_NTB_TRANSPORT is not set
# CONFIG_VME_BUS is not setCONFIG_PWM=yCONFIG_PWM_SYSFS=y
# CONFIG_PWM_DEBUG is not setCONFIG_PWM_LPSS=mCONFIG_PWM_LPSS_PCI=mCONFIG_PWM_LPSS_PLATFORM=m
# CONFIG_PWM_PCA9685 is not set
#
# IRQ chip support
#
# end of IRQ chip support
# CONFIG_IPACK_BUS is not set
# CONFIG_RESET_CONTROLLER is not set
#
# PHY Subsystem
#
# CONFIG_GENERIC_PHY is not set
# CONFIG_USB_LGM_PHY is not set
# CONFIG_BCM_KONA_USB2_PHY is not set
# CONFIG_PHY_PXA_28NM_HSIC is not set
# CONFIG_PHY_PXA_28NM_USB2 is not set
# CONFIG_PHY_INTEL_LGM_EMMC is not set
# end of PHY Subsystem
CONFIG_POWERCAP=yCONFIG_INTEL_RAPL_CORE=mCONFIG_INTEL_RAPL=m
# CONFIG_IDLE_INJECT is not set
# CONFIG_MCB is not set
#
# Performance monitor support
#
# end of Performance monitor support
CONFIG_RAS=y
# CONFIG_RAS_CEC is not set
# CONFIG_USB4 is not set
#
# Android
#
# CONFIG_ANDROID is not set
# end of Android
CONFIG_LIBNVDIMM=mCONFIG_BLK_DEV_PMEM=mCONFIG_ND_BLK=mCONFIG_ND_CLAIM=yCONFIG_ND_BTT=mCONFIG_BTT=yCONFIG_ND_PFN=mCONFIG_NVDIMM_PFN=yCONFIG_NVDIMM_DAX=yCONFIG_NVDIMM_KEYS=yCONFIG_DAX_DRIVER=yCONFIG_DAX=yCONFIG_DEV_DAX=mCONFIG_DEV_DAX_PMEM=mCONFIG_DEV_DAX_KMEM=mCONFIG_DEV_DAX_PMEM_COMPAT=mCONFIG_NVMEM=yCONFIG_NVMEM_SYSFS=y
#
# HW tracing support
#CONFIG_STM=m
# CONFIG_STM_PROTO_BASIC is not set
# CONFIG_STM_PROTO_SYS_T is not setCONFIG_STM_DUMMY=mCONFIG_STM_SOURCE_CONSOLE=mCONFIG_STM_SOURCE_HEARTBEAT=mCONFIG_STM_SOURCE_FTRACE=mCONFIG_INTEL_TH=mCONFIG_INTEL_TH_PCI=mCONFIG_INTEL_TH_ACPI=mCONFIG_INTEL_TH_GTH=mCONFIG_INTEL_TH_STH=mCONFIG_INTEL_TH_MSU=mCONFIG_INTEL_TH_PTI=m
# CONFIG_INTEL_TH_DEBUG is not set
# end of HW tracing support
# CONFIG_FPGA is not set
# CONFIG_TEE is not set
# CONFIG_UNISYS_VISORBUS is not set
# CONFIG_SIOX is not set
# CONFIG_SLIMBUS is not set
# CONFIG_INTERCONNECT is not set
# CONFIG_COUNTER is not set
# CONFIG_MOST is not set
# end of Device Drivers
#
# File systems
#CONFIG_DCACHE_WORD_ACCESS=y
# CONFIG_VALIDATE_FS_PARSER is not set CONFIG_FS_IOMAP=yCONFIG_EXT2_FS=m
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT3_FS is not setCONFIG_EXT4_FS=yCONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set CONFIG_EXT4_KUNIT_TESTS=mCONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not setCONFIG_XFS_FS=mCONFIG_XFS_SUPPORT_V4=yCONFIG_XFS_QUOTA=yCONFIG_XFS_POSIX_ACL=yCONFIG_XFS_RT=yCONFIG_XFS_ONLINE_SCRUB=y CONFIG_XFS_ONLINE_REPAIR=yCONFIG_XFS_DEBUG=yCONFIG_XFS_ASSERT_FATAL=yCONFIG_GFS2_FS=mCONFIG_GFS2_FS_LOCKING_DLM=y CONFIG_OCFS2_FS=mCONFIG_OCFS2_FS_O2CB=m CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m CONFIG_OCFS2_FS_STATS=y CONFIG_OCFS2_DEBUG_MASKLOG=y
# CONFIG_OCFS2_DEBUG_FS is not set CONFIG_BTRFS_FS=mCONFIG_BTRFS_FS_POSIX_ACL=y
# CONFIG_BTRFS_FS_CHECK_INTEGRITY is not set # CONFIG_BTRFS_FS_RUN_SANITY_TESTS is not set # CONFIG_BTRFS_DEBUG is not set
# CONFIG_BTRFS_ASSERT is not set
# CONFIG_BTRFS_FS_REF_VERIFY is not set
# CONFIG_NILFS2_FS is not set CONFIG_F2FS_FS=mCONFIG_F2FS_STAT_FS=yCONFIG_F2FS_FS_XATTR=y CONFIG_F2FS_FS_POSIX_ACL=y CONFIG_F2FS_FS_SECURITY=y
# CONFIG_F2FS_CHECK_FS is not set
# CONFIG_F2FS_IO_TRACE is not set
# CONFIG_F2FS_FAULT_INJECTION is not set
# CONFIG_F2FS_FS_COMPRESSION is not set
# CONFIG_ZONEFS_FS is not setCONFIG_FS_DAX=yCONFIG_FS_DAX_PMD=yCONFIG_FS_POSIX_ACL=yCONFIG_EXPORTFS=yCONFIG_EXPORTFS_BLOCK_OPS=y CONFIG_FILE_LOCKING=y CONFIG_MANDATORY_FILE_LOCKING=y CONFIG_FS_ENCRYPTION=y CONFIG_FS_ENCRYPTION_ALGS=y
# CONFIG_FS_VERITY is not set CONFIG_FSNOTIFY=yCONFIG_DNOTIFY=yCONFIG_INOTIFY_USER=yCONFIG_FANOTIFY=y CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y CONFIG_QUOTA=y CONFIG_QUOTA_NETLINK_INTERFACE=y CONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QUOTA_DEBUG is not set CONFIG_QUOTA_TREE=y
# CONFIG_QFMT_V1 is not setCONFIG_QFMT_V2=yCONFIG_QUOTACTL=yCONFIG_AUTOFS4_FS=yCONFIG_AUTOFS_FS=yCONFIG_FUSE_FS=mCONFIG_CUSE=m
# CONFIG_VIRTIO_FS is not set CONFIG_OVERLAY_FS=m
# CONFIG_OVERLAY_FS_REDIRECT_DIR is not set
# CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW is not set # CONFIG_OVERLAY_FS_INDEX is not set
# CONFIG_OVERLAY_FS_XINO_AUTO is not set
# CONFIG_OVERLAY_FS_METACOPY is not set
#
# Caches
#CONFIG_FSCACHE=mCONFIG_FSCACHE_STATS=y
# CONFIG_FSCACHE_HISTOGRAM is not set
# CONFIG_FSCACHE_DEBUG is not set
# CONFIG_FSCACHE_OBJECT_LIST is not setCONFIG_CACHEFILES=m
# CONFIG_CACHEFILES_DEBUG is not set
# CONFIG_CACHEFILES_HISTOGRAM is not set
# end of Caches
#
# CD-ROM/DVD Filesystems
#CONFIG_ISO9660_FS=mCONFIG_JOLIET=yCONFIG_ZISOFS=yCONFIG_UDF_FS=m
# end of CD-ROM/DVD Filesystems
#
# DOS/FAT/EXFAT/NT Filesystems
#CONFIG_FAT_FS=mCONFIG_MSDOS_FS=mCONFIG_VFAT_FS=mCONFIG_FAT_DEFAULT_CODEPAGE=437CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
# CONFIG_FAT_DEFAULT_UTF8 is not set
# CONFIG_EXFAT_FS is not set
# CONFIG_NTFS_FS is not set
# end of DOS/FAT/EXFAT/NT Filesystems
#
# Pseudo filesystems
#CONFIG_PROC_FS=yCONFIG_PROC_KCORE=yCONFIG_PROC_VMCORE=yCONFIG_PROC_VMCORE_DEVICE_DUMP=yCONFIG_PROC_SYSCTL=yCONFIG_PROC_PAGE_MONITOR=yCONFIG_PROC_CHILDREN=yCONFIG_PROC_PID_ARCH_STATUS=yCONFIG_PROC_CPU_RESCTRL=yCONFIG_KERNFS=yCONFIG_SYSFS=yCONFIG_TMPFS=yCONFIG_TMPFS_POSIX_ACL=yCONFIG_TMPFS_XATTR=y
# CONFIG_TMPFS_INODE64 is not setCONFIG_HUGETLBFS=yCONFIG_HUGETLB_PAGE=yCONFIG_MEMFD_CREATE=yCONFIG_ARCH_HAS_GIGANTIC_PAGE=yCONFIG_CONFIGFS_FS=yCONFIG_EFIVAR_FS=y
# end of Pseudo filesystems
1,296 lines not shown · raw message
Part of this message is not shown here. View the raw message.
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
In reply to Saravana KannanQuoted 33 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch uses all the setup done by the previous patches in this series to refactor
fw_devlinkto be more efficient. Most of the code has been moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.
Quoted 4 lines
[1] - https://lore.kernel.org/linux-omap/[email protected]/
Signed-off-by Saravana Kannan <[email protected]>Tested-by Laurent Pinchart <[email protected]>Tested-by Grygorii Strashko <[email protected]>
Reverting this commit and its dependency:
2d09e6eb4a6f driver core: Delete pointless parameter in fwnode_operations.add_links
from today's linux-next fixed a boot crash on an arm64 Thunder X2 server.
.config: https://cailca.coding.net/public/linux/mm/git/files/master/arm64.config
[ 57.413929][ T1] ACPI: 5 ACPI AML tables successfully acquired and loaded [ 60.571643][ T1] ACPI: Interpreter enabled [ 60.576104][ T1] ACPI: Using GIC for interrupt routing [ 60.582474][ T1] ACPI: MCFG table detected, 1 entries [ 60.588051][ T1] ACPI: IORT: SMMU-v3[402300000] Mapped to Proximity domain 0 [ 60.601374][ T1] Unable to handle kernel paging request at virtual address dfff800000000000 [ 60.610146][ T1] Mem abort info: [ 60.613694][ T1] ESR = 0x96000004 [ 60.617496][ T1] EC = 0x25: DABT (current EL), IL = 32 bits [ 60.623616][ T1] SET = 0, FnV = 0 [ 60.627420][ T1] EA = 0, S1PTW = 0 [ 60.631304][ T1] Data abort info: [ 60.634957][ T1] ISV = 0, ISS = 0x00000004 [ 60.639546][ T1] CM = 0, WnR = 0 [ 60.643255][ T1] [dfff800000000000] address between user and kernel address ranges [ 60.651226][ T1] Internal error: Oops: 96000004 [#1] SMP [ 60.656864][ T1] Modules linked in: [ 60.660658][ T1] CPU: 38 PID: 1 Comm: swapper/0 Tainted: G W 5.10.0-rc7-next-20201211 #2 [ 60.670424][ T1] Hardware name: HPE Apollo 70 /C01_APACHE_MB , BIOS L50_5.13_1.16 07/29/2020 [ 60.680979][ T1] pstate: 10400009 (nzcV daif +PAN -UAO -TCO BTYPE=--) [ 60.687757][ T1] pc : device_add+0xf60/0x16b0 [ 60.692430][ T1] lr : device_add+0xf08/0x16b0 [ 60.697098][ T1] sp : ffff0000063bf7d0 [ 60.701147][ T1] x29: ffff0000063bf7d0 x28: ffff00001f760810 [ 60.707226][ T1] x27: fffffffffffffff8 x26: ffff00001f760858 [ 60.713304][ T1] x25: ffff00001f760c58 x24: fffffffffffffff8 [ 60.719381][ T1] x23: 1fffe00003eec10b x22: ffff8000190d0260 [ 60.725458][ T1] x21: ffff800011dba708 x20: 0000000000000000 [ 60.731535][ T1] x19: 1fffe00000c77f10 x18: 1fffe001cf0d53ed [ 60.737616][ T1] x17: 0000000000000000 x16: 1ffff000033676f1 [ 60.743709][ T1] x15: 0000000000000000 x14: ffff800011731e34 [ 60.749786][ T1] x13: ffff700003217fb9 x12: 1ffff00003217fb8 [ 60.755864][ T1] x11: 1ffff00003217fb8 x10: ffff700003217fb8 [ 60.761940][ T1] x9 : dfff800000000000 x8 : ffff8000190bfdc7 [ 60.768017][ T1] x7 : 0000000000000001 x6 : ffff700003217fb9 [ 60.774094][ T1] x5 : ffff700003217fb9 x4 : ffff000006324a80 [ 60.780170][ T1] x3 : 1fffe00000c64951 x2 : 0000000000000000 [ 60.786247][ T1] x1 : 0000000000000000 x0 : dfff800000000000 [ 60.792324][ T1] Call trace: [ 60.795495][ T1] device_add+0xf60/0x16b0 __fw_devlink_link_to_consumers at drivers/base/core.c:1583 (inlined by) fw_devlink_link_device at drivers/base/core.c:1726 (inlined by) device_add at drivers/base/core.c:3088 [ 60.799813][ T1] platform_device_add+0x274/0x628 [ 60.804833][ T1] acpi_iort_init+0x9d8/0xc50 [ 60.809415][ T1] acpi_init+0x45c/0x4e8 [ 60.813556][ T1] do_one_initcall+0x170/0xb70 [ 60.818224][ T1] kernel_init_freeable+0x6a8/0x734 [ 60.823332][ T1] kernel_init+0x18/0x12c [ 60.827566][ T1] ret_from_fork+0x10/0x1c [ 60.831890][ T1] Code: f2fbffe0 d100205b d343fc41 aa1b03f8 (38e06820) [ 60.838756][ T1] ---[ end trace fa5c8ce17a226d83 ]--- [ 60.844127][ T1] Kernel panic - not syncing: Oops: Fatal exception [ 60.850881][ T1] SMP: stopping secondary CPUs [ 60.855733][ T1] ---[ end Kernel panic - not syncing: Oops: Fatal exception ]---
Quoted 393 lines
--- drivers/base/core.c | 325 ++++++++++++++++++++++++++++++----------- include/linux/device.h | 5 - 2 files changed, 238 insertions(+), 92 deletions(-)drivers/base/core.c +238
-87@@ -46,8 +46,6 @@ early_param("sysfs.deprecated", sysfs_deprecated_setup);#endif /* Device links support. */ -static LIST_HEAD (wait_for_suppliers); -static DEFINE_MUTEX (wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock);@@ -803,74 +801,6 @@ struct device_link *device_link_add(struct device *consumer, }EXPORT_SYMBOL_GPL (device_link_add); -/** -* device_link_wait_for_supplier - Add device to wait_for_suppliers list -* @consumer: Consumer device -* -* Marks the @consumer device as waiting for suppliers to become available by -* adding it to the wait_for_suppliers list. The consumer device will never be -* probed until it's removed from the wait_for_suppliers list. -* -* The caller is responsible for adding the links to the supplier devices once -* they are available and removing the @consumer device from the -* wait_for_suppliers list once links to all the suppliers have been created. -* -* This function is NOT meant to be called from the probe function of the -* consumer but rather from code that creates/adds the consumer device. -*/ -static void device_link_wait_for_supplier (struct device *consumer, -bool need_for_probe) -{ -mutex_lock (&wfs_lock); -list_add_tail (&consumer->links.needs_suppliers, &wait_for_suppliers); - consumer->links.need_for_probe = need_for_probe; -mutex_unlock (&wfs_lock); -} - -static void device_link_wait_for_mandatory_supplier (struct device *consumer) -{ -device_link_wait_for_supplier (consumer, true); -} - -static void device_link_wait_for_optional_supplier (struct device *consumer) -{ -device_link_wait_for_supplier (consumer, false); -} - -/** -* device_link_add_missing_supplier_links - Add links from consumer devices to -* supplier devices, leaving any -* consumer with inactive suppliers on -* the wait_for_suppliers list -* -* Loops through all consumers waiting on suppliers and tries to add all their -* supplier links. If that succeeds, the consumer device is removed from -* wait_for_suppliers list. Otherwise, they are left in the wait_for_suppliers -* list. Devices left on the wait_for_suppliers list will not be probed. -* -* The fwnode add_links callback is expected to return 0 if it has found and -* added all the supplier links for the consumer device. It should return an -* error if it isn't able to do so. -* -* The caller of device_link_wait_for_supplier() is expected to call this once -* it's aware of potential suppliers becoming available. -*/ -static void device_link_add_missing_supplier_links (void ) -{ -struct device *dev, *tmp; - -mutex_lock (&wfs_lock); -list_for_each_entry_safe (dev, tmp, &wait_for_suppliers, - links.needs_suppliers) { -int ret =fwnode_call_int_op (dev->fwnode, add_links, dev); -if (!ret) -list_del_init (&dev->links.needs_suppliers); -else if (ret != -ENODEV ) - dev->links.need_for_probe = false; - } -mutex_unlock (&wfs_lock); -} -#ifdef CONFIG_SRCU static void __device_link_del (struct kref *kref) {@@ -1195,9 +1125,8 @@ void device_links_driver_bound(struct device *dev)* the device links it needs to or make new device links as it needs * them. So, it no longer needs to wait on any suppliers. */ -mutex_lock (&wfs_lock); -list_del_init (&dev->links.needs_suppliers); -mutex_unlock (&wfs_lock); +if (dev->fwnode && dev->fwnode->dev == dev) +fwnode_links_purge_suppliers (dev->fwnode);device_remove_file (dev, &dev_attr_waiting_for_supplier);device_links_write_lock ();@@ -1488,10 +1417,6 @@ static void device_links_purge(struct device *dev)if (dev->class == &devlink_class)return ; -mutex_lock (&wfs_lock); -list_del (&dev->links.needs_suppliers); -mutex_unlock (&wfs_lock); -/* * Delete all of the remaining links from this device to any other * devices (either consumers or suppliers). @@ -1561,19 +1486,246 @@ static void fw_devlink_parse_fwtree(struct fwnode_handle *fwnode)fw_devlink_parse_fwtree (child); } -static void fw_devlink_link_device (struct device *dev) +/** +* fw_devlink_create_devlink - Create a device link from a consumer to fwnode +* @con - Consumer device for the device link +* @sup_handle - fwnode handle of supplier +* +* This function will try to create a device link between the consumer device +* @con and the supplier device represented by @sup_handle. +* +* The supplier has to be provided as a fwnode because incorrect cycles in +* fwnode links can sometimes cause the supplier device to never be created. +* This function detects such cases and returns an error if it cannot create a +* device link from the consumer to a missing supplier. +* +* Returns, +* 0 on successfully creating a device link +* -EINVAL if the device link cannot be created as expected +* -EAGAIN if the device link cannot be created right now, but it may be +* possible to do that in the future +*/ +static int fw_devlink_create_devlink (struct device *con, +struct fwnode_handle *sup_handle,u32 flags) +{ +struct device *sup_dev; +int ret =0 ; + + sup_dev =get_dev_from_fwnode (sup_handle); +if (sup_dev) { +/* +* If this fails, it is due to cycles in device links. Just +* give up on this link and treat it as invalid. +*/ +if (!device_link_add (con, sup_dev, flags)) + ret = -EINVAL ; + + goto out; + } + +/* +* DL_FLAG_SYNC_STATE_ONLY doesn't block probing and supports +* cycles. So cycle detection isn't necessary and shouldn't be +* done. +*/ +if (flags &DL_FLAG_SYNC_STATE_ONLY ) +return -EAGAIN ; + +/* +* If we can't find the supplier device from its fwnode, it might be +* due to a cyclic dependency between fwnodes. Some of these cycles can +* be broken by applying logic. Check for these types of cycles and +* break them so that devices in the cycle probe properly. +* +* If the supplier's parent is dependent on the consumer, then +* the consumer-supplier dependency is a false dependency. So, +* treat it as an invalid link. +*/ + sup_dev =fwnode_get_next_parent_dev (sup_handle); +if (sup_dev &&device_is_dependent (con, sup_dev)) { +dev_dbg (con,"Not linking to %pfwP - False link\n" , + sup_handle); + ret = -EINVAL ; + }else { +/* +* Can't check for cycles or no cycles. So let's try +* again later. +*/ + ret = -EAGAIN ; + } + +out: +put_device (sup_dev); +return ret; +} + +/** +* __fw_devlink_link_to_consumers - Create device links to consumers of a device +* @dev - Device that needs to be linked to its consumers +* +* This function looks at all the consumer fwnodes of @dev and creates device +* links between the consumer device and @dev (supplier). +* +* If the consumer device has not been added yet, then this function creates a +* SYNC_STATE_ONLY link between @dev (supplier) and the closest ancestor device +* of the consumer fwnode. This is necessary to make sure @dev doesn't get a +* sync_state() callback before the real consumer device gets to be added and +* then probed. +* +* Once device links are created from the real consumer to @dev (supplier), the +* fwnode links are deleted. +*/ +static void __fw_devlink_link_to_consumers (struct device *dev) +{ +struct fwnode_handle *fwnode = dev->fwnode; +struct fwnode_link *link, *tmp; + +list_for_each_entry_safe (link, tmp, &fwnode->consumers, s_hook) { +u32 dl_flags =fw_devlink_get_flags (); +struct device *con_dev; +bool own_link = true; +int ret; + + con_dev =get_dev_from_fwnode (link->consumer); +/* +* If consumer device is not available yet, make a "proxy" +* SYNC_STATE_ONLY link from the consumer's parent device to +* the supplier device. This is necessary to make sure the +* supplier doesn't get a sync_state() callback before the real +* consumer can create a device link to the supplier. +* +* This proxy link step is needed to handle the case where the +* consumer's parent device is added before the supplier. +*/ +if (!con_dev) { + con_dev =fwnode_get_next_parent_dev (link->consumer); +/* +* However, if the consumer's parent device is also the +* parent of the supplier, don't create a +* consumer-supplier link from the parent to its child +* device. Such a dependency is impossible. +*/ +if (con_dev && +fwnode_is_ancestor_of (con_dev->fwnode, fwnode)) { +put_device (con_dev); + con_dev =NULL ; + }else { + own_link = false; + dl_flags =DL_FLAG_SYNC_STATE_ONLY ; + } + } + +if (!con_dev) +continue ; + + ret =fw_devlink_create_devlink (con_dev, fwnode, dl_flags); +put_device (con_dev); +if (!own_link || ret == -EAGAIN ) +continue ; + +list_del (&link->s_hook); +list_del (&link->c_hook); +kfree (link); + } +} + +/** +* __fw_devlink_link_to_suppliers - Create device links to suppliers of a device +* @dev - The consumer device that needs to be linked to its suppliers +* @fwnode - Root of the fwnode tree that is used to create device links +* +* This function looks at all the supplier fwnodes of fwnode tree rooted at +* @fwnode and creates device links between @dev (consumer) and all the +* supplier devices of the entire fwnode tree at @fwnode. +* +* The function creates normal (non-SYNC_STATE_ONLY) device links between @dev +* and the real suppliers of @dev. Once these device links are created, the +* fwnode links are deleted. When such device links are successfully created, +* this function is called recursively on those supplier devices. This is +* needed to detect and break some invalid cycles in fwnode links. See +* fw_devlink_create_devlink() for more details. +* +* In addition, it also looks at all the suppliers of the entire fwnode tree +* because some of the child devices of @dev that have not been added yet +* (because @dev hasn't probed) might already have their suppliers added to +* driver core. So, this function creates SYNC_STATE_ONLY device links between +* @dev (consumer) and these suppliers to make sure they don't execute their +* sync_state() callbacks before these child devices have a chance to create +* their device links. The fwnode links that correspond to the child devices +* aren't delete because they are needed later to create the device links +* between the real consumer and supplier devices. +*/ +static void __fw_devlink_link_to_suppliers (struct device *dev, +struct fwnode_handle *fwnode) { -int fw_ret; +bool own_link = (dev->fwnode == fwnode); +struct fwnode_link *link, *tmp; +struct fwnode_handle *child =NULL ; +u32 dl_flags; + +if (own_link) + dl_flags =fw_devlink_get_flags (); +else + dl_flags =DL_FLAG_SYNC_STATE_ONLY ; -device_link_add_missing_supplier_links (); +list_for_each_entry_safe (link, tmp, &fwnode->suppliers, c_hook) { +int ret; +struct device *sup_dev; +struct fwnode_handle *sup = link->supplier; + + ret =fw_devlink_create_devlink (dev, sup, dl_flags); +if (!own_link || ret == -EAGAIN ) +continue ; -if (fw_devlink_flags &&fwnode_has_op (dev->fwnode, add_links)) { - fw_ret =fwnode_call_int_op (dev->fwnode, add_links, dev); -if (fw_ret == -ENODEV && !fw_devlink_is_permissive ()) -device_link_wait_for_mandatory_supplier (dev); -else if (fw_ret) -device_link_wait_for_optional_supplier (dev); +list_del (&link->s_hook); +list_del (&link->c_hook); +kfree (link); + +/* If no device link was created, nothing more to do. */ +if (ret) +continue ; + +/* +* If a device link was successfully created to a supplier, we +* now need to try and link the supplier to all its suppliers. +* +* This is needed to detect and delete false dependencies in +* fwnode links that haven't been converted to a device link +* yet. See comments in fw_devlink_create_devlink() for more +* details on the false dependency. +* +* Without deleting these false dependencies, some devices will +* never probe because they'll keep waiting for their false +* dependency fwnode links to be converted to device links. +*/ + sup_dev =get_dev_from_fwnode (sup); +__fw_devlink_link_to_suppliers (sup_dev, sup_dev->fwnode); +put_device (sup_dev); } + +/* +* Make "proxy" SYNC_STATE_ONLY device links to represent the needs of +* all the descendants. This proxy link step is needed to handle the +* case where the supplier is added before the consumer's parent device +* (@dev). +*/ +while ((child =fwnode_get_next_available_child_node (fwnode, child))) +__fw_devlink_link_to_suppliers (dev, child); +} + +static void fw_devlink_link_device (struct device *dev) +{ +struct fwnode_handle *fwnode = dev->fwnode; + +if (!fw_devlink_flags) +return ; + +fw_devlink_parse_fwtree (fwnode); + +mutex_lock (&fwnode_link_lock); +__fw_devlink_link_to_consumers (dev); +__fw_devlink_link_to_suppliers (dev, fwnode); +mutex_unlock (&fwnode_link_lock); }/* Device links support end. */ @@ -2431,7 +2583,6 @@ void device_initialize(struct device *dev)#endif INIT_LIST_HEAD (&dev->links.consumers);INIT_LIST_HEAD (&dev->links.suppliers); -INIT_LIST_HEAD (&dev->links.needs_suppliers);INIT_LIST_HEAD (&dev->links.defer_sync); dev->links.status =DL_DEV_NO_DRIVER ; }include/linux/device.h +0
-3@@ -351,18 +351,13 @@ enum dl_dev_state {* struct dev_links_info - Device data related to device links. * @suppliers: List of links to supplier devices. * @consumers: List of links to consumer devices. -* @needs_suppliers: Hook to global list of devices waiting for suppliers. * @defer_sync: Hook to global list of devices that have deferred sync_state. -* @need_for_probe: If needs_suppliers is on a list, this indicates if the -* suppliers are needed for probe or not. * @status: Driver status information.
include/linux/device.h enum dl_dev_state { · line 363
Quoted 10 lines
include/linux/device.h +0
-2*/ struct dev_links_info {struct list_head suppliers;struct list_head consumers; -struct list_head needs_suppliers;struct list_head defer_sync; -bool need_for_probe;enum dl_dev_state status; };
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
Quoted 39 lines · Qian Cai
Quoted 33 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch uses all the setup done by the previous patches in this series to refactor
fw_devlinkto be more efficient. Most of the code has been moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.Quoted 4 lines
[1] - https://lore.kernel.org/linux-omap/[email protected]/
Signed-off-by Saravana Kannan <[email protected]>Tested-by Laurent Pinchart <[email protected]>Tested-by Grygorii Strashko <[email protected]>
Quoted 5 lines
Reverting this commit and its dependency:
2d09e6eb4a6fdriver core: Delete pointless parameter in fwnode_operations.add_linksfrom today's linux-next fixed a boot crash on an arm64 Thunder X2 server.
Since the call stack implicates the platform-device-wrangling we do in IORT code I took a quick look; AFAICS my guess would be it's blowing up trying to walk a zeroed list head since "driver core: Add fwnode_init()" missed acpi_alloc_fwnode_static().
Robin.
Quoted 458 lines
.config: https://cailca.coding.net/public/linux/mm/git/files/master/arm64.config
[ 57.413929][ T1] ACPI: 5 ACPI AML tables successfully acquired and loaded [ 60.571643][ T1] ACPI: Interpreter enabled [ 60.576104][ T1] ACPI: Using GIC for interrupt routing [ 60.582474][ T1] ACPI: MCFG table detected, 1 entries [ 60.588051][ T1] ACPI: IORT: SMMU-v3[402300000] Mapped to Proximity domain 0 [ 60.601374][ T1] Unable to handle kernel paging request at virtual address dfff800000000000 [ 60.610146][ T1] Mem abort info: [ 60.613694][ T1] ESR = 0x96000004 [ 60.617496][ T1] EC = 0x25: DABT (current EL), IL = 32 bits [ 60.623616][ T1] SET = 0, FnV = 0 [ 60.627420][ T1] EA = 0, S1PTW = 0 [ 60.631304][ T1] Data abort info: [ 60.634957][ T1] ISV = 0, ISS = 0x00000004 [ 60.639546][ T1] CM = 0, WnR = 0 [ 60.643255][ T1] [dfff800000000000] address between user and kernel address ranges [ 60.651226][ T1] Internal error: Oops: 96000004 [#1] SMP [ 60.656864][ T1] Modules linked in: [ 60.660658][ T1] CPU: 38 PID: 1 Comm: swapper/0 Tainted: G W 5.10.0-rc7-next-20201211 #2 [ 60.670424][ T1] Hardware name: HPE Apollo 70 /C01_APACHE_MB , BIOS L50_5.13_1.16 07/29/2020 [ 60.680979][ T1] pstate: 10400009 (nzcV daif +PAN -UAO -TCO BTYPE=--) [ 60.687757][ T1] pc : device_add+0xf60/0x16b0 [ 60.692430][ T1] lr : device_add+0xf08/0x16b0 [ 60.697098][ T1] sp : ffff0000063bf7d0 [ 60.701147][ T1] x29: ffff0000063bf7d0 x28: ffff00001f760810 [ 60.707226][ T1] x27: fffffffffffffff8 x26: ffff00001f760858 [ 60.713304][ T1] x25: ffff00001f760c58 x24: fffffffffffffff8 [ 60.719381][ T1] x23: 1fffe00003eec10b x22: ffff8000190d0260 [ 60.725458][ T1] x21: ffff800011dba708 x20: 0000000000000000 [ 60.731535][ T1] x19: 1fffe00000c77f10 x18: 1fffe001cf0d53ed [ 60.737616][ T1] x17: 0000000000000000 x16: 1ffff000033676f1 [ 60.743709][ T1] x15: 0000000000000000 x14: ffff800011731e34 [ 60.749786][ T1] x13: ffff700003217fb9 x12: 1ffff00003217fb8 [ 60.755864][ T1] x11: 1ffff00003217fb8 x10: ffff700003217fb8 [ 60.761940][ T1] x9 : dfff800000000000 x8 : ffff8000190bfdc7 [ 60.768017][ T1] x7 : 0000000000000001 x6 : ffff700003217fb9 [ 60.774094][ T1] x5 : ffff700003217fb9 x4 : ffff000006324a80 [ 60.780170][ T1] x3 : 1fffe00000c64951 x2 : 0000000000000000 [ 60.786247][ T1] x1 : 0000000000000000 x0 : dfff800000000000 [ 60.792324][ T1] Call trace: [ 60.795495][ T1] device_add+0xf60/0x16b0 __fw_devlink_link_to_consumers at drivers/base/core.c:1583 (inlined by) fw_devlink_link_device at drivers/base/core.c:1726 (inlined by) device_add at drivers/base/core.c:3088 [ 60.799813][ T1] platform_device_add+0x274/0x628 [ 60.804833][ T1] acpi_iort_init+0x9d8/0xc50 [ 60.809415][ T1] acpi_init+0x45c/0x4e8 [ 60.813556][ T1] do_one_initcall+0x170/0xb70 [ 60.818224][ T1] kernel_init_freeable+0x6a8/0x734 [ 60.823332][ T1] kernel_init+0x18/0x12c [ 60.827566][ T1] ret_from_fork+0x10/0x1c [ 60.831890][ T1] Code: f2fbffe0 d100205b d343fc41 aa1b03f8 (38e06820) [ 60.838756][ T1] ---[ end trace fa5c8ce17a226d83 ]--- [ 60.844127][ T1] Kernel panic - not syncing: Oops: Fatal exception [ 60.850881][ T1] SMP: stopping secondary CPUs [ 60.855733][ T1] ---[ end Kernel panic - not syncing: Oops: Fatal exception ]---Quoted 401 lines
--- drivers/base/core.c | 325 ++++++++++++++++++++++++++++++----------- include/linux/device.h | 5 - 2 files changed, 238 insertions(+), 92 deletions(-)drivers/base/core.c +238
-87@@ -46,8 +46,6 @@ early_param("sysfs.deprecated", sysfs_deprecated_setup);#endif /* Device links support. */ -static LIST_HEAD (wait_for_suppliers); -static DEFINE_MUTEX (wfs_lock);static LIST_HEAD (deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock);@@ -803,74 +801,6 @@ struct device_link *device_link_add(struct device *consumer, }EXPORT_SYMBOL_GPL (device_link_add); -/** -* device_link_wait_for_supplier - Add device to wait_for_suppliers list -* @consumer: Consumer device -* -* Marks the @consumer device as waiting for suppliers to become available by -* adding it to the wait_for_suppliers list. The consumer device will never be -* probed until it's removed from the wait_for_suppliers list. -* -* The caller is responsible for adding the links to the supplier devices once -* they are available and removing the @consumer device from the -* wait_for_suppliers list once links to all the suppliers have been created. -* -* This function is NOT meant to be called from the probe function of the -* consumer but rather from code that creates/adds the consumer device. -*/ -static void device_link_wait_for_supplier (struct device *consumer, -bool need_for_probe) -{ -mutex_lock (&wfs_lock); -list_add_tail (&consumer->links.needs_suppliers, &wait_for_suppliers); - consumer->links.need_for_probe = need_for_probe; -mutex_unlock (&wfs_lock); -} - -static void device_link_wait_for_mandatory_supplier (struct device *consumer) -{ -device_link_wait_for_supplier (consumer, true); -} - -static void device_link_wait_for_optional_supplier (struct device *consumer) -{ -device_link_wait_for_supplier (consumer, false); -} - -/** -* device_link_add_missing_supplier_links - Add links from consumer devices to -* supplier devices, leaving any -* consumer with inactive suppliers on -* the wait_for_suppliers list -* -* Loops through all consumers waiting on suppliers and tries to add all their -* supplier links. If that succeeds, the consumer device is removed from -* wait_for_suppliers list. Otherwise, they are left in the wait_for_suppliers -* list. Devices left on the wait_for_suppliers list will not be probed. -* -* The fwnode add_links callback is expected to return 0 if it has found and -* added all the supplier links for the consumer device. It should return an -* error if it isn't able to do so. -* -* The caller of device_link_wait_for_supplier() is expected to call this once -* it's aware of potential suppliers becoming available. -*/ -static void device_link_add_missing_supplier_links (void ) -{ -struct device *dev, *tmp; - -mutex_lock (&wfs_lock); -list_for_each_entry_safe (dev, tmp, &wait_for_suppliers, - links.needs_suppliers) { -int ret =fwnode_call_int_op (dev->fwnode, add_links, dev); -if (!ret) -list_del_init (&dev->links.needs_suppliers); -else if (ret != -ENODEV ) - dev->links.need_for_probe = false; - } -mutex_unlock (&wfs_lock); -} -#ifdef CONFIG_SRCU static void __device_link_del (struct kref *kref) {@@ -1195,9 +1125,8 @@ void device_links_driver_bound(struct device *dev)* the device links it needs to or make new device links as it needs * them. So, it no longer needs to wait on any suppliers. */ -mutex_lock (&wfs_lock); -list_del_init (&dev->links.needs_suppliers); -mutex_unlock (&wfs_lock); +if (dev->fwnode && dev->fwnode->dev == dev) +fwnode_links_purge_suppliers (dev->fwnode);device_remove_file (dev, &dev_attr_waiting_for_supplier);device_links_write_lock ();@@ -1488,10 +1417,6 @@ static void device_links_purge(struct device *dev)if (dev->class == &devlink_class)return ; -mutex_lock (&wfs_lock); -list_del (&dev->links.needs_suppliers); -mutex_unlock (&wfs_lock); -/* * Delete all of the remaining links from this device to any other * devices (either consumers or suppliers). @@ -1561,19 +1486,246 @@ static void fw_devlink_parse_fwtree(struct fwnode_handle *fwnode)fw_devlink_parse_fwtree (child); } -static void fw_devlink_link_device (struct device *dev) +/** +* fw_devlink_create_devlink - Create a device link from a consumer to fwnode +* @con - Consumer device for the device link +* @sup_handle - fwnode handle of supplier +* +* This function will try to create a device link between the consumer device +* @con and the supplier device represented by @sup_handle. +* +* The supplier has to be provided as a fwnode because incorrect cycles in +* fwnode links can sometimes cause the supplier device to never be created. +* This function detects such cases and returns an error if it cannot create a +* device link from the consumer to a missing supplier. +* +* Returns, +* 0 on successfully creating a device link +* -EINVAL if the device link cannot be created as expected +* -EAGAIN if the device link cannot be created right now, but it may be +* possible to do that in the future +*/ +static int fw_devlink_create_devlink (struct device *con, +struct fwnode_handle *sup_handle,u32 flags) +{ +struct device *sup_dev; +int ret =0 ; + + sup_dev =get_dev_from_fwnode (sup_handle); +if (sup_dev) { +/* +* If this fails, it is due to cycles in device links. Just +* give up on this link and treat it as invalid. +*/ +if (!device_link_add (con, sup_dev, flags)) + ret = -EINVAL ; + + goto out; + } + +/* +* DL_FLAG_SYNC_STATE_ONLY doesn't block probing and supports +* cycles. So cycle detection isn't necessary and shouldn't be +* done. +*/ +if (flags &DL_FLAG_SYNC_STATE_ONLY ) +return -EAGAIN ; + +/* +* If we can't find the supplier device from its fwnode, it might be +* due to a cyclic dependency between fwnodes. Some of these cycles can +* be broken by applying logic. Check for these types of cycles and +* break them so that devices in the cycle probe properly. +* +* If the supplier's parent is dependent on the consumer, then +* the consumer-supplier dependency is a false dependency. So, +* treat it as an invalid link. +*/ + sup_dev =fwnode_get_next_parent_dev (sup_handle); +if (sup_dev &&device_is_dependent (con, sup_dev)) { +dev_dbg (con,"Not linking to %pfwP - False link\n" , + sup_handle); + ret = -EINVAL ; + }else { +/* +* Can't check for cycles or no cycles. So let's try +* again later. +*/ + ret = -EAGAIN ; + } + +out: +put_device (sup_dev); +return ret; +} + +/** +* __fw_devlink_link_to_consumers - Create device links to consumers of a device +* @dev - Device that needs to be linked to its consumers +* +* This function looks at all the consumer fwnodes of @dev and creates device +* links between the consumer device and @dev (supplier). +* +* If the consumer device has not been added yet, then this function creates a +* SYNC_STATE_ONLY link between @dev (supplier) and the closest ancestor device +* of the consumer fwnode. This is necessary to make sure @dev doesn't get a +* sync_state() callback before the real consumer device gets to be added and +* then probed. +* +* Once device links are created from the real consumer to @dev (supplier), the +* fwnode links are deleted. +*/ +static void __fw_devlink_link_to_consumers (struct device *dev) +{ +struct fwnode_handle *fwnode = dev->fwnode; +struct fwnode_link *link, *tmp; + +list_for_each_entry_safe (link, tmp, &fwnode->consumers, s_hook) { +u32 dl_flags =fw_devlink_get_flags (); +struct device *con_dev; +bool own_link = true; +int ret; + + con_dev =get_dev_from_fwnode (link->consumer); +/* +* If consumer device is not available yet, make a "proxy" +* SYNC_STATE_ONLY link from the consumer's parent device to +* the supplier device. This is necessary to make sure the +* supplier doesn't get a sync_state() callback before the real +* consumer can create a device link to the supplier. +* +* This proxy link step is needed to handle the case where the +* consumer's parent device is added before the supplier. +*/ +if (!con_dev) { + con_dev =fwnode_get_next_parent_dev (link->consumer); +/* +* However, if the consumer's parent device is also the +* parent of the supplier, don't create a +* consumer-supplier link from the parent to its child +* device. Such a dependency is impossible. +*/ +if (con_dev && +fwnode_is_ancestor_of (con_dev->fwnode, fwnode)) { +put_device (con_dev); + con_dev =NULL ; + }else { + own_link = false; + dl_flags =DL_FLAG_SYNC_STATE_ONLY ; + } + } + +if (!con_dev) +continue ; + + ret =fw_devlink_create_devlink (con_dev, fwnode, dl_flags); +put_device (con_dev); +if (!own_link || ret == -EAGAIN ) +continue ; + +list_del (&link->s_hook); +list_del (&link->c_hook); +kfree (link); + } +} + +/** +* __fw_devlink_link_to_suppliers - Create device links to suppliers of a device +* @dev - The consumer device that needs to be linked to its suppliers +* @fwnode - Root of the fwnode tree that is used to create device links +* +* This function looks at all the supplier fwnodes of fwnode tree rooted at +* @fwnode and creates device links between @dev (consumer) and all the +* supplier devices of the entire fwnode tree at @fwnode. +* +* The function creates normal (non-SYNC_STATE_ONLY) device links between @dev +* and the real suppliers of @dev. Once these device links are created, the +* fwnode links are deleted. When such device links are successfully created, +* this function is called recursively on those supplier devices. This is +* needed to detect and break some invalid cycles in fwnode links. See +* fw_devlink_create_devlink() for more details. +* +* In addition, it also looks at all the suppliers of the entire fwnode tree +* because some of the child devices of @dev that have not been added yet +* (because @dev hasn't probed) might already have their suppliers added to +* driver core. So, this function creates SYNC_STATE_ONLY device links between +* @dev (consumer) and these suppliers to make sure they don't execute their +* sync_state() callbacks before these child devices have a chance to create +* their device links. The fwnode links that correspond to the child devices +* aren't delete because they are needed later to create the device links +* between the real consumer and supplier devices. +*/ +static void __fw_devlink_link_to_suppliers (struct device *dev, +struct fwnode_handle *fwnode) { -int fw_ret; +bool own_link = (dev->fwnode == fwnode); +struct fwnode_link *link, *tmp; +struct fwnode_handle *child =NULL ; +u32 dl_flags; + +if (own_link) + dl_flags =fw_devlink_get_flags (); +else + dl_flags =DL_FLAG_SYNC_STATE_ONLY ; -device_link_add_missing_supplier_links (); +list_for_each_entry_safe (link, tmp, &fwnode->suppliers, c_hook) { +int ret; +struct device *sup_dev; +struct fwnode_handle *sup = link->supplier; + + ret =fw_devlink_create_devlink (dev, sup, dl_flags); +if (!own_link || ret == -EAGAIN ) +continue ; -if (fw_devlink_flags &&fwnode_has_op (dev->fwnode, add_links)) { - fw_ret =fwnode_call_int_op (dev->fwnode, add_links, dev); -if (fw_ret == -ENODEV && !fw_devlink_is_permissive ()) -device_link_wait_for_mandatory_supplier (dev); -else if (fw_ret) -device_link_wait_for_optional_supplier (dev); +list_del (&link->s_hook); +list_del (&link->c_hook); +kfree (link); + +/* If no device link was created, nothing more to do. */ +if (ret) +continue ; + +/* +* If a device link was successfully created to a supplier, we +* now need to try and link the supplier to all its suppliers. +* +* This is needed to detect and delete false dependencies in +* fwnode links that haven't been converted to a device link +* yet. See comments in fw_devlink_create_devlink() for more +* details on the false dependency. +* +* Without deleting these false dependencies, some devices will +* never probe because they'll keep waiting for their false +* dependency fwnode links to be converted to device links. +*/ + sup_dev =get_dev_from_fwnode (sup); +__fw_devlink_link_to_suppliers (sup_dev, sup_dev->fwnode); +put_device (sup_dev); } + +/* +* Make "proxy" SYNC_STATE_ONLY device links to represent the needs of +* all the descendants. This proxy link step is needed to handle the +* case where the supplier is added before the consumer's parent device +* (@dev). +*/ +while ((child =fwnode_get_next_available_child_node (fwnode, child))) +__fw_devlink_link_to_suppliers (dev, child); +} + +static void fw_devlink_link_device (struct device *dev) +{ +struct fwnode_handle *fwnode = dev->fwnode; + +if (!fw_devlink_flags) +return ; + +fw_devlink_parse_fwtree (fwnode); + +mutex_lock (&fwnode_link_lock); +__fw_devlink_link_to_consumers (dev); +__fw_devlink_link_to_suppliers (dev, fwnode); +mutex_unlock (&fwnode_link_lock); }/* Device links support end. */ @@ -2431,7 +2583,6 @@ void device_initialize(struct device *dev)#endif INIT_LIST_HEAD (&dev->links.consumers);INIT_LIST_HEAD (&dev->links.suppliers); -INIT_LIST_HEAD (&dev->links.needs_suppliers);INIT_LIST_HEAD (&dev->links.defer_sync); dev->links.status =DL_DEV_NO_DRIVER ; }include/linux/device.h +0
-5@@ -351,18 +351,13 @@ enum dl_dev_state {* struct dev_links_info - Device data related to device links. * @suppliers: List of links to supplier devices. * @consumers: List of links to consumer devices. -* @needs_suppliers: Hook to global list of devices waiting for suppliers. * @defer_sync: Hook to global list of devices that have deferred sync_state. -* @need_for_probe: If needs_suppliers is on a list, this indicates if the -* suppliers are needed for probe or not. * @status: Driver status information. */ struct dev_links_info {struct list_head suppliers;struct list_head consumers; -struct list_head needs_suppliers;struct list_head defer_sync; -bool need_for_probe;enum dl_dev_state status;
Quoted 9 lines
include/linux/device.h enum dl_dev_state { · line 363
Quoted 2 lines
include/linux/device.h +0
-0};_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
Quoted 43 lines · Robin Murphy
Quoted 41 lines · Qian Cai
Quoted 33 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch uses all the setup done by the previous patches in this series to refactor
fw_devlinkto be more efficient. Most of the code has been moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.Quoted 4 lines
[1] - https://lore.kernel.org/linux-omap/[email protected]/
Signed-off-by Saravana Kannan <[email protected]>Tested-by Laurent Pinchart <[email protected]>Tested-by Grygorii Strashko <[email protected]>Reverting this commit and its dependency:
Quoted 8 lines
Quoted 3 lines
2d09e6eb4a6fdriver core: Delete pointless parameter in fwnode_operations.add_linksfrom today's linux-next fixed a boot crash on an arm64 Thunder X2 server.
Since the call stack implicates the platform-device-wrangling we do in IORT code I took a quick look; AFAICS my guess would be it's blowing up trying to walk a zeroed list head since "driver core: Add
fwnode_init()" missedacpi_alloc_fwnode_static().
Thanks Robin. I'm pretty sure this is the reason. I thought I fixed all ACPI cases, but clearly I missed this one. I'll send out a patch for this today. If you think there are any other places I missed please let me know. I'll try some git grep foo to see if I missed any other instances of fwnode ops being set.
-Saravana
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
Quoted 53 lines · Saravana Kannan
Quoted 43 lines · Robin Murphy
Quoted 41 lines · Qian Cai
Quoted 33 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch uses all the setup done by the previous patches in this series to refactor
fw_devlinkto be more efficient. Most of the code has been moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.Quoted 4 lines
[1] - https://lore.kernel.org/linux-omap/[email protected]/
Signed-off-by Saravana Kannan <[email protected]>Tested-by Laurent Pinchart <[email protected]>Tested-by Grygorii Strashko <[email protected]>Reverting this commit and its dependency:
Quoted 8 lines
Quoted 3 lines
2d09e6eb4a6fdriver core: Delete pointless parameter in fwnode_operations.add_linksfrom today's linux-next fixed a boot crash on an arm64 Thunder X2 server.
Since the call stack implicates the platform-device-wrangling we do in IORT code I took a quick look; AFAICS my guess would be it's blowing up trying to walk a zeroed list head since "driver core: Add
fwnode_init()" missedacpi_alloc_fwnode_static().
Quoted 5 lines
Thanks Robin. I'm pretty sure this is the reason. I thought I fixed all ACPI cases, but clearly I missed this one. I'll send out a patch for this today. If you think there are any other places I missed please let me know. I'll try some git grep foo to see if I missed any other instances of fwnode ops being set.
Yup, that fixed it here (QDF2400).
Thanks,
M.
include/linux/acpi.h +1 -1
@@ -55,7 +55,7 @@ static inline struct fwnode_handle *acpi_alloc_fwnode_static(void)if (!fwnode)return NULL ; - fwnode->ops = &acpi_static_fwnode_ops; +fwnode_init (fwnode, &acpi_static_fwnode_ops);return fwnode; }
Signature · 6 lines
Jazz is not dead. It just smells funny... _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
Quoted 83 lines · Marc Zyngier
Quoted 56 lines · Saravana Kannan
Quoted 45 lines · Robin Murphy
Quoted 43 lines · Qian Cai
Quoted 33 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch uses all the setup done by the previous patches in this series to refactor
fw_devlinkto be more efficient. Most of the code has been moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.Quoted 4 lines
[1] - https://lore.kernel.org/linux-omap/[email protected]/
Signed-off-by Saravana Kannan <[email protected]>Tested-by Laurent Pinchart <[email protected]>Tested-by Grygorii Strashko <[email protected]>Reverting this commit and its dependency:
2d09e6eb4a6fdriver core: Delete pointless parameter in fwnode_operations.add_linksQuoted 8 lines
Quoted 1 line
from today's linux-next fixed a boot crash on an arm64 Thunder X2 server.
Since the call stack implicates the platform-device-wrangling we do in IORT code I took a quick look; AFAICS my guess would be it's blowing up
trying to walk a zeroed list head since "driver core: Addfwnode_init()"
missedacpi_alloc_fwnode_static().Quoted 5 lines
Thanks Robin. I'm pretty sure this is the reason. I thought I fixed all ACPI cases, but clearly I missed this one. I'll send out a patch for this today. If you think there are any other places I missed please let me know. I'll try some git grep foo to see if I missed any other instances of fwnode ops being set.
Yup, that fixed it here (QDF2400).
Thanks,
M.include/linux/acpi.h +1
-1@@ -55,7 +55,7 @@ static inline struct fwnode_handle *acpi_alloc_fwnode_static(void)if (!fwnode)return NULL ; - fwnode->ops = &acpi_static_fwnode_ops; +fwnode_init (fwnode, &acpi_static_fwnode_ops);return fwnode;
Quoted 2 lines
}
Lol, my only contribution to the patch will be the commit text. I'll send them with reported-by, suggested-by and tested-by if no one less beats me to it.
-Saravana
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
Quoted 3 lines · Saravana Kannan
Lol, my only contribution to the patch will be the commit text. I'll send them with reported-by, suggested-by and tested-by if no one less beats me to it.
Teamwork!
M.
Signature · 6 lines
Jazz is not dead. It just smells funny... _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
Quoted 10 lines · Marc Zyngier
Quoted 3 lines · Saravana Kannan
Lol, my only contribution to the patch will be the commit text. I'll send them with reported-by, suggested-by and tested-by if no one less beats me to it.
Teamwork!
M.
Forgot to CC most of the folks/lists here, but patch has been sent.
https://lore.kernel.org/lkml/[email protected]/
-Saravana
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
In reply to Saravana KannanQuoted 33 lines
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch uses all the setup done by the previous patches in this series to refactor
fw_devlinkto be more efficient. Most of the code has been moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.
Quoted 4 lines
[1] - https://lore.kernel.org/linux-omap/[email protected]/
Signed-off-by Saravana Kannan <[email protected]>Tested-by Laurent Pinchart <[email protected]>Tested-by Grygorii Strashko <[email protected]>
git bisect show that this commit broke my board in 5.11-rc1:
[ 2.294375] sysfs: cannot create duplicate filename '/devices/virtual/devlink/0000:00:00.1--0000:00:00.1' [ 2.303999] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.11.0-rc1-00016-ga0fb284b267 #267 [ 2.312125] Hardware name: Kontron SMARC-sAL28 (4 Lane) (DT) [ 2.317804] Call trace: [ 2.320253] dump_backtrace+0x0/0x1b8 [ 2.323936] show_stack+0x20/0x70 [ 2.327263] dump_stack+0xd8/0x134 [ 2.330677] sysfs_warn_dup+0x6c/0x88 [ 2.334351] sysfs_create_dir_ns+0xe8/0x100 [ 2.338547] kobject_add_internal+0x9c/0x290 [ 2.342833] kobject_add+0xa0/0x108 [ 2.346331] device_add+0xfc/0x798 [ 2.349746] device_link_add+0x454/0x5e0 [ 2.353682] fw_devlink_create_devlink+0xb8/0xc8 [ 2.358316] __fw_devlink_link_to_suppliers+0x84/0x180 [ 2.363474] __fw_devlink_link_to_suppliers+0x134/0x180 [ 2.368718] device_add+0x778/0x798 [ 2.372217] device_register+0x28/0x38 [ 2.375979] __mdiobus_register+0x94/0x340 [ 2.380089] of_mdiobus_register+0xb4/0x380 [ 2.384285] enetc_pf_probe+0x73c/0xb10 [ 2.388132] local_pci_probe+0x48/0xb8 [ 2.391896] pci_device_probe+0x120/0x1c0 [ 2.395920] really_probe+0xec/0x3c0 [ 2.399505] driver_probe_device+0x60/0xc0 [ 2.403614] device_driver_attach+0x7c/0x88 [ 2.407810] __driver_attach+0x60/0xe8 [ 2.411570] bus_for_each_dev+0x7c/0xd0 [ 2.415419] driver_attach+0x2c/0x38 [ 2.419004] bus_add_driver+0x194/0x1f8 [ 2.422851] driver_register+0x6c/0x128 [ 2.426698] __pci_register_driver+0x4c/0x58 [ 2.430983] enetc_pf_driver_init+0x2c/0x38 [ 2.435181] do_one_initcall+0x54/0x2d8 [ 2.439029] kernel_init_freeable+0x1fc/0x268 [ 2.443403] kernel_init+0x1c/0x120 [ 2.446904] ret_from_fork+0x10/0x30 [ 2.450502] kobject_add_internal failed for 0000:00:00.1--0000:00:00.1 with -EEXIST, don't try to register things with the same name in the same directory.
Looks like it will generate that link twice? Let me know if I can help testing.
See also: https://lavalab.kontron.com/scheduler/job/3894#L831
-michael
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
Quoted 80 lines · Michael Walle
Quoted 34 lines
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch uses all the setup done by the previous patches in this series to refactor
fw_devlinkto be more efficient. Most of the code has been moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.Quoted 4 lines
[1] - https://lore.kernel.org/linux-omap/[email protected]/
Signed-off-by Saravana Kannan <[email protected]>Tested-by Laurent Pinchart <[email protected]>Tested-by Grygorii Strashko <[email protected]>git bisect show that this commit broke my board in 5.11-rc1:
[ 2.294375] sysfs: cannot create duplicate filename '/devices/virtual/devlink/0000:00:00.1--0000:00:00.1' [ 2.303999] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.11.0-rc1-00016-ga0fb284b267 #267 [ 2.312125] Hardware name: Kontron SMARC-sAL28 (4 Lane) (DT) [ 2.317804] Call trace: [ 2.320253] dump_backtrace+0x0/0x1b8 [ 2.323936] show_stack+0x20/0x70 [ 2.327263] dump_stack+0xd8/0x134 [ 2.330677] sysfs_warn_dup+0x6c/0x88 [ 2.334351] sysfs_create_dir_ns+0xe8/0x100 [ 2.338547] kobject_add_internal+0x9c/0x290 [ 2.342833] kobject_add+0xa0/0x108 [ 2.346331] device_add+0xfc/0x798 [ 2.349746] device_link_add+0x454/0x5e0 [ 2.353682] fw_devlink_create_devlink+0xb8/0xc8 [ 2.358316] __fw_devlink_link_to_suppliers+0x84/0x180 [ 2.363474] __fw_devlink_link_to_suppliers+0x134/0x180 [ 2.368718] device_add+0x778/0x798 [ 2.372217] device_register+0x28/0x38 [ 2.375979] __mdiobus_register+0x94/0x340 [ 2.380089] of_mdiobus_register+0xb4/0x380 [ 2.384285] enetc_pf_probe+0x73c/0xb10 [ 2.388132] local_pci_probe+0x48/0xb8 [ 2.391896] pci_device_probe+0x120/0x1c0 [ 2.395920] really_probe+0xec/0x3c0 [ 2.399505] driver_probe_device+0x60/0xc0 [ 2.403614] device_driver_attach+0x7c/0x88 [ 2.407810] __driver_attach+0x60/0xe8 [ 2.411570] bus_for_each_dev+0x7c/0xd0 [ 2.415419] driver_attach+0x2c/0x38 [ 2.419004] bus_add_driver+0x194/0x1f8 [ 2.422851] driver_register+0x6c/0x128 [ 2.426698] __pci_register_driver+0x4c/0x58 [ 2.430983] enetc_pf_driver_init+0x2c/0x38 [ 2.435181] do_one_initcall+0x54/0x2d8 [ 2.439029] kernel_init_freeable+0x1fc/0x268 [ 2.443403] kernel_init+0x1c/0x120 [ 2.446904] ret_from_fork+0x10/0x30 [ 2.450502] kobject_add_internal failed for 0000:00:00.1--0000:00:00.1 with -EEXIST, don't try to register things with the same name in the same directory.
Quoted 4 lines
Looks like it will generate that link twice? Let me know if I can help testing.
See also: https://lavalab.kontron.com/scheduler/job/3894#L831
I'll look into this this week. Is the DT for this board in upstream? If so, can you point me to the DT file(s)?
Also, can you give me the output of this?
find /sys/devices -type d | grep "0000:00:00.1"
Thanks,
Saravana
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
Am 2021-01-05 20:00, schrieb Saravana Kannan:
Quoted 81 lines · Michael Walle
Quoted 80 lines
Quoted 34 lines
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch uses all the setup done by the previous patches in this series to refactor
fw_devlinkto be more efficient. Most of the code has been moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.Quoted 4 lines
[1] - https://lore.kernel.org/linux-omap/[email protected]/
Signed-off-by Saravana Kannan <[email protected]>Tested-by Laurent Pinchart <[email protected]>Tested-by Grygorii Strashko <[email protected]>git bisect show that this commit broke my board in 5.11-rc1:
[ 2.294375] sysfs: cannot create duplicate filename '/devices/virtual/devlink/0000:00:00.1--0000:00:00.1' [ 2.303999] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.11.0-rc1-00016-ga0fb284b267 #267 [ 2.312125] Hardware name: Kontron SMARC-sAL28 (4 Lane) (DT) [ 2.317804] Call trace: [ 2.320253] dump_backtrace+0x0/0x1b8 [ 2.323936] show_stack+0x20/0x70 [ 2.327263] dump_stack+0xd8/0x134 [ 2.330677] sysfs_warn_dup+0x6c/0x88 [ 2.334351] sysfs_create_dir_ns+0xe8/0x100 [ 2.338547] kobject_add_internal+0x9c/0x290 [ 2.342833] kobject_add+0xa0/0x108 [ 2.346331] device_add+0xfc/0x798 [ 2.349746] device_link_add+0x454/0x5e0 [ 2.353682] fw_devlink_create_devlink+0xb8/0xc8 [ 2.358316] __fw_devlink_link_to_suppliers+0x84/0x180 [ 2.363474] __fw_devlink_link_to_suppliers+0x134/0x180 [ 2.368718] device_add+0x778/0x798 [ 2.372217] device_register+0x28/0x38 [ 2.375979] __mdiobus_register+0x94/0x340 [ 2.380089] of_mdiobus_register+0xb4/0x380 [ 2.384285] enetc_pf_probe+0x73c/0xb10 [ 2.388132] local_pci_probe+0x48/0xb8 [ 2.391896] pci_device_probe+0x120/0x1c0 [ 2.395920] really_probe+0xec/0x3c0 [ 2.399505] driver_probe_device+0x60/0xc0 [ 2.403614] device_driver_attach+0x7c/0x88 [ 2.407810] __driver_attach+0x60/0xe8 [ 2.411570] bus_for_each_dev+0x7c/0xd0 [ 2.415419] driver_attach+0x2c/0x38 [ 2.419004] bus_add_driver+0x194/0x1f8 [ 2.422851] driver_register+0x6c/0x128 [ 2.426698] __pci_register_driver+0x4c/0x58 [ 2.430983] enetc_pf_driver_init+0x2c/0x38 [ 2.435181] do_one_initcall+0x54/0x2d8 [ 2.439029] kernel_init_freeable+0x1fc/0x268 [ 2.443403] kernel_init+0x1c/0x120 [ 2.446904] ret_from_fork+0x10/0x30 [ 2.450502] kobject_add_internal failed for 0000:00:00.1--0000:00:00.1 with -EEXIST, don't try to register things with the same name in the same directory.
Quoted 7 lines
Quoted 4 lines
Looks like it will generate that link twice? Let me know if I can help testing.
See also: https://lavalab.kontron.com/scheduler/job/3894#L831
I'll look into this this week. Is the DT for this board in upstream? If so, can you point me to the DT file(s)?
arch/arm64/boot/dts/freescale/fsl-ls1028a-kontron-kbox-a-230-ls.dts
Quoted 2 lines
Also, can you give me the output of this?
find/sys/devices-type d | grep "0000:00:00.1"
# uname -a Linux buildroot 5.11.0-rc1-next-20210104 #298 SMP PREEMPT Tue Jan 5 21:55:23 CET 2021 aarch64 GNU/Linux # find /sys/devices -type d | grep "0000:00:00.1" /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/statistics /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-6 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-6/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-4 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-4/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-7 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-2 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-2/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-5 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-0 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-0/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-3 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-1 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-7 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-7/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-5 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-5/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-3 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-3/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-6 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-1 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-1/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-4 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-2 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-0 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/statistics /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/statistics /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/regulator /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/regulator/regulator.3 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/regulator/regulator.3/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/regulator/regulator.4 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/regulator/regulator.4/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/msi_irqs /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/link /sys/devices/virtual/devlink/5000000.iommu--0000:00:00.1
HTH,
-michael
Re: [PATCH v2 16/17] driver core: Refactor fw_devlink feature
Quoted 142 lines · Michael Walle
Am 2021-01-05 20:00, schrieb Saravana Kannan:
Quoted 85 lines · Michael Walle
Quoted 84 lines
Quoted 34 lines
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch uses all the setup done by the previous patches in this series to refactor
fw_devlinkto be more efficient. Most of the code has been moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.Quoted 4 lines
[1] - https://lore.kernel.org/linux-omap/[email protected]/
Signed-off-by Saravana Kannan <[email protected]>Tested-by Laurent Pinchart <[email protected]>Tested-by Grygorii Strashko <[email protected]>git bisect show that this commit broke my board in 5.11-rc1:
[ 2.294375] sysfs: cannot create duplicate filename '/devices/virtual/devlink/0000:00:00.1--0000:00:00.1' [ 2.303999] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.11.0-rc1-00016-ga0fb284b267 #267 [ 2.312125] Hardware name: Kontron SMARC-sAL28 (4 Lane) (DT) [ 2.317804] Call trace: [ 2.320253] dump_backtrace+0x0/0x1b8 [ 2.323936] show_stack+0x20/0x70 [ 2.327263] dump_stack+0xd8/0x134 [ 2.330677] sysfs_warn_dup+0x6c/0x88 [ 2.334351] sysfs_create_dir_ns+0xe8/0x100 [ 2.338547] kobject_add_internal+0x9c/0x290 [ 2.342833] kobject_add+0xa0/0x108 [ 2.346331] device_add+0xfc/0x798 [ 2.349746] device_link_add+0x454/0x5e0 [ 2.353682] fw_devlink_create_devlink+0xb8/0xc8 [ 2.358316] __fw_devlink_link_to_suppliers+0x84/0x180 [ 2.363474] __fw_devlink_link_to_suppliers+0x134/0x180 [ 2.368718] device_add+0x778/0x798 [ 2.372217] device_register+0x28/0x38 [ 2.375979] __mdiobus_register+0x94/0x340 [ 2.380089] of_mdiobus_register+0xb4/0x380 [ 2.384285] enetc_pf_probe+0x73c/0xb10 [ 2.388132] local_pci_probe+0x48/0xb8 [ 2.391896] pci_device_probe+0x120/0x1c0 [ 2.395920] really_probe+0xec/0x3c0 [ 2.399505] driver_probe_device+0x60/0xc0 [ 2.403614] device_driver_attach+0x7c/0x88 [ 2.407810] __driver_attach+0x60/0xe8 [ 2.411570] bus_for_each_dev+0x7c/0xd0 [ 2.415419] driver_attach+0x2c/0x38 [ 2.419004] bus_add_driver+0x194/0x1f8 [ 2.422851] driver_register+0x6c/0x128 [ 2.426698] __pci_register_driver+0x4c/0x58 [ 2.430983] enetc_pf_driver_init+0x2c/0x38 [ 2.435181] do_one_initcall+0x54/0x2d8 [ 2.439029] kernel_init_freeable+0x1fc/0x268 [ 2.443403] kernel_init+0x1c/0x120 [ 2.446904] ret_from_fork+0x10/0x30 [ 2.450502] kobject_add_internal failed for0000:00:00.1--0000:00:00.1 with
-EEXIST, don't try to register things with the same name in the same directory.Quoted 7 lines
Quoted 4 lines
Looks like it will generate that link twice? Let me know if I can help testing.
See also: https://lavalab.kontron.com/scheduler/job/3894#L831
I'll look into this this week. Is the DT for this board in upstream? If so, can you point me to the DT file(s)?
arch/arm64/boot/dts/freescale/fsl-ls1028a-kontron-kbox-a-230-ls.dtsQuoted 2 lines
Also, can you give me the output of this?
find/sys/devices-type d | grep "0000:00:00.1"# uname -a Linux buildroot 5.11.0-rc1-next-20210104 #298 SMP PREEMPT Tue Jan 5 21:55:23 CET 2021 aarch64 GNU/Linux # find /sys/devices -type d | grep "0000:00:00.1" /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/statistics /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-6 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-6/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-4 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-4/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-7 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-2 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-2/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-5 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-0 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-0/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-3 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-1 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-7 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-7/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-5 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-5/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-3 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-3/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-6 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-1 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/tx-1/byte_queue_limits /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-4 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-2 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/net/eno1/queues/rx-0 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/statistics /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/statistics /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/regulator
Quoted 8 lines
/sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/regulator/regulator.3 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/regulator/regulator.3/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/regulator/regulator.4 /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/regulator/regulator.4/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/mdio_bus/0000:00:00.1/0000:00:00.1:04/power /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/msi_irqs /sys/devices/platform/soc/1f0000000.pcie/pci0000:00/0000:00:00.1/link /sys/devices/virtual/devlink/5000000.iommu--0000:00:00.1
Sent a fix. Any further discussion will most likely continue in that thread.
https://lore.kernel.org/lkml/[email protected]/T/#u
-Saravana
PATCH v2 17/17 driver core: Delete pointless parameter in fwnode_operations.add_links
In reply to Saravana KannanThe struct device input to add_links() is not used for anything. So delete it.
--- drivers/base/core.c | 2 +- drivers/firmware/efi/efi-init.c | 3 +-- drivers/of/property.c | 3 +-- include/linux/fwnode.h | 3 +-- 4 files changed, 4 insertions(+), 7 deletions(-)
drivers/base/core.c +1 -1
@@ -1472,7 +1472,7 @@ static void fw_devlink_parse_fwnode(struct fwnode_handle *fwnode)if (fwnode->flags &FWNODE_FLAG_LINKS_ADDED )return ; -fwnode_call_int_op (fwnode, add_links,NULL ); +fwnode_call_int_op (fwnode, add_links); fwnode->flags |=FWNODE_FLAG_LINKS_ADDED ; }
drivers/firmware/efi/efi-init.c +1 -2
@@ -316,8 +316,7 @@ static struct device_node *find_pci_overlap_node(void)* resource reservation conflict on the memory window that the efifb * framebuffer steals from the PCIe host bridge. */ -static int efifb_add_links (struct fwnode_handle *fwnode, -struct device *dev) +static int efifb_add_links (struct fwnode_handle *fwnode) {struct device_node *sup_np;
drivers/of/property.c +1 -2
@@ -1343,8 +1343,7 @@ static int of_link_property(struct device_node *con_np, const char *prop_name)return ret; } -static int of_fwnode_add_links (struct fwnode_handle *fwnode, -struct device *dev) +static int of_fwnode_add_links (struct fwnode_handle *fwnode) {struct property *p;struct device_node *con_np =to_of_node (fwnode);
include/linux/fwnode.h +1 -2
@@ -127,8 +127,7 @@ struct fwnode_operations { (*graph_get_port_parent)(struct fwnode_handle *fwnode);int (*graph_parse_endpoint)(const struct fwnode_handle *fwnode,struct fwnode_endpoint *endpoint); -int (*add_links)(struct fwnode_handle *fwnode, -struct device *dev); +int (*add_links)(struct fwnode_handle *fwnode); };#define fwnode_has_op (fwnode, op) \
Signature · 1 line
2.29.2.454.gaff20da3a2-goog
Re: [PATCH v2 17/17] driver core: Delete pointless parameter in fwnode_operations.add_links
Quoted 11 lines · Saravana Kannan
The struct device input to
add_links()is not used for anything. So delete it.Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/core.c | 2 +- drivers/firmware/efi/efi-init.c | 3 +-- drivers/of/property.c | 3 +-- include/linux/fwnode.h | 3 +-- 4 files changed, 4 insertions(+), 7 deletions(-)
Hi,
Quoted 30 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch series refactors
fw_devlinkto be more efficient. The key difference now is the addition of support for fwnode links -- just a few simple APIs. This also allows most of the code to be moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times (complexity was close to O(N^3) where N in the number of properties) during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.
Quoted 7 lines
- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.Laurent and Grygorii tested the v1 series and they saw boot time improvment of about 12 seconds and 3 seconds, respectively.
Tested v2 on OMAP4 SDP. With my particular config, boot time to starting init went from 18.5 seconds to 12.5 seconds.
Tomi
Signature · 2 lines
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
Quoted 39 lines · Tomi Valkeinen' via kernel-team
Hi,
Quoted 35 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch series refactors
fw_devlinkto be more efficient. The key difference now is the addition of support for fwnode links -- just a few simple APIs. This also allows most of the code to be moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times (complexity was close to O(N^3) where N in the number of properties) during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.
Quoted 5 lines
Quoted 2 lines
Laurent and Grygorii tested the v1 series and they saw boot time improvment of about 12 seconds and 3 seconds, respectively.
Tested v2 on OMAP4 SDP. With my particular config, boot time to starting init went from 18.5 seconds to 12.5 seconds.
Thanks for testing Tomi!
-Saravana
Quoted 39 lines · Tomi Valkeinen' via kernel-team
Hi,
Quoted 35 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch series refactors
fw_devlinkto be more efficient. The key difference now is the addition of support for fwnode links -- just a few simple APIs. This also allows most of the code to be moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times (complexity was close to O(N^3) where N in the number of properties) during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.
Quoted 7 lines
Quoted 2 lines
Laurent and Grygorii tested the v1 series and they saw boot time improvment of about 12 seconds and 3 seconds, respectively.
Tested v2 on OMAP4 SDP. With my particular config, boot time to starting init went from 18.5 seconds to 12.5 seconds.
Tomi
Rafael,
Friendly reminder for a review.
-Saravana
Greg Kroah-Hartman
maintainerQuoted 30 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch series refactors
fw_devlinkto be more efficient. The key difference now is the addition of support for fwnode links -- just a few simple APIs. This also allows most of the code to be moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times (complexity was close to O(N^3) where N in the number of properties) during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.
Quoted 7 lines
- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.Laurent and Grygorii tested the v1 series and they saw boot time improvment of about 12 seconds and 3 seconds, respectively.
Now queued up to my tree. Note, I had to hand-apply patches 13 and 16 due to some reason (for 13, I have no idea, for 16 it was due to a previous patch applied to my tree that I cc:ed you on.)
Verifying I got it all correct would be great :)
thanks,
greg k-h
Quoted 37 lines · Greg Kroah-Hartman
Quoted 35 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch series refactors
fw_devlinkto be more efficient. The key difference now is the addition of support for fwnode links -- just a few simple APIs. This also allows most of the code to be moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times (complexity was close to O(N^3) where N in the number of properties) during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.
Quoted 8 lines
Quoted 2 lines
Laurent and Grygorii tested the v1 series and they saw boot time improvment of about 12 seconds and 3 seconds, respectively.
Now queued up to my tree. Note, I had to hand-apply patches 13 and 16 due to some reason (for 13, I have no idea, for 16 it was due to a previous patch applied to my tree that I cc:ed you on.)
Verifying I got it all correct would be great :)
A quick diff of drivers/base/core.c between driver-core-testing and my local tree doesn't show any major diff (only some unrelated comment fixes). So, it looks fine.
The patch 13 conflict is probably due to having to rebase the v2 series on top of this:
https://lore.kernel.org/lkml/[email protected]/
And looks like Patch 16 was handled fine.
Thanks for applying the series.
-Saravana
Greg Kroah-Hartman
maintainerQuoted 52 lines · Saravana Kannan
Quoted 37 lines · Greg Kroah-Hartman
Quoted 35 lines · Saravana Kannan
The current implementation of
fw_devlinkis very inefficient because it tries to get away without creating fwnode links in the name of saving memory usage. Past attempts to optimize runtime at the cost of memory usage were blocked with request for data showing that the optimization made significant improvement for real world scenarios.We have those scenarios now. There have been several reports of boot time increase in the order of seconds in this thread [1]. Several OEMs and SoC manufacturers have also privately reported significant (350-400ms) increase in boot time due to all the parsing done by
fw_devlink.So this patch series refactors
fw_devlinkto be more efficient. The key difference now is the addition of support for fwnode links -- just a few simple APIs. This also allows most of the code to be moved out of firmware specific (DT mostly) code into driver core.This brings the following benefits:
- Instead of parsing the device tree multiple times (complexity was close to O(N^3) where N in the number of properties) during bootup,fw_devlinkparses each fwnode node/property only once and creates fwnode links. The rest of thefw_devlinkcode then just looks at these fwnode links to do rest of the work.- Makes it much easier to debug probe issue due to
fw_devlinkin the future. fw_devlink=on blocks the probing of devices if they depend on a device that hasn't been added yet. With this refactor, it'll be very easy to tell what that device is because we now have a reference to the fwnode of the device.- Much easier to add
fw_devlinksupport to ACPI and other firmware types. A refactor to move the common bits from DT specific code to driver core was in my TODO list as a prerequisite to adding ACPI support tofw_devlink. This series gets that done.Quoted 8 lines
Quoted 2 lines
Laurent and Grygorii tested the v1 series and they saw boot time improvment of about 12 seconds and 3 seconds, respectively.
Now queued up to my tree. Note, I had to hand-apply patches 13 and 16 due to some reason (for 13, I have no idea, for 16 it was due to a previous patch applied to my tree that I cc:ed you on.)
Verifying I got it all correct would be great :)
A quick diff of
drivers/base/core.cbetween driver-core-testing and my local tree doesn't show any major diff (only some unrelated comment fixes). So, it looks fine.
Quoted 5 lines
The patch 13 conflict is probably due to having to rebase the v2 series on top of this:
https://lore.kernel.org/lkml/[email protected]/And looks like Patch 16 was handled fine.
Great, thanks for verifying!
greg k-h