fujitsu-laptop: renames and cleanups
Subsystems (2)
cover fujitsu-laptop: renames and cleanups
This series of patches was originally submitted by Alan Jenkins in September 2009. For various reasons they were never acted upon before. Sadly, their original state makes them unreviewable due to multiple changes happening within one patch and unreliable commit messages.
In order for Alan's efforts not to go to waste, I have rebased his patches on top of dvhart/for-next, further split them into logically separate changes and rewrote commit messages from scratch, based on the assumed intent of the original author.
Here is how the original patches map to the rebased and split patches:
1/4 -> 1-6/10
2/4 -> 7-8/10
3/4 -> 9/10
4/4 -> 10/10Some of these patches raise checkpatch warnings. This is intentional, in order to make renames clean and easy to review. All of these issues will be fixed by upcoming patch series.
Not all ideas suggested by Alan are present in the rebased series. A brief discussion of each rejected suggestion follows (most important issues first).
- Restructure fujitsu_init(). Quite frankly, I am pretty sure Alan did not test his series on Fujitsu hardware with a logo lamp and/or keyboard lamps. Neither have I, but with his original patches applied, what happens on such a model is:
1. fujitsu_init() calls acpi_bus_register_driver().
2. acpi_fujitsu_laptop_add() is called.
3. fujitsu_laptop is kzalloc()'ed.
4. fujitsu_laptop->pf_device->dev is accessed.
This results in a NULL dereference, because the platform device is only allocated and registered later in fujitsu_init().
On the other hand, registering the platform device before the ACPI driver is also incorrect due to reasons I already pointed out in another thread (in short: we cannot _assume_ FUJ02E3 is present). This can only be fixed properly by registering the platform device inside acpi_fujitsu_laptop_add(), but I am still waiting for comments from Darren and Andy in the other thread before moving forward down this path.
- Bail out when FUJ02B1 is not present. It could have been deemed correct back in the day, but we now know that Fujitsu started shipping devices without that ACPI device present, though with FUJ02E3 still in place. These two ACPI devices are independent and thus should not rely on each other's presence.
- Move keycode[1-5] fields to struct fujitsu_laptop. Doing this causes ordering issues inside fujitsu_init(), while a patch series I have queued that makes fujitsu-laptop use a sparse keymap removes these fields altogether.
- Allocate and free fujitsu_bl and fujitsu_laptop inside ACPI callbacks. While elegant and correct, this also causes ordering issues inside fujitsu_init() and can only be done once platform device registration is properly fixed.
- Sync backlight power status in acpi_fujitsu_bl_add(). The long-term objective for fujitsu-laptop should be to achieve a clean split between the backlight-related part and the laptop-related part. This change keeps both parts intertwined. My fujitsu_init() cleanup series contains a similar fix, but I have since found a different solution to this problem which I will post once Alan's rebased series gets applied.
- Remove dmi_check_cb_common(). The sparse keymap series I have queued gets rid of this function without introducing an additional field inside struct fujitsu_laptop.
Moreover, some other minor changes present in original patch 1/4 were left out. A brief discussion of each such case follows.
-#define ACPI_FUJITSU_BL_NOTIFY_CODE1 0x80
+#define ACPI_FUJITSU_NOTIFY_CODE1 0x80
Notify code 0x80 is used by both parts of the driver (the brightness-related one and the laptop-related one) and thus it should not be annotated using the "_BL" infix specific to brightness-related code.
-#if defined(CONFIG_LEDS_CLASS) || defined(CONFIG_LEDS_CLASS_MODULE)
...
-#endif
This does not really bring any benefit while breaking consistency with other parts of the driver.
- dmi_check_system(fujitsu_laptop_dmi_table);
+ dmi_check_system(fujitsu_dmi_table);
The original patches moved this dmi_check_system() call to acpi_fujitsu_laptop_add(), which justifies renaming fujitsu_dmi_table to fujitsu_laptop_dmi_table. However, for reasons discussed above, the rebased patches leave the dmi_check_system() call inside fujitsu_init(), thus making the rename dubious.
- DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU SIEMENS"),
+ DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU_LAPTOP SIEMENS"),
There are multiple changes like this in original patch 1/4. They are obviously wrong and were probably introduced by an unreviewed automatic replacement.
@@ -495,7 +495,6 @@ static ssize_t
show_max_brightness(struct device *dev,
struct device_attribute *attr, char *buf)
{
-
int ret;
There are four instances of such a removal in original patch 1/4. They are obviously correct, though they all happen inside functions related to platform device attributes which I hope will soon get removed altogether. Thus I refrained from applying these to reduce churn (at least a bit).
Finally, some of the changes suggested by Alan were already applied along the way:
- kmalloc() + memset() occurences were changed to kzalloc() by commit
6c75dd0f965b ("drivers/platform/x86: Use kzalloc"). - Unused debug macros were removed by commit 00816e1b3839 ("fujitsu-laptop: Remove unused macros").
drivers/platform/x86/fujitsu-laptop.c | 476 +++++++++++++++++----------------- 1 file changed, 232 insertions(+), 244 deletions(-)
Signature · 1 line
2.11.1
PATCH 1/10 platform/x86: fujitsu-laptop: clearly denote backlight-related symbols
From: Alan Jenkins <[email protected]>
Unify naming for all backlight-related functions, structures, variables and constants by using a consistent "_bl"/"_BL" suffix/infix. Adjust indentation to make checkpatch happy.
--- drivers/platform/x86/fujitsu-laptop.c | 214 +++++++++++++++++----------------- 1 file changed, 107 insertions(+), 107 deletions(-)
drivers/platform/x86/fujitsu-laptop.c +107 -107
@@ -78,10 +78,10 @@#define FUJITSU_LCD_N_LEVELS 8 -#define ACPI_FUJITSU_CLASS "fujitsu" -#define ACPI_FUJITSU_HID "FUJ02B1" -#define ACPI_FUJITSU_DRIVER_NAME "Fujitsu laptop FUJ02B1 ACPI brightness driver" -#define ACPI_FUJITSU_DEVICE_NAME "Fujitsu FUJ02B1" +#define ACPI_FUJITSU_CLASS "fujitsu" +#define ACPI_FUJITSU_BL_HID "FUJ02B1" +#define ACPI_FUJITSU_BL_DRIVER_NAME "Fujitsu laptop FUJ02B1 ACPI brightness driver" +#define ACPI_FUJITSU_BL_DEVICE_NAME "Fujitsu FUJ02B1"#define ACPI_FUJITSU_HOTKEY_HID "FUJ02E3"#define ACPI_FUJITSU_HOTKEY_DRIVER_NAME "Fujitsu laptop FUJ02E3 ACPI hotkeys driver"#define ACPI_FUJITSU_HOTKEY_DEVICE_NAME "Fujitsu FUJ02E3"
@@ -136,7 +136,7 @@#endif /* Device controlling the backlight and associated keys */ -struct fujitsu_t { +struct fujitsu_bl {acpi_handle acpi_handle;struct acpi_device *dev;struct input_dev *input;
@@ -150,7 +150,7 @@ struct fujitsu_t {unsigned int brightness_level; }; -static struct fujitsu_t *fujitsu; +static struct fujitsu_bl *fujitsu_bl;static int use_alt_lcd_levels =-1 ;static int disable_brightness_adjust =-1 ;
@@ -222,7 +222,7 @@ static struct led_classdev eco_led = {static u32 dbg_level =0x03 ;#endif -static void acpi_fujitsu_notify (struct acpi_device *device,u32 event); +static void acpi_fujitsu_bl_notify (struct acpi_device *device,u32 event);/* Fujitsu ACPI interface function */
@@ -373,10 +373,10 @@ static int set_lcd_level(int level)vdbg_printk (FUJLAPTOP_DBG_TRACE ,"set lcd level via SBLL [%d]\n" , level); -if (level <0 || level >= fujitsu->max_brightness) +if (level <0 || level >= fujitsu_bl->max_brightness)return -EINVAL ; - status =acpi_get_handle (fujitsu->acpi_handle,"SBLL" , &handle); + status =acpi_get_handle (fujitsu_bl->acpi_handle,"SBLL" , &handle);if (ACPI_FAILURE (status)) {vdbg_printk (FUJLAPTOP_DBG_ERROR ,"SBLL not present\n" );return -ENODEV ;
@@ -398,10 +398,10 @@ static int set_lcd_level_alt(int level)vdbg_printk (FUJLAPTOP_DBG_TRACE ,"set lcd level via SBL2 [%d]\n" , level); -if (level <0 || level >= fujitsu->max_brightness) +if (level <0 || level >= fujitsu_bl->max_brightness)return -EINVAL ; - status =acpi_get_handle (fujitsu->acpi_handle,"SBL2" , &handle); + status =acpi_get_handle (fujitsu_bl->acpi_handle,"SBL2" , &handle);if (ACPI_FAILURE (status)) {vdbg_printk (FUJLAPTOP_DBG_ERROR ,"SBL2 not present\n" );return -ENODEV ;
@@ -421,19 +421,19 @@ static int get_lcd_level(void)vdbg_printk (FUJLAPTOP_DBG_TRACE ,"get lcd level via GBLL\n" ); - status = -acpi_evaluate_integer (fujitsu->acpi_handle,"GBLL" ,NULL , &state); + status =acpi_evaluate_integer (fujitsu_bl->acpi_handle,"GBLL" ,NULL , + &state);if (ACPI_FAILURE (status))return 0 ; - fujitsu->brightness_level = state &0x0fffffff ; + fujitsu_bl->brightness_level = state &0x0fffffff ;if (state &0x80000000 ) - fujitsu->brightness_changed =1 ; + fujitsu_bl->brightness_changed =1 ;else - fujitsu->brightness_changed =0 ; + fujitsu_bl->brightness_changed =0 ; -return fujitsu->brightness_level; +return fujitsu_bl->brightness_level; }static int get_max_brightness (void )
@@ -443,14 +443,14 @@ static int get_max_brightness(void)vdbg_printk (FUJLAPTOP_DBG_TRACE ,"get max lcd level via RBLL\n" ); - status = -acpi_evaluate_integer (fujitsu->acpi_handle,"RBLL" ,NULL , &state); + status =acpi_evaluate_integer (fujitsu_bl->acpi_handle,"RBLL" ,NULL , + &state);if (ACPI_FAILURE (status))return -1 ; - fujitsu->max_brightness = state; + fujitsu_bl->max_brightness = state; -return fujitsu->max_brightness; +return fujitsu_bl->max_brightness; }/* Backlight device stuff */
@@ -483,7 +483,7 @@ static int bl_update_status(struct backlight_device *b)return ret; } -static const struct backlight_ops fujitsubl_ops = { +static const struct backlight_ops fujitsu_bl_ops = { .get_brightness = bl_get_brightness, .update_status = bl_update_status, };
@@ -511,7 +511,7 @@ show_brightness_changed(struct device *dev,int ret; - ret = fujitsu->brightness_changed; + ret = fujitsu_bl->brightness_changed;if (ret <0 )return ret;
@@ -539,7 +539,7 @@ static ssize_t store_lcd_level(struct device *dev,int level, ret;if (sscanf (buf,"%i" , &level) !=1 - || (level <0 || level >= fujitsu->max_brightness)) + || (level <0 || level >= fujitsu_bl->max_brightness))return -EINVAL ;if (use_alt_lcd_levels)
@@ -644,25 +644,25 @@ static void __init dmi_check_cb_common(const struct dmi_system_id *id)static int __init dmi_check_cb_s6410 (const struct dmi_system_id *id) {dmi_check_cb_common (id); - fujitsu->keycode1 =KEY_SCREENLOCK ;/* "Lock" */ - fujitsu->keycode2 =KEY_HELP ;/* "Mobility Center" */ + fujitsu_bl->keycode1 =KEY_SCREENLOCK ;/* "Lock" */ + fujitsu_bl->keycode2 =KEY_HELP ;/* "Mobility Center" */ return 1 ; }static int __init dmi_check_cb_s6420 (const struct dmi_system_id *id) {dmi_check_cb_common (id); - fujitsu->keycode1 =KEY_SCREENLOCK ;/* "Lock" */ - fujitsu->keycode2 =KEY_HELP ;/* "Mobility Center" */ + fujitsu_bl->keycode1 =KEY_SCREENLOCK ;/* "Lock" */ + fujitsu_bl->keycode2 =KEY_HELP ;/* "Mobility Center" */ return 1 ; }static int __init dmi_check_cb_p8010 (const struct dmi_system_id *id) {dmi_check_cb_common (id); - fujitsu->keycode1 =KEY_HELP ;/* "Support" */ - fujitsu->keycode3 =KEY_SWITCHVIDEOMODE ;/* "Presentation" */ - fujitsu->keycode4 =KEY_WWW ;/* "Internet" */ + fujitsu_bl->keycode1 =KEY_HELP ;/* "Support" */ + fujitsu_bl->keycode3 =KEY_SWITCHVIDEOMODE ;/* "Presentation" */ + fujitsu_bl->keycode4 =KEY_WWW ;/* "Internet" */ return 1 ; }
@@ -693,7 +693,7 @@ static const struct dmi_system_id fujitsu_dmi_table[] __initconst = {/* ACPI device for LCD brightness control */ -static int acpi_fujitsu_add (struct acpi_device *device) +static int acpi_fujitsu_bl_add (struct acpi_device *device) {int state =0 ;struct input_dev *input;
@@ -702,22 +702,22 @@ static int acpi_fujitsu_add(struct acpi_device *device)if (!device)return -EINVAL ; - fujitsu->acpi_handle = device->handle; -sprintf (acpi_device_name (device),"%s" ,ACPI_FUJITSU_DEVICE_NAME ); + fujitsu_bl->acpi_handle = device->handle; +sprintf (acpi_device_name (device),"%s" ,ACPI_FUJITSU_BL_DEVICE_NAME );sprintf (acpi_device_class (device),"%s" ,ACPI_FUJITSU_CLASS ); - device->driver_data = fujitsu; + device->driver_data = fujitsu_bl; - fujitsu->input = input =input_allocate_device (); + fujitsu_bl->input = input =input_allocate_device ();if (!input) { error = -ENOMEM ; goto err_stop; } -snprintf (fujitsu->phys,sizeof (fujitsu->phys), +snprintf (fujitsu_bl->phys,sizeof (fujitsu_bl->phys),"%s/video/input0" ,acpi_device_hid (device)); input->name =acpi_device_name (device); - input->phys = fujitsu->phys; + input->phys = fujitsu_bl->phys; input->id.bustype =BUS_HOST ; input->id.product =0x06 ; input->dev.parent = &device->dev;
@@ -730,7 +730,7 @@ static int acpi_fujitsu_add(struct acpi_device *device)if (error) goto err_free_input_dev; - error =acpi_bus_update_power (fujitsu->acpi_handle, &state); + error =acpi_bus_update_power (fujitsu_bl->acpi_handle, &state);if (error) {pr_err ("Error reading power state\n" ); goto err_unregister_input_dev;
@@ -740,7 +740,7 @@ static int acpi_fujitsu_add(struct acpi_device *device)acpi_device_name (device),acpi_device_bid (device), !device->power.state ? "on" : "off"); - fujitsu->dev = device; + fujitsu_bl->dev = device;if (acpi_has_method (device->handle,METHOD_NAME__INI )) {vdbg_printk (FUJLAPTOP_DBG_INFO ,"Invoking _INI\n" );
@@ -758,7 +758,7 @@ static int acpi_fujitsu_add(struct acpi_device *device) use_alt_lcd_levels, disable_brightness_adjust);if (get_max_brightness () <=0 ) - fujitsu->max_brightness =FUJITSU_LCD_N_LEVELS ; + fujitsu_bl->max_brightness =FUJITSU_LCD_N_LEVELS ;get_lcd_level ();return 0 ;
@@ -772,38 +772,38 @@ static int acpi_fujitsu_add(struct acpi_device *device)return error; } -static int acpi_fujitsu_remove (struct acpi_device *device) +static int acpi_fujitsu_bl_remove (struct acpi_device *device) { -struct fujitsu_t *fujitsu =acpi_driver_data (device); -struct input_dev *input = fujitsu->input; +struct fujitsu_bl *fujitsu_bl =acpi_driver_data (device); +struct input_dev *input = fujitsu_bl->input;input_unregister_device (input); - fujitsu->acpi_handle =NULL ; + fujitsu_bl->acpi_handle =NULL ;return 0 ; }/* Brightness notify */ -static void acpi_fujitsu_notify (struct acpi_device *device,u32 event) +static void acpi_fujitsu_bl_notify (struct acpi_device *device,u32 event) {struct input_dev *input;int keycode;int oldb, newb; - input = fujitsu->input; + input = fujitsu_bl->input;switch (event) {case ACPI_FUJITSU_NOTIFY_CODE1 : keycode =0 ; - oldb = fujitsu->brightness_level; + oldb = fujitsu_bl->brightness_level;get_lcd_level (); - newb = fujitsu->brightness_level; + newb = fujitsu_bl->brightness_level;vdbg_printk (FUJLAPTOP_DBG_TRACE ,"brightness button event [%i -> %i (%i)]\n" , - oldb, newb, fujitsu->brightness_changed); + oldb, newb, fujitsu_bl->brightness_changed);if (oldb < newb) {if (disable_brightness_adjust !=1 ) {
@@ -882,11 +882,11 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device) input->dev.parent = &device->dev;set_bit (EV_KEY , input->evbit); -set_bit (fujitsu->keycode1, input->keybit); -set_bit (fujitsu->keycode2, input->keybit); -set_bit (fujitsu->keycode3, input->keybit); -set_bit (fujitsu->keycode4, input->keybit); -set_bit (fujitsu->keycode5, input->keybit); +set_bit (fujitsu_bl->keycode1, input->keybit); +set_bit (fujitsu_bl->keycode2, input->keybit); +set_bit (fujitsu_bl->keycode3, input->keybit); +set_bit (fujitsu_bl->keycode4, input->keybit); +set_bit (fujitsu_bl->keycode5, input->keybit);set_bit (KEY_TOUCHPAD_TOGGLE , input->keybit);set_bit (KEY_UNKNOWN , input->keybit);
@@ -937,7 +937,7 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device)#if IS_ENABLED (CONFIG_LEDS_CLASS )if (call_fext_func (FUNC_LEDS ,0x0 ,0x0 ,0x0 ) &LOGOLAMP_POWERON ) { - result =led_classdev_register (&fujitsu->pf_device->dev, + result =led_classdev_register (&fujitsu_bl->pf_device->dev, &logolamp_led);if (result ==0 ) { fujitsu_hotkey->logolamp_registered =1 ;
@@ -949,7 +949,7 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device)if ((call_fext_func (FUNC_LEDS ,0x0 ,0x0 ,0x0 ) &KEYBOARD_LAMPS ) && (call_fext_func (FUNC_BUTTONS ,0x0 ,0x0 ,0x0 ) ==0x0 )) { - result =led_classdev_register (&fujitsu->pf_device->dev, + result =led_classdev_register (&fujitsu_bl->pf_device->dev, &kblamps_led);if (result ==0 ) { fujitsu_hotkey->kblamps_registered =1 ;
@@ -966,7 +966,7 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device)* that an RF LED is present. */ if (call_fext_func (FUNC_BUTTONS ,0x0 ,0x0 ,0x0 ) &BIT (24 )) { - result =led_classdev_register (&fujitsu->pf_device->dev, + result =led_classdev_register (&fujitsu_bl->pf_device->dev, &radio_led);if (result ==0 ) { fujitsu_hotkey->radio_led_registered =1 ;
@@ -983,7 +983,7 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device)*/ if ((call_fext_func (FUNC_LEDS ,0x0 ,0x0 ,0x0 ) &BIT (14 )) && (call_fext_func (FUNC_LEDS ,0x2 ,ECO_LED ,0x0 ) !=UNSUPPORTED_CMD )) { - result =led_classdev_register (&fujitsu->pf_device->dev, + result =led_classdev_register (&fujitsu_bl->pf_device->dev, &eco_led);if (result ==0 ) { fujitsu_hotkey->eco_led_registered =1 ;
@@ -1103,19 +1103,19 @@ static void acpi_fujitsu_hotkey_notify(struct acpi_device *device, u32 event) && (i++) < MAX_HOTKEY_RINGBUFFER_SIZE) {switch (irb &0x4ff ) {case KEY1_CODE : - keycode = fujitsu->keycode1; + keycode = fujitsu_bl->keycode1;break ;case KEY2_CODE : - keycode = fujitsu->keycode2; + keycode = fujitsu_bl->keycode2;break ;case KEY3_CODE : - keycode = fujitsu->keycode3; + keycode = fujitsu_bl->keycode3;break ;case KEY4_CODE : - keycode = fujitsu->keycode4; + keycode = fujitsu_bl->keycode4;break ;case KEY5_CODE : - keycode = fujitsu->keycode5; + keycode = fujitsu_bl->keycode5;break ;case 0 : keycode =0 ;
@@ -1150,19 +1150,19 @@ static void acpi_fujitsu_hotkey_notify(struct acpi_device *device, u32 event)/* Initialization */ -static const struct acpi_device_id fujitsu_device_ids[] = { - {ACPI_FUJITSU_HID ,0 }, +static const struct acpi_device_id fujitsu_bl_device_ids[] = { + {ACPI_FUJITSU_BL_HID ,0 }, {"" ,0 }, }; -static struct acpi_driver acpi_fujitsu_driver = { - .name =ACPI_FUJITSU_DRIVER_NAME , +static struct acpi_driver acpi_fujitsu_bl_driver = { + .name =ACPI_FUJITSU_BL_DRIVER_NAME , .class =ACPI_FUJITSU_CLASS , - .ids = fujitsu_device_ids, + .ids = fujitsu_bl_device_ids, .ops = { - .add = acpi_fujitsu_add, - .remove = acpi_fujitsu_remove, - .notify = acpi_fujitsu_notify, + .add = acpi_fujitsu_bl_add, + .remove = acpi_fujitsu_bl_remove, + .notify = acpi_fujitsu_bl_notify, }, };
@@ -1183,7 +1183,7 @@ static struct acpi_driver acpi_fujitsu_hotkey_driver = { };static const struct acpi_device_id fujitsu_ids[]__used = { - {ACPI_FUJITSU_HID ,0 }, + {ACPI_FUJITSU_BL_HID ,0 }, {ACPI_FUJITSU_HOTKEY_HID ,0 }, {"" ,0 } };
@@ -1196,17 +1196,17 @@ static int __init fujitsu_init(void)if (acpi_disabled)return -ENODEV ; - fujitsu =kzalloc (sizeof (struct fujitsu_t ),GFP_KERNEL ); -if (!fujitsu) + fujitsu_bl =kzalloc (sizeof (struct fujitsu_bl ),GFP_KERNEL ); +if (!fujitsu_bl)return -ENOMEM ; - fujitsu->keycode1 =KEY_PROG1 ; - fujitsu->keycode2 =KEY_PROG2 ; - fujitsu->keycode3 =KEY_PROG3 ; - fujitsu->keycode4 =KEY_PROG4 ; - fujitsu->keycode5 =KEY_RFKILL ; + fujitsu_bl->keycode1 =KEY_PROG1 ; + fujitsu_bl->keycode2 =KEY_PROG2 ; + fujitsu_bl->keycode3 =KEY_PROG3 ; + fujitsu_bl->keycode4 =KEY_PROG4 ; + fujitsu_bl->keycode5 =KEY_RFKILL ;dmi_check_system (fujitsu_dmi_table); - result =acpi_bus_register_driver (&acpi_fujitsu_driver); + result =acpi_bus_register_driver (&acpi_fujitsu_bl_driver);if (result <0 ) { ret = -ENODEV ; goto fail_acpi;
@@ -1214,18 +1214,18 @@ static int __init fujitsu_init(void)/* Register platform stuff */ - fujitsu->pf_device =platform_device_alloc ("fujitsu-laptop" ,-1 ); -if (!fujitsu->pf_device) { + fujitsu_bl->pf_device =platform_device_alloc ("fujitsu-laptop" ,-1 ); +if (!fujitsu_bl->pf_device) { ret = -ENOMEM ; goto fail_platform_driver; } - ret =platform_device_add (fujitsu->pf_device); + ret =platform_device_add (fujitsu_bl->pf_device);if (ret) goto fail_platform_device1; ret = -sysfs_create_group (&fujitsu->pf_device->dev.kobj, +sysfs_create_group (&fujitsu_bl->pf_device->dev.kobj, &fujitsupf_attribute_group);if (ret) goto fail_platform_device2;
@@ -1236,19 +1236,19 @@ static int __init fujitsu_init(void)struct backlight_properties props;memset (&props,0 ,sizeof (struct backlight_properties )); - max_brightness = fujitsu->max_brightness; + max_brightness = fujitsu_bl->max_brightness; props.type =BACKLIGHT_PLATFORM ; props.max_brightness = max_brightness -1 ; - fujitsu->bl_device =backlight_device_register ("fujitsu-laptop" , -NULL ,NULL , - &fujitsubl_ops, - &props); -if (IS_ERR (fujitsu->bl_device)) { - ret =PTR_ERR (fujitsu->bl_device); - fujitsu->bl_device =NULL ; + fujitsu_bl->bl_device =backlight_device_register ("fujitsu-laptop" , +NULL ,NULL , + &fujitsu_bl_ops, + &props); +if (IS_ERR (fujitsu_bl->bl_device)) { + ret =PTR_ERR (fujitsu_bl->bl_device); + fujitsu_bl->bl_device =NULL ; goto fail_sysfs_group; } - fujitsu->bl_device->props.brightness = fujitsu->brightness_level; + fujitsu_bl->bl_device->props.brightness = fujitsu_bl->brightness_level; } ret =platform_driver_register (&fujitsupf_driver);
@@ -1272,9 +1272,9 @@ static int __init fujitsu_init(void)/* Sync backlight power status (needs FUJ02E3 device, hence deferred) */ if (acpi_video_get_backlight_type () == acpi_backlight_vendor) {if (call_fext_func (FUNC_BACKLIGHT ,0x2 ,0x4 ,0x0 ) ==3 ) - fujitsu->bl_device->props.power =FB_BLANK_POWERDOWN ; + fujitsu_bl->bl_device->props.power =FB_BLANK_POWERDOWN ;else - fujitsu->bl_device->props.power =FB_BLANK_UNBLANK ; + fujitsu_bl->bl_device->props.power =FB_BLANK_UNBLANK ; }pr_info ("driver " FUJITSU_DRIVER_VERSION " successfully loaded\n" );
@@ -1286,18 +1286,18 @@ static int __init fujitsu_init(void) fail_hotkey:platform_driver_unregister (&fujitsupf_driver); fail_backlight: -backlight_device_unregister (fujitsu->bl_device); +backlight_device_unregister (fujitsu_bl->bl_device); fail_sysfs_group: -sysfs_remove_group (&fujitsu->pf_device->dev.kobj, +sysfs_remove_group (&fujitsu_bl->pf_device->dev.kobj, &fujitsupf_attribute_group); fail_platform_device2: -platform_device_del (fujitsu->pf_device); +platform_device_del (fujitsu_bl->pf_device); fail_platform_device1: -platform_device_put (fujitsu->pf_device); +platform_device_put (fujitsu_bl->pf_device); fail_platform_driver: -acpi_bus_unregister_driver (&acpi_fujitsu_driver); +acpi_bus_unregister_driver (&acpi_fujitsu_bl_driver); fail_acpi: -kfree (fujitsu); +kfree (fujitsu_bl);return ret; }
@@ -1310,16 +1310,16 @@ static void __exit fujitsu_cleanup(void)platform_driver_unregister (&fujitsupf_driver); -backlight_device_unregister (fujitsu->bl_device); +backlight_device_unregister (fujitsu_bl->bl_device); -sysfs_remove_group (&fujitsu->pf_device->dev.kobj, +sysfs_remove_group (&fujitsu_bl->pf_device->dev.kobj, &fujitsupf_attribute_group); -platform_device_unregister (fujitsu->pf_device); +platform_device_unregister (fujitsu_bl->pf_device); -acpi_bus_unregister_driver (&acpi_fujitsu_driver); +acpi_bus_unregister_driver (&acpi_fujitsu_bl_driver); -kfree (fujitsu); +kfree (fujitsu_bl);pr_info ("driver unloaded\n" ); }
Signature · 1 line
2.11.1
PATCH 2/10 platform/x86: fujitsu-laptop: replace "hotkey" with "laptop" in symbol names
In reply to Michał KępieńFrom: Alan Jenkins <[email protected]>
Functions, structures, variables and constants whose names currently contain the "hotkey" keyword are not only responsible for handling hotkeys, but also other laptop-related features (rfkill, lid, dock, LEDs). Fix their naming by using a consistent "_laptop"/"_LAPTOP" suffix/infix. Update comments so that they reflect this change.
--- drivers/platform/x86/fujitsu-laptop.c | 158 +++++++++++++++++----------------- 1 file changed, 79 insertions(+), 79 deletions(-)
drivers/platform/x86/fujitsu-laptop.c +79 -79
@@ -82,9 +82,9 @@#define ACPI_FUJITSU_BL_HID "FUJ02B1"#define ACPI_FUJITSU_BL_DRIVER_NAME "Fujitsu laptop FUJ02B1 ACPI brightness driver"#define ACPI_FUJITSU_BL_DEVICE_NAME "Fujitsu FUJ02B1" -#define ACPI_FUJITSU_HOTKEY_HID "FUJ02E3" -#define ACPI_FUJITSU_HOTKEY_DRIVER_NAME "Fujitsu laptop FUJ02E3 ACPI hotkeys driver" -#define ACPI_FUJITSU_HOTKEY_DEVICE_NAME "Fujitsu FUJ02E3" +#define ACPI_FUJITSU_LAPTOP_HID "FUJ02E3" +#define ACPI_FUJITSU_LAPTOP_DRIVER_NAME "Fujitsu laptop FUJ02E3 ACPI hotkeys driver" +#define ACPI_FUJITSU_LAPTOP_DEVICE_NAME "Fujitsu FUJ02E3"#define ACPI_FUJITSU_NOTIFY_CODE1 0x80
@@ -154,8 +154,8 @@ static struct fujitsu_bl *fujitsu_bl;static int use_alt_lcd_levels =-1 ;static int disable_brightness_adjust =-1 ; -/* Device used to access other hotkeys on the laptop */ -struct fujitsu_hotkey_t { +/* Device used to access hotkeys and other features on the laptop */ +struct fujitsu_laptop {acpi_handle acpi_handle;struct acpi_device *dev;struct input_dev *input;
@@ -171,9 +171,9 @@ struct fujitsu_hotkey_t {int eco_led_registered; }; -static struct fujitsu_hotkey_t *fujitsu_hotkey; +static struct fujitsu_laptop *fujitsu_laptop; -static void acpi_fujitsu_hotkey_notify (struct acpi_device *device,u32 event); +static void acpi_fujitsu_laptop_notify (struct acpi_device *device,u32 event);#if IS_ENABLED (CONFIG_LEDS_CLASS )static enum led_brightness logolamp_get (struct led_classdev *cdev);
@@ -239,7 +239,7 @@ static int call_fext_func(int cmd, int arg0, int arg1, int arg2)unsigned long long value;acpi_handle handle =NULL ; - status =acpi_get_handle (fujitsu_hotkey->acpi_handle,"FUNC" , &handle); + status =acpi_get_handle (fujitsu_laptop->acpi_handle,"FUNC" , &handle);if (ACPI_FAILURE (status)) {vdbg_printk (FUJLAPTOP_DBG_ERROR ,"FUNC interface is not present\n" );
@@ -567,9 +567,9 @@ static ssize_t show_lid_state(struct device *dev, struct device_attribute *attr, char *buf) { - if (!(fujitsu_hotkey->rfkill_supported & 0x100)) + if (!(fujitsu_laptop->rfkill_supported & 0x100)) return sprintf(buf, "unknown\n"); - if (fujitsu_hotkey->rfkill_state & 0x100) + if (fujitsu_laptop->rfkill_state & 0x100) return sprintf(buf, "open\n"); else return sprintf(buf, "closed\n");
@@ -579,9 +579,9 @@ static ssize_t show_dock_state(struct device *dev, struct device_attribute *attr, char *buf) { - if (!(fujitsu_hotkey->rfkill_supported & 0x200)) + if (!(fujitsu_laptop->rfkill_supported & 0x200)) return sprintf(buf, "unknown\n"); - if (fujitsu_hotkey->rfkill_state & 0x200) + if (fujitsu_laptop->rfkill_state & 0x200) return sprintf(buf, "docked\n"); else return sprintf(buf, "undocked\n");
@@ -591,9 +591,9 @@ static ssize_t show_radios_state(struct device *dev, struct device_attribute *attr, char *buf) { - if (!(fujitsu_hotkey->rfkill_supported & 0x20)) + if (!(fujitsu_laptop->rfkill_supported & 0x20)) return sprintf(buf, "unknown\n"); - if (fujitsu_hotkey->rfkill_state & 0x20) + if (fujitsu_laptop->rfkill_state & 0x20) return sprintf(buf, "on\n"); else return sprintf(buf, "killed\n");
@@ -840,7 +840,7 @@ static void acpi_fujitsu_bl_notify(struct acpi_device *device, u32 event)/* ACPI device for hotkey handling */ -static int acpi_fujitsu_hotkey_add (struct acpi_device *device) +static int acpi_fujitsu_laptop_add (struct acpi_device *device) {int result =0 ;int state =0 ;
@@ -851,32 +851,32 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device)if (!device)return -EINVAL ; - fujitsu_hotkey->acpi_handle = device->handle; + fujitsu_laptop->acpi_handle = device->handle;sprintf (acpi_device_name (device),"%s" , -ACPI_FUJITSU_HOTKEY_DEVICE_NAME ); +ACPI_FUJITSU_LAPTOP_DEVICE_NAME );sprintf (acpi_device_class (device),"%s" ,ACPI_FUJITSU_CLASS ); - device->driver_data = fujitsu_hotkey; + device->driver_data = fujitsu_laptop;/* kfifo */ -spin_lock_init (&fujitsu_hotkey->fifo_lock); - error =kfifo_alloc (&fujitsu_hotkey->fifo,RINGBUFFERSIZE *sizeof (int ), +spin_lock_init (&fujitsu_laptop->fifo_lock); + error =kfifo_alloc (&fujitsu_laptop->fifo,RINGBUFFERSIZE *sizeof (int ),GFP_KERNEL );if (error) {pr_err ("kfifo_alloc failed\n" ); goto err_stop; } - fujitsu_hotkey->input = input =input_allocate_device (); + fujitsu_laptop->input = input =input_allocate_device ();if (!input) { error = -ENOMEM ; goto err_free_fifo; } -snprintf (fujitsu_hotkey->phys,sizeof (fujitsu_hotkey->phys), +snprintf (fujitsu_laptop->phys,sizeof (fujitsu_laptop->phys),"%s/video/input0" ,acpi_device_hid (device)); input->name =acpi_device_name (device); - input->phys = fujitsu_hotkey->phys; + input->phys = fujitsu_laptop->phys; input->id.bustype =BUS_HOST ; input->id.product =0x06 ; input->dev.parent = &device->dev;
@@ -894,7 +894,7 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device)if (error) goto err_free_input_dev; - error =acpi_bus_update_power (fujitsu_hotkey->acpi_handle, &state); + error =acpi_bus_update_power (fujitsu_laptop->acpi_handle, &state);if (error) {pr_err ("Error reading power state\n" ); goto err_unregister_input_dev;
@@ -904,7 +904,7 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device)acpi_device_name (device),acpi_device_bid (device), !device->power.state ? "on" : "off"); - fujitsu_hotkey->dev = device; + fujitsu_laptop->dev = device;if (acpi_has_method (device->handle,METHOD_NAME__INI )) {vdbg_printk (FUJLAPTOP_DBG_INFO ,"Invoking _INI\n" );
@@ -920,16 +920,16 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device) ;/* No action, result is discarded */ vdbg_printk (FUJLAPTOP_DBG_INFO ,"Discarded %i ringbuffer entries\n" , i); - fujitsu_hotkey->rfkill_supported = + fujitsu_laptop->rfkill_supported =call_fext_func (FUNC_RFKILL ,0x0 ,0x0 ,0x0 );/* Make sure our bitmask of supported functions is cleared if the RFKILL function block is not implemented, like on the S7020. */ -if (fujitsu_hotkey->rfkill_supported ==UNSUPPORTED_CMD ) - fujitsu_hotkey->rfkill_supported =0 ; +if (fujitsu_laptop->rfkill_supported ==UNSUPPORTED_CMD ) + fujitsu_laptop->rfkill_supported =0 ; -if (fujitsu_hotkey->rfkill_supported) - fujitsu_hotkey->rfkill_state = +if (fujitsu_laptop->rfkill_supported) + fujitsu_laptop->rfkill_state =call_fext_func (FUNC_RFKILL ,0x4 ,0x0 ,0x0 );/* Suspect this is a keymap of the application panel, print it */
@@ -940,7 +940,7 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device) result =led_classdev_register (&fujitsu_bl->pf_device->dev, &logolamp_led);if (result ==0 ) { - fujitsu_hotkey->logolamp_registered =1 ; + fujitsu_laptop->logolamp_registered =1 ; }else {pr_err ("Could not register LED handler for logo lamp, error %i\n" , result);
@@ -952,7 +952,7 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device) result =led_classdev_register (&fujitsu_bl->pf_device->dev, &kblamps_led);if (result ==0 ) { - fujitsu_hotkey->kblamps_registered =1 ; + fujitsu_laptop->kblamps_registered =1 ; }else {pr_err ("Could not register LED handler for keyboard lamps, error %i\n" , result);
@@ -969,7 +969,7 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device) result =led_classdev_register (&fujitsu_bl->pf_device->dev, &radio_led);if (result ==0 ) { - fujitsu_hotkey->radio_led_registered =1 ; + fujitsu_laptop->radio_led_registered =1 ; }else {pr_err ("Could not register LED handler for radio LED, error %i\n" , result);
@@ -986,7 +986,7 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device) result =led_classdev_register (&fujitsu_bl->pf_device->dev, &eco_led);if (result ==0 ) { - fujitsu_hotkey->eco_led_registered =1 ; + fujitsu_laptop->eco_led_registered =1 ; }else {pr_err ("Could not register LED handler for eco LED, error %i\n" , result);
@@ -1002,47 +1002,47 @@ static int acpi_fujitsu_hotkey_add(struct acpi_device *device) err_free_input_dev:input_free_device (input); err_free_fifo: -kfifo_free (&fujitsu_hotkey->fifo); +kfifo_free (&fujitsu_laptop->fifo); err_stop:return error; } -static int acpi_fujitsu_hotkey_remove (struct acpi_device *device) +static int acpi_fujitsu_laptop_remove (struct acpi_device *device) { -struct fujitsu_hotkey_t *fujitsu_hotkey =acpi_driver_data (device); -struct input_dev *input = fujitsu_hotkey->input; +struct fujitsu_laptop *fujitsu_laptop =acpi_driver_data (device); +struct input_dev *input = fujitsu_laptop->input;#if IS_ENABLED (CONFIG_LEDS_CLASS ) -if (fujitsu_hotkey->logolamp_registered) +if (fujitsu_laptop->logolamp_registered)led_classdev_unregister (&logolamp_led); -if (fujitsu_hotkey->kblamps_registered) +if (fujitsu_laptop->kblamps_registered)led_classdev_unregister (&kblamps_led); -if (fujitsu_hotkey->radio_led_registered) +if (fujitsu_laptop->radio_led_registered)led_classdev_unregister (&radio_led); -if (fujitsu_hotkey->eco_led_registered) +if (fujitsu_laptop->eco_led_registered)led_classdev_unregister (&eco_led);#endif input_unregister_device (input); -kfifo_free (&fujitsu_hotkey->fifo); +kfifo_free (&fujitsu_laptop->fifo); - fujitsu_hotkey->acpi_handle =NULL ; + fujitsu_laptop->acpi_handle =NULL ;return 0 ; } -static void acpi_fujitsu_hotkey_press (int keycode) +static void acpi_fujitsu_laptop_press (int keycode) { -struct input_dev *input = fujitsu_hotkey->input; +struct input_dev *input = fujitsu_laptop->input;int status; - status =kfifo_in_locked (&fujitsu_hotkey->fifo, + status =kfifo_in_locked (&fujitsu_laptop->fifo, (unsigned char *)&keycode,sizeof (keycode), - &fujitsu_hotkey->fifo_lock); + &fujitsu_laptop->fifo_lock);if (status !=sizeof (keycode)) {vdbg_printk (FUJLAPTOP_DBG_WARN ,"Could not push keycode [0x%x]\n" , keycode);
@@ -1054,16 +1054,16 @@ static void acpi_fujitsu_hotkey_press(int keycode) "Push keycode into ringbuffer [%d]\n", keycode); } -static void acpi_fujitsu_hotkey_release (void ) +static void acpi_fujitsu_laptop_release (void ) { -struct input_dev *input = fujitsu_hotkey->input; +struct input_dev *input = fujitsu_laptop->input;int keycode, status;while (true) { - status =kfifo_out_locked (&fujitsu_hotkey->fifo, + status =kfifo_out_locked (&fujitsu_laptop->fifo, (unsigned char *)&keycode,sizeof (keycode), - &fujitsu_hotkey->fifo_lock); + &fujitsu_laptop->fifo_lock);if (status !=sizeof (keycode))return ;input_report_key (input, keycode,0 );
@@ -1073,14 +1073,14 @@ static void acpi_fujitsu_hotkey_release(void) } } -static void acpi_fujitsu_hotkey_notify (struct acpi_device *device,u32 event) +static void acpi_fujitsu_laptop_notify (struct acpi_device *device,u32 event) {struct input_dev *input;int keycode;unsigned int irb =1 ;int i; - input = fujitsu_hotkey->input; + input = fujitsu_laptop->input;if (event !=ACPI_FUJITSU_NOTIFY_CODE1 ) { keycode =KEY_UNKNOWN ;
@@ -1093,8 +1093,8 @@ static void acpi_fujitsu_hotkey_notify(struct acpi_device *device, u32 event)return ; } -if (fujitsu_hotkey->rfkill_supported) - fujitsu_hotkey->rfkill_state = +if (fujitsu_laptop->rfkill_supported) + fujitsu_laptop->rfkill_state =call_fext_func (FUNC_RFKILL ,0x4 ,0x0 ,0x0 ); i =0 ;
@@ -1128,16 +1128,16 @@ static void acpi_fujitsu_hotkey_notify(struct acpi_device *device, u32 event) }if (keycode >0 ) -acpi_fujitsu_hotkey_press (keycode); +acpi_fujitsu_laptop_press (keycode);else if (keycode ==0 ) -acpi_fujitsu_hotkey_release (); +acpi_fujitsu_laptop_release (); }/* On some models (first seen on the Skylake-based Lifebook * E736/E746/E756), the touchpad toggle hotkey (Fn+F4) is * handled in software; its state is queried using FUNC_RFKILL */ -if ((fujitsu_hotkey->rfkill_supported &BIT (26 )) && +if ((fujitsu_laptop->rfkill_supported &BIT (26 )) && (call_fext_func (FUNC_RFKILL ,0x1 ,0x0 ,0x0 ) &BIT (26 ))) { keycode =KEY_TOUCHPAD_TOGGLE ;input_report_key (input, keycode,1 );
@@ -1166,25 +1166,25 @@ static struct acpi_driver acpi_fujitsu_bl_driver = { }, }; -static const struct acpi_device_id fujitsu_hotkey_device_ids[] = { - {ACPI_FUJITSU_HOTKEY_HID ,0 }, +static const struct acpi_device_id fujitsu_laptop_device_ids[] = { + {ACPI_FUJITSU_LAPTOP_HID ,0 }, {"" ,0 }, }; -static struct acpi_driver acpi_fujitsu_hotkey_driver = { - .name =ACPI_FUJITSU_HOTKEY_DRIVER_NAME , +static struct acpi_driver acpi_fujitsu_laptop_driver = { + .name =ACPI_FUJITSU_LAPTOP_DRIVER_NAME , .class =ACPI_FUJITSU_CLASS , - .ids = fujitsu_hotkey_device_ids, + .ids = fujitsu_laptop_device_ids, .ops = { - .add = acpi_fujitsu_hotkey_add, - .remove = acpi_fujitsu_hotkey_remove, - .notify = acpi_fujitsu_hotkey_notify, + .add = acpi_fujitsu_laptop_add, + .remove = acpi_fujitsu_laptop_remove, + .notify = acpi_fujitsu_laptop_notify, }, };static const struct acpi_device_id fujitsu_ids[]__used = { {ACPI_FUJITSU_BL_HID ,0 }, - {ACPI_FUJITSU_HOTKEY_HID ,0 }, + {ACPI_FUJITSU_LAPTOP_HID ,0 }, {"" ,0 } };MODULE_DEVICE_TABLE (acpi, fujitsu_ids);
@@ -1255,18 +1255,18 @@ static int __init fujitsu_init(void)if (ret) goto fail_backlight; -/* Register hotkey driver */ +/* Register laptop driver */ - fujitsu_hotkey =kzalloc (sizeof (struct fujitsu_hotkey_t ),GFP_KERNEL ); -if (!fujitsu_hotkey) { + fujitsu_laptop =kzalloc (sizeof (struct fujitsu_laptop ),GFP_KERNEL ); +if (!fujitsu_laptop) { ret = -ENOMEM ; - goto fail_hotkey; + goto fail_laptop; } - result =acpi_bus_register_driver (&acpi_fujitsu_hotkey_driver); + result =acpi_bus_register_driver (&acpi_fujitsu_laptop_driver);if (result <0 ) { ret = -ENODEV ; - goto fail_hotkey1; + goto fail_laptop1; }/* Sync backlight power status (needs FUJ02E3 device, hence deferred) */
@@ -1281,9 +1281,9 @@ static int __init fujitsu_init(void)return 0 ; -fail_hotkey1: -kfree (fujitsu_hotkey); -fail_hotkey: +fail_laptop1: +kfree (fujitsu_laptop); +fail_laptop:platform_driver_unregister (&fujitsupf_driver); fail_backlight:backlight_device_unregister (fujitsu_bl->bl_device);
@@ -1304,9 +1304,9 @@ static int __init fujitsu_init(void) static void __exit fujitsu_cleanup(void) { -acpi_bus_unregister_driver (&acpi_fujitsu_hotkey_driver); +acpi_bus_unregister_driver (&acpi_fujitsu_laptop_driver); -kfree (fujitsu_hotkey); +kfree (fujitsu_laptop);platform_driver_unregister (&fujitsupf_driver);
Signature · 1 line
2.11.1
PATCH 3/10 platform/x86: fujitsu-laptop: make platform-related variables match naming convention
In reply to Michał KępieńFrom: Alan Jenkins <[email protected]>
Replace "fujitsupf" with "fujitsu_pf" in all platform-related variable names to match the module-wide naming convention.
--- drivers/platform/x86/fujitsu-laptop.c | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-)
drivers/platform/x86/fujitsu-laptop.c +10 -10
@@ -607,7 +607,7 @@ static DEVICE_ATTR(lid, 0444, show_lid_state, ignore_store); static DEVICE_ATTR(dock, 0444, show_dock_state, ignore_store); static DEVICE_ATTR(radios, 0444, show_radios_state, ignore_store); -static struct attribute *fujitsupf_attributes[] = { +static struct attribute *fujitsu_pf_attributes[] = { &dev_attr_brightness_changed.attr, &dev_attr_max_brightness.attr, &dev_attr_lcd_level.attr,
@@ -617,11 +617,11 @@ static struct attribute *fujitsupf_attributes[] = {NULL }; -static struct attribute_group fujitsupf_attribute_group = { - .attrs = fujitsupf_attributes +static struct attribute_group fujitsu_pf_attribute_group = { + .attrs = fujitsu_pf_attributes }; -static struct platform_driver fujitsupf_driver = { +static struct platform_driver fujitsu_pf_driver = { .driver = { .name ="fujitsu-laptop" , }
@@ -1226,7 +1226,7 @@ static int __init fujitsu_init(void) ret =sysfs_create_group (&fujitsu_bl->pf_device->dev.kobj, - &fujitsupf_attribute_group); + &fujitsu_pf_attribute_group);if (ret) goto fail_platform_device2;
@@ -1251,7 +1251,7 @@ static int __init fujitsu_init(void) fujitsu_bl->bl_device->props.brightness = fujitsu_bl->brightness_level; } - ret =platform_driver_register (&fujitsupf_driver); + ret =platform_driver_register (&fujitsu_pf_driver);if (ret) goto fail_backlight;
@@ -1284,12 +1284,12 @@ static int __init fujitsu_init(void) fail_laptop1:kfree (fujitsu_laptop); fail_laptop: -platform_driver_unregister (&fujitsupf_driver); +platform_driver_unregister (&fujitsu_pf_driver); fail_backlight:backlight_device_unregister (fujitsu_bl->bl_device); fail_sysfs_group:sysfs_remove_group (&fujitsu_bl->pf_device->dev.kobj, - &fujitsupf_attribute_group); + &fujitsu_pf_attribute_group); fail_platform_device2:platform_device_del (fujitsu_bl->pf_device); fail_platform_device1:
@@ -1308,12 +1308,12 @@ static void __exit fujitsu_cleanup(void)kfree (fujitsu_laptop); -platform_driver_unregister (&fujitsupf_driver); +platform_driver_unregister (&fujitsu_pf_driver);backlight_device_unregister (fujitsu_bl->bl_device);sysfs_remove_group (&fujitsu_bl->pf_device->dev.kobj, - &fujitsupf_attribute_group); + &fujitsu_pf_attribute_group);platform_device_unregister (fujitsu_bl->pf_device);
Signature · 1 line
2.11.1
PATCH 4/10 platform/x86: fujitsu-laptop: rename FUNC_RFKILL to FUNC_FLAGS
In reply to Michał KępieńFrom: Alan Jenkins <[email protected]>
FUNC subfunction 0x1000 is currently referred to as FUNC_RFKILL, which is misleading, because it handles more than just radio devices (also lid, dock, LEDs). Rename the FUNC_RFKILL constant to FUNC_FLAGS. Replace "rfkill" with "flags" in the names of its associated fields inside struct fujitsu_laptop.
--- drivers/platform/x86/fujitsu-laptop.c | 50 +++++++++++++++++------------------ 1 file changed, 25 insertions(+), 25 deletions(-)
drivers/platform/x86/fujitsu-laptop.c +25 -25
@@ -89,7 +89,7 @@#define ACPI_FUJITSU_NOTIFY_CODE1 0x80/* FUNC interface - command values */ -#define FUNC_RFKILL 0x1000 +#define FUNC_FLAGS 0x1000#define FUNC_LEDS 0x1001#define FUNC_BUTTONS 0x1002#define FUNC_BACKLIGHT 0x1004
@@ -163,8 +163,8 @@ struct fujitsu_laptop {struct platform_device *pf_device;struct kfifo fifo;spinlock_t fifo_lock; -int rfkill_supported; -int rfkill_state; +int flags_supported; +int flags_state;int logolamp_registered;int kblamps_registered;int radio_led_registered;
@@ -300,9 +300,9 @@ static int radio_led_set(struct led_classdev *cdev, enum led_brightness brightness) {if (brightness >=LED_FULL ) -return call_fext_func (FUNC_RFKILL ,0x5 ,RADIO_LED_ON ,RADIO_LED_ON ); +return call_fext_func (FUNC_FLAGS ,0x5 ,RADIO_LED_ON ,RADIO_LED_ON );else -return call_fext_func (FUNC_RFKILL ,0x5 ,RADIO_LED_ON ,0x0 ); +return call_fext_func (FUNC_FLAGS ,0x5 ,RADIO_LED_ON ,0x0 ); } static int eco_led_set(struct led_classdev *cdev,
@@ -346,7 +346,7 @@ static enum led_brightness radio_led_get(struct led_classdev *cdev) {enum led_brightness brightness =LED_OFF ; -if (call_fext_func (FUNC_RFKILL ,0x4 ,0x0 ,0x0 ) &RADIO_LED_ON ) +if (call_fext_func (FUNC_FLAGS ,0x4 ,0x0 ,0x0 ) &RADIO_LED_ON ) brightness =LED_FULL ;return brightness;
@@ -567,9 +567,9 @@ static ssize_t show_lid_state(struct device *dev, struct device_attribute *attr, char *buf) { - if (!(fujitsu_laptop->rfkill_supported & 0x100)) + if (!(fujitsu_laptop->flags_supported & 0x100)) return sprintf(buf, "unknown\n"); - if (fujitsu_laptop->rfkill_state & 0x100) + if (fujitsu_laptop->flags_state & 0x100) return sprintf(buf, "open\n"); else return sprintf(buf, "closed\n");
@@ -579,9 +579,9 @@ static ssize_t show_dock_state(struct device *dev, struct device_attribute *attr, char *buf) { - if (!(fujitsu_laptop->rfkill_supported & 0x200)) + if (!(fujitsu_laptop->flags_supported & 0x200)) return sprintf(buf, "unknown\n"); - if (fujitsu_laptop->rfkill_state & 0x200) + if (fujitsu_laptop->flags_state & 0x200) return sprintf(buf, "docked\n"); else return sprintf(buf, "undocked\n");
@@ -591,9 +591,9 @@ static ssize_t show_radios_state(struct device *dev, struct device_attribute *attr, char *buf) { - if (!(fujitsu_laptop->rfkill_supported & 0x20)) + if (!(fujitsu_laptop->flags_supported & 0x20)) return sprintf(buf, "unknown\n"); - if (fujitsu_laptop->rfkill_state & 0x20) + if (fujitsu_laptop->flags_state & 0x20) return sprintf(buf, "on\n"); else return sprintf(buf, "killed\n");
@@ -920,17 +920,17 @@ static int acpi_fujitsu_laptop_add(struct acpi_device *device) ;/* No action, result is discarded */ vdbg_printk (FUJLAPTOP_DBG_INFO ,"Discarded %i ringbuffer entries\n" , i); - fujitsu_laptop->rfkill_supported = -call_fext_func (FUNC_RFKILL ,0x0 ,0x0 ,0x0 ); + fujitsu_laptop->flags_supported = +call_fext_func (FUNC_FLAGS ,0x0 ,0x0 ,0x0 );/* Make sure our bitmask of supported functions is cleared if the RFKILL function block is not implemented, like on the S7020. */ -if (fujitsu_laptop->rfkill_supported ==UNSUPPORTED_CMD ) - fujitsu_laptop->rfkill_supported =0 ; +if (fujitsu_laptop->flags_supported ==UNSUPPORTED_CMD ) + fujitsu_laptop->flags_supported =0 ; -if (fujitsu_laptop->rfkill_supported) - fujitsu_laptop->rfkill_state = -call_fext_func (FUNC_RFKILL ,0x4 ,0x0 ,0x0 ); +if (fujitsu_laptop->flags_supported) + fujitsu_laptop->flags_state = +call_fext_func (FUNC_FLAGS ,0x4 ,0x0 ,0x0 );/* Suspect this is a keymap of the application panel, print it */ pr_info ("BTNI: [0x%x]\n" ,call_fext_func (FUNC_BUTTONS ,0x0 ,0x0 ,0x0 ));
@@ -1093,9 +1093,9 @@ static void acpi_fujitsu_laptop_notify(struct acpi_device *device, u32 event)return ; } -if (fujitsu_laptop->rfkill_supported) - fujitsu_laptop->rfkill_state = -call_fext_func (FUNC_RFKILL ,0x4 ,0x0 ,0x0 ); +if (fujitsu_laptop->flags_supported) + fujitsu_laptop->flags_state = +call_fext_func (FUNC_FLAGS ,0x4 ,0x0 ,0x0 ); i =0 ; while ((irb =
@@ -1135,10 +1135,10 @@ static void acpi_fujitsu_laptop_notify(struct acpi_device *device, u32 event)/* On some models (first seen on the Skylake-based Lifebook * E736/E746/E756), the touchpad toggle hotkey (Fn+F4) is -* handled in software; its state is queried using FUNC_RFKILL +* handled in software; its state is queried using FUNC_FLAGS */ -if ((fujitsu_laptop->rfkill_supported &BIT (26 )) && - (call_fext_func (FUNC_RFKILL ,0x1 ,0x0 ,0x0 ) &BIT (26 ))) { +if ((fujitsu_laptop->flags_supported &BIT (26 )) && + (call_fext_func (FUNC_FLAGS ,0x1 ,0x0 ,0x0 ) &BIT (26 ))) { keycode =KEY_TOUCHPAD_TOGGLE ;input_report_key (input, keycode,1 );input_sync (input);
Signature · 1 line
2.11.1
PATCH 5/10 platform/x86: fujitsu-laptop: replace numeric values with constants
In reply to Michał KępieńFrom: Alan Jenkins <[email protected]>
Replace three repeating numeric values with constants to improve code clarity.
--- drivers/platform/x86/fujitsu-laptop.c | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-)
drivers/platform/x86/fujitsu-laptop.c +11 -6
@@ -97,6 +97,11 @@/* FUNC interface - responses */ #define UNSUPPORTED_CMD 0x80000000 +/* FUNC interface - status flags */ +#define FLAG_RFKILL 0x020 +#define FLAG_LID 0x100 +#define FLAG_DOCK 0x200 +#if IS_ENABLED (CONFIG_LEDS_CLASS )/* FUNC interface - LED control */ #define FUNC_LED_OFF 0x1
@@ -567,9 +572,9 @@ static ssize_t show_lid_state(struct device *dev, struct device_attribute *attr, char *buf) { - if (!(fujitsu_laptop->flags_supported & 0x100)) + if (!(fujitsu_laptop->flags_supported & FLAG_LID)) return sprintf(buf, "unknown\n"); - if (fujitsu_laptop->flags_state & 0x100) + if (fujitsu_laptop->flags_state & FLAG_LID) return sprintf(buf, "open\n"); else return sprintf(buf, "closed\n");
@@ -579,9 +584,9 @@ static ssize_t show_dock_state(struct device *dev, struct device_attribute *attr, char *buf) { - if (!(fujitsu_laptop->flags_supported & 0x200)) + if (!(fujitsu_laptop->flags_supported & FLAG_DOCK)) return sprintf(buf, "unknown\n"); - if (fujitsu_laptop->flags_state & 0x200) + if (fujitsu_laptop->flags_state & FLAG_DOCK) return sprintf(buf, "docked\n"); else return sprintf(buf, "undocked\n");
@@ -591,9 +596,9 @@ static ssize_t show_radios_state(struct device *dev, struct device_attribute *attr, char *buf) { - if (!(fujitsu_laptop->flags_supported & 0x20)) + if (!(fujitsu_laptop->flags_supported & FLAG_RFKILL)) return sprintf(buf, "unknown\n"); - if (fujitsu_laptop->flags_state & 0x20) + if (fujitsu_laptop->flags_state & FLAG_RFKILL) return sprintf(buf, "on\n"); else return sprintf(buf, "killed\n");
Signature · 1 line
2.11.1
PATCH 6/10 platform/x86: fujitsu-laptop: remove redundant forward declarations
In reply to Michał KępieńFrom: Alan Jenkins <[email protected]>
Both acpi_fujitsu_bl_notify() and acpi_fujitsu_laptop_notify() are defined before they are first used, so remove their forward declarations as they are redundant.
--- drivers/platform/x86/fujitsu-laptop.c | 4 ---- 1 file changed, 4 deletions(-)
drivers/platform/x86/fujitsu-laptop.c +0 -4
@@ -178,8 +178,6 @@ struct fujitsu_laptop {static struct fujitsu_laptop *fujitsu_laptop; -static void acpi_fujitsu_laptop_notify (struct acpi_device *device,u32 event); -#if IS_ENABLED (CONFIG_LEDS_CLASS )static enum led_brightness logolamp_get (struct led_classdev *cdev); static int logolamp_set(struct led_classdev *cdev,
@@ -227,8 +225,6 @@ static struct led_classdev eco_led = {static u32 dbg_level =0x03 ;#endif -static void acpi_fujitsu_bl_notify (struct acpi_device *device,u32 event); -/* Fujitsu ACPI interface function */ static int call_fext_func (int cmd,int arg0,int arg1,int arg2)
Signature · 1 line
2.11.1
PATCH 7/10 platform/x86: fujitsu-laptop: simplify acpi_bus_register_driver() error handling
In reply to Michał KępieńFrom: Alan Jenkins <[email protected]>
A separate variable is not needed to handle error codes returned by acpi_bus_register_driver(). If the latter fails, just use the value it returned as the value returned by fujitsu_init().
--- drivers/platform/x86/fujitsu-laptop.c | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-)
drivers/platform/x86/fujitsu-laptop.c +5 -9
@@ -1192,7 +1192,7 @@ MODULE_DEVICE_TABLE(acpi, fujitsu_ids);static int __init fujitsu_init (void ) { -int ret, result, max_brightness; +int ret, max_brightness;if (acpi_disabled)return -ENODEV ;
@@ -1207,11 +1207,9 @@ static int __init fujitsu_init(void) fujitsu_bl->keycode5 =KEY_RFKILL ;dmi_check_system (fujitsu_dmi_table); - result =acpi_bus_register_driver (&acpi_fujitsu_bl_driver); -if (result <0 ) { - ret = -ENODEV ; + ret =acpi_bus_register_driver (&acpi_fujitsu_bl_driver); +if (ret) goto fail_acpi; - }/* Register platform stuff */
@@ -1264,11 +1262,9 @@ static int __init fujitsu_init(void) goto fail_laptop; } - result =acpi_bus_register_driver (&acpi_fujitsu_laptop_driver); -if (result <0 ) { - ret = -ENODEV ; + ret =acpi_bus_register_driver (&acpi_fujitsu_laptop_driver); +if (ret) goto fail_laptop1; - }/* Sync backlight power status (needs FUJ02E3 device, hence deferred) */ if (acpi_video_get_backlight_type () == acpi_backlight_vendor) {
Signature · 1 line
2.11.1
PATCH 8/10 platform/x86: fujitsu-laptop: only register backlight device if FUJ02B1 is present
In reply to Michał KępieńFrom: Alan Jenkins <[email protected]>
As the backlight device registered by fujitsu-laptop relies on the FUJ02B1 ACPI device being present, only register the backlight device once that ACPI device is detected. Drop redundant max_brightness local variable. Assign current brightness before registering the backlight device. Adjust indentation to make checkpatch happy.
--- drivers/platform/x86/fujitsu-laptop.c | 49 ++++++++++++++++------------------- 1 file changed, 22 insertions(+), 27 deletions(-)
drivers/platform/x86/fujitsu-laptop.c +22 -27
@@ -762,6 +762,23 @@ static int acpi_fujitsu_bl_add(struct acpi_device *device) fujitsu_bl->max_brightness =FUJITSU_LCD_N_LEVELS ;get_lcd_level (); +if (acpi_video_get_backlight_type () == acpi_backlight_vendor) { +struct backlight_properties props; + +memset (&props,0 ,sizeof (struct backlight_properties )); + props.type =BACKLIGHT_PLATFORM ; + props.max_brightness = fujitsu_bl->max_brightness -1 ; + props.brightness = fujitsu_bl->brightness_level; + fujitsu_bl->bl_device = +backlight_device_register ("fujitsu-laptop" ,NULL ,NULL , + &fujitsu_bl_ops, &props); +if (IS_ERR (fujitsu_bl->bl_device)) { + error =PTR_ERR (fujitsu_bl->bl_device); + fujitsu_bl->bl_device =NULL ; + goto err_unregister_input_dev; + } + } +return 0 ; err_unregister_input_dev:
@@ -778,6 +795,9 @@ static int acpi_fujitsu_bl_remove(struct acpi_device *device)struct fujitsu_bl *fujitsu_bl =acpi_driver_data (device);struct input_dev *input = fujitsu_bl->input; +if (fujitsu_bl->bl_device) +backlight_device_unregister (fujitsu_bl->bl_device); +input_unregister_device (input); fujitsu_bl->acpi_handle =NULL ;
@@ -1192,7 +1212,7 @@ MODULE_DEVICE_TABLE(acpi, fujitsu_ids);static int __init fujitsu_init (void ) { -int ret, max_brightness; +int ret;if (acpi_disabled)return -ENODEV ;
@@ -1229,30 +1249,9 @@ static int __init fujitsu_init(void)if (ret) goto fail_platform_device2; -/* Register backlight stuff */ - -if (acpi_video_get_backlight_type () == acpi_backlight_vendor) { -struct backlight_properties props; - -memset (&props,0 ,sizeof (struct backlight_properties )); - max_brightness = fujitsu_bl->max_brightness; - props.type =BACKLIGHT_PLATFORM ; - props.max_brightness = max_brightness -1 ; - fujitsu_bl->bl_device =backlight_device_register ("fujitsu-laptop" , -NULL ,NULL , - &fujitsu_bl_ops, - &props); -if (IS_ERR (fujitsu_bl->bl_device)) { - ret =PTR_ERR (fujitsu_bl->bl_device); - fujitsu_bl->bl_device =NULL ; - goto fail_sysfs_group; - } - fujitsu_bl->bl_device->props.brightness = fujitsu_bl->brightness_level; - } - ret =platform_driver_register (&fujitsu_pf_driver);if (ret) - goto fail_backlight; + goto fail_sysfs_group;/* Register laptop driver */
@@ -1282,8 +1281,6 @@ static int __init fujitsu_init(void)kfree (fujitsu_laptop); fail_laptop:platform_driver_unregister (&fujitsu_pf_driver); -fail_backlight: -backlight_device_unregister (fujitsu_bl->bl_device); fail_sysfs_group:sysfs_remove_group (&fujitsu_bl->pf_device->dev.kobj, &fujitsu_pf_attribute_group);
@@ -1307,8 +1304,6 @@ static void __exit fujitsu_cleanup(void)platform_driver_unregister (&fujitsu_pf_driver); -backlight_device_unregister (fujitsu_bl->bl_device); -sysfs_remove_group (&fujitsu_bl->pf_device->dev.kobj, &fujitsu_pf_attribute_group);
Signature · 1 line
2.11.1
kernel test robot
build bot[lkp-robot] [platform/x86] b925ff7dcd: BUG:unable_to_handle_kernel
FYI, we noticed the following commit:
FYI, we noticed the following commit:
commit: b925ff7dcd1fc45b86baaebd3442f8b484123716 ("platform/x86: fujitsu-laptop: only register backlight device if FUJ02B1 is present")
url: https://github.com/0day-ci/linux/commits/Micha-K-pie/fujitsu-laptop-renames-and-cleanups/20170209-030748
base: git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git for-next
in testcase: boot
on test machine: qemu-system-i386 -enable-kvm -cpu Haswell,+smep,+smap -m 360M
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
+------------------------------------------+------------+------------+ | | 5b2f1ad8eb | b925ff7dcd | +------------------------------------------+------------+------------+ | boot_successes | 14 | 0 | | boot_failures | 0 | 14 | | BUG:unable_to_handle_kernel | 0 | 14 | | Oops:#[##] | 0 | 14 | | Kernel_panic-not_syncing:Fatal_exception | 0 | 14 | +------------------------------------------+------------+------------+
[ 4.657478] BUG: unable to handle kernel NULL pointer dereference at 00000008 [ 4.658433] IP: fujitsu_init+0x137/0x1b7 [ 4.659208] *pdpt = 0000000000000000 *pde = f000ff53f000ff53 [ 4.659218] [ 4.660432] Oops: 0002 [#1] [ 4.660781] CPU: 0 PID: 1 Comm: swapper Not tainted 4.10.0-rc6-00039-gb925ff7 #1 [ 4.662127] task: c0011000 task.stack: c001a000 [ 4.662684] EIP: fujitsu_init+0x137/0x1b7 [ 4.663608] EFLAGS: 00210282 CPU: 0 [ 4.664060] EAX: 00000000 EBX: 00000000 ECX: d1e775f7 EDX: 00000000 [ 4.665098] ESI: 00000000 EDI: ffffffff EBP: c001bf18 ESP: c001bf14 [ 4.665864] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 [ 4.666338] CR0: 80050033 CR2: 00000008 CR3: 12d9e000 CR4: 000406b0 [ 4.667193] Call Trace: [ 4.667417] ? hdaps_init+0x20/0x20 [ 4.667727] do_one_initcall+0x7c/0x119 [ 4.668106] ? parse_args+0x269/0x470 [ 4.668481] ? kernel_init_freeable+0xd3/0x172 [ 4.668999] kernel_init_freeable+0xef/0x172 [ 4.669432] ? rest_init+0xb0/0xb0 [ 4.669733] kernel_init+0xb/0x100 [ 4.670160] ? schedule_tail+0xc/0x50 [ 4.670484] ? rest_init+0xb0/0xb0 [ 4.670795] ret_from_fork+0x21/0x30 [ 4.671232] Code: ba 02 00 00 00 b9 04 00 00 00 b8 04 10 00 00 e8 0c 25 86 ff 83 f8 03 a1 20 f4 34 d3 5a 8b 40 2c 75 09 c7 40 08 04 00 00 00 eb 07 <c7> 40 08 00 00 00 00 68 18 b4 be d2 e8 4e 17 15 ff 58 eb 65 a1 [ 4.673075] EIP: fujitsu_init+0x137/0x1b7 SS:ESP: 0068:c001bf14 [ 4.673737] CR2: 0000000000000008 [ 4.674040] ---[ end trace 8e0e45e20088f01f ]---
To reproduce:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email
Thanks,
Xiaolong
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 4.10.0-rc6 Kernel Configuration
#
# CONFIG_64BIT is not setCONFIG_X86_32=yCONFIG_X86=yCONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf32-i386" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=yCONFIG_MMU=yCONFIG_ARCH_MMAP_RND_BITS_MIN=8 CONFIG_ARCH_MMAP_RND_BITS_MAX=16 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16 CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_BUG=yCONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_ARCH_WANT_GENERAL_HUGETLB=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_X86_32_LAZY_GS=y CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_FIX_EARLYCON_MEM=yCONFIG_DEBUG_RODATA=yCONFIG_PGTABLE_LEVELS=3 CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_CONSTRUCTORS=yCONFIG_IRQ_WORK=yCONFIG_BUILDTIME_EXTABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y
#
# General setup
#CONFIG_BROKEN_ON_SMP=yCONFIG_INIT_ENV_ARG_LIMIT=32CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not setCONFIG_LOCALVERSION=""CONFIG_LOCALVERSION_AUTO=yCONFIG_HAVE_KERNEL_GZIP=yCONFIG_HAVE_KERNEL_BZIP2=yCONFIG_HAVE_KERNEL_LZMA=yCONFIG_HAVE_KERNEL_XZ=yCONFIG_HAVE_KERNEL_LZO=yCONFIG_HAVE_KERNEL_LZ4=y
# CONFIG_KERNEL_GZIP is not setCONFIG_KERNEL_BZIP2=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not setCONFIG_DEFAULT_HOSTNAME="(none)"CONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_CROSS_MEMORY_ATTACH is not setCONFIG_FHANDLE=y
# CONFIG_USELIB is not set
# CONFIG_AUDIT is not setCONFIG_HAVE_ARCH_AUDITSYSCALL=y
#
# IRQ subsystem
#CONFIG_GENERIC_IRQ_PROBE=yCONFIG_GENERIC_IRQ_SHOW=yCONFIG_GENERIC_IRQ_CHIP=yCONFIG_IRQ_DOMAIN=yCONFIG_IRQ_DOMAIN_HIERARCHY=yCONFIG_GENERIC_MSI_IRQ=yCONFIG_GENERIC_MSI_IRQ_DOMAIN=y
# CONFIG_IRQ_DOMAIN_DEBUG is not setCONFIG_IRQ_FORCED_THREADING=yCONFIG_SPARSE_IRQ=yCONFIG_CLOCKSOURCE_WATCHDOG=yCONFIG_ARCH_CLOCKSOURCE_DATA=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=y
#
# Timers subsystem
#CONFIG_TICK_ONESHOT=yCONFIG_HZ_PERIODIC=y
# CONFIG_NO_HZ_IDLE is not set
# CONFIG_NO_HZ is not setCONFIG_HIGH_RES_TIMERS=y
#
# CPU/Task time and stats accounting
#CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_IRQ_TIME_ACCOUNTING is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
#
# RCU Subsystem
#CONFIG_TINY_RCU=y
# CONFIG_RCU_EXPERT is not setCONFIG_SRCU=yCONFIG_TASKS_RCU=y
# CONFIG_RCU_STALL_COMMON is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_RCU_EXPEDITE_BOOT is not setCONFIG_BUILD_BIN2C=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=yCONFIG_LOG_BUF_SHIFT=17CONFIG_NMI_LOG_BUF_SHIFT=13CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=yCONFIG_CGROUPS=y
# CONFIG_MEMCG is not set
# CONFIG_CGROUP_SCHED is not set
# CONFIG_CGROUP_PIDS is not set
# CONFIG_CGROUP_FREEZER is not set
# CONFIG_CGROUP_HUGETLB is not set
# CONFIG_CPUSETS is not set
# CONFIG_CGROUP_DEVICE is not set
# CONFIG_CGROUP_CPUACCT is not set
# CONFIG_CGROUP_PERF is not set
# CONFIG_CGROUP_BPF is not set
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_SOCK_CGROUP_DATA is not setCONFIG_CHECKPOINT_RESTORE=y
# CONFIG_NAMESPACES is not set
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not setCONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=yCONFIG_RD_LZMA=y
# CONFIG_RD_XZ is not setCONFIG_RD_LZO=y
# CONFIG_RD_LZ4 is not setCONFIG_INITRAMFS_COMPRESSION=".gz"CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not setCONFIG_SYSCTL=yCONFIG_ANON_INODES=yCONFIG_HAVE_UID16=yCONFIG_SYSCTL_EXCEPTION_TRACE=yCONFIG_HAVE_PCSPKR_PLATFORM=yCONFIG_BPF=yCONFIG_EXPERT=yCONFIG_UID16=yCONFIG_MULTIUSER=yCONFIG_SGETMASK_SYSCALL=yCONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not set
# CONFIG_POSIX_TIMERS is not setCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_ABSOLUTE_PERCPU is not setCONFIG_KALLSYMS_BASE_RELATIVE=yCONFIG_PRINTK=yCONFIG_PRINTK_NMI=yCONFIG_BUG=yCONFIG_ELF_CORE=y
# CONFIG_PCSPKR_PLATFORM is not set
# CONFIG_BASE_FULL is not setCONFIG_FUTEX=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=y
# CONFIG_EVENTFD is not setCONFIG_BPF_SYSCALL=y
# CONFIG_SHMEM is not set
# CONFIG_AIO is not setCONFIG_ADVISE_SYSCALLS=y
# CONFIG_USERFAULTFD is not setCONFIG_PCI_QUIRKS=y
# CONFIG_MEMBARRIER is not setCONFIG_EMBEDDED=yCONFIG_HAVE_PERF_EVENTS=yCONFIG_PERF_USE_VMALLOC=y
#
# Kernel Performance Events And Counters
#CONFIG_PERF_EVENTS=yCONFIG_DEBUG_PERF_USE_VMALLOC=y
# CONFIG_VM_EVENT_COUNTERS is not set
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
# CONFIG_SLUB is not setCONFIG_SLOB=y
# CONFIG_SYSTEM_DATA_VERIFICATION is not set
# CONFIG_PROFILING is not setCONFIG_HAVE_OPROFILE=yCONFIG_OPROFILE_NMI_TIMER=yCONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not set
# CONFIG_UPROBES is not set
# CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not setCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_ARCH_USE_BUILTIN_BSWAP=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_OPTPROBES=yCONFIG_HAVE_KPROBES_ON_FTRACE=yCONFIG_HAVE_NMI=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_DMA_CONTIGUOUS=yCONFIG_GENERIC_SMP_IDLE_THREAD=yCONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT=yCONFIG_HAVE_REGS_AND_STACK_ACCESS_API=yCONFIG_HAVE_CLK=yCONFIG_HAVE_DMA_API_DEBUG=yCONFIG_HAVE_HW_BREAKPOINT=yCONFIG_HAVE_MIXED_BREAKPOINTS_REGS=yCONFIG_HAVE_USER_RETURN_NOTIFIER=yCONFIG_HAVE_PERF_EVENTS_NMI=yCONFIG_HAVE_PERF_REGS=yCONFIG_HAVE_PERF_USER_STACK_DUMP=yCONFIG_HAVE_ARCH_JUMP_LABEL=yCONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=yCONFIG_HAVE_CMPXCHG_LOCAL=yCONFIG_HAVE_CMPXCHG_DOUBLE=yCONFIG_ARCH_WANT_IPC_PARSE_VERSION=yCONFIG_HAVE_ARCH_SECCOMP_FILTER=yCONFIG_SECCOMP_FILTER=yCONFIG_HAVE_GCC_PLUGINS=y
# CONFIG_GCC_PLUGINS is not setCONFIG_HAVE_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR is not setCONFIG_CC_STACKPROTECTOR_NONE=y
# CONFIG_CC_STACKPROTECTOR_REGULAR is not set
# CONFIG_CC_STACKPROTECTOR_STRONG is not setCONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=yCONFIG_HAVE_IRQ_TIME_ACCOUNTING=yCONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=yCONFIG_HAVE_ARCH_HUGE_VMAP=yCONFIG_MODULES_USE_ELF_REL=yCONFIG_ARCH_HAS_ELF_RANDOMIZE=yCONFIG_HAVE_ARCH_MMAP_RND_BITS=yCONFIG_HAVE_EXIT_THREAD=yCONFIG_ARCH_MMAP_RND_BITS=8CONFIG_HAVE_COPY_THREAD_TLS=y
# CONFIG_HAVE_ARCH_HASH is not setCONFIG_ISA_BUS_API=yCONFIG_CLONE_BACKWARDS=yCONFIG_OLD_SIGSUSPEND3=yCONFIG_OLD_SIGACTION=y
# CONFIG_CPU_NO_EFFICIENT_FFS is not set
# CONFIG_HAVE_ARCH_VMAP_STACK is not set
#
# GCOV-based kernel profiling
#CONFIG_GCOV_KERNEL=yCONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# CONFIG_GCOV_PROFILE_ALL is not set
# CONFIG_GCOV_FORMAT_AUTODETECT is not setCONFIG_GCOV_FORMAT_3_4=y
# CONFIG_GCOV_FORMAT_4_7 is not setCONFIG_HAVE_GENERIC_DMA_COHERENT=yCONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=1
# CONFIG_MODULES is not setCONFIG_MODULES_TREE_LOOKUP=y
# CONFIG_BLOCK is not setCONFIG_UNINLINE_SPIN_UNLOCK=yCONFIG_ARCH_SUPPORTS_ATOMIC_RMW=yCONFIG_ARCH_USE_QUEUED_SPINLOCKS=yCONFIG_ARCH_USE_QUEUED_RWLOCKS=y
# CONFIG_FREEZER is not set
#
# Processor type and features
#
# CONFIG_ZONE_DMA is not set
# CONFIG_SMP is not set CONFIG_X86_FEATURE_NAMES=y CONFIG_X86_FAST_FEATURE_TESTS=y CONFIG_X86_MPPARSE=y
# CONFIG_GOLDFISH is not set
# CONFIG_INTEL_RDT_A is not set
# CONFIG_X86_EXTENDED_PLATFORM is not set CONFIG_X86_INTEL_LPSS=y CONFIG_X86_AMD_PLATFORM_DEVICE=y CONFIG_IOSF_MBI=y
# CONFIG_IOSF_MBI_DEBUG is not set
# CONFIG_X86_32_IRIS is not set
# CONFIG_SCHED_OMIT_FRAME_POINTER is not set CONFIG_HYPERVISOR_GUEST=yCONFIG_PARAVIRT=y
# CONFIG_PARAVIRT_DEBUG is not set CONFIG_KVM_GUEST=y
# CONFIG_KVM_DEBUG_FS is not set
# CONFIG_LGUEST_GUEST is not set
# CONFIG_PARAVIRT_TIME_ACCOUNTING is not set CONFIG_PARAVIRT_CLOCK=yCONFIG_NO_BOOTMEM=y
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set CONFIG_MWINCHIPC6=y
# CONFIG_MWINCHIP3D is not set
# CONFIG_MELAN is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set CONFIG_X86_GENERIC=y CONFIG_X86_INTERNODE_CACHE_SHIFT=6 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_ALIGNMENT_16=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_MINIMUM_CPU_FAMILY=5
# CONFIG_PROCESSOR_SELECT is not set CONFIG_CPU_SUP_INTEL=y CONFIG_CPU_SUP_CYRIX_32=y CONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_CENTAUR=y CONFIG_CPU_SUP_TRANSMETA_32=y CONFIG_CPU_SUP_UMC_32=yCONFIG_HPET_TIMER=y
# CONFIG_DMI is not setCONFIG_SWIOTLB=yCONFIG_IOMMU_HELPER=yCONFIG_NR_CPUS=1
# CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set CONFIG_PREEMPT_COUNT=yCONFIG_UP_LATE_INIT=yCONFIG_X86_UP_APIC=y
# CONFIG_X86_UP_IOAPIC is not set CONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=y
# CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set # CONFIG_X86_MCE is not set
#
# Performance monitoring
#
# CONFIG_PERF_EVENTS_INTEL_UNCORE is not set CONFIG_PERF_EVENTS_INTEL_RAPL=y CONFIG_PERF_EVENTS_INTEL_CSTATE=y
# CONFIG_PERF_EVENTS_AMD_POWER is not set CONFIG_X86_LEGACY_VM86=yCONFIG_VM86=yCONFIG_TOSHIBA=yCONFIG_I8K=y
# CONFIG_X86_REBOOTFIXUPS is not set CONFIG_MICROCODE=y
# CONFIG_MICROCODE_INTEL is not set
# CONFIG_MICROCODE_AMD is not set CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=y
# CONFIG_X86_CPUID is not set
# CONFIG_NOHIGHMEM is not set
# CONFIG_HIGHMEM4G is not set CONFIG_HIGHMEM64G=yCONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set CONFIG_PAGE_OFFSET=0xC0000000CONFIG_HIGHMEM=yCONFIG_X86_PAE=yCONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_ARCH_DMA_ADDR_T_64BIT=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ILLEGAL_POINTER_VALUE=0 CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y
# CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=yCONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPARSEMEM_STATIC=yCONFIG_HAVE_MEMBLOCK=y CONFIG_HAVE_MEMBLOCK_NODE_MAP=y CONFIG_ARCH_DISCARD_MEMBLOCK=y
# CONFIG_HAVE_BOOTMEM_INFO_NODE is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y CONFIG_COMPACTION=yCONFIG_MIGRATION=yCONFIG_PHYS_ADDR_T_64BIT=yCONFIG_VIRT_TO_BUS=yCONFIG_KSM=yCONFIG_DEFAULT_MMAP_MIN_ADDR=4096
# CONFIG_TRANSPARENT_HUGEPAGE is not set CONFIG_NEED_PER_CPU_KM=y
# CONFIG_CLEANCACHE is not set
# CONFIG_CMA is not setCONFIG_ZPOOL=yCONFIG_ZBUD=y
# CONFIG_Z3FOLD is not set
# CONFIG_ZSMALLOC is not set CONFIG_GENERIC_EARLY_IOREMAP=y CONFIG_ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT=y # CONFIG_IDLE_PAGE_TRACKING is not set
# CONFIG_HIGHPTE is not set CONFIG_X86_CHECK_BIOS_CORRUPTION=y
# CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set CONFIG_X86_RESERVE_LOW=64CONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set
# CONFIG_X86_PAT is not setCONFIG_ARCH_RANDOM=yCONFIG_X86_SMAP=y
# CONFIG_X86_INTEL_MPX is not setCONFIG_EFI=yCONFIG_EFI_STUB=yCONFIG_SECCOMP=y
# CONFIG_HZ_100 is not setCONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not setCONFIG_HZ=250CONFIG_SCHED_HRTICK=y
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x1000000 CONFIG_RELOCATABLE=yCONFIG_RANDOMIZE_BASE=yCONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
# CONFIG_MODIFY_LDT_SYSCALL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
#
# Power management and ACPI options
#
# CONFIG_SUSPEND is not set
# CONFIG_PM is not setCONFIG_ACPI=yCONFIG_ACPI_LEGACY_TABLES_LOOKUP=yCONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=yCONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y
# CONFIG_ACPI_DEBUGGER is not set
# CONFIG_ACPI_PROCFS_POWER is not setCONFIG_ACPI_REV_OVERRIDE_POSSIBLE=yCONFIG_ACPI_EC_DEBUGFS=yCONFIG_ACPI_AC=y
# CONFIG_ACPI_BATTERY is not setCONFIG_ACPI_BUTTON=yCONFIG_ACPI_VIDEO=yCONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not setCONFIG_ACPI_PROCESSOR_CSTATE=y
# CONFIG_ACPI_PROCESSOR is not setCONFIG_ACPI_IPMI=y
# CONFIG_ACPI_CUSTOM_DSDT is not setCONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=yCONFIG_ACPI_TABLE_UPGRADE=y
# CONFIG_ACPI_DEBUG is not set
# CONFIG_ACPI_PCI_SLOT is not setCONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not setCONFIG_ACPI_HOTPLUG_IOAPIC=y
# CONFIG_ACPI_SBS is not set
# CONFIG_ACPI_HED is not setCONFIG_ACPI_CUSTOM_METHOD=y
# CONFIG_ACPI_BGRT is not setCONFIG_ACPI_REDUCED_HARDWARE_ONLY=yCONFIG_HAVE_ACPI_APEI=yCONFIG_HAVE_ACPI_APEI_NMI=y
# CONFIG_ACPI_APEI is not set
# CONFIG_DPTF_POWER is not set
# CONFIG_PMIC_OPREGION is not set
# CONFIG_ACPI_CONFIGFS is not setCONFIG_SFI=y
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# CPU Idle
#CONFIG_CPU_IDLE=yCONFIG_CPU_IDLE_GOV_LADDER=y
# CONFIG_CPU_IDLE_GOV_MENU is not set
# CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not setCONFIG_INTEL_IDLE=y
#
# Bus options (PCI etc.)
#CONFIG_PCI=yCONFIG_PCI_GOBIOS=y
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
# CONFIG_PCI_GOANY is not setCONFIG_PCI_BIOS=yCONFIG_PCI_DOMAINS=y
# CONFIG_PCI_CNB20LE_QUIRK is not setCONFIG_PCIEPORTBUS=y
# CONFIG_PCIEAER is not setCONFIG_PCIEASPM=yCONFIG_PCIEASPM_DEBUG=y
# CONFIG_PCIEASPM_DEFAULT is not set
# CONFIG_PCIEASPM_POWERSAVE is not setCONFIG_PCIEASPM_PERFORMANCE=yCONFIG_PCIE_DPC=y
# CONFIG_PCIE_PTM is not setCONFIG_PCI_BUS_ADDR_T_64BIT=yCONFIG_PCI_MSI=yCONFIG_PCI_MSI_IRQ_DOMAIN=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_REALLOC_ENABLE_AUTO is not set
# CONFIG_PCI_STUB is not setCONFIG_HT_IRQ=yCONFIG_PCI_ATS=yCONFIG_PCI_IOV=y
# CONFIG_PCI_PRI is not set
# CONFIG_PCI_PASID is not setCONFIG_PCI_LABEL=y
# CONFIG_HOTPLUG_PCI is not set
#
# PCI host controller drivers
#CONFIG_PCIE_DW_PLAT=yCONFIG_PCIE_DW=y
# CONFIG_ISA_BUS is not setCONFIG_ISA_DMA_API=yCONFIG_ISA=y
# CONFIG_EISA is not set
CONFIG_SCx200=y
CONFIG_SCx200HR_TIMER=y
# CONFIG_ALIX is not set
# CONFIG_NET5501 is not setCONFIG_AMD_NB=yCONFIG_PCCARD=y
# CONFIG_PCMCIA is not setCONFIG_CARDBUS=y
#
# PC-card bridges
#
# CONFIG_YENTA is not setCONFIG_PCMCIA_PROBE=yCONFIG_RAPIDIO=yCONFIG_RAPIDIO_TSI721=yCONFIG_RAPIDIO_DISC_TIMEOUT=30CONFIG_RAPIDIO_ENABLE_RX_TX_PORTS=yCONFIG_RAPIDIO_DMA_ENGINE=y
# CONFIG_RAPIDIO_DEBUG is not setCONFIG_RAPIDIO_ENUM_BASIC=yCONFIG_RAPIDIO_CHMAN=yCONFIG_RAPIDIO_MPORT_CDEV=y
#
# RapidIO Switch drivers
#CONFIG_RAPIDIO_TSI57X=y
# CONFIG_RAPIDIO_CPS_XX is not set
# CONFIG_RAPIDIO_TSI568 is not setCONFIG_RAPIDIO_CPS_GEN2=yCONFIG_RAPIDIO_RXS_GEN3=y
# CONFIG_X86_SYSFB is not set
#
# Executable file formats / Emulations
#CONFIG_BINFMT_ELF=yCONFIG_ELFCORE=yCONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=yCONFIG_BINFMT_SCRIPT=yCONFIG_HAVE_AOUT=yCONFIG_BINFMT_AOUT=yCONFIG_BINFMT_MISC=yCONFIG_COREDUMP=yCONFIG_COMPAT_32=yCONFIG_HAVE_ATOMIC_IOMAP=yCONFIG_PMC_ATOM=yCONFIG_NET=y
#
# Networking options
#
# CONFIG_PACKET is not setCONFIG_UNIX=y
# CONFIG_UNIX_DIAG is not set
# CONFIG_NET_KEY is not set
# CONFIG_INET is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NET_PTP_CLASSIFY is not set
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
# CONFIG_NETFILTER is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
# CONFIG_BATMAN_ADV is not set
# CONFIG_VSOCKETS is not set
# CONFIG_NETLINK_DIAG is not set
# CONFIG_MPLS is not set
# CONFIG_HSR is not set
# CONFIG_CGROUP_NET_PRIO is not set
# CONFIG_CGROUP_NET_CLASSID is not setCONFIG_NET_RX_BUSY_POLL=yCONFIG_BQL=y
#
# Network testing
#
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_STREAM_PARSER is not setCONFIG_WIRELESS=y
# CONFIG_CFG80211 is not set
# CONFIG_LIB80211 is not set
#
# CFG80211 needs to be enabled for MAC80211
#CONFIG_MAC80211_STA_HASH_MAX_SIZE=0
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
# CONFIG_RFKILL_REGULATOR is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
# CONFIG_NFC is not set
# CONFIG_LWTUNNEL is not set
# CONFIG_DST_CACHE is not set
# CONFIG_NET_DEVLINK is not setCONFIG_MAY_USE_DEVLINK=y
#
# Device Drivers
#
#
# Generic Driver Options
#
# CONFIG_UEVENT_HELPER is not setCONFIG_DEVTMPFS=yCONFIG_DEVTMPFS_MOUNT=yCONFIG_STANDALONE=y
# CONFIG_PREVENT_FIRMWARE_BUILD is not setCONFIG_FW_LOADER=yCONFIG_FIRMWARE_IN_KERNEL=yCONFIG_EXTRA_FIRMWARE=""CONFIG_FW_LOADER_USER_HELPER=yCONFIG_FW_LOADER_USER_HELPER_FALLBACK=yCONFIG_ALLOW_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not setCONFIG_DEBUG_TEST_DRIVER_REMOVE=y
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_GENERIC_CPU_DEVICES is not setCONFIG_GENERIC_CPU_AUTOPROBE=yCONFIG_REGMAP=yCONFIG_REGMAP_I2C=yCONFIG_REGMAP_MMIO=yCONFIG_REGMAP_IRQ=yCONFIG_DMA_SHARED_BUFFER=yCONFIG_DMA_FENCE_TRACE=y
#
# Bus devices
#
# CONFIG_CONNECTOR is not setCONFIG_MTD=y
# CONFIG_MTD_REDBOOT_PARTS is not setCONFIG_MTD_CMDLINE_PARTS=yCONFIG_MTD_AR7_PARTS=y
#
# User Modules And Translation Layers
#CONFIG_MTD_OOPS=yCONFIG_MTD_PARTITIONED_MASTER=y
#
# RAM/ROM/Flash chip drivers
#CONFIG_MTD_CFI=y
# CONFIG_MTD_JEDECPROBE is not setCONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not setCONFIG_MTD_MAP_BANK_WIDTH_1=yCONFIG_MTD_MAP_BANK_WIDTH_2=yCONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not setCONFIG_MTD_CFI_I1=yCONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not setCONFIG_MTD_CFI_INTELEXT=yCONFIG_MTD_CFI_AMDSTD=yCONFIG_MTD_CFI_STAA=yCONFIG_MTD_CFI_UTIL=yCONFIG_MTD_RAM=y
# CONFIG_MTD_ROM is not setCONFIG_MTD_ABSENT=y
#
# Mapping drivers for chip access
#CONFIG_MTD_COMPLEX_MAPPINGS=yCONFIG_MTD_PHYSMAP=yCONFIG_MTD_PHYSMAP_COMPAT=yCONFIG_MTD_PHYSMAP_START=0x8000000CONFIG_MTD_PHYSMAP_LEN=0CONFIG_MTD_PHYSMAP_BANKWIDTH=2
# CONFIG_MTD_SBC_GXX is not set
# CONFIG_MTD_SCx200_DOCFLASH is not setCONFIG_MTD_PCI=y
# CONFIG_MTD_GPIO_ADDR is not setCONFIG_MTD_INTEL_VR_NOR=yCONFIG_MTD_PLATRAM=y
# CONFIG_MTD_LATCH_ADDR is not set
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not setCONFIG_MTD_SLRAM=yCONFIG_MTD_PHRAM=y
# CONFIG_MTD_MTDRAM is not set
#
# Disk-On-Chip Device Drivers
#CONFIG_MTD_DOCG3=yCONFIG_BCH_CONST_M=14CONFIG_BCH_CONST_T=4CONFIG_MTD_NAND_ECC=y CONFIG_MTD_NAND_ECC_SMC=y CONFIG_MTD_NAND=yCONFIG_MTD_NAND_BCH=y CONFIG_MTD_NAND_ECC_BCH=y CONFIG_MTD_SM_COMMON=y CONFIG_MTD_NAND_DENALI=y CONFIG_MTD_NAND_DENALI_PCI=y CONFIG_MTD_NAND_DENALI_SCRATCH_REG_ADDR=0xFF108018 CONFIG_MTD_NAND_GPIO=y
# CONFIG_MTD_NAND_OMAP_BCH_BUILD is not set CONFIG_MTD_NAND_IDS=y CONFIG_MTD_NAND_RICOH=y CONFIG_MTD_NAND_DISKONCHIP=y CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED=y CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0 # CONFIG_MTD_NAND_DISKONCHIP_PROBE_HIGH is not set CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE=y CONFIG_MTD_NAND_DOCG4=y CONFIG_MTD_NAND_CAFE=y CONFIG_MTD_NAND_CS553X=y CONFIG_MTD_NAND_NANDSIM=y CONFIG_MTD_NAND_PLATFORM=y CONFIG_MTD_NAND_OXNAS=y
# CONFIG_MTD_NAND_HISI504 is not set
# CONFIG_MTD_NAND_MTK is not set CONFIG_MTD_ONENAND=y
# CONFIG_MTD_ONENAND_VERIFY_WRITE is not set # CONFIG_MTD_ONENAND_GENERIC is not set CONFIG_MTD_ONENAND_OTP=y
# CONFIG_MTD_ONENAND_2X_PROGRAM is not set
#
# LPDDR & LPDDR2 PCM memory drivers
#
# CONFIG_MTD_LPDDR is not setCONFIG_MTD_SPI_NOR=y
CONFIG_MTD_MT81xx_NOR=y
# CONFIG_MTD_SPI_NOR_USE_4K_SECTORS is not setCONFIG_MTD_UBI=yCONFIG_MTD_UBI_WL_THRESHOLD=4096CONFIG_MTD_UBI_BEB_LIMIT=20
# CONFIG_MTD_UBI_FASTMAP is not setCONFIG_MTD_UBI_GLUEBI=y
# CONFIG_OF is not setCONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=yCONFIG_PARPORT=y
# CONFIG_PARPORT_PC is not set
# CONFIG_PARPORT_GSC is not setCONFIG_PARPORT_AX88796=yCONFIG_PARPORT_1284=yCONFIG_PARPORT_NOT_PC=yCONFIG_PNP=yCONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#CONFIG_ISAPNP=yCONFIG_PNPBIOS=y
# CONFIG_PNPBIOS_PROC_FS is not setCONFIG_PNPACPI=y
#
# Misc devices
#CONFIG_SENSORS_LIS3LV02D=yCONFIG_AD525X_DPOT=yCONFIG_AD525X_DPOT_I2C=y
# CONFIG_DUMMY_IRQ is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not setCONFIG_SGI_IOC4=yCONFIG_TIFM_CORE=y
# CONFIG_TIFM_7XX1 is not set
# CONFIG_ICS932S401 is not setCONFIG_ENCLOSURE_SERVICES=yCONFIG_HP_ILO=yCONFIG_APDS9802ALS=yCONFIG_ISL29003=yCONFIG_ISL29020=yCONFIG_SENSORS_TSL2550=y
# CONFIG_SENSORS_BH1770 is not setCONFIG_SENSORS_APDS990X=yCONFIG_HMC6352=yCONFIG_DS1682=y
# CONFIG_VMWARE_BALLOON is not set
# CONFIG_PCH_PHUB is not set
# CONFIG_USB_SWITCH_FSA9480 is not set
# CONFIG_SRAM is not setCONFIG_PANEL=yCONFIG_PANEL_PARPORT=0CONFIG_PANEL_PROFILE=5
# CONFIG_PANEL_CHANGE_MESSAGE is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not setCONFIG_EEPROM_LEGACY=yCONFIG_EEPROM_MAX6875=y
# CONFIG_EEPROM_93CX6 is not setCONFIG_CB710_CORE=y
# CONFIG_CB710_DEBUG is not setCONFIG_CB710_DEBUG_ASSUMPTIONS=y
#
# Texas Instruments shared transport line discipline #
# CONFIG_TI_ST is not set CONFIG_SENSORS_LIS3_I2C=y
#
# Altera FPGA firmware download module
#CONFIG_ALTERA_STAPL=yCONFIG_INTEL_MEI=y
# CONFIG_INTEL_MEI_ME is not setCONFIG_INTEL_MEI_TXE=yCONFIG_VMWARE_VMCI=y
#
# Intel MIC Bus Driver
#
#
# SCIF Bus Driver
#
#
# VOP Bus Driver
#
#
# Intel MIC Host Driver
#
#
# Intel MIC Card Driver
#
#
# SCIF Driver
#
#
# Intel MIC Coprocessor State Management (COSM) Drivers #
#
# VOP Driver
#CONFIG_ECHO=y
# CONFIG_CXL_BASE is not set
# CONFIG_CXL_AFU_DRIVER_OPS is not setCONFIG_HAVE_IDE=y
#
# SCSI device support
#CONFIG_SCSI_MOD=y
# CONFIG_SCSI_DMA is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#CONFIG_FIREWIRE=yCONFIG_FIREWIRE_OHCI=y
# CONFIG_FIREWIRE_NOSY is not set
# CONFIG_MACINTOSH_DRIVERS is not set
# CONFIG_NETDEVICES is not set
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_LEDS=yCONFIG_INPUT_FF_MEMLESS=yCONFIG_INPUT_POLLDEV=yCONFIG_INPUT_SPARSEKMAP=y
# CONFIG_INPUT_MATRIXKMAP is not set
#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not setCONFIG_INPUT_JOYDEV=y
# CONFIG_INPUT_EVDEV is not setCONFIG_INPUT_EVBUG=y
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADC is not set
# CONFIG_KEYBOARD_ADP5520 is not set
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not setCONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 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_TWL4030 is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_CROS_EC is not setCONFIG_INPUT_MOUSE=y
# CONFIG_MOUSE_PS2 is not setCONFIG_MOUSE_SERIAL=y
# CONFIG_MOUSE_APPLETOUCH is not setCONFIG_MOUSE_BCM5974=y
# CONFIG_MOUSE_CYAPA is not setCONFIG_MOUSE_ELAN_I2C=yCONFIG_MOUSE_ELAN_I2C_I2C=yCONFIG_MOUSE_ELAN_I2C_SMBUS=yCONFIG_MOUSE_INPORT=y
# CONFIG_MOUSE_ATIXL is not setCONFIG_MOUSE_LOGIBM=y
# CONFIG_MOUSE_PC110PAD is not setCONFIG_MOUSE_VSXXXAA=yCONFIG_MOUSE_GPIO=yCONFIG_MOUSE_SYNAPTICS_I2C=yCONFIG_MOUSE_SYNAPTICS_USB=y
# 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=yCONFIG_RMI4_I2C=yCONFIG_RMI4_SMB=y
# CONFIG_RMI4_F03 is not set
# CONFIG_RMI4_F11 is not set
# CONFIG_RMI4_F12 is not setCONFIG_RMI4_F30=yCONFIG_RMI4_F34=y
# CONFIG_RMI4_F55 is not set
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_ARCH_MIGHT_HAVE_PC_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=yCONFIG_SERIO_CT82C710=yCONFIG_SERIO_PARKBD=yCONFIG_SERIO_PCIPS2=yCONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not setCONFIG_SERIO_PS2MULT=yCONFIG_SERIO_ARC_PS2=y
# CONFIG_USERIO is not setCONFIG_GAMEPORT=yCONFIG_GAMEPORT_NS558=yCONFIG_GAMEPORT_L4=yCONFIG_GAMEPORT_EMU10K1=yCONFIG_GAMEPORT_FM801=y
#
# Character devices
#CONFIG_TTY=y
# CONFIG_VT is not setCONFIG_UNIX98_PTYS=yCONFIG_LEGACY_PTYS=yCONFIG_LEGACY_PTY_COUNT=256
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
# CONFIG_N_GSM is not set
# CONFIG_TRACE_SINK is not set
# CONFIG_DEVMEM is not set
# CONFIG_DEVKMEM is not set
#
# Serial drivers
#CONFIG_SERIAL_EARLYCON=yCONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_DEPRECATED_OPTIONS=yCONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_FINTEK is not setCONFIG_SERIAL_8250_CONSOLE=yCONFIG_SERIAL_8250_DMA=yCONFIG_SERIAL_8250_PCI=yCONFIG_SERIAL_8250_NR_UARTS=4CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
# CONFIG_SERIAL_8250_FSL is not set
# CONFIG_SERIAL_8250_DW is not set
# CONFIG_SERIAL_8250_RT288X is not setCONFIG_SERIAL_8250_LPSS=yCONFIG_SERIAL_8250_MID=y
# CONFIG_SERIAL_8250_MOXA is not set
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_UARTLITE is not setCONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_PCH_UART is not set
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_TTY_PRINTK is not setCONFIG_PRINTER=yCONFIG_LP_CONSOLE=yCONFIG_PPDEV=y
# CONFIG_VIRTIO_CONSOLE is not setCONFIG_IPMI_HANDLER=yCONFIG_IPMI_PANIC_EVENT=yCONFIG_IPMI_PANIC_STRING=y
# CONFIG_IPMI_DEVICE_INTERFACE is not setCONFIG_IPMI_SI=yCONFIG_IPMI_SSIF=y
# CONFIG_IPMI_WATCHDOG is not setCONFIG_IPMI_POWEROFF=y
# CONFIG_HW_RANDOM is not setCONFIG_NVRAM=yCONFIG_DTLK=y
# CONFIG_R3964 is not setCONFIG_APPLICOM=yCONFIG_SONYPI=y
# CONFIG_MWAVE is not set
# CONFIG_SCx200_GPIO is not set
# CONFIG_PC8736x_GPIO is not setCONFIG_NSC_GPIO=y
# CONFIG_HPET is not setCONFIG_HANGCHECK_TIMER=yCONFIG_TCG_TPM=y
# CONFIG_TCG_TIS is not setCONFIG_TCG_TIS_I2C_ATMEL=yCONFIG_TCG_TIS_I2C_INFINEON=yCONFIG_TCG_TIS_I2C_NUVOTON=yCONFIG_TCG_NSC=yCONFIG_TCG_ATMEL=yCONFIG_TCG_INFINEON=y
# CONFIG_TCG_CRB is not setCONFIG_TCG_VTPM_PROXY=yCONFIG_TCG_TIS_ST33ZP24=yCONFIG_TCG_TIS_ST33ZP24_I2C=y
# CONFIG_TELCLOCK is not setCONFIG_DEVPORT=yCONFIG_XILLYBUS=yCONFIG_XILLYBUS_PCIE=y
#
# I2C support
#CONFIG_I2C=y
# CONFIG_ACPI_I2C_OPREGION is not setCONFIG_I2C_BOARDINFO=y
# CONFIG_I2C_COMPAT is not setCONFIG_I2C_CHARDEV=yCONFIG_I2C_MUX=y
#
# Multiplexer I2C Chip support
#CONFIG_I2C_MUX_GPIO=yCONFIG_I2C_MUX_PCA9541=y
CONFIG_I2C_MUX_PCA954x=yCONFIG_I2C_MUX_PINCTRL=yCONFIG_I2C_MUX_REG=y
# CONFIG_I2C_MUX_MLXCPLD is not setCONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_SMBUS=yCONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCA=y
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#CONFIG_I2C_ALI1535=y
# CONFIG_I2C_ALI1563 is not setCONFIG_I2C_ALI15X3=yCONFIG_I2C_AMD756=y
# CONFIG_I2C_AMD756_S4882 is not set
# CONFIG_I2C_AMD8111 is not setCONFIG_I2C_I801=yCONFIG_I2C_ISCH=yCONFIG_I2C_ISMT=yCONFIG_I2C_PIIX4=yCONFIG_I2C_NFORCE2=yCONFIG_I2C_NFORCE2_S4985=yCONFIG_I2C_SIS5595=yCONFIG_I2C_SIS630=y
# CONFIG_I2C_SIS96X is not setCONFIG_I2C_VIA=y
# CONFIG_I2C_VIAPRO is not set
#
# ACPI drivers
#CONFIG_I2C_SCMI=y
#
# I2C system bus drivers (mostly embedded / system-on-chip) #CONFIG_I2C_CBUS_GPIO=y CONFIG_I2C_DESIGNWARE_CORE=y CONFIG_I2C_DESIGNWARE_PLATFORM=y
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_DESIGNWARE_BAYTRAIL is not set CONFIG_I2C_EG20T=yCONFIG_I2C_EMEV2=yCONFIG_I2C_GPIO=yCONFIG_I2C_OCORES=yCONFIG_I2C_PCA_PLATFORM=y
# CONFIG_I2C_PXA_PCI is not set
# CONFIG_I2C_SIMTEC is not setCONFIG_I2C_XILINX=y
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_DLN2 is not set
# CONFIG_I2C_PARPORT is not setCONFIG_I2C_PARPORT_LIGHT=yCONFIG_I2C_ROBOTFUZZ_OSIF=y
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_ELEKTOR is not set
# CONFIG_I2C_PCA_ISA is not setCONFIG_I2C_CROS_EC_TUNNEL=y
CONFIG_SCx200_ACB=yCONFIG_I2C_SLAVE=yCONFIG_I2C_SLAVE_EEPROM=y
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_SPI is not set
# CONFIG_SPMI is not set
# CONFIG_HSI is not set
#
# PPS support
#CONFIG_PPS=y
# CONFIG_PPS_DEBUG is not setCONFIG_NTP_PPS=y
#
# PPS clients support
#CONFIG_PPS_CLIENT_KTIMER=y
# CONFIG_PPS_CLIENT_LDISC is not set
# CONFIG_PPS_CLIENT_PARPORT is not setCONFIG_PPS_CLIENT_GPIO=y
#
# PPS generators support
#
#
# PTP clock support
#
#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks. #
# CONFIG_PTP_1588_CLOCK_PCH is not setCONFIG_PINCTRL=y
#
# Pin controllers
#CONFIG_PINMUX=yCONFIG_PINCONF=yCONFIG_GENERIC_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not setCONFIG_PINCTRL_AMD=yCONFIG_PINCTRL_SX150X=y
# CONFIG_PINCTRL_BAYTRAIL is not setCONFIG_PINCTRL_CHERRYVIEW=y
# CONFIG_PINCTRL_BROXTON is not set
# CONFIG_PINCTRL_SUNRISEPOINT is not setCONFIG_GPIOLIB=yCONFIG_GPIO_ACPI=yCONFIG_GPIOLIB_IRQCHIP=yCONFIG_DEBUG_GPIO=yCONFIG_GPIO_SYSFS=yCONFIG_GPIO_GENERIC=yCONFIG_GPIO_MAX730X=y
#
# Memory mapped GPIO drivers
#CONFIG_GPIO_AMDPT=yCONFIG_GPIO_AXP209=yCONFIG_GPIO_DWAPB=yCONFIG_GPIO_GENERIC_PLATFORM=yCONFIG_GPIO_ICH=yCONFIG_GPIO_LYNXPOINT=yCONFIG_GPIO_MOCKUP=yCONFIG_GPIO_VX855=y
#
# Port-mapped I/O GPIO drivers
#CONFIG_GPIO_104_DIO_48E=yCONFIG_GPIO_104_IDIO_16=yCONFIG_GPIO_104_IDI_48=yCONFIG_GPIO_F7188X=yCONFIG_GPIO_GPIO_MM=yCONFIG_GPIO_IT87=yCONFIG_GPIO_SCH=yCONFIG_GPIO_SCH311X=yCONFIG_GPIO_WS16C48=y
#
# I2C GPIO expanders
#CONFIG_GPIO_ADP5588=y
# CONFIG_GPIO_ADP5588_IRQ is not setCONFIG_GPIO_MAX7300=yCONFIG_GPIO_MAX732X=y
# CONFIG_GPIO_MAX732X_IRQ is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not setCONFIG_GPIO_SX150X=yCONFIG_GPIO_TPIC2810=y
#
# MFD GPIO expanders
#CONFIG_GPIO_ADP5520=yCONFIG_GPIO_ARIZONA=y
# CONFIG_GPIO_DA9052 is not set
# CONFIG_GPIO_DA9055 is not set
# CONFIG_GPIO_DLN2 is not set
# CONFIG_GPIO_JANZ_TTL is not setCONFIG_GPIO_LP3943=y
# CONFIG_GPIO_LP873X is not setCONFIG_GPIO_RC5T583=y
# CONFIG_GPIO_TIMBERDALE is not set
# CONFIG_GPIO_TPS65218 is not set
# CONFIG_GPIO_TWL4030 is not set
# CONFIG_GPIO_TWL6040 is not set
# CONFIG_GPIO_WM8350 is not set
# CONFIG_GPIO_WM8994 is not set
#
# PCI GPIO expanders
#CONFIG_GPIO_AMD8111=y
# CONFIG_GPIO_BT8XX is not setCONFIG_GPIO_ML_IOH=yCONFIG_GPIO_PCH=yCONFIG_GPIO_RDC321X=y
#
# SPI or I2C GPIO expanders
#
#
# USB GPIO expanders
#CONFIG_W1=y
#
# 1-wire Bus Masters
#CONFIG_W1_MASTER_MATROX=yCONFIG_W1_MASTER_DS2490=yCONFIG_W1_MASTER_DS2482=y
# CONFIG_W1_MASTER_DS1WM is not set
# CONFIG_W1_MASTER_GPIO is not set
#
# 1-wire Slaves
#CONFIG_W1_SLAVE_THERM=yCONFIG_W1_SLAVE_SMEM=yCONFIG_W1_SLAVE_DS2408=y
# CONFIG_W1_SLAVE_DS2408_READBACK is not set
# CONFIG_W1_SLAVE_DS2413 is not setCONFIG_W1_SLAVE_DS2406=yCONFIG_W1_SLAVE_DS2423=yCONFIG_W1_SLAVE_DS2431=yCONFIG_W1_SLAVE_DS2433=yCONFIG_W1_SLAVE_DS2433_CRC=yCONFIG_W1_SLAVE_DS2760=yCONFIG_W1_SLAVE_DS2780=yCONFIG_W1_SLAVE_DS2781=yCONFIG_W1_SLAVE_DS28E04=yCONFIG_W1_SLAVE_BQ27000=yCONFIG_POWER_AVS=yCONFIG_POWER_RESET=yCONFIG_POWER_RESET_RESTART=yCONFIG_POWER_SUPPLY=yCONFIG_POWER_SUPPLY_DEBUG=yCONFIG_PDA_POWER=yCONFIG_GENERIC_ADC_BATTERY=yCONFIG_WM8350_POWER=yCONFIG_TEST_POWER=yCONFIG_BATTERY_88PM860X=yCONFIG_BATTERY_DS2760=yCONFIG_BATTERY_DS2780=yCONFIG_BATTERY_DS2781=y
# CONFIG_BATTERY_DS2782 is not setCONFIG_BATTERY_SBS=yCONFIG_BATTERY_BQ27XXX=yCONFIG_BATTERY_BQ27XXX_I2C=yCONFIG_BATTERY_DA9052=y
# CONFIG_CHARGER_DA9150 is not setCONFIG_BATTERY_DA9150=yCONFIG_AXP288_CHARGER=y
# CONFIG_AXP288_FUEL_GAUGE is not set
# CONFIG_BATTERY_MAX17040 is not setCONFIG_BATTERY_MAX17042=yCONFIG_CHARGER_88PM860X=yCONFIG_CHARGER_PCF50633=y
# CONFIG_CHARGER_ISP1704 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_TWL4030 is not set
# CONFIG_CHARGER_LP8727 is not setCONFIG_CHARGER_LP8788=yCONFIG_CHARGER_GPIO=yCONFIG_CHARGER_MANAGER=yCONFIG_CHARGER_MAX14577=yCONFIG_CHARGER_MAX77693=yCONFIG_CHARGER_MAX8998=yCONFIG_CHARGER_BQ2415X=yCONFIG_CHARGER_BQ24190=yCONFIG_CHARGER_BQ24257=yCONFIG_CHARGER_BQ24735=yCONFIG_CHARGER_BQ25890=yCONFIG_CHARGER_SMB347=yCONFIG_BATTERY_GAUGE_LTC2941=y
# CONFIG_CHARGER_RT9455 is not setCONFIG_AXP20X_POWER=yCONFIG_HWMON=yCONFIG_HWMON_VID=y
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
# CONFIG_SENSORS_AD7414 is not setCONFIG_SENSORS_AD7418=yCONFIG_SENSORS_ADM1021=y
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not setCONFIG_SENSORS_ADM1029=yCONFIG_SENSORS_ADM1031=yCONFIG_SENSORS_ADM9240=yCONFIG_SENSORS_ADT7X10=yCONFIG_SENSORS_ADT7410=y
# CONFIG_SENSORS_ADT7411 is not setCONFIG_SENSORS_ADT7462=yCONFIG_SENSORS_ADT7470=y
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_ASC7621 is not setCONFIG_SENSORS_K8TEMP=yCONFIG_SENSORS_K10TEMP=yCONFIG_SENSORS_FAM15H_POWER=yCONFIG_SENSORS_APPLESMC=y
# CONFIG_SENSORS_ARM_SCPI is not set
# CONFIG_SENSORS_ASB100 is not setCONFIG_SENSORS_ATXP1=y
# CONFIG_SENSORS_DS620 is not set
# CONFIG_SENSORS_DS1621 is not setCONFIG_SENSORS_DELL_SMM=yCONFIG_SENSORS_DA9052_ADC=yCONFIG_SENSORS_DA9055=y
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not setCONFIG_SENSORS_F71882FG=y
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_MC13783_ADC is not setCONFIG_SENSORS_FSCHMD=yCONFIG_SENSORS_GL518SM=yCONFIG_SENSORS_GL520SM=y
# CONFIG_SENSORS_G760A is not setCONFIG_SENSORS_G762=yCONFIG_SENSORS_GPIO_FAN=yCONFIG_SENSORS_HIH6130=y
# CONFIG_SENSORS_IBMAEM is not setCONFIG_SENSORS_IBMPEX=yCONFIG_SENSORS_IIO_HWMON=yCONFIG_SENSORS_I5500=y
# CONFIG_SENSORS_CORETEMP is not setCONFIG_SENSORS_IT87=y
# CONFIG_SENSORS_JC42 is not set
# CONFIG_SENSORS_POWR1220 is not setCONFIG_SENSORS_LINEAGE=yCONFIG_SENSORS_LTC2945=y
# CONFIG_SENSORS_LTC2990 is not setCONFIG_SENSORS_LTC4151=yCONFIG_SENSORS_LTC4215=y
# CONFIG_SENSORS_LTC4222 is not setCONFIG_SENSORS_LTC4245=yCONFIG_SENSORS_LTC4260=y
# CONFIG_SENSORS_LTC4261 is not setCONFIG_SENSORS_MAX16065=y
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX1668 is not set
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX6639 is not set
# CONFIG_SENSORS_MAX6642 is not setCONFIG_SENSORS_MAX6650=yCONFIG_SENSORS_MAX6697=yCONFIG_SENSORS_MAX31790=yCONFIG_SENSORS_MCP3021=yCONFIG_SENSORS_TC654=yCONFIG_SENSORS_MENF21BMC_HWMON=yCONFIG_SENSORS_LM63=yCONFIG_SENSORS_LM73=yCONFIG_SENSORS_LM75=yCONFIG_SENSORS_LM77=y
# CONFIG_SENSORS_LM78 is not setCONFIG_SENSORS_LM80=yCONFIG_SENSORS_LM83=yCONFIG_SENSORS_LM85=yCONFIG_SENSORS_LM87=yCONFIG_SENSORS_LM90=y
# CONFIG_SENSORS_LM92 is not setCONFIG_SENSORS_LM93=yCONFIG_SENSORS_LM95234=yCONFIG_SENSORS_LM95241=y
# CONFIG_SENSORS_LM95245 is not setCONFIG_SENSORS_PC87360=yCONFIG_SENSORS_PC87427=yCONFIG_SENSORS_NTC_THERMISTOR=y
# CONFIG_SENSORS_NCT6683 is not setCONFIG_SENSORS_NCT6775=yCONFIG_SENSORS_NCT7802=y
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_SHT15 is not set
# CONFIG_SENSORS_SHT21 is not set
CONFIG_SENSORS_SHT3x=yCONFIG_SENSORS_SHTC1=yCONFIG_SENSORS_SIS5595=yCONFIG_SENSORS_DME1737=yCONFIG_SENSORS_EMC1403=yCONFIG_SENSORS_EMC2103=y
# CONFIG_SENSORS_EMC6W201 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SCH56XX_COMMON is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_ADC128D818 is not setCONFIG_SENSORS_ADS1015=yCONFIG_SENSORS_ADS7828=yCONFIG_SENSORS_AMC6821=yCONFIG_SENSORS_INA209=yCONFIG_SENSORS_INA2XX=yCONFIG_SENSORS_INA3221=yCONFIG_SENSORS_TC74=yCONFIG_SENSORS_THMC50=y
# CONFIG_SENSORS_TMP102 is not setCONFIG_SENSORS_TMP103=yCONFIG_SENSORS_TMP108=y
# CONFIG_SENSORS_TMP401 is not setCONFIG_SENSORS_TMP421=y
# CONFIG_SENSORS_VIA_CPUTEMP is not setCONFIG_SENSORS_VIA686A=y
# CONFIG_SENSORS_VT1211 is not setCONFIG_SENSORS_VT8231=yCONFIG_SENSORS_W83781D=yCONFIG_SENSORS_W83791D=yCONFIG_SENSORS_W83792D=yCONFIG_SENSORS_W83793=yCONFIG_SENSORS_W83795=yCONFIG_SENSORS_W83795_FANCTRL=yCONFIG_SENSORS_W83L785TS=y
# CONFIG_SENSORS_W83L786NG is not setCONFIG_SENSORS_W83627HF=yCONFIG_SENSORS_W83627EHF=y
# CONFIG_SENSORS_WM8350 is not setCONFIG_SENSORS_XGENE=y
#
# ACPI drivers
#
# CONFIG_SENSORS_ACPI_POWER is not set
# CONFIG_SENSORS_ATK0110 is not set CONFIG_THERMAL=y
# CONFIG_THERMAL_HWMON is not set CONFIG_THERMAL_WRITABLE_TRIPS=y
# CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE is not set # CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set CONFIG_THERMAL_DEFAULT_GOV_POWER_ALLOCATOR=y # CONFIG_THERMAL_GOV_FAIR_SHARE is not set CONFIG_THERMAL_GOV_STEP_WISE=y
# CONFIG_THERMAL_GOV_BANG_BANG is not set CONFIG_THERMAL_GOV_USER_SPACE=y CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y
# CONFIG_THERMAL_EMULATION is not set CONFIG_INTEL_POWERCLAMP=y CONFIG_INTEL_SOC_DTS_IOSF_CORE=y CONFIG_INTEL_SOC_DTS_THERMAL=y
#
# ACPI INT340X thermal drivers
#CONFIG_INT340X_THERMAL=yCONFIG_ACPI_THERMAL_REL=yCONFIG_INT3406_THERMAL=yCONFIG_INTEL_PCH_THERMAL=yCONFIG_GENERIC_ADC_THERMAL=y
# CONFIG_WATCHDOG is not setCONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#CONFIG_SSB=yCONFIG_SSB_SPROM=yCONFIG_SSB_PCIHOST_POSSIBLE=yCONFIG_SSB_PCIHOST=y
# CONFIG_SSB_B43_PCI_BRIDGE is not setCONFIG_SSB_SDIOHOST_POSSIBLE=yCONFIG_SSB_SDIOHOST=y
# CONFIG_SSB_SILENT is not set
# CONFIG_SSB_DEBUG is not setCONFIG_SSB_DRIVER_PCICORE_POSSIBLE=yCONFIG_SSB_DRIVER_PCICORE=yCONFIG_SSB_DRIVER_GPIO=yCONFIG_BCMA_POSSIBLE=y
#
# Broadcom specific AMBA
#
# CONFIG_BCMA is not set
#
# Multifunction device drivers
#CONFIG_MFD_CORE=y
# CONFIG_MFD_CS5535 is not setCONFIG_MFD_AS3711=yCONFIG_PMIC_ADP5520=yCONFIG_MFD_AAT2870_CORE=y
# CONFIG_MFD_BCM590XX is not setCONFIG_MFD_AXP20X=yCONFIG_MFD_AXP20X_I2C=yCONFIG_MFD_CROS_EC=yCONFIG_MFD_CROS_EC_I2C=y
# CONFIG_PMIC_DA903X is not setCONFIG_PMIC_DA9052=yCONFIG_MFD_DA9052_I2C=yCONFIG_MFD_DA9055=yCONFIG_MFD_DA9062=y
# CONFIG_MFD_DA9063 is not setCONFIG_MFD_DA9150=yCONFIG_MFD_DLN2=yCONFIG_MFD_MC13XXX=yCONFIG_MFD_MC13XXX_I2C=yCONFIG_HTC_PASIC3=yCONFIG_HTC_I2CPLD=yCONFIG_MFD_INTEL_QUARK_I2C_GPIO=yCONFIG_LPC_ICH=yCONFIG_LPC_SCH=y
# CONFIG_INTEL_SOC_PMIC is not setCONFIG_MFD_INTEL_LPSS=y
# CONFIG_MFD_INTEL_LPSS_ACPI is not setCONFIG_MFD_INTEL_LPSS_PCI=yCONFIG_MFD_JANZ_CMODIO=y
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not setCONFIG_MFD_88PM805=yCONFIG_MFD_88PM860X=yCONFIG_MFD_MAX14577=yCONFIG_MFD_MAX77693=y
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not setCONFIG_MFD_MAX8998=y
# CONFIG_MFD_MT6397 is not setCONFIG_MFD_MENF21BMC=y
# CONFIG_MFD_VIPERBOARD is not setCONFIG_MFD_RETU=yCONFIG_MFD_PCF50633=yCONFIG_PCF50633_ADC=y
# CONFIG_PCF50633_GPIO is not set
# CONFIG_UCB1400_CORE is not setCONFIG_MFD_RDC321X=y
# CONFIG_MFD_RTSX_PCI is not set
# CONFIG_MFD_RT5033 is not setCONFIG_MFD_RTSX_USB=yCONFIG_MFD_RC5T583=y
# CONFIG_MFD_SEC_CORE is not set
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SM501 is not setCONFIG_MFD_SKY81452=yCONFIG_MFD_SMSC=y
# CONFIG_ABX500_CORE is not setCONFIG_MFD_SYSCON=yCONFIG_MFD_TI_AM335X_TSCADC=yCONFIG_MFD_LP3943=yCONFIG_MFD_LP8788=y
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not setCONFIG_TPS6507X=y
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TPS65217 is not setCONFIG_MFD_TI_LP873X=yCONFIG_MFD_TPS65218=y
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS80031 is not setCONFIG_TWL4030_CORE=yCONFIG_MFD_TWL4030_AUDIO=yCONFIG_TWL6040_CORE=y
# CONFIG_MFD_WL1273_CORE is not setCONFIG_MFD_LM3533=yCONFIG_MFD_TIMBERDALE=y
# CONFIG_MFD_TMIO is not setCONFIG_MFD_VX855=yCONFIG_MFD_ARIZONA=yCONFIG_MFD_ARIZONA_I2C=y
# CONFIG_MFD_CS47L24 is not set
# CONFIG_MFD_WM5102 is not setCONFIG_MFD_WM5110=y
# CONFIG_MFD_WM8997 is not set
# CONFIG_MFD_WM8998 is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not setCONFIG_MFD_WM8350=yCONFIG_MFD_WM8350_I2C=yCONFIG_MFD_WM8994=yCONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not setCONFIG_REGULATOR_FIXED_VOLTAGE=y
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not setCONFIG_REGULATOR_USERSPACE_CONSUMER=yCONFIG_REGULATOR_88PM8607=yCONFIG_REGULATOR_ACT8865=y
# CONFIG_REGULATOR_AD5398 is not set
# CONFIG_REGULATOR_ANATOP is not set
# CONFIG_REGULATOR_AAT2870 is not setCONFIG_REGULATOR_ARIZONA=y
# CONFIG_REGULATOR_AS3711 is not setCONFIG_REGULATOR_AXP20X=yCONFIG_REGULATOR_DA9052=y
# CONFIG_REGULATOR_DA9055 is not setCONFIG_REGULATOR_DA9062=y
# CONFIG_REGULATOR_DA9210 is not setCONFIG_REGULATOR_DA9211=y
# CONFIG_REGULATOR_FAN53555 is not setCONFIG_REGULATOR_GPIO=yCONFIG_REGULATOR_ISL9305=yCONFIG_REGULATOR_ISL6271A=yCONFIG_REGULATOR_LP3971=yCONFIG_REGULATOR_LP3972=y
# CONFIG_REGULATOR_LP872X is not set
# CONFIG_REGULATOR_LP8755 is not setCONFIG_REGULATOR_LP8788=yCONFIG_REGULATOR_LTC3589=yCONFIG_REGULATOR_LTC3676=yCONFIG_REGULATOR_MAX14577=yCONFIG_REGULATOR_MAX1586=yCONFIG_REGULATOR_MAX8649=yCONFIG_REGULATOR_MAX8660=yCONFIG_REGULATOR_MAX8952=yCONFIG_REGULATOR_MAX8998=yCONFIG_REGULATOR_MAX77693=yCONFIG_REGULATOR_MC13XXX_CORE=yCONFIG_REGULATOR_MC13783=yCONFIG_REGULATOR_MC13892=y
# CONFIG_REGULATOR_MT6311 is not setCONFIG_REGULATOR_PCF50633=y
# CONFIG_REGULATOR_PFUZE100 is not set
# CONFIG_REGULATOR_PV88060 is not setCONFIG_REGULATOR_PV88080=yCONFIG_REGULATOR_PV88090=yCONFIG_REGULATOR_RC5T583=y
# CONFIG_REGULATOR_SKY81452 is not set
# CONFIG_REGULATOR_TPS51632 is not setCONFIG_REGULATOR_TPS62360=yCONFIG_REGULATOR_TPS65023=y
# CONFIG_REGULATOR_TPS6507X is not setCONFIG_REGULATOR_TWL4030=yCONFIG_REGULATOR_WM8350=y
# CONFIG_REGULATOR_WM8994 is not set
# CONFIG_MEDIA_SUPPORT is not set
#
# Graphics support
#
# CONFIG_AGP is not setCONFIG_VGA_ARB=yCONFIG_VGA_ARB_MAX_GPUS=16CONFIG_VGA_SWITCHEROO=yCONFIG_DRM=yCONFIG_DRM_DP_AUX_CHARDEV=y
# CONFIG_DRM_DEBUG_MM is not setCONFIG_DRM_KMS_HELPER=yCONFIG_DRM_KMS_FB_HELPER=yCONFIG_DRM_FBDEV_EMULATION=y
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not setCONFIG_DRM_TTM=y
#
# I2C encoder or helper chips
#CONFIG_DRM_I2C_CH7006=y
# CONFIG_DRM_I2C_SIL164 is not setCONFIG_DRM_I2C_NXP_TDA998X=yCONFIG_DRM_RADEON=y
# CONFIG_DRM_RADEON_USERPTR is not set
# CONFIG_DRM_AMDGPU is not set
#
# ACP (Audio CoProcessor) Configuration
#
# CONFIG_DRM_NOUVEAU is not set
# CONFIG_DRM_I915 is not setCONFIG_DRM_VGEM=y
# CONFIG_DRM_VMWGFX is not setCONFIG_DRM_GMA500=yCONFIG_DRM_GMA600=yCONFIG_DRM_GMA3600=yCONFIG_DRM_UDL=yCONFIG_DRM_AST=y
# CONFIG_DRM_MGAG200 is not set
# CONFIG_DRM_CIRRUS_QEMU is not setCONFIG_DRM_QXL=yCONFIG_DRM_BOCHS=yCONFIG_DRM_VIRTIO_GPU=yCONFIG_DRM_BRIDGE=y
#
# Display Interface Bridges
#CONFIG_DRM_ANALOGIX_ANX78XX=y
# CONFIG_DRM_HISI_HIBMC is not setCONFIG_DRM_LEGACY=yCONFIG_DRM_TDFX=yCONFIG_DRM_R128=yCONFIG_DRM_MGA=yCONFIG_DRM_VIA=yCONFIG_DRM_SAVAGE=y
#
# Frame buffer Devices
#CONFIG_FB=yCONFIG_FIRMWARE_EDID=yCONFIG_FB_CMDLINE=yCONFIG_FB_NOTIFY=yCONFIG_FB_DDC=yCONFIG_FB_BOOT_VESA_SUPPORT=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not setCONFIG_FB_SYS_FILLRECT=yCONFIG_FB_SYS_COPYAREA=yCONFIG_FB_SYS_IMAGEBLIT=yCONFIG_FB_FOREIGN_ENDIAN=yCONFIG_FB_BOTH_ENDIAN=y
# CONFIG_FB_BIG_ENDIAN is not set
# CONFIG_FB_LITTLE_ENDIAN is not setCONFIG_FB_SYS_FOPS=yCONFIG_FB_DEFERRED_IO=yCONFIG_FB_HECUBA=yCONFIG_FB_SVGALIB=y
# CONFIG_FB_MACMODES is not setCONFIG_FB_BACKLIGHT=yCONFIG_FB_MODE_HELPERS=yCONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#CONFIG_FB_CIRRUS=y
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not setCONFIG_FB_ARC=y
# CONFIG_FB_ASILIANT is not setCONFIG_FB_IMSTT=y
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
# CONFIG_FB_EFI is not setCONFIG_FB_N411=yCONFIG_FB_HGA=y
# CONFIG_FB_OPENCORES is not setCONFIG_FB_S1D13XXX=yCONFIG_FB_NVIDIA=yCONFIG_FB_NVIDIA_I2C=yCONFIG_FB_NVIDIA_DEBUG=yCONFIG_FB_NVIDIA_BACKLIGHT=yCONFIG_FB_RIVA=yCONFIG_FB_RIVA_I2C=y
# CONFIG_FB_RIVA_DEBUG is not set
# CONFIG_FB_RIVA_BACKLIGHT is not set
# CONFIG_FB_I740 is not setCONFIG_FB_LE80578=yCONFIG_FB_CARILLO_RANCH=yCONFIG_FB_MATROX=y
# CONFIG_FB_MATROX_MILLENIUM is not set
# CONFIG_FB_MATROX_MYSTIQUE is not set
# CONFIG_FB_MATROX_G is not set
# CONFIG_FB_MATROX_I2C is not setCONFIG_FB_RADEON=y
# CONFIG_FB_RADEON_I2C is not setCONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not setCONFIG_FB_ATY=y
# CONFIG_FB_ATY_CT is not setCONFIG_FB_ATY_GX=yCONFIG_FB_ATY_BACKLIGHT=yCONFIG_FB_S3=y
# CONFIG_FB_S3_DDC is not setCONFIG_FB_SAVAGE=yCONFIG_FB_SAVAGE_I2C=yCONFIG_FB_SAVAGE_ACCEL=yCONFIG_FB_SIS=yCONFIG_FB_SIS_300=yCONFIG_FB_SIS_315=yCONFIG_FB_VIA=yCONFIG_FB_VIA_DIRECT_PROCFS=y
# CONFIG_FB_VIA_X_COMPATIBILITY is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not setCONFIG_FB_3DFX=yCONFIG_FB_3DFX_ACCEL=yCONFIG_FB_3DFX_I2C=yCONFIG_FB_VOODOO1=yCONFIG_FB_VT8623=yCONFIG_FB_TRIDENT=yCONFIG_FB_ARK=yCONFIG_FB_PM3=y
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_GEODE is not setCONFIG_FB_SMSCUFX=yCONFIG_FB_UDL=yCONFIG_FB_IBM_GXT4500=yCONFIG_FB_VIRTUAL=yCONFIG_FB_METRONOME=y
# CONFIG_FB_MB862XX is not setCONFIG_FB_BROADSHEET=yCONFIG_FB_AUO_K190X=yCONFIG_FB_AUO_K1900=yCONFIG_FB_AUO_K1901=yCONFIG_FB_SIMPLE=y
# CONFIG_FB_SM712 is not setCONFIG_BACKLIGHT_LCD_SUPPORT=yCONFIG_LCD_CLASS_DEVICE=yCONFIG_LCD_PLATFORM=yCONFIG_BACKLIGHT_CLASS_DEVICE=yCONFIG_BACKLIGHT_GENERIC=yCONFIG_BACKLIGHT_LM3533=y
# CONFIG_BACKLIGHT_CARILLO_RANCH is not set
# CONFIG_BACKLIGHT_DA9052 is not set
# CONFIG_BACKLIGHT_APPLE is not setCONFIG_BACKLIGHT_PM8941_WLED=y
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP5520 is not setCONFIG_BACKLIGHT_ADP8860=yCONFIG_BACKLIGHT_ADP8870=yCONFIG_BACKLIGHT_88PM860X=y
# CONFIG_BACKLIGHT_PCF50633 is not setCONFIG_BACKLIGHT_AAT2870=yCONFIG_BACKLIGHT_LM3639=yCONFIG_BACKLIGHT_PANDORA=yCONFIG_BACKLIGHT_SKY81452=y
# CONFIG_BACKLIGHT_AS3711 is not setCONFIG_BACKLIGHT_GPIO=yCONFIG_BACKLIGHT_LV5207LP=y
# CONFIG_BACKLIGHT_BD6107 is not setCONFIG_VGASTATE=yCONFIG_HDMI=y
# CONFIG_LOGO is not setCONFIG_SOUND=yCONFIG_SOUND_OSS_CORE=yCONFIG_SOUND_OSS_CORE_PRECLAIM=yCONFIG_SND=yCONFIG_SND_TIMER=yCONFIG_SND_PCM=yCONFIG_SND_PCM_ELD=yCONFIG_SND_PCM_IEC958=yCONFIG_SND_DMAENGINE_PCM=yCONFIG_SND_HWDEP=yCONFIG_SND_RAWMIDI=yCONFIG_SND_COMPRESS_OFFLOAD=yCONFIG_SND_JACK=yCONFIG_SND_JACK_INPUT_DEV=yCONFIG_SND_SEQUENCER=yCONFIG_SND_SEQ_DUMMY=yCONFIG_SND_OSSEMUL=yCONFIG_SND_MIXER_OSS=y
# CONFIG_SND_PCM_OSS is not set
# CONFIG_SND_PCM_TIMER is not set
# CONFIG_SND_SEQUENCER_OSS is not set
# CONFIG_SND_HRTIMER is not set
# CONFIG_SND_DYNAMIC_MINORS is not setCONFIG_SND_SUPPORT_OLD_API=yCONFIG_SND_PROC_FS=yCONFIG_SND_VERBOSE_PROCFS=yCONFIG_SND_VERBOSE_PRINTK=y
# CONFIG_SND_DEBUG is not setCONFIG_SND_VMASTER=yCONFIG_SND_DMA_SGBUF=yCONFIG_SND_RAWMIDI_SEQ=yCONFIG_SND_OPL3_LIB_SEQ=yCONFIG_SND_OPL4_LIB_SEQ=yCONFIG_SND_SBAWE_SEQ=y
# CONFIG_SND_EMU10K1_SEQ is not setCONFIG_SND_MPU401_UART=yCONFIG_SND_OPL3_LIB=yCONFIG_SND_OPL4_LIB=yCONFIG_SND_AC97_CODEC=yCONFIG_SND_DRIVERS=yCONFIG_SND_DUMMY=y
# CONFIG_SND_ALOOP is not setCONFIG_SND_VIRMIDI=yCONFIG_SND_MTPAV=yCONFIG_SND_MTS64=yCONFIG_SND_SERIAL_U16550=y
# CONFIG_SND_MPU401 is not setCONFIG_SND_PORTMAN2X4=y
# CONFIG_SND_AC97_POWER_SAVE is not setCONFIG_SND_WSS_LIB=yCONFIG_SND_SB_COMMON=yCONFIG_SND_SB8_DSP=yCONFIG_SND_SB16_DSP=yCONFIG_SND_ISA=yCONFIG_SND_ADLIB=yCONFIG_SND_AD1816A=yCONFIG_SND_AD1848=yCONFIG_SND_ALS100=y
# CONFIG_SND_AZT1605 is not set
# CONFIG_SND_AZT2316 is not setCONFIG_SND_AZT2320=yCONFIG_SND_CMI8328=yCONFIG_SND_CMI8330=yCONFIG_SND_CS4231=yCONFIG_SND_CS4236=yCONFIG_SND_ES1688=yCONFIG_SND_ES18XX=yCONFIG_SND_SC6000=yCONFIG_SND_GUSCLASSIC=y
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not setCONFIG_SND_INTERWAVE=yCONFIG_SND_INTERWAVE_STB=y
# CONFIG_SND_JAZZ16 is not setCONFIG_SND_OPL3SA2=yCONFIG_SND_OPTI92X_AD1848=yCONFIG_SND_OPTI92X_CS4231=yCONFIG_SND_OPTI93X=yCONFIG_SND_MIRO=yCONFIG_SND_SB8=y
# CONFIG_SND_SB16 is not setCONFIG_SND_SBAWE=y
# CONFIG_SND_SB16_CSP is not set
# CONFIG_SND_SSCAPE is not setCONFIG_SND_WAVEFRONT=yCONFIG_SND_MSND_PINNACLE=yCONFIG_SND_MSND_CLASSIC=y
# CONFIG_SND_PCI is not set
#
# HD-Audio
#CONFIG_SND_HDA_CORE=yCONFIG_SND_HDA_DSP_LOADER=yCONFIG_SND_HDA_EXT_CORE=yCONFIG_SND_HDA_PREALLOC_SIZE=64
# CONFIG_SND_USB is not setCONFIG_SND_FIREWIRE=yCONFIG_SND_FIREWIRE_LIB=yCONFIG_SND_DICE=y
# CONFIG_SND_OXFW is not set
# CONFIG_SND_ISIGHT is not setCONFIG_SND_FIREWORKS=y
# CONFIG_SND_BEBOB is not setCONFIG_SND_FIREWIRE_DIGI00X=y
# CONFIG_SND_FIREWIRE_TASCAM is not setCONFIG_SND_SOC=yCONFIG_SND_SOC_AC97_BUS=yCONFIG_SND_SOC_GENERIC_DMAENGINE_PCM=yCONFIG_SND_SOC_COMPRESS=yCONFIG_SND_SOC_TOPOLOGY=y
# CONFIG_SND_SOC_AMD_ACP is not setCONFIG_SND_ATMEL_SOC=yCONFIG_SND_DESIGNWARE_I2S=y
# CONFIG_SND_DESIGNWARE_PCM is not set
#
# SoC Audio for Freescale CPUs
#
#
# Common SoC Audio options for Freescale CPUs:
#
# CONFIG_SND_SOC_FSL_ASRC is not set
# CONFIG_SND_SOC_FSL_SAI is not set
# CONFIG_SND_SOC_FSL_SSI is not set CONFIG_SND_SOC_FSL_SPDIF=y CONFIG_SND_SOC_FSL_ESAI=y
# CONFIG_SND_SOC_IMX_AUDMUX is not set CONFIG_SND_SOC_IMG=yCONFIG_SND_SOC_IMG_I2S_IN=y CONFIG_SND_SOC_IMG_I2S_OUT=y CONFIG_SND_SOC_IMG_PARALLEL_OUT=y CONFIG_SND_SOC_IMG_SPDIF_IN=y
# CONFIG_SND_SOC_IMG_SPDIF_OUT is not set CONFIG_SND_SOC_IMG_PISTACHIO_INTERNAL_DAC=y CONFIG_SND_SST_MFLD_PLATFORM=y CONFIG_SND_SST_IPC=yCONFIG_SND_SST_IPC_ACPI=y CONFIG_SND_SOC_INTEL_SST=y CONFIG_SND_SOC_INTEL_SST_FIRMWARE=y CONFIG_SND_SOC_INTEL_SST_ACPI=y CONFIG_SND_SOC_INTEL_SST_MATCH=y CONFIG_SND_SOC_INTEL_HASWELL=y CONFIG_SND_SOC_INTEL_HASWELL_MACH=y
# CONFIG_SND_SOC_INTEL_BXT_DA7219_MAX98357A_MACH is not set CONFIG_SND_SOC_INTEL_BXT_RT298_MACH=y
# CONFIG_SND_SOC_INTEL_BDW_RT5677_MACH is not set CONFIG_SND_SOC_INTEL_BROADWELL_MACH=y CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH=y CONFIG_SND_SOC_INTEL_BYTCR_RT5651_MACH=y CONFIG_SND_SOC_INTEL_CHT_BSW_RT5672_MACH=y
# CONFIG_SND_SOC_INTEL_CHT_BSW_RT5645_MACH is not set # CONFIG_SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH is not set CONFIG_SND_SOC_INTEL_SKYLAKE=y
# CONFIG_SND_SOC_INTEL_SKL_RT286_MACH is not set
# CONFIG_SND_SOC_INTEL_SKL_NAU88L25_SSM4567_MACH is not set CONFIG_SND_SOC_INTEL_SKL_NAU88L25_MAX98357A_MACH=y CONFIG_SND_SOC_XTFPGA_I2S=y CONFIG_SND_SOC_I2C_AND_SPI=y
#
# CODEC drivers
#CONFIG_SND_SOC_AC97_CODEC=y
# CONFIG_SND_SOC_ADAU1701 is not setCONFIG_SND_SOC_ADAU7002=y
# CONFIG_SND_SOC_AK4554 is not set
# CONFIG_SND_SOC_AK4613 is not set
# CONFIG_SND_SOC_AK4642 is not setCONFIG_SND_SOC_AK5386=y
# CONFIG_SND_SOC_ALC5623 is not set
# CONFIG_SND_SOC_BT_SCO is not setCONFIG_SND_SOC_CS35L32=yCONFIG_SND_SOC_CS35L33=yCONFIG_SND_SOC_CS35L34=yCONFIG_SND_SOC_CS42L42=yCONFIG_SND_SOC_CS42L51=yCONFIG_SND_SOC_CS42L51_I2C=yCONFIG_SND_SOC_CS42L52=y
# CONFIG_SND_SOC_CS42L56 is not setCONFIG_SND_SOC_CS42L73=yCONFIG_SND_SOC_CS4265=y
# CONFIG_SND_SOC_CS4270 is not setCONFIG_SND_SOC_CS4271=yCONFIG_SND_SOC_CS4271_I2C=yCONFIG_SND_SOC_CS42XX8=yCONFIG_SND_SOC_CS42XX8_I2C=y
# CONFIG_SND_SOC_CS4349 is not setCONFIG_SND_SOC_CS53L30=yCONFIG_SND_SOC_DMIC=yCONFIG_SND_SOC_HDMI_CODEC=y
# CONFIG_SND_SOC_ES8328 is not setCONFIG_SND_SOC_GTM601=yCONFIG_SND_SOC_HDAC_HDMI=yCONFIG_SND_SOC_INNO_RK3036=yCONFIG_SND_SOC_MAX98357A=y
# CONFIG_SND_SOC_MAX98504 is not set
# CONFIG_SND_SOC_MAX9860 is not set
# CONFIG_SND_SOC_MSM8916_WCD_DIGITAL is not setCONFIG_SND_SOC_PCM1681=y
# CONFIG_SND_SOC_PCM179X_I2C is not setCONFIG_SND_SOC_PCM3168A=yCONFIG_SND_SOC_PCM3168A_I2C=y
# CONFIG_SND_SOC_PCM512x_I2C is not setCONFIG_SND_SOC_RL6231=yCONFIG_SND_SOC_RL6347A=yCONFIG_SND_SOC_RT286=yCONFIG_SND_SOC_RT298=y
# CONFIG_SND_SOC_RT5616 is not set
# CONFIG_SND_SOC_RT5631 is not setCONFIG_SND_SOC_RT5640=yCONFIG_SND_SOC_RT5651=yCONFIG_SND_SOC_RT5670=y
# CONFIG_SND_SOC_RT5677_SPI is not setCONFIG_SND_SOC_SGTL5000=y
# CONFIG_SND_SOC_SIRF_AUDIO_CODEC is not setCONFIG_SND_SOC_SPDIF=yCONFIG_SND_SOC_SSM2602=yCONFIG_SND_SOC_SSM2602_I2C=yCONFIG_SND_SOC_SSM4567=yCONFIG_SND_SOC_STA32X=yCONFIG_SND_SOC_STA350=y
# CONFIG_SND_SOC_STI_SAS is not setCONFIG_SND_SOC_TAS2552=y
# CONFIG_SND_SOC_TAS5086 is not set
# CONFIG_SND_SOC_TAS571X is not setCONFIG_SND_SOC_TAS5720=y
# CONFIG_SND_SOC_TFA9879 is not setCONFIG_SND_SOC_TLV320AIC23=yCONFIG_SND_SOC_TLV320AIC23_I2C=y
# CONFIG_SND_SOC_TLV320AIC31XX is not setCONFIG_SND_SOC_TLV320AIC3X=y
# CONFIG_SND_SOC_TS3A227E is not setCONFIG_SND_SOC_WM8510=yCONFIG_SND_SOC_WM8523=yCONFIG_SND_SOC_WM8580=yCONFIG_SND_SOC_WM8711=yCONFIG_SND_SOC_WM8728=y
# CONFIG_SND_SOC_WM8731 is not set
# CONFIG_SND_SOC_WM8737 is not set
# CONFIG_SND_SOC_WM8741 is not set
# CONFIG_SND_SOC_WM8750 is not setCONFIG_SND_SOC_WM8753=y
# CONFIG_SND_SOC_WM8776 is not setCONFIG_SND_SOC_WM8804=yCONFIG_SND_SOC_WM8804_I2C=yCONFIG_SND_SOC_WM8903=yCONFIG_SND_SOC_WM8960=yCONFIG_SND_SOC_WM8962=yCONFIG_SND_SOC_WM8974=y
# CONFIG_SND_SOC_WM8978 is not setCONFIG_SND_SOC_WM8985=yCONFIG_SND_SOC_NAU8810=yCONFIG_SND_SOC_NAU8825=yCONFIG_SND_SOC_TPA6130A2=yCONFIG_SND_SIMPLE_CARD_UTILS=yCONFIG_SND_SIMPLE_CARD=yCONFIG_SOUND_PRIME=y
# CONFIG_SOUND_OSS is not setCONFIG_AC97_BUS=y
#
# HID support
#CONFIG_HID=yCONFIG_HID_BATTERY_STRENGTH=yCONFIG_HIDRAW=y
# CONFIG_UHID is not setCONFIG_HID_GENERIC=y
#
# Special HID drivers
#CONFIG_HID_A4TECH=yCONFIG_HID_ACRUX=y
# CONFIG_HID_ACRUX_FF is not setCONFIG_HID_APPLE=yCONFIG_HID_APPLEIR=yCONFIG_HID_ASUS=yCONFIG_HID_AUREAL=y
# CONFIG_HID_BELKIN is not setCONFIG_HID_BETOP_FF=y
# CONFIG_HID_CHERRY is not setCONFIG_HID_CHICONY=y
# CONFIG_HID_CORSAIR is not setCONFIG_HID_PRODIKEYS=y
# CONFIG_HID_CMEDIA is not set
# CONFIG_HID_CP2112 is not setCONFIG_HID_CYPRESS=y
# CONFIG_HID_DRAGONRISE is not setCONFIG_HID_EMS_FF=y
# CONFIG_HID_ELECOM is not set
# CONFIG_HID_ELO is not set
# CONFIG_HID_EZKEY is not setCONFIG_HID_GEMBIRD=yCONFIG_HID_GFRM=y
# CONFIG_HID_HOLTEK is not setCONFIG_HID_GT683R=y
# CONFIG_HID_KEYTOUCH is not setCONFIG_HID_KYE=yCONFIG_HID_UCLOGIC=yCONFIG_HID_WALTOP=y
# CONFIG_HID_GYRATION is not setCONFIG_HID_ICADE=yCONFIG_HID_TWINHAN=y
# CONFIG_HID_KENSINGTON is not setCONFIG_HID_LCPOWER=yCONFIG_HID_LED=yCONFIG_HID_LENOVO=y
# CONFIG_HID_LOGITECH is not setCONFIG_HID_MAGICMOUSE=yCONFIG_HID_MAYFLASH=yCONFIG_HID_MICROSOFT=yCONFIG_HID_MONTEREY=y
# CONFIG_HID_MULTITOUCH is not setCONFIG_HID_NTRIG=yCONFIG_HID_ORTEK=y
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PENMOUNT is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PLANTRONICS is not setCONFIG_HID_PRIMAX=y
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_SAITEK is not setCONFIG_HID_SAMSUNG=yCONFIG_HID_SONY=y
# CONFIG_SONY_FF is not set
# CONFIG_HID_SPEEDLINK is not setCONFIG_HID_STEELSERIES=y
# CONFIG_HID_SUNPLUS is not setCONFIG_HID_RMI=yCONFIG_HID_GREENASIA=y
# CONFIG_GREENASIA_FF is not setCONFIG_HID_SMARTJOYPLUS=yCONFIG_SMARTJOYPLUS_FF=yCONFIG_HID_TIVO=yCONFIG_HID_TOPSEED=yCONFIG_HID_THINGM=yCONFIG_HID_THRUSTMASTER=y
# CONFIG_THRUSTMASTER_FF is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_WACOM is not setCONFIG_HID_WIIMOTE=y
# CONFIG_HID_XINMO is not set
# CONFIG_HID_ZEROPLUS is not setCONFIG_HID_ZYDACRON=yCONFIG_HID_SENSOR_HUB=y
# CONFIG_HID_SENSOR_CUSTOM_SENSOR is not setCONFIG_HID_ALPS=y
#
# USB HID support
#CONFIG_USB_HID=y
# CONFIG_HID_PID is not setCONFIG_USB_HIDDEV=y
#
# I2C HID support
#CONFIG_I2C_HID=yCONFIG_USB_OHCI_LITTLE_ENDIAN=yCONFIG_USB_SUPPORT=yCONFIG_USB_COMMON=yCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB=yCONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#CONFIG_USB_DEFAULT_PERSIST=yCONFIG_USB_DYNAMIC_MINORS=y
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
# CONFIG_USB_MON is not setCONFIG_USB_WUSB=yCONFIG_USB_WUSB_CBAF=yCONFIG_USB_WUSB_CBAF_DEBUG=y
#
# USB Host Controller Drivers
#CONFIG_USB_C67X00_HCD=yCONFIG_USB_XHCI_HCD=yCONFIG_USB_XHCI_PCI=y
# CONFIG_USB_XHCI_PLATFORM is not set
# CONFIG_USB_EHCI_HCD is not setCONFIG_USB_OXU210HP_HCD=y
# CONFIG_USB_ISP116X_HCD is not setCONFIG_USB_ISP1362_HCD=y
# CONFIG_USB_FOTG210_HCD is not setCONFIG_USB_OHCI_HCD=yCONFIG_USB_OHCI_HCD_PCI=y
# CONFIG_USB_OHCI_HCD_SSB is not set
# CONFIG_USB_OHCI_HCD_PLATFORM is not setCONFIG_USB_UHCI_HCD=yCONFIG_USB_U132_HCD=yCONFIG_USB_SL811_HCD=y
# CONFIG_USB_SL811_HCD_ISO is not setCONFIG_USB_R8A66597_HCD=yCONFIG_USB_WHCI_HCD=yCONFIG_USB_HWA_HCD=y
# CONFIG_USB_HCD_SSB is not setCONFIG_USB_HCD_TEST_MODE=y
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not setCONFIG_USB_PRINTER=yCONFIG_USB_WDM=y
# 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 #
#
# USB Imaging devices
#CONFIG_USB_MDC800=y
# CONFIG_USBIP_CORE is not set
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_DWC3 is not setCONFIG_USB_DWC2=y
# CONFIG_USB_DWC2_HOST is not set
#
# Gadget/Dual-role mode requires USB Gadget support to be enabled #CONFIG_USB_DWC2_PERIPHERAL=y
# CONFIG_USB_DWC2_DUAL_ROLE is not set CONFIG_USB_DWC2_PCI=yCONFIG_USB_DWC2_DEBUG=yCONFIG_USB_DWC2_VERBOSE=y
# CONFIG_USB_DWC2_TRACK_MISSED_SOFS is not set CONFIG_USB_DWC2_DEBUG_PERIODIC=y
# CONFIG_USB_CHIPIDEA is not setCONFIG_USB_ISP1760=yCONFIG_USB_ISP1761_UDC=y
# CONFIG_USB_ISP1760_HOST_ROLE is not set CONFIG_USB_ISP1760_GADGET_ROLE=y
# CONFIG_USB_ISP1760_DUAL_ROLE is not set
#
# USB port drivers
#CONFIG_USB_USS720=y
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not setCONFIG_USB_EMI26=yCONFIG_USB_ADUTUX=y
# CONFIG_USB_SEVSEG is not setCONFIG_USB_RIO500=y
# CONFIG_USB_LEGOTOWER is not setCONFIG_USB_LCD=yCONFIG_USB_CYPRESS_CY7C63=y
# CONFIG_USB_CYTHERM is not setCONFIG_USB_IDMOUSE=yCONFIG_USB_FTDI_ELAN=y
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not setCONFIG_USB_TEST=y
# CONFIG_USB_EHSET_TEST_FIXTURE is not setCONFIG_USB_ISIGHTFW=yCONFIG_USB_YUREX=yCONFIG_USB_EZUSB_FX2=yCONFIG_USB_HSIC_USB3503=yCONFIG_USB_HSIC_USB4604=yCONFIG_USB_LINK_LAYER_TEST=yCONFIG_UCSI=y
#
# USB Physical Layer drivers
#CONFIG_USB_PHY=yCONFIG_NOP_USB_XCEIV=y
# CONFIG_USB_GPIO_VBUS is not setCONFIG_TAHVO_USB=y
# CONFIG_TAHVO_USB_HOST_BY_DEFAULT is not setCONFIG_USB_ISP1301=yCONFIG_USB_GADGET=yCONFIG_USB_GADGET_DEBUG=y
# CONFIG_USB_GADGET_VERBOSE is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
# CONFIG_USB_GADGET_DEBUG_FS is not setCONFIG_USB_GADGET_VBUS_DRAW=2CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2
#
# USB Peripheral Controller
#CONFIG_USB_FOTG210_UDC=yCONFIG_USB_GR_UDC=yCONFIG_USB_R8A66597=y
# CONFIG_USB_PXA27X is not setCONFIG_USB_MV_UDC=yCONFIG_USB_MV_U3D=y
# CONFIG_USB_M66592 is not setCONFIG_USB_BDC_UDC=y
#
# Platform Support
#CONFIG_USB_BDC_PCI=yCONFIG_USB_AMD5536UDC=y
# CONFIG_USB_NET2272 is not setCONFIG_USB_NET2280=yCONFIG_USB_GOKU=yCONFIG_USB_EG20T=y
# CONFIG_USB_DUMMY_HCD is not setCONFIG_USB_LIBCOMPOSITE=yCONFIG_USB_F_SS_LB=yCONFIG_USB_F_FS=yCONFIG_USB_F_UAC1=yCONFIG_USB_CONFIGFS=y
# CONFIG_USB_CONFIGFS_SERIAL is not set
# CONFIG_USB_CONFIGFS_ACM is not set
# CONFIG_USB_CONFIGFS_OBEX is not set
# CONFIG_USB_CONFIGFS_NCM is not set
# CONFIG_USB_CONFIGFS_ECM is not set
# CONFIG_USB_CONFIGFS_ECM_SUBSET is not set
# CONFIG_USB_CONFIGFS_RNDIS is not set
# CONFIG_USB_CONFIGFS_EEM is not setCONFIG_USB_CONFIGFS_F_LB_SS=yCONFIG_USB_CONFIGFS_F_FS=yCONFIG_USB_CONFIGFS_F_UAC1=y
# CONFIG_USB_CONFIGFS_F_UAC2 is not set
# CONFIG_USB_CONFIGFS_F_MIDI is not set
# CONFIG_USB_CONFIGFS_F_HID is not set
# CONFIG_USB_CONFIGFS_F_PRINTER is not setCONFIG_USB_ZERO=y
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ETH is not set
# CONFIG_USB_G_NCM is not set
# CONFIG_USB_GADGETFS is not set
# CONFIG_USB_FUNCTIONFS is not set
# CONFIG_USB_G_SERIAL is not set
# CONFIG_USB_MIDI_GADGET is not set
# CONFIG_USB_G_PRINTER is not set
# CONFIG_USB_CDC_COMPOSITE is not set
# CONFIG_USB_G_HID is not set
# CONFIG_USB_G_DBGP is not setCONFIG_USB_ULPI_BUS=yCONFIG_UWB=yCONFIG_UWB_HWA=yCONFIG_UWB_WHCI=yCONFIG_UWB_I1480U=yCONFIG_MMC=yCONFIG_MMC_DEBUG=y
# CONFIG_SDIO_UART is not setCONFIG_MMC_TEST=y
#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_SDHCI is not set
# CONFIG_MMC_WBSD is not setCONFIG_MMC_TIFM_SD=yCONFIG_MMC_CB710=yCONFIG_MMC_VIA_SDMMC=yCONFIG_MMC_VUB300=yCONFIG_MMC_USHC=yCONFIG_MMC_USDHI6ROL0=yCONFIG_MMC_REALTEK_USB=yCONFIG_MMC_TOSHIBA_PCI=yCONFIG_MMC_MTK=y
# CONFIG_MEMSTICK is not setCONFIG_NEW_LEDS=yCONFIG_LEDS_CLASS=y
# CONFIG_LEDS_CLASS_FLASH is not set
#
# LED drivers
#
# CONFIG_LEDS_88PM860X is not setCONFIG_LEDS_LM3530=yCONFIG_LEDS_LM3533=y
# CONFIG_LEDS_LM3642 is not setCONFIG_LEDS_PCA9532=yCONFIG_LEDS_PCA9532_GPIO=y
# CONFIG_LEDS_GPIO is not setCONFIG_LEDS_LP3944=y
# CONFIG_LEDS_LP3952 is not setCONFIG_LEDS_LP55XX_COMMON=yCONFIG_LEDS_LP5521=yCONFIG_LEDS_LP5523=y
# CONFIG_LEDS_LP5562 is not setCONFIG_LEDS_LP8501=yCONFIG_LEDS_LP8788=y
# CONFIG_LEDS_LP8860 is not set
# CONFIG_LEDS_PCA955X is not setCONFIG_LEDS_PCA963X=yCONFIG_LEDS_WM8350=yCONFIG_LEDS_DA9052=yCONFIG_LEDS_REGULATOR=yCONFIG_LEDS_BD2802=yCONFIG_LEDS_LT3593=y
# CONFIG_LEDS_ADP5520 is not setCONFIG_LEDS_MC13783=yCONFIG_LEDS_TCA6507=y
# CONFIG_LEDS_TLC591XX is not set
CONFIG_LEDS_LM355x=yCONFIG_LEDS_OT200=y
# CONFIG_LEDS_MENF21BMC is not set
#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM) #CONFIG_LEDS_BLINKM=yCONFIG_LEDS_USER=yCONFIG_LEDS_NIC78BX=y
#
# LED Triggers
#
# CONFIG_LEDS_TRIGGERS is not set
# CONFIG_ACCESSIBILITY is not setCONFIG_EDAC_ATOMIC_SCRUB=yCONFIG_EDAC_SUPPORT=y
# CONFIG_EDAC is not setCONFIG_RTC_LIB=yCONFIG_RTC_MC146818_LIB=yCONFIG_RTC_CLASS=y
# CONFIG_RTC_HCTOSYS is not setCONFIG_RTC_SYSTOHC=yCONFIG_RTC_SYSTOHC_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
# CONFIG_RTC_INTF_SYSFS is not setCONFIG_RTC_INTF_PROC=y
# CONFIG_RTC_INTF_DEV is not setCONFIG_RTC_DRV_TEST=y
#
# I2C RTC drivers
#CONFIG_RTC_DRV_88PM860X=yCONFIG_RTC_DRV_ABB5ZES3=y
# CONFIG_RTC_DRV_ABX80X is not setCONFIG_RTC_DRV_DS1307=yCONFIG_RTC_DRV_DS1307_HWMON=y
# CONFIG_RTC_DRV_DS1307_CENTURY is not set
# CONFIG_RTC_DRV_DS1374 is not setCONFIG_RTC_DRV_DS1672=y
# CONFIG_RTC_DRV_LP8788 is not set
# CONFIG_RTC_DRV_MAX6900 is not setCONFIG_RTC_DRV_MAX8998=yCONFIG_RTC_DRV_RS5C372=yCONFIG_RTC_DRV_ISL1208=yCONFIG_RTC_DRV_ISL12022=yCONFIG_RTC_DRV_X1205=yCONFIG_RTC_DRV_PCF8523=yCONFIG_RTC_DRV_PCF85063=y
# CONFIG_RTC_DRV_PCF8563 is not setCONFIG_RTC_DRV_PCF8583=yCONFIG_RTC_DRV_M41T80=y
# CONFIG_RTC_DRV_M41T80_WDT is not set
# CONFIG_RTC_DRV_BQ32K is not setCONFIG_RTC_DRV_RC5T583=y
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not setCONFIG_RTC_DRV_RX8010=yCONFIG_RTC_DRV_RX8581=yCONFIG_RTC_DRV_RX8025=yCONFIG_RTC_DRV_EM3027=yCONFIG_RTC_DRV_RV8803=y
#
# SPI RTC drivers
#CONFIG_RTC_I2C_AND_SPI=y
#
# SPI and I2C RTC drivers
#CONFIG_RTC_DRV_DS3232=yCONFIG_RTC_DRV_PCF2127=yCONFIG_RTC_DRV_RV3029C2=y
# CONFIG_RTC_DRV_RV3029_HWMON is not set
#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not setCONFIG_RTC_DRV_DS1553=yCONFIG_RTC_DRV_DS1685_FAMILY=y
# CONFIG_RTC_DRV_DS1685 is not set
# CONFIG_RTC_DRV_DS1689 is not set
# CONFIG_RTC_DRV_DS17285 is not set
# CONFIG_RTC_DRV_DS17485 is not setCONFIG_RTC_DRV_DS17885=y
# CONFIG_RTC_DS1685_PROC_REGS is not set
# CONFIG_RTC_DS1685_SYSFS_REGS is not setCONFIG_RTC_DRV_DS1742=yCONFIG_RTC_DRV_DS2404=y
# CONFIG_RTC_DRV_DA9052 is not setCONFIG_RTC_DRV_DA9055=yCONFIG_RTC_DRV_DA9063=y
# CONFIG_RTC_DRV_STK17TA8 is not setCONFIG_RTC_DRV_M48T86=yCONFIG_RTC_DRV_M48T35=y
# CONFIG_RTC_DRV_M48T59 is not setCONFIG_RTC_DRV_MSM6242=yCONFIG_RTC_DRV_BQ4802=yCONFIG_RTC_DRV_RP5C01=yCONFIG_RTC_DRV_V3020=yCONFIG_RTC_DRV_WM8350=yCONFIG_RTC_DRV_PCF50633=y
#
# on-CPU RTC drivers
#CONFIG_RTC_DRV_MC13XXX=y
#
# HID Sensor RTC drivers
#CONFIG_RTC_DRV_HID_SENSOR_TIME=yCONFIG_DMADEVICES=yCONFIG_DMADEVICES_DEBUG=yCONFIG_DMADEVICES_VDEBUG=y
#
# DMA Devices
#CONFIG_DMA_ENGINE=yCONFIG_DMA_VIRTUAL_CHANNELS=yCONFIG_DMA_ACPI=y
# CONFIG_INTEL_IDMA64 is not setCONFIG_PCH_DMA=yCONFIG_TIMB_DMA=y
# CONFIG_QCOM_HIDMA_MGMT is not setCONFIG_QCOM_HIDMA=yCONFIG_DW_DMAC_CORE=yCONFIG_DW_DMAC=yCONFIG_DW_DMAC_PCI=yCONFIG_HSU_DMA=y
#
# DMA Clients
#CONFIG_ASYNC_TX_DMA=yCONFIG_DMATEST=y
#
# DMABUF options
#CONFIG_SYNC_FILE=y
# CONFIG_SW_SYNC is not setCONFIG_AUXDISPLAY=yCONFIG_IMG_ASCII_LCD=yCONFIG_UIO=y
# CONFIG_UIO_CIF is not setCONFIG_UIO_PDRV_GENIRQ=yCONFIG_UIO_DMEM_GENIRQ=yCONFIG_UIO_AEC=yCONFIG_UIO_SERCOS3=y
# CONFIG_UIO_PCI_GENERIC is not setCONFIG_UIO_NETX=yCONFIG_UIO_PRUSS=y
# CONFIG_UIO_MF624 is not set
# CONFIG_VIRT_DRIVERS is not setCONFIG_VIRTIO=y
#
# Virtio drivers
#CONFIG_VIRTIO_PCI=yCONFIG_VIRTIO_PCI_LEGACY=y
# CONFIG_VIRTIO_BALLOON is not setCONFIG_VIRTIO_INPUT=yCONFIG_VIRTIO_MMIO=yCONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
#
# Microsoft Hyper-V guest support
#
# CONFIG_HYPERV is not setCONFIG_STAGING=y
#
# IIO staging drivers
#
#
# Accelerometers
#
#
# Analog to digital converters
#CONFIG_AD7606=yCONFIG_AD7606_IFACE_PARALLEL=y
#
# Analog digital bi-direction converters
#CONFIG_ADT7316=yCONFIG_ADT7316_I2C=y
#
# Capacitance to digital converters
#CONFIG_AD7150=y
# CONFIG_AD7152 is not setCONFIG_AD7746=y
#
# Direct Digital Synthesis
#
#
# Digital gyroscope sensors
#
#
# Network Analyzer, Impedance Converters
#
# CONFIG_AD5933 is not set
#
# Light sensors
#CONFIG_SENSORS_ISL29028=y
CONFIG_TSL2x7x=y
#
# Active energy metering IC
#CONFIG_ADE7854=yCONFIG_ADE7854_I2C=y
#
# Resolver to digital converters
#
#
# Triggers - standalone
#
# CONFIG_FB_SM750 is not setCONFIG_FB_XGI=y
#
# Speakup console speech
#
# CONFIG_STAGING_MEDIA is not set
#
# Android
#CONFIG_ANDROID_LOW_MEMORY_KILLER=y
# CONFIG_ION is not set
# CONFIG_FIREWIRE_SERIAL is not set
# CONFIG_DGNC is not setCONFIG_GS_FPGABOOT=yCONFIG_MOST=yCONFIG_MOSTCORE=y
# CONFIG_AIM_CDEV is not set
# CONFIG_AIM_NETWORK is not setCONFIG_AIM_SOUND=yCONFIG_HDM_I2C=y
# CONFIG_HDM_USB is not set
# CONFIG_KS7010 is not setCONFIG_GREYBUS=yCONFIG_GREYBUS_ES2=y
# CONFIG_GREYBUS_AUDIO is not set
# CONFIG_GREYBUS_BOOTROM is not setCONFIG_GREYBUS_HID=yCONFIG_GREYBUS_LIGHT=yCONFIG_GREYBUS_LOG=yCONFIG_GREYBUS_LOOPBACK=yCONFIG_GREYBUS_POWER=yCONFIG_GREYBUS_RAW=y
# CONFIG_GREYBUS_VIBRATOR is not setCONFIG_GREYBUS_BRIDGED_PHY=y
# CONFIG_GREYBUS_GPIO is not setCONFIG_GREYBUS_I2C=yCONFIG_GREYBUS_SDIO=y
# CONFIG_GREYBUS_UART is not set
# CONFIG_GREYBUS_USB is not setCONFIG_X86_PLATFORM_DEVICES=y
# CONFIG_ACER_WMI is not set
# CONFIG_ACERHDF is not set
# CONFIG_ALIENWARE_WMI is not setCONFIG_ASUS_LAPTOP=y
# CONFIG_DELL_WMI_AIO is not set
# CONFIG_DELL_SMO8800 is not setCONFIG_FUJITSU_LAPTOP=yCONFIG_FUJITSU_LAPTOP_DEBUG=yCONFIG_FUJITSU_TABLET=yCONFIG_TC1100_WMI=y
# CONFIG_HP_ACCEL is not setCONFIG_HP_WIRELESS=yCONFIG_HP_WMI=yCONFIG_PANASONIC_LAPTOP=yCONFIG_THINKPAD_ACPI=y
# CONFIG_THINKPAD_ACPI_ALSA_SUPPORT is not setCONFIG_THINKPAD_ACPI_DEBUGFACILITIES=y
# CONFIG_THINKPAD_ACPI_DEBUG is not set
# CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not setCONFIG_THINKPAD_ACPI_VIDEO=y
# CONFIG_THINKPAD_ACPI_HOTKEY_POLL is not setCONFIG_SENSORS_HDAPS=yCONFIG_ASUS_WIRELESS=yCONFIG_ACPI_WMI=y
# CONFIG_MSI_WMI is not setCONFIG_TOPSTAR_LAPTOP=y
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_TOSHIBA_BT_RFKILL is not setCONFIG_TOSHIBA_HAPS=y
# CONFIG_TOSHIBA_WMI is not set
# CONFIG_ACPI_CMPC is not set
# CONFIG_INTEL_HID_EVENT is not setCONFIG_INTEL_VBTN=yCONFIG_INTEL_IPS=y
# CONFIG_INTEL_PMC_CORE is not setCONFIG_IBM_RTL=y
# CONFIG_SAMSUNG_LAPTOP is not setCONFIG_MXM_WMI=y
# CONFIG_SAMSUNG_Q10 is not set
# CONFIG_APPLE_GMUX is not setCONFIG_INTEL_RST=yCONFIG_INTEL_SMARTCONNECT=yCONFIG_PVPANIC=y
# CONFIG_INTEL_PMC_IPC is not setCONFIG_SURFACE_PRO3_BUTTON=y
# CONFIG_INTEL_PUNIT_IPC is not setCONFIG_MLX_CPLD_PLATFORM=yCONFIG_CHROME_PLATFORMS=yCONFIG_CHROMEOS_PSTORE=yCONFIG_CROS_EC_CHARDEV=yCONFIG_CROS_EC_LPC=yCONFIG_CROS_EC_PROTO=yCONFIG_CROS_KBD_LED_BACKLIGHT=yCONFIG_CLKDEV_LOOKUP=yCONFIG_HAVE_CLK_PREPARE=yCONFIG_COMMON_CLK=y
#
# Common Clock Framework
#CONFIG_COMMON_CLK_SCPI=y
# CONFIG_COMMON_CLK_SI5351 is not setCONFIG_COMMON_CLK_CDCE706=y
# CONFIG_COMMON_CLK_CS2000_CP is not setCONFIG_CLK_TWL6040=y
# CONFIG_COMMON_CLK_NXP is not set
# CONFIG_COMMON_CLK_PXA is not set
# CONFIG_COMMON_CLK_PIC32 is not setCONFIG_COMMON_CLK_MEDIATEK=yCONFIG_COMMON_CLK_MT2701=yCONFIG_COMMON_CLK_MT2701_MMSYS=y
# CONFIG_COMMON_CLK_MT2701_IMGSYS is not set
# CONFIG_COMMON_CLK_MT2701_VDECSYS is not set
# CONFIG_COMMON_CLK_MT2701_HIFSYS is not set
# CONFIG_COMMON_CLK_MT2701_ETHSYS is not set
# CONFIG_COMMON_CLK_MT2701_BDPSYS is not set
#
# Hardware Spinlock drivers
#
#
# Clock Source drivers
#CONFIG_CLKSRC_I8253=yCONFIG_CLKEVT_I8253=yCONFIG_CLKBLD_I8253=y
# CONFIG_ATMEL_PIT is not set
# CONFIG_SH_TIMER_CMT is not set
# CONFIG_SH_TIMER_MTU2 is not set
# CONFIG_SH_TIMER_TMU is not set
# CONFIG_EM_TIMER_STI is not setCONFIG_MAILBOX=yCONFIG_PCC=yCONFIG_ALTERA_MBOX=y
# CONFIG_IOMMU_SUPPORT is not set
#
# Remoteproc drivers
#
# CONFIG_REMOTEPROC is not set
#
# Rpmsg drivers
#
#
# SOC (System On Chip) specific Drivers
#
#
# Broadcom SoC drivers
#
# CONFIG_SUNXI_SRAM is not set
# CONFIG_SOC_TI is not setCONFIG_PM_DEVFREQ=y
#
# DEVFREQ Governors
#CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND=yCONFIG_DEVFREQ_GOV_PERFORMANCE=yCONFIG_DEVFREQ_GOV_POWERSAVE=yCONFIG_DEVFREQ_GOV_USERSPACE=yCONFIG_DEVFREQ_GOV_PASSIVE=y
#
# DEVFREQ Drivers
#CONFIG_PM_DEVFREQ_EVENT=yCONFIG_EXTCON=y
#
# Extcon Device Drivers
#
# CONFIG_EXTCON_ADC_JACK is not set
# CONFIG_EXTCON_ARIZONA is not setCONFIG_EXTCON_AXP288=yCONFIG_EXTCON_GPIO=yCONFIG_EXTCON_MAX14577=y
# CONFIG_EXTCON_MAX3355 is not set
# CONFIG_EXTCON_MAX77693 is not setCONFIG_EXTCON_QCOM_SPMI_MISC=yCONFIG_EXTCON_RT8973A=yCONFIG_EXTCON_SM5502=yCONFIG_EXTCON_USB_GPIO=y
# CONFIG_MEMORY is not setCONFIG_IIO=yCONFIG_IIO_BUFFER=yCONFIG_IIO_BUFFER_CB=yCONFIG_IIO_KFIFO_BUF=yCONFIG_IIO_TRIGGERED_BUFFER=yCONFIG_IIO_CONFIGFS=yCONFIG_IIO_TRIGGER=yCONFIG_IIO_CONSUMERS_PER_TRIGGER=2
# CONFIG_IIO_SW_DEVICE is not set
# CONFIG_IIO_SW_TRIGGER is not set
#
# Accelerometers
#CONFIG_BMA180=y
# CONFIG_BMC150_ACCEL is not setCONFIG_DA280=yCONFIG_DA311=yCONFIG_DMARD09=yCONFIG_DMARD10=yCONFIG_HID_SENSOR_ACCEL_3D=yCONFIG_IIO_ST_ACCEL_3AXIS=yCONFIG_IIO_ST_ACCEL_I2C_3AXIS=yCONFIG_KXSD9=yCONFIG_KXSD9_I2C=yCONFIG_KXCJK1013=y
# CONFIG_MC3230 is not setCONFIG_MMA7455=yCONFIG_MMA7455_I2C=yCONFIG_MMA7660=yCONFIG_MMA8452=yCONFIG_MMA9551_CORE=y
# CONFIG_MMA9551 is not setCONFIG_MMA9553=yCONFIG_MXC4005=yCONFIG_MXC6255=yCONFIG_STK8312=y
# CONFIG_STK8BA50 is not set
#
# Analog to digital converters
#CONFIG_AD7291=y
# CONFIG_AD799X is not setCONFIG_AXP288_ADC=y
# CONFIG_CC10001_ADC is not setCONFIG_DA9150_GPADC=yCONFIG_LP8788_ADC=y
# CONFIG_LTC2485 is not set
# CONFIG_MAX1363 is not setCONFIG_MCP3422=y
# CONFIG_NAU7802 is not setCONFIG_STX104=yCONFIG_TI_ADC081C=yCONFIG_TI_AM335X_ADC=y
# CONFIG_TWL4030_MADC is not set
# CONFIG_TWL6030_GPADC is not set
#
# Amplifiers
#
#
# Chemical Sensors
#CONFIG_ATLAS_PH_SENSOR=y
# CONFIG_IAQCORE is not setCONFIG_VZ89X=yCONFIG_IIO_CROS_EC_SENSORS_CORE=y
# CONFIG_IIO_CROS_EC_SENSORS is not set
#
# Hid Sensor IIO Common
#CONFIG_HID_SENSOR_IIO_COMMON=yCONFIG_HID_SENSOR_IIO_TRIGGER=yCONFIG_IIO_MS_SENSORS_I2C=y
#
# SSP Sensor Common
#CONFIG_IIO_ST_SENSORS_I2C=yCONFIG_IIO_ST_SENSORS_CORE=y
#
# Counters
#
# CONFIG_104_QUAD_8 is not set
#
# Digital to analog converters
#CONFIG_AD5064=yCONFIG_AD5380=yCONFIG_AD5446=yCONFIG_AD5592R_BASE=yCONFIG_AD5593R=y
# CONFIG_CIO_DAC is not setCONFIG_M62332=yCONFIG_MAX517=yCONFIG_MCP4725=y
#
# IIO dummy driver
#
#
# Frequency Synthesizers DDS/PLL
#
#
# Clock Generator/Distribution
#
#
# Phase-Locked Loop (PLL) frequency synthesizers
#
#
# Digital gyroscope sensors
#
# CONFIG_BMG160 is not setCONFIG_HID_SENSOR_GYRO_3D=y
# CONFIG_MPU3050_I2C is not setCONFIG_IIO_ST_GYRO_3AXIS=yCONFIG_IIO_ST_GYRO_I2C_3AXIS=yCONFIG_ITG3200=y
#
# Health Sensors
#
#
# Heart Rate Monitors
#CONFIG_AFE4404=yCONFIG_MAX30100=y
#
# Humidity sensors
#CONFIG_AM2315=yCONFIG_DHT11=y
# CONFIG_HDC100X is not setCONFIG_HTS221=yCONFIG_HTS221_I2C=yCONFIG_HTU21=yCONFIG_SI7005=y
# CONFIG_SI7020 is not set
#
# Inertial measurement units
#CONFIG_BMI160=yCONFIG_BMI160_I2C=y
# CONFIG_KMX61 is not set
# CONFIG_INV_MPU6050_I2C is not set
#
# Light sensors
#
# CONFIG_ACPI_ALS is not setCONFIG_ADJD_S311=yCONFIG_AL3320A=yCONFIG_APDS9300=yCONFIG_APDS9960=yCONFIG_BH1750=yCONFIG_BH1780=y
# CONFIG_CM32181 is not setCONFIG_CM3232=yCONFIG_CM3323=y
# CONFIG_CM36651 is not setCONFIG_GP2AP020A00F=y
# CONFIG_SENSORS_ISL29018 is not set
# CONFIG_ISL29125 is not setCONFIG_HID_SENSOR_ALS=y
# CONFIG_HID_SENSOR_PROX is not setCONFIG_JSA1212=yCONFIG_RPR0521=yCONFIG_SENSORS_LM3533=yCONFIG_LTR501=yCONFIG_MAX44000=y
# CONFIG_OPT3001 is not setCONFIG_PA12203001=yCONFIG_SI1145=yCONFIG_STK3310=y
# CONFIG_TCS3414 is not set
# CONFIG_TCS3472 is not set
# CONFIG_SENSORS_TSL2563 is not setCONFIG_TSL2583=y
# CONFIG_TSL4531 is not setCONFIG_US5182D=yCONFIG_VCNL4000=yCONFIG_VEML6070=y
#
# Magnetometer sensors
#CONFIG_AK8975=yCONFIG_AK09911=y
# CONFIG_BMC150_MAGN_I2C is not setCONFIG_MAG3110=yCONFIG_HID_SENSOR_MAGNETOMETER_3D=yCONFIG_MMC35240=y
# CONFIG_IIO_ST_MAGN_3AXIS is not set
# CONFIG_SENSORS_HMC5843_I2C is not set
#
# Inclinometer sensors
#CONFIG_HID_SENSOR_INCLINOMETER_3D=yCONFIG_HID_SENSOR_DEVICE_ROTATION=y
#
# Triggers - standalone
#
# CONFIG_IIO_INTERRUPT_TRIGGER is not setCONFIG_IIO_SYSFS_TRIGGER=y
#
# Digital potentiometers
#CONFIG_DS1803=yCONFIG_MCP4531=yCONFIG_TPL0102=y
#
# Digital potentiostats
#
# CONFIG_LMP91000 is not set
#
# Pressure sensors
#CONFIG_ABP060MG=y
# CONFIG_BMP280 is not setCONFIG_HID_SENSOR_PRESS=y
# CONFIG_HP03 is not set
# CONFIG_MPL115_I2C is not set
# CONFIG_MPL3115 is not setCONFIG_MS5611=y
# CONFIG_MS5611_I2C is not setCONFIG_MS5637=y
# CONFIG_IIO_ST_PRESS is not setCONFIG_T5403=yCONFIG_HP206C=y
# CONFIG_ZPA2326 is not set
#
# Lightning sensors
#
#
# Proximity sensors
#CONFIG_LIDAR_LITE_V2=yCONFIG_SX9500=y
#
# Temperature sensors
#CONFIG_MLX90614=yCONFIG_TMP006=yCONFIG_TSYS01=yCONFIG_TSYS02D=yCONFIG_NTB=y
# CONFIG_NTB_PINGPONG is not setCONFIG_NTB_TOOL=y
# CONFIG_NTB_PERF is not set
# CONFIG_NTB_TRANSPORT is not set
# CONFIG_VME_BUS is not set
# CONFIG_PWM is not setCONFIG_ARM_GIC_MAX_NR=1CONFIG_IPACK_BUS=yCONFIG_BOARD_TPCI200=y
# CONFIG_SERIAL_IPOCTAL is not set
# CONFIG_RESET_CONTROLLER is not setCONFIG_FMC=yCONFIG_FMC_FAKEDEV=yCONFIG_FMC_TRIVIAL=y
# CONFIG_FMC_WRITE_EEPROM is not set
# CONFIG_FMC_CHARDEV is not set
#
# PHY Subsystem
#CONFIG_GENERIC_PHY=yCONFIG_PHY_PXA_28NM_HSIC=yCONFIG_PHY_PXA_28NM_USB2=yCONFIG_BCM_KONA_USB2_PHY=yCONFIG_PHY_SAMSUNG_USB2=y
# CONFIG_PHY_EXYNOS4210_USB2 is not set
# CONFIG_PHY_EXYNOS4X12_USB2 is not set
# CONFIG_PHY_EXYNOS5250_USB2 is not setCONFIG_PHY_TUSB1210=y
# CONFIG_POWERCAP is not set
# CONFIG_MCB is not set
#
# Performance monitor support
#CONFIG_RAS=yCONFIG_THUNDERBOLT=y
#
# Android
#CONFIG_ANDROID=yCONFIG_ANDROID_BINDER_IPC=yCONFIG_ANDROID_BINDER_IPC_32BIT=yCONFIG_NVMEM=yCONFIG_STM=yCONFIG_STM_DUMMY=y
# CONFIG_STM_SOURCE_CONSOLE is not set
# CONFIG_STM_SOURCE_HEARTBEAT is not setCONFIG_INTEL_TH=y
# CONFIG_INTEL_TH_PCI is not setCONFIG_INTEL_TH_GTH=y
# CONFIG_INTEL_TH_STH is not setCONFIG_INTEL_TH_MSU=y
# CONFIG_INTEL_TH_PTI is not set
# CONFIG_INTEL_TH_DEBUG is not set
#
# FPGA Configuration Support
#CONFIG_FPGA=y
#
# Firmware Drivers
#CONFIG_ARM_SCPI_PROTOCOL=yCONFIG_ARM_SCPI_POWER_DOMAIN=y
# CONFIG_EDD is not set
# CONFIG_FIRMWARE_MEMMAP is not setCONFIG_DELL_RBU=yCONFIG_DCDBAS=y
# CONFIG_ISCSI_IBFT_FIND is not setCONFIG_FW_CFG_SYSFS=yCONFIG_FW_CFG_SYSFS_CMDLINE=y
# CONFIG_GOOGLE_FIRMWARE is not set
#
# EFI (Extensible Firmware Interface) Support #CONFIG_EFI_VARS=yCONFIG_EFI_ESRT=yCONFIG_EFI_VARS_PSTORE=y
# CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE is not set CONFIG_EFI_FAKE_MEMMAP=y CONFIG_EFI_MAX_FAKE_MEM=8 CONFIG_EFI_RUNTIME_WRAPPERS=y
# CONFIG_EFI_BOOTLOADER_CONTROL is not set CONFIG_EFI_CAPSULE_LOADER=y
# CONFIG_EFI_TEST is not set CONFIG_APPLE_PROPERTIES=y CONFIG_EFI_DEV_PATH_PARSER=y
#
# Tegra firmware driver
#
#
# File systems
#CONFIG_DCACHE_WORD_ACCESS=yCONFIG_FS_POSIX_ACL=yCONFIG_EXPORTFS=y
# CONFIG_EXPORTFS_BLOCK_OPS is not setCONFIG_FILE_LOCKING=yCONFIG_MANDATORY_FILE_LOCKING=yCONFIG_FSNOTIFY=yCONFIG_DNOTIFY=yCONFIG_INOTIFY_USER=yCONFIG_FANOTIFY=yCONFIG_QUOTA=y
# CONFIG_QUOTA_NETLINK_INTERFACE is not setCONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QUOTA_DEBUG is not setCONFIG_QUOTA_TREE=yCONFIG_QFMT_V1=yCONFIG_QFMT_V2=yCONFIG_QUOTACTL=yCONFIG_AUTOFS4_FS=yCONFIG_FUSE_FS=yCONFIG_CUSE=y
# CONFIG_OVERLAY_FS is not set
#
# Caches
#CONFIG_FSCACHE=y
# CONFIG_FSCACHE_STATS is not set
# CONFIG_FSCACHE_HISTOGRAM is not setCONFIG_FSCACHE_DEBUG=y
# CONFIG_FSCACHE_OBJECT_LIST is not set
#
# Pseudo filesystems
#CONFIG_PROC_FS=y
# CONFIG_PROC_KCORE is not setCONFIG_PROC_SYSCTL=yCONFIG_PROC_PAGE_MONITOR=yCONFIG_PROC_CHILDREN=yCONFIG_KERNFS=yCONFIG_SYSFS=yCONFIG_HUGETLBFS=yCONFIG_HUGETLB_PAGE=yCONFIG_CONFIGFS_FS=yCONFIG_EFIVAR_FS=yCONFIG_MISC_FILESYSTEMS=yCONFIG_ORANGEFS_FS=y
# CONFIG_JFFS2_FS is not setCONFIG_UBIFS_FS=yCONFIG_UBIFS_FS_ADVANCED_COMPR=y
# CONFIG_UBIFS_FS_LZO is not set
# CONFIG_UBIFS_FS_ZLIB is not set
# CONFIG_UBIFS_ATIME_SUPPORT is not setCONFIG_ROMFS_FS=yCONFIG_ROMFS_BACKED_BY_MTD=yCONFIG_ROMFS_ON_MTD=yCONFIG_PSTORE=y
# CONFIG_PSTORE_ZLIB_COMPRESS is not set
# CONFIG_PSTORE_LZO_COMPRESS is not setCONFIG_PSTORE_LZ4_COMPRESS=y
# CONFIG_PSTORE_CONSOLE is not setCONFIG_PSTORE_PMSG=y
# CONFIG_PSTORE_RAM is not setCONFIG_NETWORK_FILESYSTEMS=yCONFIG_NLS=yCONFIG_NLS_DEFAULT="iso8859-1"CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not setCONFIG_NLS_CODEPAGE_775=yCONFIG_NLS_CODEPAGE_850=yCONFIG_NLS_CODEPAGE_852=yCONFIG_NLS_CODEPAGE_855=y
# CONFIG_NLS_CODEPAGE_857 is not setCONFIG_NLS_CODEPAGE_860=yCONFIG_NLS_CODEPAGE_861=yCONFIG_NLS_CODEPAGE_862=yCONFIG_NLS_CODEPAGE_863=yCONFIG_NLS_CODEPAGE_864=yCONFIG_NLS_CODEPAGE_865=yCONFIG_NLS_CODEPAGE_866=yCONFIG_NLS_CODEPAGE_869=yCONFIG_NLS_CODEPAGE_936=yCONFIG_NLS_CODEPAGE_950=yCONFIG_NLS_CODEPAGE_932=yCONFIG_NLS_CODEPAGE_949=y
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not setCONFIG_NLS_CODEPAGE_1250=yCONFIG_NLS_CODEPAGE_1251=yCONFIG_NLS_ASCII=y
# CONFIG_NLS_ISO8859_1 is not setCONFIG_NLS_ISO8859_2=yCONFIG_NLS_ISO8859_3=y
# CONFIG_NLS_ISO8859_4 is not setCONFIG_NLS_ISO8859_5=yCONFIG_NLS_ISO8859_6=yCONFIG_NLS_ISO8859_7=yCONFIG_NLS_ISO8859_9=y
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not setCONFIG_NLS_ISO8859_15=yCONFIG_NLS_KOI8_R=y
# CONFIG_NLS_KOI8_U is not setCONFIG_NLS_MAC_ROMAN=yCONFIG_NLS_MAC_CELTIC=yCONFIG_NLS_MAC_CENTEURO=yCONFIG_NLS_MAC_CROATIAN=yCONFIG_NLS_MAC_CYRILLIC=y
# CONFIG_NLS_MAC_GAELIC is not setCONFIG_NLS_MAC_GREEK=y
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not setCONFIG_NLS_MAC_ROMANIAN=yCONFIG_NLS_MAC_TURKISH=y
# CONFIG_NLS_UTF8 is not set
#
# Kernel hacking
#CONFIG_TRACE_IRQFLAGS_SUPPORT=y
#
# printk and dmesg options # CONFIG_PRINTK_TIME=y CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7 CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4 # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_DYNAMIC_DEBUG is not set
#
# Compile-time checks and compiler options
#
# CONFIG_DEBUG_INFO is not set
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not setCONFIG_FRAME_WARN=1024
# CONFIG_STRIP_ASM_SYMS is not setCONFIG_READABLE_ASM=yCONFIG_UNUSED_SYMBOLS=y
# CONFIG_PAGE_OWNER is not setCONFIG_DEBUG_FS=yCONFIG_HEADERS_CHECK=y
# CONFIG_DEBUG_SECTION_MISMATCH is not set
# CONFIG_SECTION_MISMATCH_WARN_ONLY is not setCONFIG_ARCH_WANT_FRAME_POINTERS=yCONFIG_FRAME_POINTER=y
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not setCONFIG_MAGIC_SYSRQ=yCONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1CONFIG_DEBUG_KERNEL=y
#
# Memory Debugging
#CONFIG_PAGE_EXTENSION=y
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_PAGE_POISONING is not set
# CONFIG_DEBUG_OBJECTS is not setCONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_VM is not setCONFIG_DEBUG_VIRTUAL=y
# CONFIG_DEBUG_MEMORY_INIT is not set
# CONFIG_DEBUG_HIGHMEM is not setCONFIG_HAVE_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACKOVERFLOW is not setCONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_DEBUG_SHIRQ is not set
#
# Debug Lockups and Hangs
#
# CONFIG_LOCKUP_DETECTOR is not setCONFIG_DETECT_HUNG_TASK=yCONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not setCONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0CONFIG_WQ_WATCHDOG=y
# CONFIG_PANIC_ON_OOPS is not setCONFIG_PANIC_ON_OOPS_VALUE=0CONFIG_PANIC_TIMEOUT=0CONFIG_SCHED_DEBUG=y
# CONFIG_SCHED_INFO is not set
# CONFIG_SCHEDSTATS is not setCONFIG_SCHED_STACK_END_CHECK=y
# CONFIG_DEBUG_TIMEKEEPING is not set
# CONFIG_TIMER_STATS is not set
#
# Lock Debugging (spinlocks, mutexes, etc...)
#CONFIG_DEBUG_RT_MUTEXES=yCONFIG_DEBUG_SPINLOCK=yCONFIG_DEBUG_MUTEXES=yCONFIG_DEBUG_WW_MUTEX_SLOWPATH=yCONFIG_DEBUG_LOCK_ALLOC=y
# CONFIG_PROVE_LOCKING is not setCONFIG_LOCKDEP=y
# CONFIG_LOCK_STAT is not setCONFIG_DEBUG_LOCKDEP=yCONFIG_DEBUG_ATOMIC_SLEEP=yCONFIG_DEBUG_LOCKING_API_SELFTESTS=yCONFIG_LOCK_TORTURE_TEST=yCONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not setCONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_PI_LIST is not set
# CONFIG_DEBUG_SG is not setCONFIG_DEBUG_NOTIFIERS=y
# CONFIG_DEBUG_CREDENTIALS is not set
#
# RCU Debugging
#
# CONFIG_PROVE_RCU is not setCONFIG_SPARSE_RCU_POINTER=yCONFIG_TORTURE_TEST=y
# CONFIG_RCU_PERF_TEST is not setCONFIG_RCU_TORTURE_TEST=yCONFIG_RCU_TORTURE_TEST_SLOW_PREINIT=yCONFIG_RCU_TORTURE_TEST_SLOW_PREINIT_DELAY=3CONFIG_RCU_TORTURE_TEST_SLOW_INIT=yCONFIG_RCU_TORTURE_TEST_SLOW_INIT_DELAY=3CONFIG_RCU_TORTURE_TEST_SLOW_CLEANUP=yCONFIG_RCU_TORTURE_TEST_SLOW_CLEANUP_DELAY=3
# CONFIG_RCU_TRACE is not setCONFIG_RCU_EQS_DEBUG=y
# CONFIG_DEBUG_WQ_FORCE_RR_CPU is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not setCONFIG_USER_STACKTRACE_SUPPORT=yCONFIG_HAVE_FUNCTION_TRACER=yCONFIG_HAVE_FUNCTION_GRAPH_TRACER=yCONFIG_HAVE_DYNAMIC_FTRACE=yCONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=yCONFIG_HAVE_FTRACE_MCOUNT_RECORD=yCONFIG_HAVE_SYSCALL_TRACEPOINTS=yCONFIG_HAVE_C_RECORDMCOUNT=yCONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
#
# Runtime Testing
#
# CONFIG_TEST_LIST_SORT is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_RBTREE_TEST is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_TEST_HEXDUMP is not setCONFIG_TEST_STRING_HELPERS=y
# CONFIG_TEST_KSTRTOX is not setCONFIG_TEST_PRINTF=yCONFIG_TEST_BITMAP=y
# CONFIG_TEST_UUID is not set
# CONFIG_TEST_RHASHTABLE is not setCONFIG_TEST_HASH=y
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_DMA_API_DEBUG is not setCONFIG_TEST_FIRMWARE=yCONFIG_TEST_UDELAY=yCONFIG_MEMTEST=y
# CONFIG_BUG_ON_DATA_CORRUPTION is not set
# CONFIG_SAMPLES is not setCONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not setCONFIG_ARCH_HAS_UBSAN_SANITIZE_ALL=y
# CONFIG_ARCH_WANTS_UBSAN_NO_NULL is not setCONFIG_UBSAN=y
# CONFIG_UBSAN_SANITIZE_ALL is not set
# CONFIG_UBSAN_ALIGNMENT is not setCONFIG_UBSAN_NULL=yCONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=yCONFIG_X86_VERBOSE_BOOTUP=y
# CONFIG_EARLY_PRINTK is not setCONFIG_X86_PTDUMP_CORE=yCONFIG_X86_PTDUMP=y
# CONFIG_EFI_PGT_DUMP is not set
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_WX is not set
# CONFIG_DOUBLEFAULT is not set
# CONFIG_DEBUG_TLBFLUSH is not setCONFIG_IOMMU_STRESS=yCONFIG_HAVE_MMIOTRACE_SUPPORT=yCONFIG_IO_DELAY_TYPE_0X80=0CONFIG_IO_DELAY_TYPE_0XED=1CONFIG_IO_DELAY_TYPE_UDELAY=2CONFIG_IO_DELAY_TYPE_NONE=3
# CONFIG_IO_DELAY_0X80 is not set
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not setCONFIG_IO_DELAY_NONE=yCONFIG_DEFAULT_IO_DELAY_TYPE=3CONFIG_DEBUG_BOOT_PARAMS=y
# CONFIG_CPA_DEBUG is not setCONFIG_OPTIMIZE_INLINING=yCONFIG_DEBUG_ENTRY=yCONFIG_DEBUG_NMI_SELFTEST=yCONFIG_X86_DEBUG_FPU=yCONFIG_PUNIT_ATOM_DEBUG=y
#
# Security options
#
# CONFIG_KEYS is not setCONFIG_SECURITY_DMESG_RESTRICT=y
# CONFIG_SECURITY is not setCONFIG_SECURITYFS=yCONFIG_HAVE_ARCH_HARDENED_USERCOPY=yCONFIG_DEFAULT_SECURITY_DAC=yCONFIG_DEFAULT_SECURITY=""CONFIG_CRYPTO=y
#
# Crypto core or helper
#CONFIG_CRYPTO_ALGAPI=yCONFIG_CRYPTO_ALGAPI2=yCONFIG_CRYPTO_AEAD=yCONFIG_CRYPTO_AEAD2=yCONFIG_CRYPTO_BLKCIPHER=yCONFIG_CRYPTO_BLKCIPHER2=yCONFIG_CRYPTO_HASH=yCONFIG_CRYPTO_HASH2=yCONFIG_CRYPTO_RNG=yCONFIG_CRYPTO_RNG2=yCONFIG_CRYPTO_RNG_DEFAULT=yCONFIG_CRYPTO_AKCIPHER2=yCONFIG_CRYPTO_KPP2=yCONFIG_CRYPTO_KPP=yCONFIG_CRYPTO_ACOMP2=y
# CONFIG_CRYPTO_RSA is not setCONFIG_CRYPTO_DH=yCONFIG_CRYPTO_ECDH=yCONFIG_CRYPTO_MANAGER=yCONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_USER is not setCONFIG_CRYPTO_MANAGER_DISABLE_TESTS=yCONFIG_CRYPTO_GF128MUL=yCONFIG_CRYPTO_NULL=yCONFIG_CRYPTO_NULL2=yCONFIG_CRYPTO_WORKQUEUE=yCONFIG_CRYPTO_CRYPTD=yCONFIG_CRYPTO_MCRYPTD=yCONFIG_CRYPTO_AUTHENC=yCONFIG_CRYPTO_ABLK_HELPER=yCONFIG_CRYPTO_SIMD=yCONFIG_CRYPTO_GLUE_HELPER_X86=y
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_CHACHA20POLY1305 is not setCONFIG_CRYPTO_SEQIV=y
# CONFIG_CRYPTO_ECHAINIV is not set
#
# Block modes
#CONFIG_CRYPTO_CBC=yCONFIG_CRYPTO_CTR=y
# CONFIG_CRYPTO_CTS is not set
# CONFIG_CRYPTO_ECB is not setCONFIG_CRYPTO_LRW=y
# CONFIG_CRYPTO_PCBC is not setCONFIG_CRYPTO_XTS=yCONFIG_CRYPTO_KEYWRAP=y
#
# Hash modes
#CONFIG_CRYPTO_CMAC=yCONFIG_CRYPTO_HMAC=yCONFIG_CRYPTO_XCBC=y
# CONFIG_CRYPTO_VMAC is not set
#
# Digest
#CONFIG_CRYPTO_CRC32C=yCONFIG_CRYPTO_CRC32C_INTEL=y
# CONFIG_CRYPTO_CRC32 is not setCONFIG_CRYPTO_CRC32_PCLMUL=yCONFIG_CRYPTO_CRCT10DIF=yCONFIG_CRYPTO_GHASH=yCONFIG_CRYPTO_POLY1305=yCONFIG_CRYPTO_MD4=yCONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not setCONFIG_CRYPTO_RMD128=yCONFIG_CRYPTO_RMD160=y
# CONFIG_CRYPTO_RMD256 is not setCONFIG_CRYPTO_RMD320=yCONFIG_CRYPTO_SHA1=yCONFIG_CRYPTO_SHA256=yCONFIG_CRYPTO_SHA512=yCONFIG_CRYPTO_SHA3=yCONFIG_CRYPTO_TGR192=y
# CONFIG_CRYPTO_WP512 is not set
#
# Ciphers
#CONFIG_CRYPTO_AES=yCONFIG_CRYPTO_AES_586=yCONFIG_CRYPTO_AES_NI_INTEL=y
# CONFIG_CRYPTO_ANUBIS is not setCONFIG_CRYPTO_ARC4=yCONFIG_CRYPTO_BLOWFISH=yCONFIG_CRYPTO_BLOWFISH_COMMON=yCONFIG_CRYPTO_CAMELLIA=yCONFIG_CRYPTO_CAST_COMMON=yCONFIG_CRYPTO_CAST5=yCONFIG_CRYPTO_CAST6=yCONFIG_CRYPTO_DES=yCONFIG_CRYPTO_FCRYPT=y
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not setCONFIG_CRYPTO_SALSA20_586=y
# CONFIG_CRYPTO_CHACHA20 is not set
# CONFIG_CRYPTO_SEED is not setCONFIG_CRYPTO_SERPENT=yCONFIG_CRYPTO_SERPENT_SSE2_586=y
# CONFIG_CRYPTO_TEA is not setCONFIG_CRYPTO_TWOFISH=yCONFIG_CRYPTO_TWOFISH_COMMON=yCONFIG_CRYPTO_TWOFISH_586=y
#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_LZO is not setCONFIG_CRYPTO_842=yCONFIG_CRYPTO_LZ4=yCONFIG_CRYPTO_LZ4HC=y
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not setCONFIG_CRYPTO_DRBG_MENU=yCONFIG_CRYPTO_DRBG_HMAC=yCONFIG_CRYPTO_DRBG_HASH=yCONFIG_CRYPTO_DRBG_CTR=yCONFIG_CRYPTO_DRBG=yCONFIG_CRYPTO_JITTERENTROPY=y
# CONFIG_CRYPTO_USER_API_HASH is not set
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
# CONFIG_CRYPTO_USER_API_RNG is not set
# CONFIG_CRYPTO_USER_API_AEAD is not set
# CONFIG_CRYPTO_HW is not set
#
# Certificates for signature checking
#CONFIG_HAVE_KVM=yCONFIG_VIRTUALIZATION=y
# CONFIG_KVM is not setCONFIG_VHOST_CROSS_ENDIAN_LEGACY=y
# CONFIG_BINARY_PRINTF is not set
#
# Library routines
#CONFIG_BITREVERSE=y
# CONFIG_HAVE_ARCH_BITREVERSE is not setCONFIG_RATIONAL=yCONFIG_GENERIC_STRNCPY_FROM_USER=yCONFIG_GENERIC_STRNLEN_USER=yCONFIG_GENERIC_NET_UTILS=yCONFIG_GENERIC_FIND_FIRST_BIT=yCONFIG_GENERIC_PCI_IOMAP=yCONFIG_GENERIC_IOMAP=yCONFIG_GENERIC_IO=yCONFIG_ARCH_HAS_FAST_MULTIPLIER=y
# CONFIG_CRC_CCITT is not setCONFIG_CRC16=yCONFIG_CRC_T10DIF=yCONFIG_CRC_ITU_T=yCONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
# CONFIG_CRC32_SLICEBY8 is not set
# CONFIG_CRC32_SLICEBY4 is not setCONFIG_CRC32_SARWATE=y
# CONFIG_CRC32_BIT is not set
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not setCONFIG_CRC8=y
# CONFIG_AUDIT_ARCH_COMPAT_GENERIC is not set
# CONFIG_RANDOM32_SELFTEST is not setCONFIG_842_COMPRESS=yCONFIG_842_DECOMPRESS=yCONFIG_ZLIB_INFLATE=yCONFIG_LZO_COMPRESS=yCONFIG_LZO_DECOMPRESS=yCONFIG_LZ4_COMPRESS=yCONFIG_LZ4HC_COMPRESS=yCONFIG_LZ4_DECOMPRESS=yCONFIG_XZ_DEC=yCONFIG_XZ_DEC_X86=y
# CONFIG_XZ_DEC_POWERPC is not set
# CONFIG_XZ_DEC_IA64 is not set
# CONFIG_XZ_DEC_ARM is not set
# CONFIG_XZ_DEC_ARMTHUMB is not setCONFIG_XZ_DEC_SPARC=yCONFIG_XZ_DEC_BCJ=yCONFIG_XZ_DEC_TEST=yCONFIG_DECOMPRESS_GZIP=yCONFIG_DECOMPRESS_BZIP2=yCONFIG_DECOMPRESS_LZMA=yCONFIG_DECOMPRESS_LZO=yCONFIG_GENERIC_ALLOCATOR=yCONFIG_REED_SOLOMON=yCONFIG_REED_SOLOMON_DEC16=yCONFIG_BCH=yCONFIG_BCH_CONST_PARAMS=yCONFIG_INTERVAL_TREE=yCONFIG_HAS_IOMEM=yCONFIG_HAS_IOPORT_MAP=yCONFIG_HAS_DMA=yCONFIG_DQL=yCONFIG_NLATTR=yCONFIG_CLZ_TAB=y
# CONFIG_CORDIC is not setCONFIG_DDR=yCONFIG_IRQ_POLL=yCONFIG_MPILIB=yCONFIG_UCS2_STRING=y
# CONFIG_SG_SPLIT is not set
# CONFIG_SG_POOL is not setCONFIG_ARCH_HAS_SG_CHAIN=yCONFIG_ARCH_HAS_MMIO_FLUSH=y
#!/bin/sh
export_top_env()
{
export suite='boot'
export testcase='boot'
export timeout='10m'
export job_origin='/lkp/lkp/src/jobs/boot.yaml'
export queue='bisect'
export testbox='vm-vp-quantal-i386-23'
export tbox_group='vm-vp-quantal-i386'
export branch='linux-devel/devel-hourly-2017021002'
export commit='b925ff7dcd1fc45b86baaebd3442f8b484123716'
export kconfig='i386-randconfig-x0-02100842'
export submit_id='58a01cbd0b9a93252f20acda'
export job_file='/lkp/scheduled/vm-vp-quantal-i386-23/boot-1-quantal-core-i386.cgz-b925ff7dcd1fc45b86baaebd3442f8b484123716-20170212-9519-tn3xp4-0.yaml'
export id='a982409901e552ed2c074240700189f82f370fb5'
export model='qemu-system-i386 -enable-kvm -cpu Haswell,+smep,+smap'
export nr_vm=64
export nr_cpu=1
export memory='360M'
export rootfs='quantal-core-i386.cgz'
export need_kconfig='CONFIG_KVM_GUEST=y'
export compiler='gcc-6'
export enqueue_time='2017-02-12 16:28:46 +0800'
export _id='58a01cbd0b9a93252f20acda'
export user='lkp'
export result_root='/result/boot/1/vm-vp-quantal-i386/quantal-core-i386.cgz/i386-randconfig-x0-02100842/gcc-6/b925ff7dcd1fc45b86baaebd3442f8b484123716/0'
export LKP_SERVER='inn'
export max_uptime=600
export initrd='/osimage/quantal/quantal-core-i386.cgz'
export bootloader_append='root=/dev/ram0user=lkp job=/lkp/scheduled/vm-vp-quantal-i386-23/boot-1-quantal-core-i386.cgz-b925ff7dcd1fc45b86baaebd3442f8b484123716-20170212-9519-tn3xp4-0.yaml ARCH=i386
kconfig=i386-randconfig-x0-02100842
branch=linux-devel/devel-hourly-2017021002
commit=b925ff7dcd1fc45b86baaebd3442f8b484123716 BOOT_IMAGE=/pkg/linux/i386-randconfig-x0-02100842/gcc-6/b925ff7dcd1fc45b86baaebd3442f8b484123716/vmlinuz-4.10.0-rc6-00039-gb925ff7 max_uptime=600 RESULT_ROOT=/result/boot/1/vm-vp-quantal-i386/quantal-core-i386.cgz/i386-randconfig-x0-02100842/gcc-6/b925ff7dcd1fc45b86baaebd3442f8b484123716/0 LKP_SERVER=inn
debug
apic=debugsysrq_always_enabled
rcupdate.rcu_cpu_stall_timeout=100
net.ifnames=0
printk.devkmsg=on
panic=-1
softlockup_panic=1
nmi_watchdog=panic
oops=panic
load_ramdisk=2
prompt_ramdisk=0
systemd.log_level=errignore_loglevel
earlyprintk=ttyS0,115200
console=ttyS0,115200
console=tty0
vga=normal
rw'
export lkp_initrd='/lkp/lkp/lkp-i386.cgz'
export site='inn'
export LKP_CGI_PORT=80
export LKP_CIFS_PORT=139
export kernel='/pkg/linux/i386-randconfig-x0-02100842/gcc-6/b925ff7dcd1fc45b86baaebd3442f8b484123716/vmlinuz-4.10.0-rc6-00039-gb925ff7'
export dequeue_time='2017-02-12 16:28:53 +0800'
export job_initrd='/lkp/scheduled/vm-vp-quantal-i386-23/boot-1-quantal-core-i386.cgz-b925ff7dcd1fc45b86baaebd3442f8b484123716-20170212-9519-tn3xp4-0.cgz'
[ -n "$LKP_SRC" ] ||
export LKP_SRC=/lkp/${user:-lkp}/src
}run_job()
{
echo $$ > $TMP/run-job.pid
. $LKP_SRC/lib/http.sh
. $LKP_SRC/lib/job.sh
. $LKP_SRC/lib/env.sh
export_top_env
run_monitor $LKP_SRC/monitors/one-shot/wrapper boot-slabinfo run_monitor $LKP_SRC/monitors/one-shot/wrapper boot-meminfo run_monitor $LKP_SRC/monitors/one-shot/wrapper memmap run_monitor $LKP_SRC/monitors/wrapper kmsg run_monitor $LKP_SRC/monitors/wrapper oom-killer run_monitor $LKP_SRC/monitors/plain/watchdog run_monitor $LKP_SRC/monitors/wrapper nfs-hang
run_test $LKP_SRC/tests/wrapper sleep 1
}
extract_stats()
{
$LKP_SRC/stats/wrapper boot-slabinfo
$LKP_SRC/stats/wrapper boot-meminfo
$LKP_SRC/stats/wrapper memmap
$LKP_SRC/stats/wrapper boot-memory
$LKP_SRC/stats/wrapper boot-time
$LKP_SRC/stats/wrapper kernel-size
$LKP_SRC/stats/wrapper kmsg
$LKP_SRC/stats/wrapper time sleep.time
$LKP_SRC/stats/wrapper time
$LKP_SRC/stats/wrapper dmesg
$LKP_SRC/stats/wrapper kmsg
$LKP_SRC/stats/wrapper stderr
$LKP_SRC/stats/wrapper last_state
}
"$@"
Jonathan Woithe
maintainerRe: [lkp-robot] [platform/x86] b925ff7dcd: BUG:unable_to_handle_kernel
Michael
Quoted 10 lines · kernel test robot
FYI, we noticed the following commit:
commit:
b925ff7dcd1fc45b86baaebd3442f8b484123716("platform/x86: fujitsu-laptop: only register backlight device if FUJ02B1 is present")
url: https://github.com/0day-ci/linux/commits/Micha-K-pie/fujitsu-laptop-renames-and-cleanups/20170209-030748
base:git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.gitfor-nextin testcase: boot
on test machine: qemu-system-i386 -enable-kvm -cpu Haswell,+smep,+smap -m 360M
Quoted 7 lines
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
:[ 4.656202] fujitsu_laptop: call_fext_func: FUNC interface is not present [ 4.657478] BUG: unable to handle kernel NULL pointer dereference at 00000008 [ 4.658433] IP: fujitsu_init+0x137/0x1b7 [ 4.659208] *pdpt = 0000000000000000 *pde = f000ff53f000ff53:
I'm away from my Fujitsu hardware right now, and in any case this does not get triggered on it.
I note that prior to the bug we get "FUNC interface is not present". Therefore something called call_fext_func() some time before the NULL pointer dereference. As far as I can tell the only such call which could be made prior to or within fujitsu_init() is from fujitsu_init(), but this is conditional on acpi_video_get_backlight_type() returning acpi_backlight_vendor (line 1269). Obviously if this conditional were passed but fujitsu_bl->bl_device were NULL then we would get the NULL dereference.
If ACPI_FUJITSU_LAPTOP_HID is not present then presumedly the
acpi_bus_register_driver(&acpi_fujitsu_bl_driver)
call in fujitsu_init() will fail and nothing further would happen. Therefore this HID must be in the system.
However, the acpi_fujitsu_bl_add() callback wouldn't necessarily get run by acpi_bus_register_driver(), would it? I'm not too familiar with the lower level ACPI functions but a quick trip through the source suggested that the add callback isn't called via acpi_bus_register_driver(). This would mean that that fujitsu_bl->bl_device would not yet be initialised when referenced within fujitsu_init() at line 1271 or 1273. If this were the case then I see two options:
1) Don't move the backlight registration out of fujitsu_init().
2) Move the remaining backlight code (lines 1268-1274) into
acpi_fujitsu_bl_add().
Item 1 effectively amounts to dropping this commit. I'm not sure option 2 is workable because of the code's reliance on FUJ02E3; is that guaranteed to be useable by the time acpi_fujitsu_bl_add() is called?
The only problem with the above theory is that it doesn't explain why the NULL pointer dereference wasn't triggered on my Fujitsu hardware when this code was tested on it. If the ACPI bus probed/added asynchronously I guess there could be a race whereby acpi_fujitsu_bl_add() may or may not have completed by the time fujitsu_init() referenced fujitsu_bl->bl_device. That doesn't seem right to me though.
Regards
jonathan
Re: [lkp-robot] [platform/x86] b925ff7dcd: BUG:unable_to_handle_kernel
Quoted 24 lines
Michael
Quoted 10 lines · kernel test robot
FYI, we noticed the following commit:
commit:
b925ff7dcd1fc45b86baaebd3442f8b484123716("platform/x86: fujitsu-laptop: only register backlight device if FUJ02B1 is present")
url: https://github.com/0day-ci/linux/commits/Micha-K-pie/fujitsu-laptop-renames-and-cleanups/20170209-030748
base:git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.gitfor-nextin testcase: boot
on test machine: qemu-system-i386 -enable-kvm -cpu Haswell,+smep,+smap -m 360M
Quoted 7 lines
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
:[ 4.656202] fujitsu_laptop: call_fext_func: FUNC interface is not present [ 4.657478] BUG: unable to handle kernel NULL pointer dereference at 00000008 [ 4.658433] IP: fujitsu_init+0x137/0x1b7 [ 4.659208] *pdpt = 0000000000000000 *pde = f000ff53f000ff53:
I'm away from my Fujitsu hardware right now, and in any case this does not get triggered on it.
Quoted 8 lines
I note that prior to the bug we get "FUNC interface is not present". Therefore something called
call_fext_func()some time before the NULL pointer dereference. As far as I can tell the only such call which could be made prior to or withinfujitsu_init()is fromfujitsu_init(), but this is conditional onacpi_video_get_backlight_type()returningacpi_backlight_vendor(line 1269). Obviously if this conditional were passed butfujitsu_bl->bl_devicewere NULL then we would get the NULL dereference.
Yes, this is exactly what is happening.
Quoted 2 lines
If
ACPI_FUJITSU_LAPTOP_HID
I think you meant ACPI_FUJITSU_BL_HID.
Quoted 6 lines
is not present then presumedly the
acpi_bus_register_driver(&acpi_fujitsu_bl_driver)call in
fujitsu_init()will fail and nothing further would happen. Therefore this HID must be in the system.
Not really. acpi_bus_register_driver() is just a wrapper around driver_register(). In other words, whether or not a given HID is present in the firmware does not have any influence on the return code of that function.
In fact, the bug only happens when ACPI_FUJITSU_BL_HID is _not_ present. Or, putting it differently, on all Skylake machines (when acpi_backlight=vendor). Once again I am really glad the kernel test robot is there to counter my carelessness...
Quoted 9 lines
However, the
acpi_fujitsu_bl_add()callback wouldn't necessarily get run byacpi_bus_register_driver(), would it? I'm not too familiar with the lower level ACPI functions but a quick trip through the source suggested that the add callback isn't called viaacpi_bus_register_driver(). This would mean that thatfujitsu_bl->bl_devicewould not yet be initialised when referenced withinfujitsu_init()at line 1271 or 1273. If this were the case then I see two options:
Quoted 8 lines
1) Don't move the backlight registration out of
fujitsu_init().2) Move the remaining backlight code (lines 1268-1274) into
acpi_fujitsu_bl_add().Item 1 effectively amounts to dropping this commit. I'm not sure option 2 is workable because of the code's reliance on FUJ02E3; is that guaranteed to be useable by the time
acpi_fujitsu_bl_add()is called?
To keep things simple, I think we should drop this particular patch for now. Darren, Andy, could you skip it when applying this series? Patches 9 and 10 do not rely on this one being applied. Thanks and sorry for the trouble. v2 of my fujitsu_init() cleanup series will fix this properly.
Quoted 4 lines
The only problem with the above theory is that it doesn't explain why the NULL pointer dereference wasn't triggered on my Fujitsu hardware when this code was tested on it.
Because the bug is not triggered as long as FUJ02B1 is present.
Quoted 4 lines
If the ACPI bus probed/added asynchronously I guess
there could be a race wherebyacpi_fujitsu_bl_add()may or may not have completed by the timefujitsu_init()referencedfujitsu_bl->bl_device. That doesn't seem right to me though.
When acpi_bus_register_driver() is called, the .add callback is "synchronously" called for all ACPI devices handled by the registered driver that are yet unbound to any driver. So if FUJ02B1 is present, acpi_fujitsu_bl_add() is called and bl_device is allocated. However, if that ACPI device is not present (like on Skylakes) and acpi_backlight=vendor, we get a NULL dereference.
Signature · 2 lines
Best regards, Michał Kępień
Jonathan Woithe
maintainerRe: [lkp-robot] [platform/x86] b925ff7dcd: BUG:unable_to_handle_kernel
Quoted 18 lines · Micha?? K??pie??
Quoted 11 lines · kernel test robot
Quoted 10 lines
FYI, we noticed the following commit:
commit:
b925ff7dcd1fc45b86baaebd3442f8b484123716("platform/x86: fujitsu-laptop: only register backlight device if FUJ02B1 is present")
url: https://github.com/0day-ci/linux/commits/Micha-K-pie/fujitsu-laptop-renames-and-cleanups/20170209-030748
base:git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.gitfor-nextin testcase: boot
on test machine: qemu-system-i386 -enable-kvm -cpu Haswell,+smep,+smap -m 360M
Quoted 7 lines
Quoted 7 lines
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
:[ 4.656202] fujitsu_laptop: call_fext_func: FUNC interface is not present [ 4.657478] BUG: unable to handle kernel NULL pointer dereference at 00000008 [ 4.658433] IP: fujitsu_init+0x137/0x1b7 [ 4.659208] *pdpt = 0000000000000000 *pde = f000ff53f000ff53:
Quoted 4 lines
:
Quoted 1 line
If
ACPI_FUJITSU_LAPTOP_HIDI think you meant
ACPI_FUJITSU_BL_HID.
I did. Darn cut and paste.
Quoted 11 lines
Quoted 6 lines
is not present then presumedly the
acpi_bus_register_driver(&acpi_fujitsu_bl_driver)call in
fujitsu_init()will fail and nothing further would happen. Therefore this HID must be in the system.Not really.
acpi_bus_register_driver()is just a wrapper arounddriver_register().
In other words, whether or not a given HID is present in the firmware does not have any influence on the return code of that function.
Yes, I saw that much but erroneously assumed there was an indication of device presence in the return value. Thanks for putting me right on this.
Quoted 17 lines
Quoted 8 lines
However, the
acpi_fujitsu_bl_add()callback wouldn't necessarily get run byacpi_bus_register_driver(), would it? I'm not too familiar with the lower level ACPI functions but a quick trip through the source suggested that the add callback isn't called viaacpi_bus_register_driver(). This would mean that thatfujitsu_bl->bl_devicewould not yet be initialised when referenced withinfujitsu_init()at line 1271 or 1273. If this were the case then I see two options:Quoted 8 lines
1) Don't move the backlight registration out of
fujitsu_init().2) Move the remaining backlight code (lines 1268-1274) into
acpi_fujitsu_bl_add().Item 1 effectively amounts to dropping this commit. I'm not sure option 2 is workable because of the code's reliance on FUJ02E3; is that guaranteed to be useable by the time
acpi_fujitsu_bl_add()is called?
Quoted 5 lines
To keep things simple, I think we should drop this particular patch for now. Darren, Andy, could you skip it when applying this series? Patches 9 and 10 do not rely on this one being applied. Thanks and sorry for the trouble. v2 of my
fujitsu_init()cleanup series will fix this properly.
We could just add a test for NULL on fujitsu_bl->bl_device in fujitsu_init(), couldn't we? However, if you are planning to make further structural changes to fujitsu_init() in the upcoming patch series then I agree that messing around with this now is kind of pointless. In this case, skipping this single patch is fine.
Quoted 8 lines
Quoted 4 lines
If the ACPI bus probed/added asynchronously I guess
there could be a race wherebyacpi_fujitsu_bl_add()may or may not have completed by the timefujitsu_init()referencedfujitsu_bl->bl_device. That doesn't seem right to me though.When
acpi_bus_register_driver()is called, the .add callback is "synchronously" called for all ACPI devices handled by the registered driver that are yet unbound to any driver.
That's what I first thought would be the case, but I couldn't find how the add method was called by register_driver(). I therefore thought it must be triggered at some later stage (although an async mechanism seemed a bit out there). Clearly there's an indirect mechanism that I missed.
Quoted 4 lines
So if FUJ02B1 is present,
acpi_fujitsu_bl_add()is called andbl_deviceis allocated. However, if that ACPI device is not present (like on Skylakes) and acpi_backlight=vendor, we get a NULL dereference.
Yes, that makes sense in light of the fact that acpi_bus_register_driver() can cause acpi_fujitsu_bl_add() to be called.
Regards
jonathan
PATCH 9/10 platform/x86: fujitsu-laptop: autodetect LCD interface on all models
In reply to Michał KępieńFrom: Alan Jenkins <[email protected]>
Presence of ACPI method SBL2 should be checked on all models rather than just the ones with predefined hotkey keycode overrides. Move most of dmi_check_cb_common() to acpi_fujitsu_bl_add(). Adjust indentation to make checkpatch happy.
--- drivers/platform/x86/fujitsu-laptop.c | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-)
drivers/platform/x86/fujitsu-laptop.c +9 -9
@@ -631,15 +631,6 @@ static struct platform_driver fujitsu_pf_driver = {static void __init dmi_check_cb_common (const struct dmi_system_id *id) {pr_info ("Identified laptop model '%s'\n" , id->ident); -if (use_alt_lcd_levels ==-1 ) { -if (acpi_has_method (NULL , -"\\_SB.PCI0.LPCB.FJEX.SBL2" )) - use_alt_lcd_levels =1 ; -else - use_alt_lcd_levels =0 ; -vdbg_printk (FUJLAPTOP_DBG_TRACE ,"auto-detected usealt as " -"%i\n" , use_alt_lcd_levels); - } }static int __init dmi_check_cb_s6410 (const struct dmi_system_id *id)
@@ -751,6 +742,15 @@ static int acpi_fujitsu_bl_add(struct acpi_device *device)pr_err ("_INI Method failed\n" ); } +if (use_alt_lcd_levels ==-1 ) { +if (acpi_has_method (NULL ,"\\_SB.PCI0.LPCB.FJEX.SBL2" )) + use_alt_lcd_levels =1 ; +else + use_alt_lcd_levels =0 ; +vdbg_printk (FUJLAPTOP_DBG_TRACE ,"auto-detected usealt as %i\n" , + use_alt_lcd_levels); + } +/* do config (detect defaults) */ use_alt_lcd_levels = use_alt_lcd_levels ==1 ?1 :0 ; disable_brightness_adjust = disable_brightness_adjust ==1 ?1 :0 ;
Signature · 1 line
2.11.1
PATCH 10/10 platform/x86: fujitsu-laptop: remove redundant MODULE_ALIAS entries
In reply to Michał KępieńFrom: Alan Jenkins <[email protected]>
MODULE_DEVICE_TABLE is all that is needed for fujitsu-laptop to be properly autoloaded based on presence of its associated ACPI devices, so remove redundant MODULE_ALIAS entries.
--- drivers/platform/x86/fujitsu-laptop.c | 4 ---- 1 file changed, 4 deletions(-)
drivers/platform/x86/fujitsu-laptop.c +0 -4
@@ -1333,7 +1333,3 @@ MODULE_AUTHOR("Jonathan Woithe, Peter Gruber, Tony Vroon");MODULE_DESCRIPTION ("Fujitsu laptop extras support" );MODULE_VERSION (FUJITSU_DRIVER_VERSION );MODULE_LICENSE ("GPL" ); - -MODULE_ALIAS ("dmi:*:svnFUJITSUSIEMENS:*:pvr:rvnFUJITSU:rnFJNB1D3:*:cvrS6410:*" ); -MODULE_ALIAS ("dmi:*:svnFUJITSUSIEMENS:*:pvr:rvnFUJITSU:rnFJNB1E6:*:cvrS6420:*" ); -MODULE_ALIAS ("dmi:*:svnFUJITSU:*:pvr:rvnFUJITSU:rnFJNB19C:*:cvrS7020:*" );
Signature · 1 line
2.11.1
Quoted 121 lines · Michał Kępień
This series of patches was originally submitted by Alan Jenkins in September 2009. For various reasons they were never acted upon before. Sadly, their original state makes them unreviewable due to multiple changes happening within one patch and unreliable commit messages.
In order for Alan's efforts not to go to waste, I have rebased his patches on top of dvhart/for-next, further split them into logically separate changes and rewrote commit messages from scratch, based on the assumed intent of the original author.
Here is how the original patches map to the rebased and split patches:
1/4 -> 1-6/10 2/4 -> 7-8/10 3/4 -> 9/10 4/4 -> 10/10Some of these patches raise checkpatch warnings. This is intentional, in order to make renames clean and easy to review. All of these issues will be fixed by upcoming patch series.
Not all ideas suggested by Alan are present in the rebased series. A brief discussion of each rejected suggestion follows (most important issues first).
- Restructure
fujitsu_init(). Quite frankly, I am pretty sure Alan did not test his series on Fujitsu hardware with a logo lamp and/or keyboard lamps. Neither have I, but with his original patches applied, what happens on such a model is:1.
fujitsu_init()callsacpi_bus_register_driver().
2.acpi_fujitsu_laptop_add()is called.
3.fujitsu_laptopis kzalloc()'ed.
4.fujitsu_laptop->pf_device->devis accessed.This results in a NULL dereference, because the platform device is only allocated and registered later in
fujitsu_init().On the other hand, registering the platform device before the ACPI driver is also incorrect due to reasons I already pointed out in another thread (in short: we cannot _assume_ FUJ02E3 is present). This can only be fixed properly by registering the platform device inside
acpi_fujitsu_laptop_add(), but I am still waiting for comments from Darren and Andy in the other thread before moving forward down this path.- Bail out when FUJ02B1 is not present. It could have been deemed correct back in the day, but we now know that Fujitsu started shipping devices without that ACPI device present, though with FUJ02E3 still in place. These two ACPI devices are independent and thus should not rely on each other's presence.
- Move keycode[1-5] fields to struct
fujitsu_laptop. Doing this causes ordering issues insidefujitsu_init(), while a patch series I have queued that makes fujitsu-laptop use a sparse keymap removes these fields altogether.- Allocate and free
fujitsu_blandfujitsu_laptopinside ACPI callbacks. While elegant and correct, this also causes ordering issues insidefujitsu_init()and can only be done once platform device registration is properly fixed.- Sync backlight power status in
acpi_fujitsu_bl_add(). The long-term objective for fujitsu-laptop should be to achieve a clean split between the backlight-related part and the laptop-related part. This change keeps both parts intertwined. Myfujitsu_init()cleanup series contains a similar fix, but I have since found a different solution to this problem which I will post once Alan's rebased series gets applied.- Remove
dmi_check_cb_common(). The sparse keymap series I have queued gets rid of this function without introducing an additional field inside structfujitsu_laptop.Moreover, some other minor changes present in original patch 1/4 were left out. A brief discussion of each such case follows.
(quoted diff) +1
-1-#define ACPI_FUJITSU_BL_NOTIFY_CODE1 0x80 +#define ACPI_FUJITSU_NOTIFY_CODE1 0x80Notify code
0x80is used by both parts of the driver (the brightness-related one and the laptop-related one) and thus it should not be annotated using the "_BL" infix specific to brightness-related code.(quoted diff) +0
-2-#if defined(CONFIG_LEDS_CLASS) || defined(CONFIG_LEDS_CLASS_MODULE) -#endifThis does not really bring any benefit while breaking consistency with other parts of the driver.
(quoted diff) +1
-1- dmi_check_system(fujitsu_laptop_dmi_table); + dmi_check_system(fujitsu_dmi_table);The original patches moved this
dmi_check_system()call toacpi_fujitsu_laptop_add(), which justifies renamingfujitsu_dmi_tabletofujitsu_laptop_dmi_table. However, for reasons discussed above, the rebased patches leave thedmi_check_system()call insidefujitsu_init(), thus making the rename dubious.(quoted diff) +1
-1- DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU SIEMENS"), + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU_LAPTOP SIEMENS"),There are multiple changes like this in original patch 1/4. They are obviously wrong and were probably introduced by an unreviewed automatic replacement.
(quoted diff) +0
-1@@ -495,7 +495,6 @@ static ssize_t show_max_brightness(struct device *dev, struct device_attribute *attr, char *buf) { - int ret;There are four instances of such a removal in original patch 1/4. They are obviously correct, though they all happen inside functions related to platform device attributes which I hope will soon get removed altogether. Thus I refrained from applying these to reduce churn (at least a bit).
Quoted 9 lines
Finally, some of the changes suggested by Alan were already applied along the way:
-
kmalloc()+memset()occurences were changed tokzalloc()by commit6c75dd0f965b ("drivers/platform/x86: Use kzalloc").- Unused debug macros were removed by commit
00816e1b3839("fujitsu-laptop: Remove unused macros").
Nice clean up!
So, I would apply 1-7, for the rest I need more time to review.
Regarding ACPI case and device presents you may assume it if you just call acpi_walk_namespace() (AFAIU) and check _STA for the device if it's in the table.
So, at any point you may have got understanding if device is present or not, and if it's active or not.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Quoted 1 line · Andy Shevchenko
On Wed, Feb 8, 2017 at 3:46 PM, Michał Kępień <[email protected]> wrote:
...
Quoted 3 lines
Nice clean up!
So, I would apply 1-7, for the rest I need more time to review.
As a point of policy for this tree. If the patches touch a file with a driver maintainer listed in MAINTAINERS, we need to make sure they are Cc'd and give them an opportunity to review before we commit them to the queue. In this case, Jonathan Woithe.
Jonathan has committed to review in the next couple of days, so lets please give him first say on the patches.
Thanks,
Signature · 2 lines
Darren Hart Intel Open Source Technology Center
Quoted 10 lines · Darren Hart
Quoted 4 lines · Andy Shevchenko
On Wed, Feb 8, 2017 at 3:46 PM, Michał Kępień <[email protected]> wrote:
Nice clean up!
So, I would apply 1-7, for the rest I need more time to review.As a point of policy for this tree. If the patches touch a file with a driver maintainer listed in
MAINTAINERS, we need to make sure they are Cc'd and give them an opportunity to review before we commit them to the queue. In this case, Jonathan Woithe.
Good point!
Quoted 2 lines
Jonathan has committed to review in the next couple of days, so lets please give him first say on the patches.
Indeed, I'm not going to push this to for-next.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Quoted 6 lines
Regarding ACPI case and device presents you may assume it if you just call
acpi_walk_namespace()(AFAIU) and check_STAfor the device if it's in the table.So, at any point you may have got understanding if device is present or not, and if it's active or not.
Thank you for the tip, though I am a bit confused, sorry. I infer the above is a response to this part of my message:
Quoted 3 lines
Quoted 3 lines
On the other hand, registering the platform device before the ACPI driver is also incorrect due to reasons I already pointed out in another thread (in short: we cannot _assume_ FUJ02E3 is present).
Perhaps my wording was inaccurate, but I do not have a technical problem with detecting an ACPI device. Instead, this passage was meant to be a reference to the fourth paragraph of my cover letter for the series titled "fujitsu_init() cleanup", i.e. the lengthy one awaiting comments from you and/or Darren. For your convenience, here is the paragraph in question (roughly the second half is relevant):
Quoted 10 lines
That would leave us with the remaining three sysfs attributes of the platform device, namely dock, lid and radios. These all depend on the FUJ02E3 ACPI device. Which begs the question: shall we reassign them to that ACPI device and drop the platform device altogether? This would logically be the correct thing to do (panasonic-laptop and
toshiba_acpialready assign extra sysfs attributes to ACPI nodes). But I understand that this would break an 8-year-old userspace interface as functions previously exposed through/sys/devices/platform/fujitsu-laptopwould be moved to/sys/bus/acpi/devices/FUJ02E3:00. If that is unacceptable, the least we can (and should) do is to move platform device registration to
Quoted 8 lines
acpi_fujitsu_hotkey_add(). What the driver currently does may create confusion in the future, because the platform device is registered unconditionally while it clearly depends on FUJ02E3 being present. I do not know whether FUJ02E3 is present on all Fujitsu devices today without exception, but I do know that if Fujitsu ever decides to drop that device from its firmware, we would again (see above) expose a userspace interface (dock, lid, radios) which simply will not be able to function properly.
Perhaps things will become a bit more clear once you dig through that thread :)
Signature · 2 lines
Best regards, Michał Kępień
Jonathan Woithe
maintainerHi Michael
Thanks very much for the work you've put in to clean up these patches. I very much appreciate it. I will go through them myself in the next day or so, and most importantly test them on my hardware to confirm there are no regressions. Some initial comments follow.
Quoted 2 lines · Micha?? K??pie??
Some of these patches raise checkpatch warnings. This is intentional, in order to make renames clean and easy to review.
For what it's worth, I was also planning to go through and fix the checkpatch warnings in this driver, but held off until the issues raised by Alan's patches were addressed (essentially to make it easier to apply those old patches. If you are planning on doing this then I won't start it. :-)
On to the ommitted changes from Alan's orginal patch series.
Quoted 3 lines
- Restructure
fujitsu_init(). Quite frankly, I am pretty sure Alan did not test his series on Fujitsu hardware with a logo lamp and/or keyboard lamps.
Back in 2009 I don't think there were many models with these features. This observation is therefore quite possible. I'm more than happy to leave fujitsu_init()'s structure as is, especially given that related issues will be addressed in your furture patch series.
Quoted 5 lines
- Bail out when FUJ02B1 is not present. It could have been deemed correct back in the day, but we now know that Fujitsu started shipping devices without that ACPI device present, though with FUJ02E3 still in place. These two ACPI devices are independent and thus should not rely on each other's presence.
Agreed. You are right, in 2009 I think it seemed like a good idea but it's clearly no longer valid.
Quoted 4 lines
- Move keycode[1-5] fields to struct
fujitsu_laptop. Doing this causes ordering issues insidefujitsu_init(), while a patch series I have queued that makes fujitsu-laptop use a sparse keymap removes these fields altogether.
This makes sense.
Quoted 4 lines
- Allocate and free
fujitsu_blandfujitsu_laptopinside ACPI callbacks. While elegant and correct, this also causes ordering issues insidefujitsu_init()and can only be done once platform device registration is properly fixed.
Agreed.
Quoted 7 lines
- Sync backlight power status in
acpi_fujitsu_bl_add(). The long-term objective for fujitsu-laptop should be to achieve a clean split between the backlight-related part and the laptop-related part. This change keeps both parts intertwined. Myfujitsu_init()cleanup series contains a similar fix, but I have since found a different solution to this problem which I will post once Alan's rebased series gets applied.
I'm happy to wait to see this alternative solution. In the meantime, keeping the two parts independent is a good idea.
Quoted 3 lines
- Remove
dmi_check_cb_common(). The sparse keymap series I have queued gets rid of this function without introducing an additional field inside structfujitsu_laptop.
Ok.
Quoted 10 lines
Moreover, some other minor changes present in original patch 1/4 were left out. A brief discussion of each such case follows.
(quoted diff) +1
-1-#define ACPI_FUJITSU_BL_NOTIFY_CODE1 0x80 +#define ACPI_FUJITSU_NOTIFY_CODE1 0x80Notify code
0x80is used by both parts of the driver (the brightness-related one and the laptop-related one) and thus it should not be annotated using the "_BL" infix specific to brightness-related code.
Agreed. Perhaps back in the day it was thought that it did only apply to the backlight but with the benefit of hindsight this is clearly not the case.
Quoted 6 lines
(quoted diff) +0
-2-#if defined(CONFIG_LEDS_CLASS) || defined(CONFIG_LEDS_CLASS_MODULE) -#endifThis does not really bring any benefit while breaking consistency with other parts of the driver.
Fair enough.
Quoted 9 lines
(quoted diff) +1
-1- dmi_check_system(fujitsu_laptop_dmi_table); + dmi_check_system(fujitsu_dmi_table);The original patches moved this
dmi_check_system()call toacpi_fujitsu_laptop_add(), which justifies renamingfujitsu_dmi_tabletofujitsu_laptop_dmi_table. However, for reasons discussed above, the rebased patches leave thedmi_check_system()call insidefujitsu_init(), thus making the rename dubious.
Agreed. In light of the reasons given this makes no sense.
Quoted 6 lines
(quoted diff) +1
-1- DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU SIEMENS"), + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU_LAPTOP SIEMENS"),There are multiple changes like this in original patch 1/4. They are obviously wrong and were probably introduced by an unreviewed automatic replacement.
I noticed this myself; they are clearly incorrect and have the hallmarks of a global search/replace operation. They were omitted in the initial RFC series I sent through for this reason.
[Blank line removal]
Quoted 5 lines
There are four instances of such a removal in original patch 1/4. They are obviously correct, though they all happen inside functions related to platform device attributes which I hope will soon get removed altogether. Thus I refrained from applying these to reduce churn (at least a bit).
I'm happy with that. The future checkpatch cleanup series could address these if they are deemed important enough.
Quoted 8 lines
Finally, some of the changes suggested by Alan were already applied along the way:
-
kmalloc()+memset()occurences were changed tokzalloc()by commit6c75dd0f965b ("drivers/platform/x86: Use kzalloc").- Unused debug macros were removed by commit
00816e1b3839("fujitsu-laptop: Remove unused macros").
The entire debug structure has been revised since Alan's original patch was made, making most if not all of the debug changes unnecessary.
My ack will follow once I've tested this series on my hardware. I will try to get to this in the next 24 hours.
Regards
jonathan
Quoted 6 lines
Hi Michael
Thanks very much for the work you've put in to clean up these patches. I very much appreciate it. I will go through them myself in the next day or so, and most importantly test them on my hardware to confirm there are no regressions.
Thanks! I did my best to keep track of everything, but something surely could have slipped through, given the number of changes Alan's patches introduce.
Quoted 10 lines
Some initial comments follow.
Quoted 2 lines · Micha?? K??pie??
Some of these patches raise checkpatch warnings. This is intentional, in order to make renames clean and easy to review.
For what it's worth, I was also planning to go through and fix the checkpatch warnings in this driver, but held off until the issues raised by Alan's patches were addressed (essentially to make it easier to apply those old patches. If you are planning on doing this then I won't start it. :-)
I have a few draft patch series prepared that contain "real" cleanups and incidentally also lower the total count of checkpatch issues in the driver from ~70 to ~20 (ballpark figures). I think it is way better to fix as many checkpatch issues as possible while also fixing actual code and then iron out the leftovers than to first generate a lot of churn which fixes spaces and newlines and then fix the code anyway. So yeah, I would hold off pure checkpatch fixes until the more pressing matters get sorted out.
Quoted 11 lines
On to the ommitted changes from Alan's orginal patch series.
Quoted 3 lines
- Restructure
fujitsu_init(). Quite frankly, I am pretty sure Alan did not test his series on Fujitsu hardware with a logo lamp and/or keyboard lamps.Back in 2009 I don't think there were many models with these features. This observation is therefore quite possible. I'm more than happy to leave fujitsu_init()'s structure as is, especially given that related issues will be addressed in your furture patch series.
Yes, they will. How these fixes will exactly look depends on the feedback I get from Darren and Andy.
Quoted 89 lines
Quoted 6 lines
- Bail out when FUJ02B1 is not present. It could have been deemed correct back in the day, but we now know that Fujitsu started shipping devices without that ACPI device present, though with FUJ02E3 still in place. These two ACPI devices are independent and thus should not rely on each other's presence.
Agreed. You are right, in 2009 I think it seemed like a good idea but it's clearly no longer valid.
Quoted 4 lines
- Move keycode[1-5] fields to struct
fujitsu_laptop. Doing this causes ordering issues insidefujitsu_init(), while a patch series I have queued that makes fujitsu-laptop use a sparse keymap removes these fields altogether.This makes sense.
Quoted 4 lines
- Allocate and free
fujitsu_blandfujitsu_laptopinside ACPI callbacks. While elegant and correct, this also causes ordering issues insidefujitsu_init()and can only be done once platform device registration is properly fixed.Agreed.
Quoted 7 lines
- Sync backlight power status in
acpi_fujitsu_bl_add(). The long-term objective for fujitsu-laptop should be to achieve a clean split between the backlight-related part and the laptop-related part. This change keeps both parts intertwined. Myfujitsu_init()cleanup series contains a similar fix, but I have since found a different solution to this problem which I will post once Alan's rebased series gets applied.I'm happy to wait to see this alternative solution. In the meantime, keeping the two parts independent is a good idea.
Quoted 3 lines
- Remove
dmi_check_cb_common(). The sparse keymap series I have queued gets rid of this function without introducing an additional field inside structfujitsu_laptop.Ok.
Quoted 10 lines
Moreover, some other minor changes present in original patch 1/4 were left out. A brief discussion of each such case follows.
(quoted diff) +1
-1-#define ACPI_FUJITSU_BL_NOTIFY_CODE1 0x80 +#define ACPI_FUJITSU_NOTIFY_CODE1 0x80Notify code
0x80is used by both parts of the driver (the brightness-related one and the laptop-related one) and thus it should not be annotated using the "_BL" infix specific to brightness-related code.Agreed. Perhaps back in the day it was thought that it did only apply to the backlight but with the benefit of hindsight this is clearly not the case.
Quoted 6 lines
(quoted diff) +0
-2-#if defined(CONFIG_LEDS_CLASS) || defined(CONFIG_LEDS_CLASS_MODULE) -#endifThis does not really bring any benefit while breaking consistency with other parts of the driver.
Fair enough.
Quoted 9 lines
(quoted diff) +1
-1- dmi_check_system(fujitsu_laptop_dmi_table); + dmi_check_system(fujitsu_dmi_table);The original patches moved this
dmi_check_system()call toacpi_fujitsu_laptop_add(), which justifies renamingfujitsu_dmi_tabletofujitsu_laptop_dmi_table. However, for reasons discussed above, the rebased patches leave thedmi_check_system()call insidefujitsu_init(), thus making the rename dubious.Agreed. In light of the reasons given this makes no sense.
Quoted 6 lines
(quoted diff) +1
-1- DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU SIEMENS"), + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU_LAPTOP SIEMENS"),There are multiple changes like this in original patch 1/4. They are obviously wrong and were probably introduced by an unreviewed automatic replacement.
I noticed this myself; they are clearly incorrect and have the hallmarks of a global search/replace operation. They were omitted in the initial RFC series I sent through for this reason.
[Blank line removal]
Quoted 8 lines
Quoted 5 lines
There are four instances of such a removal in original patch 1/4. They are obviously correct, though they all happen inside functions related to platform device attributes which I hope will soon get removed altogether. Thus I refrained from applying these to reduce churn (at least a bit).
I'm happy with that. The future checkpatch cleanup series could address these if they are deemed important enough.
Yes, I have this specific cleanup queued in a branch containing miscellaneous fixes anyway, so it should not get lost in the noise.
Quoted 7 lines
Quoted 7 lines
Finally, some of the changes suggested by Alan were already applied along the way:
-
kmalloc()+memset()occurences were changed tokzalloc()by commit6c75dd0f965b ("drivers/platform/x86: Use kzalloc").
Quoted 8 lines
Quoted 2 lines
- Unused debug macros were removed by commit
00816e1b3839("fujitsu-laptop: Remove unused macros").The entire debug structure has been revised since Alan's original patch was made, making most if not all of the debug changes unnecessary.
My ack will follow once I've tested this series on my hardware. I will try to get to this in the next 24 hours.
Great, thanks!
Signature · 2 lines
Best regards, Michał Kępień
Jonathan Woithe
maintainerQuoted 2 lines · Micha?? K??pie??
This series of patches was originally submitted by Alan Jenkins in September 2009. ...
I have applied and tested this patch series on an S7020. Being an older model (and the one the driver was originally targetting) means that many driver functions cannot be tested because the respective hardware isn't present. However, the driver was correctly loaded and the backlight controls continue to work as they should. That is, I see no regressions on the S7020 hardware.
Patches 1-6 are essentially renames to tidy up the naming convention used throughout the driver. The original names date to the first implementation which targeted more limited hardware than what we have now, hence the need to generalise some of the fields, structure names and so on with the benefit of hindsight.
Patch 7: I agree with this approach. There's no need to clobber the actual error code from acpi_bus_register_driver().
Patch 8: Good. I can confirm that the backlight device is correctly registered when FUJ02B1 is present. I couldn't test the case where FUJ02B1 is not present because my hardware has the FUJ02B1 device, but can see no reason why it won't work as described.
Patch 9: I think the original reasoning was that SBL2 was only ever seen on laptops which required the hotkey keycode overrides. However, testing for SBL2 across all models should not change practical behaviour. It also breaks the somewhat arbitrary dependency between SBL2 and the need for overrides which may not hold true for future hardware.
Patch 10: Agreed, there is no longer a need for these MODULE_ALIAS entries.
In summary, I see no issues with this patch series which provides a much needed clean up of the code and naming conventions within the fujitsu-laptop driver. I'm happy for this series (patches 1-10/10) to be applied.
Regards
jonathan
Quoted 7 lines · Jonathan Woithe
On Wed, Feb 08, 2017 at 02:46:23PM +0100, Micha?? K??pie?? wrote:
In summary, I see no issues with this patch series which provides a much needed clean up of the code and naming conventions within the fujitsu-laptop driver. I'm happy for this series (patches 1-10/10) to be applied.
Signed-off-by Jonathan Woithe <[email protected]>
I have noticed people start using SoB for the code they are maintaining w/o sending any pull requests.
It is okay, but there is, as Wolfram pointed, a downside for patchwork users. Patchwork is tracking tags (A/R/T) which by a glance allows to see what patches are acked/reviewed/tested.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Quoted 7 lines · Andy Shevchenko
Quoted 6 lines · Jonathan Woithe
On Wed, Feb 08, 2017 at 02:46:23PM +0100, Micha?? K??pie?? wrote:
In summary, I see no issues with this patch series which provides a much needed clean up of the code and naming conventions within the fujitsu-laptop driver. I'm happy for this series (patches 1-10/10) to be applied.
Quoted 7 lines
Quoted 1 line
Signed-off-by Jonathan Woithe <[email protected]>I have noticed people start using SoB for the code they are maintaining w/o sending any pull requests.
It is okay, but there is, as Wolfram pointed, a downside for patchwork users. Patchwork is tracking tags (A/R/T) which by a glance allows to see what patches are acked/reviewed/tested.
Signed-off-by tracks the path the code takes from author to mainline. If you are not the author or committing it to a tree followed by a pull-request, the correct tag is "Reviewed-by".
Signature · 2 lines
Darren Hart Intel Open Source Technology Center
Jonathan Woithe
maintainerQuoted 16 lines · Darren Hart
Quoted 7 lines · Andy Shevchenko
Quoted 6 lines · Jonathan Woithe
On Wed, Feb 08, 2017 at 02:46:23PM +0100, Micha?? K??pie?? wrote:
In summary, I see no issues with this patch series which provides a much needed clean up of the code and naming conventions within the fujitsu-laptop driver. I'm happy for this series (patches 1-10/10) to be applied.
Quoted 7 lines
Quoted 1 line
Signed-off-by Jonathan Woithe <[email protected]>I have noticed people start using SoB for the code they are maintaining w/o sending any pull requests.
It is okay, but there is, as Wolfram pointed, a downside for patchwork users. Patchwork is tracking tags (A/R/T) which by a glance allows to see what patches are acked/reviewed/tested.
Quoted 3 lines
Signed-off-by tracks the path the code takes from author to mainline. If you are not the author or committing it to a tree followed by a pull-request, the correct tag is "Reviewed-by".
Yes, of course - I clearly had a brain fade back there. Having said that, in the past I've used "Acked-by" intead of "Reviewed-by".
Do you want me to continue to use Acked-by, or should I switch to Reviewed-by?
Regards
jonathan
Quoted 17 lines · Jonathan Woithe
Quoted 16 lines · Darren Hart
Quoted 14 lines · Andy Shevchenko
Quoted 7 lines · Jonathan Woithe
On Wed, Feb 08, 2017 at 02:46:23PM +0100, Micha?? K??pie?? wrote:
In summary, I see no issues with this patch series which provides a much needed clean up of the code and naming conventions within the fujitsu-laptop driver. I'm happy for this series (patches 1-10/10) to be applied.
Signed-off-by Jonathan Woithe <[email protected]>I have noticed people start using SoB for the code they are maintaining w/o sending any pull requests.
It is okay, but there is, as Wolfram pointed, a downside for patchwork users. Patchwork is tracking tags (A/R/T) which by a glance allows to see what patches are acked/reviewed/tested.
Quoted 6 lines
Quoted 3 lines
Signed-off-by tracks the path the code takes from author to mainline. If you are not the author or committing it to a tree followed by a pull-request, the correct tag is "Reviewed-by".
Yes, of course - I clearly had a brain fade back there. Having said that, in the past I've used "Acked-by" intead of "Reviewed-by".
:-)
Quoted 2 lines
Do you want me to continue to use Acked-by, or should I switch to Reviewed-by?
These tags do have different meanings, and have come up at Kernel Summit the last couple of years. My interpretation of those discussions is:
Acked-by: I have no objection to this patch, but I didn't really give it a thorough review. I trust your judgement. e.g. minor change to your driver to support a subsystem API change. These are of very little value.
Reviewed-by: I have carefully reviewed this patch and would like it to be applied. This should usually come with some sort of commentary describing the level of review or an area you focused on. This is what we would like to see from all of our driver maintainers. These are high value.
Linus *really* dislikes one line acked by's, and only *slightly* more so than one line reviewed by's. :-)
Thanks!
Signature · 2 lines
Darren Hart Intel Open Source Technology Center
Quoted 11 lines · Darren Hart
Quoted 2 lines · Jonathan Woithe
Do you want me to continue to use Acked-by, or should I switch to Reviewed-by?
These tags do have different meanings, and have come up at Kernel Summit the last couple of years. My interpretation of those discussions is:
Acked-by: I have no objection to this patch, but I didn't really give it a thorough review. I trust your judgement. e.g. minor change to your driver to support a subsystem API change. These are of very little value.
Quoted 7 lines
Reviewed-by: I have carefully reviewed this patch and would like it to be applied. This should usually come with some sort of commentary describing the level of review or an area you focused on. This is what we would like to see from all of our driver maintainers. These are high value.
Linus *really* dislikes one line acked by's, and only *slightly* more so than one line reviewed by's. :-)
Got it, thanks, this is very helpful.
In light of this I give you the following.
This patch series applies a much delayed patch series which implements a very useful clean up to the fujitsu-laptop driver. Among other things it tidies up naming conventions within the driver to better reflect the functionality and to be more consistent with the rest of the kernel. This will make future maintenance and feature additions much easier for all concerned.
As per subsequent discussion we have agreed to drop patch 8/10 from the
series: it creates problems on newer hardware and the issue it is addressing will be more completely dealt with in a subsequent patch series.
Regards
jonathan
Quoted 33 lines · Jonathan Woithe
Quoted 11 lines · Darren Hart
Quoted 2 lines · Jonathan Woithe
Do you want me to continue to use Acked-by, or should I switch to Reviewed-by?
These tags do have different meanings, and have come up at Kernel Summit the last couple of years. My interpretation of those discussions is:
Acked-by: I have no objection to this patch, but I didn't really give it a thorough review. I trust your judgement. e.g. minor change to your driver to support a subsystem API change. These are of very little value.
Quoted 7 lines
Reviewed-by: I have carefully reviewed this patch and would like it to be applied. This should usually come with some sort of commentary describing the level of review or an area you focused on. This is what we would like to see from all of our driver maintainers. These are high value.
Linus *really* dislikes one line acked by's, and only *slightly* more so than one line reviewed by's. :-)
Got it, thanks, this is very helpful.
In light of this I give you the following.
Reviewed-by Jonathan Woithe <[email protected]>This patch series applies a much delayed patch series which implements a very useful clean up to the fujitsu-laptop driver. Among other things it tidies up naming conventions within the driver to better reflect the functionality and to be more consistent with the rest of the kernel. This will make future maintenance and feature additions much easier for all concerned.
Quoted 3 lines
As per subsequent discussion we have agreed to drop patch 8/10 from the
series: it creates problems on newer hardware and the issue it is addressing will be more completely dealt with in a subsequent patch series.
Absolutely awesome :-) Thanks!
Quoted 4 lines
Regards
jonathan
Signature · 2 lines
Darren Hart Intel Open Source Technology Center
Quoted 17 lines · Jonathan Woithe
Quoted 16 lines · Darren Hart
Quoted 2 lines · Jonathan Woithe
Do you want me to continue to use Acked-by, or should I switch to Reviewed-by?
These tags do have different meanings, and have come up at Kernel Summit the last couple of years. My interpretation of those discussions is:
Acked-by: I have no objection to this patch, but I didn't really give it a thorough review. I trust your judgement. e.g. minor change to your driver to support a subsystem API change. These are of very little value.
Reviewed-by: I have carefully reviewed this patch and would like it to be applied. This should usually come with some sort of commentary describing the level of review or an area you focused on. This is what we would like to see from all of our driver maintainers. These are high value.
Quoted 8 lines
Quoted 2 lines
Linus *really* dislikes one line acked by's, and only *slightly* more so than one line reviewed by's. :-)
Got it, thanks, this is very helpful.
In light of this I give you the following.
Reviewed-by Jonathan Woithe <[email protected]>
Thanks, applied for testing with above tag.
Quoted 14 lines
This patch series applies a much delayed patch series which implements a very useful clean up to the fujitsu-laptop driver. Among other things it tidies up naming conventions within the driver to better reflect the functionality and to be more consistent with the rest of the kernel. This will make future maintenance and feature additions much easier for all concerned.
As per subsequent discussion we have agreed to drop patch 8/10 from the
series: it creates problems on newer hardware and the issue it is addressing will be more completely dealt with in a subsequent patch series.Regards
jonathan
Signature · 2 lines
With Best Regards, Andy Shevchenko
Quoted 21 lines · Jonathan Woithe
Quoted 20 lines · Darren Hart
Quoted 18 lines · Jonathan Woithe
Quoted 2 lines
Do you want me to continue to use Acked-by, or should I switch to Reviewed-by?
These tags do have different meanings, and have come up at Kernel Summit the last couple of years. My interpretation of those discussions is:
Acked-by: I have no objection to this patch, but I didn't really give it a thorough review. I trust your judgement. e.g. minor change to your driver to support a subsystem API change. These are of very little value.
Reviewed-by: I have carefully reviewed this patch and would like it to be applied. This should usually come with some sort of commentary describing the level of review or an area you focused on. This is what we would like to see from all of our driver maintainers. These are high value.
Linus *really* dislikes one line acked by's, and only *slightly* more so than one line reviewed by's. :-)
Quoted 7 lines
Quoted 5 lines
Got it, thanks, this is very helpful.
In light of this I give you the following.
Reviewed-by Jonathan Woithe <[email protected]>Thanks, applied for testing with above tag.
Andy,
It looks like you missed this part of Jonathan's message:
Quoted 3 lines
As per subsequent discussion we have agreed to drop patch 8/10 from the
series: it creates problems on newer hardware and the issue it is addressing will be more completely dealt with in a subsequent patch series.
I see that patch 8/10 was applied to testing as well. Could you please drop that single patch?
Thanks,
Signature · 2 lines
Best regards, Michał Kępień
Quoted 25 lines · Michał Kępień
Quoted 25 lines · Jonathan Woithe
Quoted 24 lines · Darren Hart
Quoted 11 lines · Jonathan Woithe
Quoted 2 lines
Do you want me to continue to use Acked-by, or should I switch to Reviewed-by?
These tags do have different meanings, and have come up at Kernel Summit the last couple of years. My interpretation of those discussions is:
Acked-by: I have no objection to this patch, but I didn't really give it a thorough review. I trust your judgement. e.g. minor change to your driver to support a subsystem API change. These are of very little value.
Quoted 7 lines
Reviewed-by: I have carefully reviewed this patch and would like it to be applied. This should usually come with some sort of commentary describing the level of review or an area you focused on. This is what we would like to see from all of our driver maintainers. These are high value.
Linus *really* dislikes one line acked by's, and only *slightly* more so than one line reviewed by's. :-)
Got it, thanks, this is very helpful.
In light of this I give you the following.
Quoted 7 lines
Quoted 3 lines
Quoted 1 line
Reviewed-by Jonathan Woithe <[email protected]>Thanks, applied for testing with above tag.
Andy,
It looks like you missed this part of Jonathan's message:
Indeed.
Quoted 7 lines
Quoted 4 lines
As per subsequent discussion we have agreed to drop patch 8/10 from the
series: it creates problems on newer hardware and the issue it is addressing will be more completely dealt with in a subsequent patch series.I see that patch 8/10 was applied to testing as well. Could you please drop that single patch?
Good we have testing branch and thank you for pointing out. Should be fixed now.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Quoted 37 lines · Jonathan Woithe
Quoted 17 lines · Darren Hart
Quoted 16 lines · Andy Shevchenko
Quoted 14 lines · Jonathan Woithe
Quoted 7 lines · Micha?? K??pie??
In summary, I see no issues with this patch series which provides a much needed clean up of the code and naming conventions within the fujitsu-laptop driver. I'm happy for this series (patches 1-10/10) to be applied.
Signed-off-by Jonathan Woithe <[email protected]>I have noticed people start using SoB for the code they are maintaining w/o sending any pull requests.
It is okay, but there is, as Wolfram pointed, a downside for patchwork users. Patchwork is tracking tags (A/R/T) which by a glance allows to see what patches are acked/reviewed/tested.Quoted 6 lines
Quoted 3 lines
Signed-off-by tracks the path the code takes from author to mainline. If you are not the author or committing it to a tree followed by a pull-request, the correct tag is "Reviewed-by".
Yes, of course - I clearly had a brain fade back there. Having said that, in the past I've used "Acked-by" intead of "Reviewed-by".
:-)
Quoted 2 lines
Do you want me to continue to use Acked-by, or should I switch to Reviewed-by?
These tags do have different meanings, and have come up at Kernel Summit the last couple of years. My interpretation of those discussions is:
Acked-by: I have no objection to this patch, but I didn't really give it a thorough review. I trust your judgement. e.g. minor change to your driver to support a subsystem API change. These are of very little value.
Quoted 7 lines
Reviewed-by: I have carefully reviewed this patch and would like it to be applied. This should usually come with some sort of commentary describing the level of review or an area you focused on. This is what we would like to see from all of our driver maintainers. These are high value.
Linus *really* dislikes one line acked by's, and only *slightly* more so than one line reviewed by's. :-)
This is really useful information and I think it does not deserve to be forgotten in a mailing list archive. If this is indeed the status quo, Documentation/process/submitting-patches.rst could use some love. Here is what it currently says:
Quoted 2 lines
Acked-by: is often used by the maintainer of the affected code when that maintainer neither contributed to nor forwarded the patch.
My short experience with the x86 platform driver subsystem is consistent with that. The informal rule I inferred from mailing list discussions is that Acked-by: means the maintainer has reviewed the patch and sees no objections to it being applied.
Granted, Documentation/process/submitting-patches.rst also states that:
Quoted 6 lines
Acked-by: does not necessarily indicate acknowledgement of the entire patch. For example, if a patch affects multiple subsystems and has an Acked-by: from one subsystem maintainer then this usually indicates acknowledgement of just the part which affects that maintainer's code. Judgement should be used here. When in doubt people should refer to the original discussion in the mailing list archives.
And indeed, that is also true, especially for patch series affecting multiple subsystems.
However, while the meaning of Reviewed-by: is described very thoroughly in that same document, I cannot recall a single case of a patch series affecting a single driver that would get a Reviewed-by: _from the maintainer_. Let alone a Reviewed-by: with a description of review depth. Perhaps I have read too little threads (or the wrong ones) :)
With time, I have also grown to believe that one of the differences between Acked-by: and Reviewed-by: is that anyone interested can offer their Reviewed-by: while Acked-by: is reserved for driver maintainers.
Perhaps this is all material for a "falsehoods kernel developers believe about commit tags"-type article ;)
Signature · 2 lines
Best regards, Michał Kępień
Quoted 76 lines · Michał Kępień
Quoted 37 lines · Jonathan Woithe
Quoted 17 lines · Darren Hart
Quoted 16 lines · Andy Shevchenko
Quoted 14 lines · Jonathan Woithe
Quoted 7 lines · Micha?? K??pie??
In summary, I see no issues with this patch series which provides a much needed clean up of the code and naming conventions within the fujitsu-laptop driver. I'm happy for this series (patches 1-10/10) to be applied.
Signed-off-by Jonathan Woithe <[email protected]>I have noticed people start using SoB for the code they are maintaining w/o sending any pull requests.
It is okay, but there is, as Wolfram pointed, a downside for patchwork users. Patchwork is tracking tags (A/R/T) which by a glance allows to see what patches are acked/reviewed/tested.Quoted 6 lines
Quoted 3 lines
Signed-off-by tracks the path the code takes from author to mainline. If you are not the author or committing it to a tree followed by a pull-request, the correct tag is "Reviewed-by".
Yes, of course - I clearly had a brain fade back there. Having said that, in the past I've used "Acked-by" intead of "Reviewed-by".
:-)
Quoted 2 lines
Do you want me to continue to use Acked-by, or should I switch to Reviewed-by?
These tags do have different meanings, and have come up at Kernel Summit the last couple of years. My interpretation of those discussions is:
Acked-by: I have no objection to this patch, but I didn't really give it a thorough review. I trust your judgement. e.g. minor change to your driver to support a subsystem API change. These are of very little value.
Quoted 7 lines
Reviewed-by: I have carefully reviewed this patch and would like it to be applied. This should usually come with some sort of commentary describing the level of review or an area you focused on. This is what we would like to see from all of our driver maintainers. These are high value.
Linus *really* dislikes one line acked by's, and only *slightly* more so than one line reviewed by's. :-)
This is really useful information and I think it does not deserve to be forgotten in a mailing list archive. If this is indeed the status quo,
Documentation/process/submitting-patches.rstcould use some love. Here is what it currently says:Quoted 2 lines
Acked-by: is often used by the maintainer of the affected code when that maintainer neither contributed to nor forwarded the patch.
My short experience with the x86 platform driver subsystem is consistent with that. The informal rule I inferred from mailing list discussions is that Acked-by: means the maintainer has reviewed the patch and sees no objections to it being applied.
Granted,
Documentation/process/submitting-patches.rstalso states that:Quoted 6 lines
Acked-by: does not necessarily indicate acknowledgement of the entire patch. For example, if a patch affects multiple subsystems and has an Acked-by: from one subsystem maintainer then this usually indicates acknowledgement of just the part which affects that maintainer's code. Judgement should be used here. When in doubt people should refer to the original discussion in the mailing list archives.
And indeed, that is also true, especially for patch series affecting multiple subsystems.
However, while the meaning of Reviewed-by: is described very thoroughly in that same document, I cannot recall a single case of a patch series affecting a single driver that would get a Reviewed-by:
_fromthemaintainer_. Let alone a Reviewed-by: with a description of review depth. Perhaps I have read too little threads (or the wrong ones) :)
Quoted 6 lines
With time, I have also grown to believe that one of the differences between Acked-by: and Reviewed-by: is that anyone interested can offer their Reviewed-by: while Acked-by: is reserved for driver maintainers.
Perhaps this is all material for a "falsehoods kernel developers believe about commit tags"-type article ;)
Thanks Michał for your thoughts/experience. My definitions above are based largely on the recent kernel summit discussions and if that is not reflected in the submitting patches document, it should be. I'm happy to propose a patch to that affect and hopefully that will shake out any differences of opinion on definitions.
Thanks,
Signature · 2 lines
Darren Hart Intel Open Source Technology Center