[GIT-PULL] IOTG broad market patches#53
Closed
joshonnable wants to merge 23 commits intothesofproject:topic/sof-devfrom
Closed
[GIT-PULL] IOTG broad market patches#53joshonnable wants to merge 23 commits intothesofproject:topic/sof-devfrom
joshonnable wants to merge 23 commits intothesofproject:topic/sof-devfrom
Conversation
…meter Added support for loading the machine driver for RSE and HU using module parameter.For loading the RSE or HU machine driver "bxt_ivi_rse_i2s" or "bxt_ivi_hu_i2s" parameter should be passed as a module parameter. Change-Id: Icc948a9dfdf24d9b1f305fb0f9d784e077566102 Signed-off-by: Mousumi Jana <mousumix.jana@intel.com> Reviewed-on: https://git-gar-1.devtools.intel.com/gerrit/7818 Reviewed-by: Babu, Ramesh <ramesh.babu@intel.com> Tested-by: Babu, Ramesh <ramesh.babu@intel.com> Conflicts: sound/soc/intel/skylake/skl.c
This commit is to add new dummy codec machine drivers for Apollo Lake-I LeafHill CRB. LeafHill CRB Machine driver enable SSP2 and SSP4 port with settings: - Master Mode - I2S protocol - 48000Hz - S16_LE, S24_LE and S32_LE format Signed-off-by: Tan, Seng Kai <seng.kai.tan@intel.com> Signed-off-by: Vinod Kumar <vinod.kumarx.vinod.kumar@intel.com> Conflicts: sound/soc/intel/boards/Makefile Conflicts: MAINTAINERS
Enhance the capabilties of the FE and BE DAIs with respect to new features implemented for IVI. Number of FEs have been increased to support a total of 4 System Playback Pins and 1 Multi Channel HDMI Pin that carries I2S data from SSP. On the other side, the BE capabilities have been enhanced to support more SSPs as per new platforms Change-Id: I7c7efa52d9b36fbc06b77c56f0c59f73e7a0030c Signed-off-by: Pardha Saradhi K <pardha.saradhi.kesapragada@intel.com> Reviewed-on: https://git-gar-1.devtools.intel.com/gerrit/7580 Reviewed-by: Babu, Ramesh <ramesh.babu@intel.com> Tested-by: Babu, Ramesh <ramesh.babu@intel.com> Conflicts: sound/soc/intel/skylake/skl-pcm.c
Add support for S24_LE, S24_3LE, S32_LE and FLOAT PCM formats. The sample type field of the gateway copiers have to be set such that the format is conveyed to the DSP. Based on this, the copier will do a type conversion Change-Id: I7a6ff9d2b078db086ddf9a1907b7aaac0ad7e922 Signed-off-by: Pardha Saradhi K <pardha.saradhi.kesapragada@intel.com> Reviewed-on: https://git-gar-1.devtools.intel.com/gerrit/9550 Reviewed-by: B, Jayachandran <jayachandran.b@intel.com> Reviewed-by: Babu, Ramesh <ramesh.babu@intel.com> Tested-by: Babu, Ramesh <ramesh.babu@intel.com> Conflicts: sound/soc/intel/skylake/skl-pcm.c
Add more capabilities to the existing streams so as to support IVI usecases. IVI needs a total of 6 PB and 6 CP streams that can run simultaneously on 6 different SSPs. Change-Id: I2d88cd1cf5bb8da0ca1f247971d504ee097fdc99 Signed-off-by: Mousumi Jana <mousumix.jana@intel.com> Reviewed-on: https://git-gar-1.devtools.intel.com/gerrit/10568 Reviewed-by: Jayanti, Satya Charitardha <satya.charitardha.jayanti@intel.com> Tested-by: Jayanti, Satya Charitardha <satya.charitardha.jayanti@intel.com> Conflicts: sound/soc/intel/skylake/skl-pcm.c
Add capabilities to FE streams such that Playback and Capture for all sample rates from 8K to 192K and all channels from Mono to 8 Channel are supported Change-Id: I318bf237aa3e9e6a841c6deeb3e8cd5bf300d997 Signed-off-by: Pardha Saradhi K <pardha.saradhi.kesapragada@intel.com> Reviewed-on: https://git-gar-1.devtools.intel.com/gerrit/10792 Reviewed-by: B, Jayachandran <jayachandran.b@intel.com> Reviewed-by: Babu, Ramesh <ramesh.babu@intel.com> Tested-by: Jayanti, Satya Charitardha <satya.charitardha.jayanti@intel.com> Conflicts: sound/soc/intel/skylake/skl-pcm.c
Add more capabilities to the existing streams so as to support APLI usecases. APLI needs a total of 6 PB/CP streams that can run on 6 different SSPs with different sample rate and channel number. Signed-off-by: Vinod Kumar <vinod.kumarx.vinod.kumar@intel.com> Conflicts: sound/soc/intel/skylake/skl-pcm.c
This commit is to add new wm8731 codec machine drivers for Apollo Lake-I LeafHill CRB. LeafHill CRB Machine driver enable SSP2 as a dummy codec and SSP4 port connect with wm8731 codec with settings: - Master Mode - I2S protocol - 48000Hz - S16_LE, S24_LE and S32_LE format Signed-off-by: Tan, Seng Kai <seng.kai.tan@intel.com> Signed-off-by: Joshua Wong Weng Onn <joshua.weng.onn.wong@intel.com> Conflicts: sound/soc/intel/Kconfig
This commit is to add new machine drivers for TI codec, for both soc master and slave control mode, which are named lfcrb_aic3107M_i2s and lfcrb_aic3107S_i2s respectively. The codec support is linked to SSP1 port. Signed-off-by: Ho, Yu Xin <yu.xin.ho@intel.com> Signed-off-by: Tan, Seng Kai <seng.kai.tan@intel.com> Conflicts: sound/soc/intel/Kconfig
This commit attempts to remove mute unmute control for SSP ports with dummy codec. This is due to the fact that mute and unmute command is not supported in FW unless there is a gain block. If mute and unmute command is sent to FW, unknown IPC message and pipeline error will occur. Signed-off-by: Ho, Yu Xin <yu.xin.ho@intel.com> (cherry picked from commit c80aa78cceb961f31d9b19d55e2a1fc9a2b4975a) Signed-off-by: SengKai,Tan <seng.kai.tan@intel.com>
…hine drivers This commit attempts to add back DAPM widgets for all machine drivers including dummy codec, WM8731 and also TLV320AIC3107. Previous with the removal of DAPM widgets, there will be failure on no sink/source widget found, causing no audio playback signal. Signed-off-by: Ho, Yu Xin <yu.xin.ho@intel.com>
This commit register I2C bus 3 for wm8731 codec specific for Apollo Lake-I Leaf Hill CRB Signed-off-by: Tan, Seng Kai <seng.kai.tan@intel.com>
This commit register I2C bus 3 for aic3107 codec specific for Apollo Lake-I Leaf Hill CRB Signed-off-by: Tan, Seng Kai <seng.kai.tan@intel.com>
Remove unused variable to fix klocwork issue Signed-off-by: Tan, Seng Kai <seng.kai.tan@intel.com>
BIOS default ACPI setting is set to:- INT34C1 - disable INT343A - enable Due to no actual codec in our Leaf Hill board, we have to make INT343A as our example to automatic load dummy codec. This only serves as an example. In actual application, ACPI ID has to register with uefi.org This commit also revised typo error from lfcrb to lhcrb (Leaf Hill Customer Reference Board) Signed-off-by: Tan, Seng Kai <seng.kai.tan@intel.com> (cherry picked from commit 05730937b7ed527abd734ac51cd8341f0886a02c) Signed-off-by: Vinod Kumar <vinod.kumarx.vinod.kumar@intel.com> Conflicts: sound/soc/intel/skylake/skl.c
Enable all the SSP port with multi channel,samplig rate,protocol, bit depth for Apli(Apollo Lake). Add the the New dummy codec with the following support: - SSP Port: SSP 1,2,3,4,5,6 - Channel support: 1ch/2ch/4ch/6ch/8ch - Sampling Rate: 8k,16k,22.05k,24k,32k,44.1k,48k,96k,192k - bit depth/width: 16/16,16/32,24/32,32/32 - protocol: I2S for 2ch and PCM for 1,4,6,8ch. Signed-off-by: Vinod Kumar <vinod.kumarx.vinod.kumar@intel.com> Conflicts: MAINTAINERS sound/soc/intel/Kconfig sound/soc/intel/boards/Makefile Conflicts: MAINTAINERS sound/soc/intel/Kconfig
Add support of missing S24_3LE PCM formats for System Pin 6, Deepbuffer and Reference Pin of FE CPU DAI. Signed-off-by: Vinod Kumar <vinod.kumarx.vinod.kumar@intel.com> Conflicts: sound/soc/intel/skylake/skl-pcm.c
I2S5 BCLK Pin was configuring during the enablment of I2S 6 and I2S 5. This patch contains the following changes: - Removed the I2S 5 BLCK entry for I2S 6. - Removed the I2S 1 MCLK Pin configuration as not required. - Optimized the code by reducing allocated memory region. Signed-off-by: Vinod Kumar <vinod.kumarx.vinod.kumar@intel.com>
… driver Leaf Hill Hardware support the S16_LE, S24_LE and S32_LE format. Any other needed conversions like S24_3LE are not required to declare in the kernel driver their conversion are done in user space, So removed the S24_3LE format support from the driver. Signed-off-by: Vinod Kumar <vinod.kumarx.vinod.kumar@intel.com>
…call Kernel was crashing due to NULL pointer dereference of dapm widget pointer while playing the audio file with multiple pipeline configuration topology This patch is to make sure to check the dapm widget pointer before the every recursive call. Signed-off-by: Vinod Kumar <vinod.kumarx.vinod.kumar@intel.com> Conflicts: sound/soc/intel/skylake/skl-topology.c
param definition that causes kernel crash Remove skl_controls and topology back end parameter definition that causes kernel crash during boot up and also when commanding amixer -c0. Signed-off-by: Ho, Yu Xin <yu.xin.ho@intel.com> Conflicts: sound/soc/intel/skylake/skl-pcm.c sound/soc/intel/skylake/skl-topology.c
The be_id variable has been replaced with id. Hence, change be_id to id for the following machine drivers. 1. lhcrb_dummy_i2s 2. lhcrb_wm8731_i2s 3. lhcrb_aic3107M_i2s 4. lhcrb_aic3107S_i2s 5. apli_lhcrb_generic_i2s Signed-off-by: Joshua Wong Weng Onn <joshua.weng.onn.wong@intel.com>
…t and topology param definition that causes kernel crash" This reverts commit a4dbe6c82fe6654930489d978994112399e4e1f9 This patch is reverted to enable snd_controls so that dsp log level selection and sampling rate settings can be adjusted via alsamixer. Signed-off-by: Joshua Wong Weng Onn <joshua.weng.onn.wong@intel.com> Conflicts: sound/soc/intel/skylake/skl-topology.c
Member
|
Sorry, none of those patches seem to be related to SOF? |
Author
|
+Seng Kai, Yu Xin
Hi Pierre,
We would like to seek your help to review these patches and then merge them to the 4.14-lts production kernel.
Thank you.
Best regards,
Joshua
From: Pierre Bossart [mailto:notifications@github.com]
Sent: Monday, July 23, 2018 11:13 PM
To: thesofproject/linux <linux@noreply.github.com>
Cc: Wong, Joshua Weng Onn <joshua.weng.onn.wong@intel.com>; Author <author@noreply.github.com>
Subject: Re: [thesofproject/linux] [GIT-PULL] IOTG broad market patches (#53)
Sorry, none of those patches seem to be related to SOF?
What are you trying to do here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#53 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AU_w6HuTZ_VzuH9f8XnhQvGnnbU_rosjks5uJefsgaJpZM4VbIIb>.
|
Member
|
This is not the right channel, this site is for SOF development. You are asking for an Intel-only review and this has to take place on the internal mailing list. |
plbossart
pushed a commit
that referenced
this pull request
Feb 13, 2019
syzbot was able to catch a bug in rds [1] The issue here is that the socket might be found in a hash table but that its refcount has already be set to 0 by another cpu. We need to use refcount_inc_not_zero() to be safe here. [1] refcount_t: increment on 0; use-after-free. WARNING: CPU: 1 PID: 23129 at lib/refcount.c:153 refcount_inc_checked lib/refcount.c:153 [inline] WARNING: CPU: 1 PID: 23129 at lib/refcount.c:153 refcount_inc_checked+0x61/0x70 lib/refcount.c:151 Kernel panic - not syncing: panic_on_warn set ... CPU: 1 PID: 23129 Comm: syz-executor3 Not tainted 5.0.0-rc4+ #53 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1db/0x2d0 lib/dump_stack.c:113 panic+0x2cb/0x65c kernel/panic.c:214 __warn.cold+0x20/0x48 kernel/panic.c:571 report_bug+0x263/0x2b0 lib/bug.c:186 fixup_bug arch/x86/kernel/traps.c:178 [inline] fixup_bug arch/x86/kernel/traps.c:173 [inline] do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:271 do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:290 invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:973 RIP: 0010:refcount_inc_checked lib/refcount.c:153 [inline] RIP: 0010:refcount_inc_checked+0x61/0x70 lib/refcount.c:151 Code: 1d 51 63 c8 06 31 ff 89 de e8 eb 1b f2 fd 84 db 75 dd e8 a2 1a f2 fd 48 c7 c7 60 9f 81 88 c6 05 31 63 c8 06 01 e8 af 65 bb fd <0f> 0b eb c1 90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 54 49 RSP: 0018:ffff8880a0cbf1e8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffc90006113000 RDX: 000000000001047d RSI: ffffffff81685776 RDI: 0000000000000005 RBP: ffff8880a0cbf1f8 R08: ffff888097c9e100 R09: ffffed1015ce5021 R10: ffffed1015ce5020 R11: ffff8880ae728107 R12: ffff8880723c20c0 R13: ffff8880723c24b0 R14: dffffc0000000000 R15: ffffed1014197e64 sock_hold include/net/sock.h:647 [inline] rds_sock_addref+0x19/0x20 net/rds/af_rds.c:675 rds_find_bound+0x97c/0x1080 net/rds/bind.c:82 rds_recv_incoming+0x3be/0x1430 net/rds/recv.c:362 rds_loop_xmit+0xf3/0x2a0 net/rds/loop.c:96 rds_send_xmit+0x1355/0x2a10 net/rds/send.c:355 rds_sendmsg+0x323c/0x44e0 net/rds/send.c:1368 sock_sendmsg_nosec net/socket.c:621 [inline] sock_sendmsg+0xdd/0x130 net/socket.c:631 __sys_sendto+0x387/0x5f0 net/socket.c:1788 __do_sys_sendto net/socket.c:1800 [inline] __se_sys_sendto net/socket.c:1796 [inline] __x64_sys_sendto+0xe1/0x1a0 net/socket.c:1796 do_syscall_64+0x1a3/0x800 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x458089 Code: 6d b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 3b b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007fc266df8c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 0000000000000006 RCX: 0000000000458089 RDX: 0000000000000000 RSI: 00000000204b3fff RDI: 0000000000000005 RBP: 000000000073bf00 R08: 00000000202b4000 R09: 0000000000000010 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fc266df96d4 R13: 00000000004c56e4 R14: 00000000004d94a8 R15: 00000000ffffffff Fixes: cc4dfb7 ("rds: fix two RCU related problems") Signed-off-by: Eric Dumazet <edumazet@google.com> Reported-by: syzbot <syzkaller@googlegroups.com> Cc: Sowmini Varadhan <sowmini.varadhan@oracle.com> Cc: Santosh Shilimkar <santosh.shilimkar@oracle.com> Cc: rds-devel@oss.oracle.com Cc: Cong Wang <xiyou.wangcong@gmail.com> Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com> Signed-off-by: David S. Miller <davem@davemloft.net>
plbossart
pushed a commit
that referenced
this pull request
Feb 13, 2019
KASAN detects a use-after-free when vop devices are removed. This problem was introduced by commit 0063e8b ("virtio_vop: don't kfree device on register failure"). That patch moved the freeing of the struct _vop_vdev to the release function, but failed to ensure that vop holds a reference to the device when it doesn't want it to go away. A kfree() was replaced with a put_device() in the unregistration path, but the last reference to the device is already dropped in unregister_virtio_device() so the struct is freed before vop is done with it. Fix it by holding a reference until cleanup is done. This is similar to the fix in virtio_pci in commit 2989be0 ("virtio_pci: fix use after free on release"). ================================================================== BUG: KASAN: use-after-free in vop_scan_devices+0xc6c/0xe50 [vop] Read of size 8 at addr ffff88800da18580 by task kworker/0:1/12 CPU: 0 PID: 12 Comm: kworker/0:1 Not tainted 5.0.0-rc4+ #53 Workqueue: events vop_hotplug_devices [vop] Call Trace: dump_stack+0x74/0xbb print_address_description+0x5d/0x2b0 ? vop_scan_devices+0xc6c/0xe50 [vop] kasan_report+0x152/0x1aa ? vop_scan_devices+0xc6c/0xe50 [vop] ? vop_scan_devices+0xc6c/0xe50 [vop] vop_scan_devices+0xc6c/0xe50 [vop] ? vop_loopback_free_irq+0x160/0x160 [vop_loopback] process_one_work+0x7c0/0x14b0 ? pwq_dec_nr_in_flight+0x2d0/0x2d0 ? do_raw_spin_lock+0x120/0x280 worker_thread+0x8f/0xbf0 ? __kthread_parkme+0x78/0xf0 ? process_one_work+0x14b0/0x14b0 kthread+0x2ae/0x3a0 ? kthread_park+0x120/0x120 ret_from_fork+0x3a/0x50 Allocated by task 12: kmem_cache_alloc_trace+0x13a/0x2a0 vop_scan_devices+0x473/0xe50 [vop] process_one_work+0x7c0/0x14b0 worker_thread+0x8f/0xbf0 kthread+0x2ae/0x3a0 ret_from_fork+0x3a/0x50 Freed by task 12: kfree+0x104/0x310 device_release+0x73/0x1d0 kobject_put+0x14f/0x420 unregister_virtio_device+0x32/0x50 vop_scan_devices+0x19d/0xe50 [vop] process_one_work+0x7c0/0x14b0 worker_thread+0x8f/0xbf0 kthread+0x2ae/0x3a0 ret_from_fork+0x3a/0x50 The buggy address belongs to the object at ffff88800da18008 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 1400 bytes inside of 2048-byte region [ffff88800da18008, ffff88800da18808) The buggy address belongs to the page: page:ffffea0000368600 count:1 mapcount:0 mapping:ffff88801440dbc0 index:0x0 compound_mapcount: 0 flags: 0x4000000000010200(slab|head) raw: 4000000000010200 ffffea0000378608 ffffea000037a008 ffff88801440dbc0 raw: 0000000000000000 00000000000d000d 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff88800da18480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88800da18500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff88800da18580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff88800da18600: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88800da18680: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== Fixes: 0063e8b ("virtio_vop: don't kfree device on register failure") Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com> Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
ranj063
pushed a commit
to ranj063/linux
that referenced
this pull request
Mar 11, 2020
For the duration of mapping eVMCS, it derefences ->memslots without holding ->srcu or ->slots_lock when accessing hv assist page. This patch fixes it by moving nested_sync_vmcs12_to_shadow to prepare_guest_switch, where the SRCU is already taken. It can be reproduced by running kvm's evmcs_test selftest. ============================= warning: suspicious rcu usage 5.6.0-rc1+ thesofproject#53 tainted: g w ioe ----------------------------- ./include/linux/kvm_host.h:623 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by evmcs_test/8507: #0: ffff9ddd156d00d0 (&vcpu->mutex){+.+.}, at: kvm_vcpu_ioctl+0x85/0x680 [kvm] stack backtrace: cpu: 6 pid: 8507 comm: evmcs_test tainted: g w ioe 5.6.0-rc1+ thesofproject#53 hardware name: dell inc. optiplex 7040/0jctf8, bios 1.4.9 09/12/2016 call trace: dump_stack+0x68/0x9b kvm_read_guest_cached+0x11d/0x150 [kvm] kvm_hv_get_assist_page+0x33/0x40 [kvm] nested_enlightened_vmentry+0x2c/0x60 [kvm_intel] nested_vmx_handle_enlightened_vmptrld.part.52+0x32/0x1c0 [kvm_intel] nested_sync_vmcs12_to_shadow+0x439/0x680 [kvm_intel] vmx_vcpu_run+0x67a/0xe60 [kvm_intel] vcpu_enter_guest+0x35e/0x1bc0 [kvm] kvm_arch_vcpu_ioctl_run+0x40b/0x670 [kvm] kvm_vcpu_ioctl+0x370/0x680 [kvm] ksys_ioctl+0x235/0x850 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x77/0x780 entry_syscall_64_after_hwframe+0x49/0xbe Signed-off-by: Wanpeng Li <wanpengli@tencent.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
cujomalainey
pushed a commit
to cujomalainey/linux
that referenced
this pull request
Apr 23, 2020
commit 351cbf6 upstream. Zygo reported the following lockdep splat while testing the balance patches ====================================================== WARNING: possible circular locking dependency detected 5.6.0-c6f0579d496a+ thesofproject#53 Not tainted ------------------------------------------------------ kswapd0/1133 is trying to acquire lock: ffff888092f622c0 (&delayed_node->mutex){+.+.}, at: __btrfs_release_delayed_node+0x7c/0x5b0 but task is already holding lock: ffffffff8fc5f860 (fs_reclaim){+.+.}, at: __fs_reclaim_acquire+0x5/0x30 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (fs_reclaim){+.+.}: fs_reclaim_acquire.part.91+0x29/0x30 fs_reclaim_acquire+0x19/0x20 kmem_cache_alloc_trace+0x32/0x740 add_block_entry+0x45/0x260 btrfs_ref_tree_mod+0x6e2/0x8b0 btrfs_alloc_tree_block+0x789/0x880 alloc_tree_block_no_bg_flush+0xc6/0xf0 __btrfs_cow_block+0x270/0x940 btrfs_cow_block+0x1ba/0x3a0 btrfs_search_slot+0x999/0x1030 btrfs_insert_empty_items+0x81/0xe0 btrfs_insert_delayed_items+0x128/0x7d0 __btrfs_run_delayed_items+0xf4/0x2a0 btrfs_run_delayed_items+0x13/0x20 btrfs_commit_transaction+0x5cc/0x1390 insert_balance_item.isra.39+0x6b2/0x6e0 btrfs_balance+0x72d/0x18d0 btrfs_ioctl_balance+0x3de/0x4c0 btrfs_ioctl+0x30ab/0x44a0 ksys_ioctl+0xa1/0xe0 __x64_sys_ioctl+0x43/0x50 do_syscall_64+0x77/0x2c0 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&delayed_node->mutex){+.+.}: __lock_acquire+0x197e/0x2550 lock_acquire+0x103/0x220 __mutex_lock+0x13d/0xce0 mutex_lock_nested+0x1b/0x20 __btrfs_release_delayed_node+0x7c/0x5b0 btrfs_remove_delayed_node+0x49/0x50 btrfs_evict_inode+0x6fc/0x900 evict+0x19a/0x2c0 dispose_list+0xa0/0xe0 prune_icache_sb+0xbd/0xf0 super_cache_scan+0x1b5/0x250 do_shrink_slab+0x1f6/0x530 shrink_slab+0x32e/0x410 shrink_node+0x2a5/0xba0 balance_pgdat+0x4bd/0x8a0 kswapd+0x35a/0x800 kthread+0x1e9/0x210 ret_from_fork+0x3a/0x50 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(fs_reclaim); lock(&delayed_node->mutex); lock(fs_reclaim); lock(&delayed_node->mutex); *** DEADLOCK *** 3 locks held by kswapd0/1133: #0: ffffffff8fc5f860 (fs_reclaim){+.+.}, at: __fs_reclaim_acquire+0x5/0x30 #1: ffffffff8fc380d8 (shrinker_rwsem){++++}, at: shrink_slab+0x1e8/0x410 #2: ffff8881e0e6c0e8 (&type->s_umount_key#42){++++}, at: trylock_super+0x1b/0x70 stack backtrace: CPU: 2 PID: 1133 Comm: kswapd0 Not tainted 5.6.0-c6f0579d496a+ thesofproject#53 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Call Trace: dump_stack+0xc1/0x11a print_circular_bug.isra.38.cold.57+0x145/0x14a check_noncircular+0x2a9/0x2f0 ? print_circular_bug.isra.38+0x130/0x130 ? stack_trace_consume_entry+0x90/0x90 ? save_trace+0x3cc/0x420 __lock_acquire+0x197e/0x2550 ? btrfs_inode_clear_file_extent_range+0x9b/0xb0 ? register_lock_class+0x960/0x960 lock_acquire+0x103/0x220 ? __btrfs_release_delayed_node+0x7c/0x5b0 __mutex_lock+0x13d/0xce0 ? __btrfs_release_delayed_node+0x7c/0x5b0 ? __asan_loadN+0xf/0x20 ? pvclock_clocksource_read+0xeb/0x190 ? __btrfs_release_delayed_node+0x7c/0x5b0 ? mutex_lock_io_nested+0xc20/0xc20 ? __kasan_check_read+0x11/0x20 ? check_chain_key+0x1e6/0x2e0 mutex_lock_nested+0x1b/0x20 ? mutex_lock_nested+0x1b/0x20 __btrfs_release_delayed_node+0x7c/0x5b0 btrfs_remove_delayed_node+0x49/0x50 btrfs_evict_inode+0x6fc/0x900 ? btrfs_setattr+0x840/0x840 ? do_raw_spin_unlock+0xa8/0x140 evict+0x19a/0x2c0 dispose_list+0xa0/0xe0 prune_icache_sb+0xbd/0xf0 ? invalidate_inodes+0x310/0x310 super_cache_scan+0x1b5/0x250 do_shrink_slab+0x1f6/0x530 shrink_slab+0x32e/0x410 ? do_shrink_slab+0x530/0x530 ? do_shrink_slab+0x530/0x530 ? __kasan_check_read+0x11/0x20 ? mem_cgroup_protected+0x13d/0x260 shrink_node+0x2a5/0xba0 balance_pgdat+0x4bd/0x8a0 ? mem_cgroup_shrink_node+0x490/0x490 ? _raw_spin_unlock_irq+0x27/0x40 ? finish_task_switch+0xce/0x390 ? rcu_read_lock_bh_held+0xb0/0xb0 kswapd+0x35a/0x800 ? _raw_spin_unlock_irqrestore+0x4c/0x60 ? balance_pgdat+0x8a0/0x8a0 ? finish_wait+0x110/0x110 ? __kasan_check_read+0x11/0x20 ? __kthread_parkme+0xc6/0xe0 ? balance_pgdat+0x8a0/0x8a0 kthread+0x1e9/0x210 ? kthread_create_worker_on_cpu+0xc0/0xc0 ret_from_fork+0x3a/0x50 This is because we hold that delayed node's mutex while doing tree operations. Fix this by just wrapping the searches in nofs. CC: stable@vger.kernel.org # 4.4+ Signed-off-by: Josef Bacik <josef@toxicpanda.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
aiChaoSONG
pushed a commit
to aiChaoSONG/linux
that referenced
this pull request
May 6, 2021
This makes the safety more a part of the type-system. Also changes the chrdev API to a) require compile-time declaration of how many items it can have, b) allows gradual registration of chrdevs. Fixes thesofproject#53
bardliao
pushed a commit
to bardliao/linux
that referenced
this pull request
Jul 14, 2021
The to_ti_syscon_reset_data macro currently only works if the parameter passed into it is called 'rcdev'. Fixes a checkpatch --strict issue: CHECK: Macro argument reuse 'rcdev' - possible side-effects? thesofproject#53: FILE: drivers/reset/reset-ti-syscon.c:53: +#define to_ti_syscon_reset_data(rcdev) \ + container_of(rcdev, struct ti_syscon_reset_data, rcdev) Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
ujfalusi
pushed a commit
to ujfalusi/sof-linux
that referenced
this pull request
Sep 27, 2021
…et() Currently the bpf selftest "get_stack_raw_tp" triggered the warning: [ 1411.304463] WARNING: CPU: 3 PID: 140 at include/linux/mmap_lock.h:164 find_vma+0x47/0xa0 [ 1411.304469] Modules linked in: bpf_testmod(O) [last unloaded: bpf_testmod] [ 1411.304476] CPU: 3 PID: 140 Comm: systemd-journal Tainted: G W O 5.14.0+ thesofproject#53 [ 1411.304479] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 1411.304481] RIP: 0010:find_vma+0x47/0xa0 [ 1411.304484] Code: de 48 89 ef e8 ba f5 fe ff 48 85 c0 74 2e 48 83 c4 08 5b 5d c3 48 8d bf 28 01 00 00 be ff ff ff ff e8 2d 9f d8 00 85 c0 75 d4 <0f> 0b 48 89 de 48 8 [ 1411.304487] RSP: 0018:ffffabd440403db8 EFLAGS: 00010246 [ 1411.304490] RAX: 0000000000000000 RBX: 00007f00ad80a0e0 RCX: 0000000000000000 [ 1411.304492] RDX: 0000000000000001 RSI: ffffffff9776b144 RDI: ffffffff977e1b0e [ 1411.304494] RBP: ffff9cf5c2f50000 R08: ffff9cf5c3eb25d8 R09: 00000000fffffffe [ 1411.304496] R10: 0000000000000001 R11: 00000000ef974e19 R12: ffff9cf5c39ae0e0 [ 1411.304498] R13: 0000000000000000 R14: 0000000000000000 R15: ffff9cf5c39ae0e0 [ 1411.304501] FS: 00007f00ae754780(0000) GS:ffff9cf5fba00000(0000) knlGS:0000000000000000 [ 1411.304504] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1411.304506] CR2: 000000003e34343c CR3: 0000000103a98005 CR4: 0000000000370ee0 [ 1411.304508] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1411.304510] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 1411.304512] Call Trace: [ 1411.304517] stack_map_get_build_id_offset+0x17c/0x260 [ 1411.304528] __bpf_get_stack+0x18f/0x230 [ 1411.304541] bpf_get_stack_raw_tp+0x5a/0x70 [ 1411.305752] RAX: 0000000000000000 RBX: 5541f689495641d7 RCX: 0000000000000000 [ 1411.305756] RDX: 0000000000000001 RSI: ffffffff9776b144 RDI: ffffffff977e1b0e [ 1411.305758] RBP: ffff9cf5c02b2f40 R08: ffff9cf5ca7606c0 R09: ffffcbd43ee02c04 [ 1411.306978] bpf_prog_32007c34f7726d29_bpf_prog1+0xaf/0xd9c [ 1411.307861] R10: 0000000000000001 R11: 0000000000000044 R12: ffff9cf5c2ef60e0 [ 1411.307865] R13: 0000000000000005 R14: 0000000000000000 R15: ffff9cf5c2ef6108 [ 1411.309074] bpf_trace_run2+0x8f/0x1a0 [ 1411.309891] FS: 00007ff485141700(0000) GS:ffff9cf5fae00000(0000) knlGS:0000000000000000 [ 1411.309896] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1411.311221] syscall_trace_enter.isra.20+0x161/0x1f0 [ 1411.311600] CR2: 00007ff48514d90e CR3: 0000000107114001 CR4: 0000000000370ef0 [ 1411.312291] do_syscall_64+0x15/0x80 [ 1411.312941] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1411.313803] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1411.314223] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 1411.315082] RIP: 0033:0x7f00ad80a0e0 [ 1411.315626] Call Trace: [ 1411.315632] stack_map_get_build_id_offset+0x17c/0x260 To reproduce, first build `test_progs` binary: make -C tools/testing/selftests/bpf -j60 and then run the binary at tools/testing/selftests/bpf directory: ./test_progs -t get_stack_raw_tp The warning is due to commit 5b78ed2 ("mm/pagemap: add mmap_assert_locked() annotations to find_vma*()") which added mmap_assert_locked() in find_vma() function. The mmap_assert_locked() function asserts that mm->mmap_lock needs to be held. But this is not the case for bpf_get_stack() or bpf_get_stackid() helper (kernel/bpf/stackmap.c), which uses mmap_read_trylock_non_owner() instead. Since mm->mmap_lock is not held in bpf_get_stack[id]() use case, the above warning is emitted during test run. This patch fixed the issue by (1). using mmap_read_trylock() instead of mmap_read_trylock_non_owner() to satisfy lockdep checking in find_vma(), and (2). droping lockdep for mmap_lock right before the irq_work_queue(). The function mmap_read_trylock_non_owner() is also removed since after this patch nobody calls it any more. Fixes: 5b78ed2 ("mm/pagemap: add mmap_assert_locked() annotations to find_vma*()") Suggested-by: Jason Gunthorpe <jgg@ziepe.ca> Signed-off-by: Yonghong Song <yhs@fb.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com> Cc: Luigi Rizzo <lrizzo@google.com> Cc: Jason Gunthorpe <jgg@ziepe.ca> Cc: linux-mm@kvack.org Link: https://lore.kernel.org/bpf/20210909155000.1610299-1-yhs@fb.com
plbossart
pushed a commit
that referenced
this pull request
Apr 8, 2024
When unregister pd capabilitie in tcpm, KASAN will capture below double -free issue. The root cause is the same capabilitiy will be kfreed twice, the first time is kfreed by pd_capabilities_release() and the second time is explicitly kfreed by tcpm_port_unregister_pd(). [ 3.988059] BUG: KASAN: double-free in tcpm_port_unregister_pd+0x1a4/0x3dc [ 3.995001] Free of addr ffff0008164d3000 by task kworker/u16:0/10 [ 4.001206] [ 4.002712] CPU: 2 PID: 10 Comm: kworker/u16:0 Not tainted 6.8.0-rc5-next-20240220-05616-g52728c567a55 #53 [ 4.012402] Hardware name: Freescale i.MX8QXP MEK (DT) [ 4.017569] Workqueue: events_unbound deferred_probe_work_func [ 4.023456] Call trace: [ 4.025920] dump_backtrace+0x94/0xec [ 4.029629] show_stack+0x18/0x24 [ 4.032974] dump_stack_lvl+0x78/0x90 [ 4.036675] print_report+0xfc/0x5c0 [ 4.040289] kasan_report_invalid_free+0xa0/0xc0 [ 4.044937] __kasan_slab_free+0x124/0x154 [ 4.049072] kfree+0xb4/0x1e8 [ 4.052069] tcpm_port_unregister_pd+0x1a4/0x3dc [ 4.056725] tcpm_register_port+0x1dd0/0x2558 [ 4.061121] tcpci_register_port+0x420/0x71c [ 4.065430] tcpci_probe+0x118/0x2e0 To fix the issue, this will remove kree() from tcpm_port_unregister_pd(). Fixes: cd099cd ("usb: typec: tcpm: Support multiple capabilities") cc: stable@vger.kernel.org Suggested-by: Aisheng Dong <aisheng.dong@nxp.com> Signed-off-by: Xu Yang <xu.yang_2@nxp.com> Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com> Link: https://lore.kernel.org/r/20240311065219.777037-1-xu.yang_2@nxp.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
bardliao
pushed a commit
to bardliao/linux
that referenced
this pull request
Jan 14, 2025
There is a race condition at startup between disabling power domains not
used and disabling clocks not used on the rk3328. When the clocks are
disabled first, the hevc power domain fails to shut off leading to a
splat of failures. Add the hevc core clock to the rk3328 power domain
node to prevent this condition.
rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 3-.... }
1087 jiffies s: 89 root: 0x8/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 0 to CPUs 3:
NMI backtrace for cpu 3
CPU: 3 UID: 0 PID: 86 Comm: kworker/3:3 Not tainted 6.12.0-rc5+ thesofproject#53
Hardware name: Firefly ROC-RK3328-CC (DT)
Workqueue: pm genpd_power_off_work_fn
pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : regmap_unlock_spinlock+0x18/0x30
lr : regmap_read+0x60/0x88
sp : ffff800081123c00
x29: ffff800081123c00 x28: ffff2fa4c62cad80 x27: 0000000000000000
x26: ffffd74e6e660eb8 x25: ffff2fa4c62cae00 x24: 0000000000000040
x23: ffffd74e6d2f3ab8 x22: 0000000000000001 x21: ffff800081123c74
x20: 0000000000000000 x19: ffff2fa4c0412000 x18: 0000000000000000
x17: 77202c31203d2065 x16: 6c6469203a72656c x15: 6c6f72746e6f632d
x14: 7265776f703a6e6f x13: 2063766568206e69 x12: 616d6f64202c3431
x11: 347830206f742030 x10: 3430303034783020 x9 : ffffd74e6c7369e0
x8 : 3030316666206e69 x7 : 205d383738353733 x6 : 332e31202020205b
x5 : ffffd74e6c73fc88 x4 : ffffd74e6c73fcd4 x3 : ffffd74e6c740b40
x2 : ffff800080015484 x1 : 0000000000000000 x0 : ffff2fa4c0412000
Call trace:
regmap_unlock_spinlock+0x18/0x30
rockchip_pmu_set_idle_request+0xac/0x2c0
rockchip_pd_power+0x144/0x5f8
rockchip_pd_power_off+0x1c/0x30
_genpd_power_off+0x9c/0x180
genpd_power_off.part.0.isra.0+0x130/0x2a8
genpd_power_off_work_fn+0x6c/0x98
process_one_work+0x170/0x3f0
worker_thread+0x290/0x4a8
kthread+0xec/0xf8
ret_from_fork+0x10/0x20
rockchip-pm-domain ff100000.syscon:power-controller: failed to get ack on domain 'hevc', val=0x88220
Fixes: 52e02d3 ("arm64: dts: rockchip: add core dtsi file for RK3328 SoCs")
Signed-off-by: Peter Geis <pgwipeout@gmail.com>
Reviewed-by: Dragan Simic <dsimic@manjaro.org>
Link: https://lore.kernel.org/r/20241214224339.24674-1-pgwipeout@gmail.com
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
bardliao
pushed a commit
to bardliao/linux
that referenced
this pull request
Dec 1, 2025
The following lockdep splat was observed while kernel auto-online a CXL memory region: ====================================================== WARNING: possible circular locking dependency detected 6.17.0djtest+ thesofproject#53 Tainted: G W ------------------------------------------------------ systemd-udevd/3334 is trying to acquire lock: ffffffff90346188 (hmem_resource_lock){+.+.}-{4:4}, at: hmem_register_resource+0x31/0x50 but task is already holding lock: ffffffff90338890 ((node_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x2e/0x70 which lock already depends on the new lock. [..] Chain exists of: hmem_resource_lock --> mem_hotplug_lock --> (node_chain).rwsem Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock((node_chain).rwsem); lock(mem_hotplug_lock); lock((node_chain).rwsem); lock(hmem_resource_lock); The lock ordering can cause potential deadlock. There are instances where hmem_resource_lock is taken after (node_chain).rwsem, and vice versa. Split out the target update section of hmat_register_target() so that hmat_callback() only envokes that section instead of attempt to register hmem devices that it does not need to. [ dj: Fix up comment to be closer to 80cols. (Jonathan) ] Fixes: cf8741a ("ACPI: NUMA: HMAT: Register "soft reserved" memory as an "hmem" device") Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com> Tested-by: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com> Reviewed-by: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com> Reviewed-by: Dan Williams <dan.j.williams@intel.com> Link: https://patch.msgid.link/20251105235115.85062-3-dave.jiang@intel.com Signed-off-by: Dave Jiang <dave.jiang@intel.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The following changes since commit 9fc79c4:
[SQUASHME]ASoC: sof: topology: fix memleak when errror happen (2018-07-21 14:30:16 -0500)
are available in the git repository at:
https://github.com/joshonnable/linux.git topic/sof-dev
for you to fetch changes up to d6e7acf:
ASoC: Intel: Revert "ASoC: Intel: Skylake: Remove unused soc component and topology param definition that causes kernel crash" (2018-07-23 22:33:19 +0800)
Ho, Yu Xin (3):
ASoC: Intel: Skylake: Remove dummy codec SSP ports mute unmute switch
ASoC: Intel: Skylake: Adding back dummy codec dapm widget for all machine drivers
ASoC: Intel: Skylake: Remove unused soc component and topology param definition that causes kernel crash
Joshua Wong Weng Onn (2):
ASoC: Intel: Change be_id variable in machine drivers
ASoC: Intel: Revert "ASoC: Intel: Skylake: Remove unused soc component and topology param definition that causes kernel crash"
Mousumi Jana (2):
ASoC: Intel: Support for loading the machine driver using module parameter
ASoC: Intel: Skylake: Increase the capabilities of front end streams
Pardha Saradhi K (3):
ASoC: Intel: Skylake: Add new capabilities of DAIs
ASoC: Intel: Skylake: Add support for various PCM formats
ASoC: Intel: Skylake: Support upto 8 Channels on Playback & Capture
SengKai,Tan (7):
ASoC: Intel: Skylake: Add dummy machine drivers
ASoC: Intel: Skylake: Add wm8731 machine driver
ASoC: Intel: Skylake: Add machine drivers for TLV320AIC3107
x86: wm8731 I2C Interface register for APLI LHCRB
x86: aic3107 I2C Interface register for APLI LHCRB
x86: remove unused variable
ASoC: Intel: Skylake: ACPI example INT343A for LeafHill CRB
Vinod Kumar (6):
ASoC: Intel: Skylake: Increase the capabilities of FE/BE streams
ASoC: Intel: Skylake: Enable all SSP port on APL board.
ASoC: Intel: Skylake: Add support of S24_3LE PCM formats for FE
ASoC: Intel: Skylake: Removed the I2S 5 BCLK multiple configuration
ASoC: Intel: Skylake: Removed the S24_3LE format support from generic driver
ASoC: Intel: Skylake: Checking the dapm widgtet before the recursive call
MAINTAINERS | 22 +++++
arch/x86/Kconfig | 16 ++++
arch/x86/platform/Makefile | 1 +
arch/x86/platform/apli_lhcrb/Makefile | 2 +
arch/x86/platform/apli_lhcrb/apli_lhcrb_aic3107_i2c.c | 70 ++++++++++++++++
arch/x86/platform/apli_lhcrb/apli_lhcrb_wm8731_i2c.c | 69 ++++++++++++++++
sound/soc/intel/boards/Kconfig | 44 ++++++++++
sound/soc/intel/boards/Makefile | 10 +++
sound/soc/intel/boards/apli_lhcrb_aic3107M.c | 402 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
sound/soc/intel/boards/apli_lhcrb_aic3107S.c | 402 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
sound/soc/intel/boards/apli_lhcrb_dummy.c | 235 ++++++++++++++++++++++++++++++++++++++++++++++++++++
sound/soc/intel/boards/apli_lhcrb_generic.c | 578 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
sound/soc/intel/boards/apli_lhcrb_wm8731.c | 269 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
sound/soc/intel/skylake/skl-pcm.c | 277 +++++++++++++++++++++++++++++++++++++++++++++++--------------
sound/soc/intel/skylake/skl-topology.c | 59 +++++++++----
sound/soc/intel/skylake/skl-topology.h | 12 ++-
sound/soc/intel/skylake/skl.c | 33 ++++++--
17 files changed, 2416 insertions(+), 85 deletions(-)
create mode 100644 arch/x86/platform/apli_lhcrb/Makefile
create mode 100644 arch/x86/platform/apli_lhcrb/apli_lhcrb_aic3107_i2c.c
create mode 100644 arch/x86/platform/apli_lhcrb/apli_lhcrb_wm8731_i2c.c
create mode 100644 sound/soc/intel/boards/apli_lhcrb_aic3107M.c
create mode 100644 sound/soc/intel/boards/apli_lhcrb_aic3107S.c
create mode 100644 sound/soc/intel/boards/apli_lhcrb_dummy.c
create mode 100644 sound/soc/intel/boards/apli_lhcrb_generic.c
create mode 100644 sound/soc/intel/boards/apli_lhcrb_wm8731.c
mode change 100644 => 100755 sound/soc/intel/skylake/skl-pcm.c
mode change 100644 => 100755 sound/soc/intel/skylake/skl-topology.c