Hi,
2015-06-29 11:48 GMT+02:00 Mark Brown broonie@kernel.org:
On Mon, Jun 29, 2015 at 09:27:17AM +0200, Christian Hartmann wrote:
FYI: I can confirm that with the changed DSDT.dsl file and loading the new custom DSDT table, I do not need this patch mentioned above.
Are you sure?
[ 0.000000] ACPI: Override [DSDT-CS-02 ], this is unsafe: tainting kernel [ 0.000000] Disabling lock debugging due to kernel taint [ 0.000000] ACPI: DSDT 0x0000000078CE2000 Logical table override, new table: 0x00000000C0EBB470 [ 0.000000] ACPI: DSDT 0x00000000C0EBB470 00A6A2 (v02 LENOVO CS-02 00000001 INTL 20150410) [ 0.000000] ACPI: Local APIC address 0xfee00000 ... [ 7.308741] pxa2xx-spi 80860F0E:00: no DMA channels available, using PIO [ 7.308837] pxa2xx-spi 80860F0E:00: registered master spi32766 (dynamic) [ 7.308978] spi spi-WM510205:00: 8333333 Hz actual, PIO [ 7.309002] spi spi-WM510205:00: setup mode 0, 8 bits/w, 8000000 Hz max --> 0 ...
without the DSDT load, I must have this patch applied, otherwise the wm5102 will not be attached. I have checked it both and yes I am really sure since yesterday.
[ 5.927801] spi-WM510205:00 supply DCVDD not found, using dummy regulator [ 5.928958] arizona spi-WM510205:00: Unknown device ID: ffff [ 5.929098] pxa2xx-spi 80860F0E:00: registered child spi-WM510205:00
The above is saying that SPI I/O to the device isn't working - the device ID is not being read back successfully.
Ok that is the next problem that must be solved. I have yesterday made a patchset where I have added the enum type 5, but as you said already, that was not needed. All what I see the same: : Unknown device ID: ffff
So where I have to look now or what can I do to let this device id register correctly? I hope the baytrail machine driver is easy peasy to add, but here I stuck at the moment.
cheers Christian