Bug 113151

--Working-4.7----------
Boot: YES
Detect hard drive(s): YES (/dev/mmcblk0)
CPU: Baytrail-T Z3735F (requires intel_idle.max_cstate=1 workaround)
Shutdown: YES
Reboot: YES
Xorg: YES
OpenGL: YES (3.3)
Screen Backlight: YES
Built-in Touchpad: YES
Built-in Keyboard: YES
Keyboard's Hotkeys: YES
Built-in camera: YES
MicroSD card reader: YES
Switch to External Screen (HDMI): YES (was not able to select mirrored)

--Not Working/Unknown--
Hibernation: ?
Suspend / Resume: NO (black screen)
Battery Monitor: NO (BIOS BUG)
Bluetooth: NO (out of tree driver)
Wireless/Wifi: NO (out of tree driver)
Sound: NO (detected by not setup correctly)

--Working-4.11-RC1-------
Boot: YES
Shutdown: YES
Reboot: YES

CPU: Baytrail-T Z3735F
Display:    YES (i915)
Backlight:  YES
Lid Switch: YES
Battery:    YES (axp288)
eMMC:       YES
Touchpad:   YES
Keyboard:   YES
Camera:     YES
Audio:      YES (rt5640 / tlv320aic31xx)
MicroSD:    YES
HDMI:       YES
USB:        YES


--Not Working/Unknown----
Microphone: NO
Bluetooth:  NO (8723bs, out of tree driver)
Wifi:       NO (8723bs, out of tree driver)
Audio jack detection: NO
HDMI Audio: ?? (not tested)
Hibernation: ? (not tested)
Suspend / Resume: NO (hangs)

requires intel_idle.max_cstate=1 workaround

--Working-4.11-------
Boot: YES
Shutdown: YES
Reboot: YES

CPU: Baytrail-T Z3735F
Display:        YES (i915)
Backlight:      YES
Lid Switch:     YES
Battery:        YES (axp288)
eMMC:           YES
Touchpad:       YES
Keyboard:       YES
Camera:         YES
Audio:          YES (rt5640 / tlv320aic31xx)
MicroSD:        YES
HDMI:           YES
HDMI Audio:     YES (no audio at all if system is booted with hdmi unplugged)
USB:            YES
Suspend/Resume: YES (only wakeup device appears to be the lid switch)


--Not Working/Unknown----
Microphone: NO
Bluetooth:  NO (8723bs, out of tree driver)
Wifi:       NO (8723bs, out of tree driver. staged for 4.12 but buggy)
Audio jack detection: NO
Hibernation: ? (not tested)
Suspend/Resume: sometimes keyboard not responsive after resume
Suspend/Resume: cant wake via keyboard, touchpad, power button etc
HDMI Audio: no audio at all if system is booted with hdmi unplugged. If cable is plugged after boot theres still no audio (internal or HDMI) (fix is to blacklist 'blacklist snd_hdmi_lpe_audio' for now)
Battery: Broken ACPI battery is still reported

--Working-4.12-------------
Wifi: MOSTLY (8723bs in staging, occasionally breaks at Suspend/Resume)

--Not Working/Unknown----
Microphone: NO
Bluetooth:  NO (8723bs, out of tree driver)
Audio jack detection: NO
Hibernation: ? (not tested)
Suspend/Resume: cant wake via keyboard, touchpad, power button etc (probably hardware design)
HDMI Audio: no audio at all if system is booted with hdmi unplugged. If cable is plugged after boot there's still no audio (internal or HDMI) (fix is to blacklist 'blacklist snd_hdmi_lpe_audio' for now)
Battery: Broken ACPI battery and charger are now removed (only one battery is shown) charge state updates instantly now however charge level seems to not be accurate anymore (time estimate is)

Charge level is working properly again since latest 4.12.x stable updates

Does anyone else have problems with keyboard and mouse with 4.13 kernel? I am using 100s-11iby and when the laptop boots keyboard always works in grub but it's not working anymore when I have to type in password for cryptsetup to unlock my rootfs. And the strange thing is that sometimes keyboard works just fine with 4.13 kernel but fails maybe 50% of boots.

Plugging in an USB keyboard works so I can enter password at cryptsetup. However keyboard and mouse are still unavailable when the machine has booted up.

With 4.12 kernel keyboard and mouse worked just fine.

I have not been able to figure out what changed between 4.12 and 4.13 that would affect the keyboard. dmesg (with 4.13.9) says:
[    2.703624] input: ENEE3730:00 6243:0001 as /devices/platform/80860F41:02/i2c-2/i2c-ENEE3730:00/0018:6243:0001.0001/input/input1
[    2.704635] hid-generic 0018:6243:0001.0001: input,hidraw0: I2C HID v1.00 Keyboard [ENEE3730:00 6243:0001] on i2c-ENEE3730:00

I have now tried blacklisting i915 module and with quick tests (few boots) the keyboard has now worked. But time will tell... And I am using debian testing.

Addendum to dan.g.tob's observations
(latest kernel I tried here is 4.14-rc1):

Resume with Power button now works with kernel 4.14 .
Hibernate does not work (system freezes instantly; after a hard reboot no resume image is found, so apparently creating the resume image fails).

On a few things my personal experience differs from dan's:

Suspend/resume generally works, but sometimes the system freezes on suspend or resume.
Sound has never been working here.
Battery level seemed to work briefly with 4.12, however after a few minutes of uptime the system would "reliably" freeze. With 4.14 the system instantly freezes when the axp288-fuel-gauge driver is loaded.

@Jaakko:
never any keyboard/mouse problems here since early 4.x kernels, however I never tried 4.13 . Just a guess: if blacklisting i915 helps, might this suggest that it could be a firmware related issue?

Good to hear some comments.

I thought blacklisting i915 helped but No. After some time I got non-working keyboard with i915 blacklisted so now I load it normally again. No success finding the cause for keyboard problems but now (with 4.13.11/12) the problem occurs quite rarely (maybe every 6-7th boot). I have also tried to get past the problem by connecting external usb keyboard and ctrl-alt-delling as many times as is required and often 1-3 times is enough.

@klappnase:
I have never had sound here either but axp288-fuel-gauge works despite the continuous "axp288_fuel_gauge axp288_fuel_gauge: ADC charge current read failed:-19" errors I get in dmesg. So I guess the driver does not know when it is  plugged in and charging but I get reliable readings for remaining battery when not plugged in.

@Jaakko
Weird, here after modprobe axp288-fuel-gauge I get a number of relatively harmless looking error messages similar to the one you posted and then the machines freezes almost instantly. Maybe some other kernel module interferes here and should be blacklisted instead, but that is hard to tell, especially since nothing is being logged when the machine freezes. I guess I will have to live without battery indicator for now.

I need to correct myself. Should have read the docs properly in the first place, my bad. Reconfigured the kernel now with CONFIG_MFD_AXP20X_I2C, I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_BAYTRAIL=y instead of "=m". Now the status is here (with 4.13.12):

Suspend/Resume: works and seems stable; resume with power button works.
Hibernate:      works, however after resuming from hibernation wifi and
                power button no longer work (appears to be consistent
                behavior here).
                modprobe -r r8723bs && modprobe r8723bs seems to reliably
                revive wifi, modprobe -r axp20x_pek && modprobe axp20x_pek
                revives the power button.
Battery:        works (gives error messages, however these errors seem to be
                relatively benign).
Still no sound, though.

Apologies for the misleading information I submitted before.

@ Jaakko
no problems here with keyboard/touchpad with 4.13.12 .
About the charging issue, I did not check what happens in /sys, however xfce4-power-manager after a few seconds changes its icon and message texts accordingly when the AC-adaptor is plugged in or plugged out, so I assume the driver handles this properly.

I'm also seeing the 4.13 regression with the touchpad & keyboard not working (its random; not every boot). It's fine with 4.12. Open a new bug and make it depend on this bug

Charging mostly works, occasionally the machine wakes itself from suspend to report low battery when the battery is fine.

"axp288_fuel_gauge axp288_fuel_gauge: ADC charge current read failed:-19"
I get this warning too, but it doesn't seem to cause any problems..

To get working audio you need to grab these UCM files
https://github.com/plbossart/UCM/tree/master/bytcr-rt5640
probably make sure you have a new-ish firmware package too, I think everything else is upstream as of 4.11.

I can confirm the keyboard/touchpad issue now, too with 4.13.12. Happened once after about 15 or 20 boots. Happens also with 4.14.0.
Still no luck with sound here, maybe still a firmware issue (latest firmware packages from debian installed) or yet another kernel config problem.
With pulseaudio I still get lots of messages like

[   82.649840] intel_sst_acpi 80860F28:00: FW Version 01.0c.00.01
[   82.650272]  Baytrail Audio Port: ASoC: no backend DAIs enabled for Baytrail Audio Port
(...)

with plain alsa it's 

$ aplay Noise.wav
Playing WAVE 'Noise.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
aplay: set_params:1363: Unable to install hw params:
(...)

@dan.g.tob:
Thanks for the tip. I got sound working now.

@klappnase:
With 4.14.0 I get:
[   23.574584] bytcr_rt5640 bytcr_rt5640: BIOS Routing: AIF1 connected
[   23.574590] bytcr_rt5640 bytcr_rt5640: quirk IN1_MAP enabled
[   23.574592] bytcr_rt5640 bytcr_rt5640: quirk DIFF_MIC enabled
[   23.574594] bytcr_rt5640 bytcr_rt5640: quirk SSP0_AIF1 enabled
[   23.574596] bytcr_rt5640 bytcr_rt5640: quirk MCLK_EN enabled
[   23.589819] bytcr_rt5640 bytcr_rt5640: snd-soc-dummy-dai <-> media-cpu-dai mapping ok
[   23.589887] bytcr_rt5640 bytcr_rt5640: snd-soc-dummy-dai <-> deepbuffer-cpu-dai mapping ok
[   23.589925] compress asoc: snd-soc-dummy-dai <-> compress-cpu-dai mapping ok
[   23.590524] bytcr_rt5640 bytcr_rt5640: rt5640-aif1 <-> ssp0-port mapping ok


I have noticed that the keyboard/touchpad issue occurs more ofthen with a reboot than with a cold boot. With 4.13.12 I got about 15 cold boot ups and one keyboard issue. With 4.14.0 so far 3 cold boots and no issues. But with reboot the keyboard problem issue seems to happen every other or third reboot. Has anyone else observed similar?

I am also wondering could there be some connection between this and https://bugzilla.kernel.org/show_bug.cgi?id=197287 even though the hardware is very different.

Fyi, I opened a new bug about the keyboard/touchpad issue at https://bugzilla.kernel.org/show_bug.cgi?id=197903 .

@Jaakko
Not sure if there is a difference between cold boots and reboots, just now I had to reboot about 15 times to get the keyboard/touchpad failure.

About the sound driver, the messages look the same here. I think I will have to debug this systematically, but I don't want to clutter this board with what now appears to be merely a configuration problem. I wonder if maybe you could do me a favor and send me your .config for 4.14.0 attached to a PM off-list, so I could rule out the possibility that there is still something wrong with my kernel?

I just to say I had the issue where the touchpad pointer was working find when I originally installed lubuntu with kernel 6.5.0-41.  Soon after using it for a little while, I think I performed a reboot and the mouse pointer started jumping all over the place, but it generally allowed left-right control, but up-down control using the touchpad didn't work hardly at all.  I came across this thread where you folks have noticed issues as well.  I tried multiple reboots and the issue remained, but I did try the hard shutdown and cold boot and then it started working again, so this suggests a couple things:

1.  Cold boots do appear to make a difference in this regard
2.  This issue remains

Is it possible there's an issue finding the right device when loading up on boot, timing issue, etc.?  I'm not sure how to fix this permanently, but hopefully this information is useful.

One other note that may not have anything to do with this, but I was playing audio from another windows machine with krdc before the sound stopped working, giving a long beep sound.  After some research, I tried making a modification to 

/etc/modprobe.d/alsa-base.conf
options snd-intel-dspcfg dsp_driver=3

And reboot prior to the issue occurring.  Since the sound issue came back, I instead used this:

options snd_sof sof_debug=1

Is it possible these issues are related?