btrfs: fix race between quota disable and quota assign ioctls

commit 2f1a6be12ab6c8470d5776e68644726c94257c54 upstream.

The quota assign ioctl can currently run in parallel with a quota disable
ioctl call. The assign ioctl uses the quota root, while the disable ioctl
frees that root, and therefore we can have a use-after-free triggered in
the assign ioctl, leading to a trace like the following when KASAN is
enabled:

  [672.723][T736] BUG: KASAN: slab-use-after-free in btrfs_search_slot+0x2962/0x2db0
  [672.723][T736] Read of size 8 at addr ffff888022ec0208 by task btrfs_search_sl/27736
  [672.724][T736]
  [672.725][T736] CPU: 1 PID: 27736 Comm: btrfs_search_sl Not tainted 6.3.0-rc3 #37
  [672.723][T736] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
  [672.727][T736] Call Trace:
  [672.728][T736]  <TASK>
  [672.728][T736]  dump_stack_lvl+0xd9/0x150
  [672.725][T736]  print_report+0xc1/0x5e0
  [672.720][T736]  ? __virt_addr_valid+0x61/0x2e0
  [672.727][T736]  ? __phys_addr+0xc9/0x150
  [672.725][T736]  ? btrfs_search_slot+0x2962/0x2db0
  [672.722][T736]  kasan_report+0xc0/0xf0
  [672.729][T736]  ? btrfs_search_slot+0x2962/0x2db0
  [672.724][T736]  btrfs_search_slot+0x2962/0x2db0
  [672.723][T736]  ? fs_reclaim_acquire+0xba/0x160
  [672.722][T736]  ? split_leaf+0x13d0/0x13d0
  [672.726][T736]  ? rcu_is_watching+0x12/0xb0
  [672.723][T736]  ? kmem_cache_alloc+0x338/0x3c0
  [672.722][T736]  update_qgroup_status_item+0xf7/0x320
  [672.724][T736]  ? add_qgroup_rb+0x3d0/0x3d0
  [672.739][T736]  ? do_raw_spin_lock+0x12d/0x2b0
  [672.730][T736]  ? spin_bug+0x1d0/0x1d0
  [672.737][T736]  btrfs_run_qgroups+0x5de/0x840
  [672.730][T736]  ? btrfs_qgroup_rescan_worker+0xa70/0xa70
  [672.738][T736]  ? __del_qgroup_relation+0x4ba/0xe00
  [672.738][T736]  btrfs_ioctl+0x3d58/0x5d80
  [672.735][T736]  ? tomoyo_path_number_perm+0x16a/0x550
  [672.737][T736]  ? tomoyo_execute_permission+0x4a0/0x4a0
  [672.731][T736]  ? btrfs_ioctl_get_supported_features+0x50/0x50
  [672.737][T736]  ? __sanitizer_cov_trace_switch+0x54/0x90
  [672.734][T736]  ? do_vfs_ioctl+0x132/0x1660
  [672.730][T736]  ? vfs_fileattr_set+0xc40/0xc40
  [672.730][T736]  ? _raw_spin_unlock_irq+0x2e/0x50
  [672.732][T736]  ? sigprocmask+0xf2/0x340
  [672.737][T736]  ? __fget_files+0x26a/0x480
  [672.732][T736]  ? bpf_lsm_file_ioctl+0x9/0x10
  [672.738][T736]  ? btrfs_ioctl_get_supported_features+0x50/0x50
  [672.736][T736]  __x64_sys_ioctl+0x198/0x210
  [672.736][T736]  do_syscall_64+0x39/0xb0
  [672.731][T736]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  [672.739][T736] RIP: 0033:0x4556ad
  [672.742][T736]  </TASK>
  [672.743][T736]
  [672.748][T736] Allocated by task 27677:
  [672.743][T736]  kasan_save_stack+0x22/0x40
  [672.741][T736]  kasan_set_track+0x25/0x30
  [672.741][T736]  __kasan_kmalloc+0xa4/0xb0
  [672.749][T736]  btrfs_alloc_root+0x48/0x90
  [672.746][T736]  btrfs_create_tree+0x146/0xa20
  [672.744][T736]  btrfs_quota_enable+0x461/0x1d20
  [672.743][T736]  btrfs_ioctl+0x4a1c/0x5d80
  [672.747][T736]  __x64_sys_ioctl+0x198/0x210
  [672.749][T736]  do_syscall_64+0x39/0xb0
  [672.744][T736]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  [672.756][T736]
  [672.757][T736] Freed by task 27677:
  [672.759][T736]  kasan_save_stack+0x22/0x40
  [672.759][T736]  kasan_set_track+0x25/0x30
  [672.756][T736]  kasan_save_free_info+0x2e/0x50
  [672.751][T736]  ____kasan_slab_free+0x162/0x1c0
  [672.758][T736]  slab_free_freelist_hook+0x89/0x1c0
  [672.752][T736]  __kmem_cache_free+0xaf/0x2e0
  [672.752][T736]  btrfs_put_root+0x1ff/0x2b0
  [672.759][T736]  btrfs_quota_disable+0x80a/0xbc0
  [672.752][T736]  btrfs_ioctl+0x3e5f/0x5d80
  [672.756][T736]  __x64_sys_ioctl+0x198/0x210
  [672.753][T736]  do_syscall_64+0x39/0xb0
  [672.765][T736]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  [672.769][T736]
  [672.768][T736] The buggy address belongs to the object at ffff888022ec0000
  [672.768][T736]  which belongs to the cache kmalloc-4k of size 4096
  [672.769][T736] The buggy address is located 520 bytes inside of
  [672.769][T736]  freed 4096-byte region [ffff888022ec0000, ffff888022ec1000)
  [672.760][T736]
  [672.764][T736] The buggy address belongs to the physical page:
  [672.761][T736] page:ffffea00008bb000 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x22ec0
  [672.766][T736] head:ffffea00008bb000 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0
  [672.779][T736] flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff)
  [672.770][T736] raw: 00fff00000010200 ffff888012842140 ffffea000054ba00 dead000000000002
  [672.770][T736] raw: 0000000000000000 0000000000040004 00000001ffffffff 0000000000000000
  [672.771][T736] page dumped because: kasan: bad access detected
  [672.778][T736] page_owner tracks the page as allocated
  [672.777][T736] page last allocated via order 3, migratetype Unmovable, gfp_mask 0xd2040(__GFP_IO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 88
  [672.779][T736]  get_page_from_freelist+0x119c/0x2d50
  [672.779][T736]  __alloc_pages+0x1cb/0x4a0
  [672.776][T736]  alloc_pages+0x1aa/0x270
  [672.773][T736]  allocate_slab+0x260/0x390
  [672.771][T736]  ___slab_alloc+0xa9a/0x13e0
  [672.778][T736]  __slab_alloc.constprop.0+0x56/0xb0
  [672.771][T736]  __kmem_cache_alloc_node+0x136/0x320
  [672.789][T736]  __kmalloc+0x4e/0x1a0
  [672.783][T736]  tomoyo_realpath_from_path+0xc3/0x600
  [672.781][T736]  tomoyo_path_perm+0x22f/0x420
  [672.782][T736]  tomoyo_path_unlink+0x92/0xd0
  [672.780][T736]  security_path_unlink+0xdb/0x150
  [672.788][T736]  do_unlinkat+0x377/0x680
  [672.788][T736]  __x64_sys_unlink+0xca/0x110
  [672.789][T736]  do_syscall_64+0x39/0xb0
  [672.783][T736]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  [672.784][T736] page last free stack trace:
  [672.787][T736]  free_pcp_prepare+0x4e5/0x920
  [672.787][T736]  free_unref_page+0x1d/0x4e0
  [672.784][T736]  __unfreeze_partials+0x17c/0x1a0
  [672.797][T736]  qlist_free_all+0x6a/0x180
  [672.796][T736]  kasan_quarantine_reduce+0x189/0x1d0
  [672.797][T736]  __kasan_slab_alloc+0x64/0x90
  [672.793][T736]  kmem_cache_alloc+0x17c/0x3c0
  [672.799][T736]  getname_flags.part.0+0x50/0x4e0
  [672.799][T736]  getname_flags+0x9e/0xe0
  [672.792][T736]  vfs_fstatat+0x77/0xb0
  [672.791][T736]  __do_sys_newlstat+0x84/0x100
  [672.798][T736]  do_syscall_64+0x39/0xb0
  [672.796][T736]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  [672.790][T736]
  [672.791][T736] Memory state around the buggy address:
  [672.799][T736]  ffff888022ec0100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
  [672.805][T736]  ffff888022ec0180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
  [672.802][T736] >ffff888022ec0200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
  [672.809][T736]                       ^
  [672.809][T736]  ffff888022ec0280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
  [672.809][T736]  ffff888022ec0300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb

Fix this by having the qgroup assign ioctl take the qgroup ioctl mutex
before calling btrfs_run_qgroups(), which is what all qgroup ioctls should
call.

Reported-by: butt3rflyh4ck <butterflyhuangxx@gmail.com>
Link: https://lore.kernel.org/linux-btrfs/CAFcO6XN3VD8ogmHwqRk4kbiwtpUSNySu2VAxN8waEPciCHJvMA@mail.gmail.com/
CC: stable@vger.kernel.org # 5.10+
Reviewed-by: Qu Wenruo <wqu@suse.com>
Signed-off-by: Filipe Manana <fdmanana@suse.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>
[ cherry-pick c976f9233ef926e090db5614a837824a0bcab3fb from linux-stable-5.15.x, fixes CVE-2023-1611 ]
Signed-off-by: Karol Lewandowski <k.lewandowsk@samsung.com>
Change-Id: I907508fa0f0daf8ed923dd6bfeda3f8059d1f2bd

mac80211: correct legacy rates check in ieee80211_calc_rx_airtime

There are no legacy rates on 60GHz or sub-1GHz band, so modify the check.

Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
Signed-off-by: MeiChia Chiu <MeiChia.Chiu@mediatek.com>
Link: https://lore.kernel.org/r/20220308021645.16272-1-MeiChia.Chiu@mediatek.com
[Ghz ->  GHz]
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
[cherry picked from commit 022143d0c52b6e63d49ffc3542dc9d3ae15a5178]
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
Change-Id: I83bba0992b6f1d54bd3565cd8a1c819d15c2f60d

ARM/ARM64: tizen_bcm2711_defconfig: enable PSI

Enable PSI module config option to monitor the resources.

Change-Id: Ic70a72285edde102e57c38828bb0d7843279734c
Signed-off-by: SangYoun Kwak <sy.kwak@samsung.com>

packaging: Change the kernel version of the spec file

Change the kernel version to 5.15.92

Change-Id: I40a63f16ac6a288507addb5d86455dcb7e840c96
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

rpi4: boot: Update the firmwares for kernel v5.15.92

The updated files comes from https://github.com/raspberrypi/firmware.git
master branch, commit(0d3395d1e065 kernel: Bump to 5.15.92)

Change-Id: I8df49461e381444f251193ccfa56768ad285c3ab
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

packaging: Upgrade build required openssl version from 1.1 to 3

Openssl 1.1.1 is supported until September 2023, so Tizen 8.0
upgrades Openssl 3.0.x. To meet this, change build required
openssl version. Also, required with pkgconfig.

Change-Id: I7d9ab2e4a1c1d1b8ee6d4ed4f15924f90a89fc48
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

rpi4: boot: config: Add camera_auto_detect config for mipi csi camera

Automatically load overlays for detected csi camera modules
to support rpi camera modules instead of not anymore supported
legacy camera firmware control.

Change-Id: Ib5eda3d73e7a3ab324123cd83c95b357abbdfc0d
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

ARM/ARM64: config: enable raspberry pi camera module options

Enable raspberry pi camera module config options extracted from
bcm2711_defconfig.

Change-Id: I4da4c5c0d2ce7ab53784b5b8fb2bdf373f07fd8e
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

Revert "Bluetooth: Store advertising handle so it can be re-enabled"

This reverts commit 7087c4f69487f017722df7d299ef9b7709996b79.

Patch revert is needed as it is the cause for GATT Server TCT fail.

Change-Id: I55bedbb6b0d44058c13ac06df121c5d936611c74
Signed-off-by: Anuj Jain <anuj01.jain@samsung.com>

packaging: ignore Werror for tools

With gcc-12 and new binutils, there are some warnings in tools.
Do not cause error for the warnings.

Change-Id: If75607ca3acc2104a6a33bbc3d13b02757ddbcf7
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

tools bpftool: Fix compilation error with new binutils

commit 600b7b26c07a070d0153daa76b3806c1e52c9e00 upstream.

binutils changed the signature of init_disassemble_info(), which now causes
compilation to fail for tools/bpf/bpftool/jit_disasm.c, e.g. on debian
unstable.

Relevant binutils commit:

  https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=60a3da00bd5407f07

Wire up the feature test and switch to init_disassemble_info_compat(),
which were introduced in prior commits, fixing the compilation failure.

I verified that bpftool can still disassemble bpf programs, both with an
old and new dis-asm.h API. There are no output changes for plain and json
formats. When comparing the output from old binutils (2.35)
to new bintuils with the patch (upstream snapshot) there are a few output
differences, but they are unrelated to this patch. An example hunk is:

     2f: pop    %r14
     31: pop    %r13
     33: pop    %rbx
  -  34: leaveq
  -  35: retq
  +  34: leave
  +  35: ret

Signed-off-by: Andres Freund <andres@anarazel.de>
Acked-by: Quentin Monnet <quentin@isovalent.com>
Cc: Alexei Starovoitov <ast@kernel.org>
Cc: Ben Hutchings <benh@debian.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Quentin Monnet <quentin@isovalent.com>
Cc: Sedat Dilek <sedat.dilek@gmail.com>
Cc: bpf@vger.kernel.org
Link: http://lore.kernel.org/lkml/20220622181918.ykrs5rsnmx3og4sv@alap3.anarazel.de
Link: https://lore.kernel.org/r/20220801013834.156015-8-andres@anarazel.de
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[sw0312.kim: cherry-pick stable linux-5.15.y commit 4441a9009193 to resolve gcc-12-build issue]
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
Change-Id: I4bc40a822995acad090f987a2937a6db47a6f511

tools bpf_jit_disasm: Fix compilation error with new binutils

commit 96ed066054abf11c7d3e106e3011a51f3f1227a3 upstream.

binutils changed the signature of init_disassemble_info(), which now causes
compilation to fail for tools/bpf/bpf_jit_disasm.c, e.g. on debian
unstable.

Relevant binutils commit:

  https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=60a3da00bd5407f07

Wire up the feature test and switch to init_disassemble_info_compat(),
which were introduced in prior commits, fixing the compilation failure.

I verified that bpf_jit_disasm can still disassemble bpf programs, both
with the old and new dis-asm.h API. With old binutils there's no change in
output before/after this patch. When comparing the output from old
binutils (2.35) to new bintuils with the patch (upstream snapshot) there
are a few output differences, but they are unrelated to this patch. An
example hunk is:

     f4: mov    %r14,%rsi
     f7: mov    %r15,%rdx
     fa: mov    $0x2a,%ecx
  -  ff: callq  0xffffffffea8c4988
  +  ff: call   0xffffffffea8c4988
    104: test   %rax,%rax
    107: jge    0x0000000000000110
    109: xor    %eax,%eax
  - 10b: jmpq   0x0000000000000073
  + 10b: jmp    0x0000000000000073
    110: cmp    $0x16,%rax

However, I had to use an older kernel to generate the bpf_jit_enabled =
2 output, as that has been broken since 5.18 / 1022a5498f6f745c ("bpf,
x86_64: Use bpf_jit_binary_pack_alloc").

  https://lore.kernel.org/20220703030210.pmjft7qc2eajzi6c@alap3.anarazel.de

Signed-off-by: Andres Freund <andres@anarazel.de>
Acked-by: Quentin Monnet <quentin@isovalent.com>
Cc: Alexei Starovoitov <ast@kernel.org>
Cc: Ben Hutchings <benh@debian.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Quentin Monnet <quentin@isovalent.com>
Cc: Sedat Dilek <sedat.dilek@gmail.com>
Cc: bpf@vger.kernel.org
Link: http://lore.kernel.org/lkml/20220622181918.ykrs5rsnmx3og4sv@alap3.anarazel.de
Link: https://lore.kernel.org/r/20220801013834.156015-6-andres@anarazel.de
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[sw0312.kim: cherry-pick stable linux-5.15.y commit 1c27fab24333 to resolve gcc-12-build issue]
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
Change-Id: Ie64ecd2f88c14389110d8fab6e1f595bd38b1516

tools perf: Fix compilation error with new binutils

commit 83aa0120487e8bc3f231e72c460add783f71f17c upstream.

binutils changed the signature of init_disassemble_info(), which now causes
compilation failures for tools/perf/util/annotate.c, e.g. on debian
unstable.

Relevant binutils commit:

  https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=60a3da00bd5407f07

Wire up the feature test and switch to init_disassemble_info_compat(),
which were introduced in prior commits, fixing the compilation failure.

I verified that perf can still disassemble bpf programs by using bpftrace
under load, recording a perf trace, and then annotating the bpf "function"
with and without the changes. With old binutils there's no change in output
before/after this patch. When comparing the output from old binutils (2.35)
to new bintuils with the patch (upstream snapshot) there are a few output
differences, but they are unrelated to this patch. An example hunk is:

       1.15 :   55:mov    %rbp,%rdx
       0.00 :   58:add    $0xfffffffffffffff8,%rdx
       0.00 :   5c:xor    %ecx,%ecx
  -    1.03 :   5e:callq  0xffffffffe12aca3c
  +    1.03 :   5e:call   0xffffffffe12aca3c
       0.00 :   63:xor    %eax,%eax
  -    2.18 :   65:leaveq
  -    2.82 :   66:retq
  +    2.18 :   65:leave
  +    2.82 :   66:ret

Signed-off-by: Andres Freund <andres@anarazel.de>
Acked-by: Quentin Monnet <quentin@isovalent.com>
Cc: Alexei Starovoitov <ast@kernel.org>
Cc: Ben Hutchings <benh@debian.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Sedat Dilek <sedat.dilek@gmail.com>
Cc: bpf@vger.kernel.org
Link: http://lore.kernel.org/lkml/20220622181918.ykrs5rsnmx3og4sv@alap3.anarazel.de
Link: https://lore.kernel.org/r/20220801013834.156015-5-andres@anarazel.de
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[sw0312.kim: cherry-pick stable linux-5.15.y commit 97f005c0bdba to resolve gcc-12 build issue]
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
Change-Id: Ib9c0a83b11e28e1d1f5846b7b1bf21e007aaa1fd

tools include: add dis-asm-compat.h to handle version differences

commit a45b3d6926231c3d024ea0de4f7bd967f83709ee upstream.

binutils changed the signature of init_disassemble_info(), which now causes
compilation failures for tools/{perf,bpf}, e.g. on debian unstable.

Relevant binutils commit:

  https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=60a3da00bd5407f07

This commit introduces a wrapper for init_disassemble_info(), to avoid
spreading #ifdef DISASM_INIT_STYLED to a bunch of places. Subsequent
commits will use it to fix the build failures.

It likely is worth adding a wrapper for disassember(), to avoid the already
existing DISASM_FOUR_ARGS_SIGNATURE ifdefery.

Signed-off-by: Andres Freund <andres@anarazel.de>
Signed-off-by: Ben Hutchings <benh@debian.org>
Acked-by: Quentin Monnet <quentin@isovalent.com>
Cc: Alexei Starovoitov <ast@kernel.org>
Cc: Ben Hutchings <benh@debian.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Quentin Monnet <quentin@isovalent.com>
Cc: Sedat Dilek <sedat.dilek@gmail.com>
Cc: bpf@vger.kernel.org
Link: http://lore.kernel.org/lkml/20220622181918.ykrs5rsnmx3og4sv@alap3.anarazel.de
Link: https://lore.kernel.org/r/20220801013834.156015-4-andres@anarazel.de
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[sw0312.kim: cherry-pick stable linux-5.15.y commit 451c9d7b1616 to resolve gcc-12 build issue]
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
Change-Id: I41fde6de2055b838dfbdc3d6de1b64eea3ab20c5

tools build: Add feature test for init_disassemble_info API changes

commit cfd59ca91467056bb2c36907b2fa67b8e1af9952 upstream.

binutils changed the signature of init_disassemble_info(), which now causes
compilation failures for tools/{perf,bpf}, e.g. on debian unstable.

Relevant binutils commit:

  https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=60a3da00bd5407f07

This commit adds a feature test to detect the new signature.  Subsequent
commits will use it to fix the build failures.

Signed-off-by: Andres Freund <andres@anarazel.de>
Acked-by: Quentin Monnet <quentin@isovalent.com>
Cc: Alexei Starovoitov <ast@kernel.org>
Cc: Ben Hutchings <benh@debian.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Quentin Monnet <quentin@isovalent.com>
Cc: Sedat Dilek <sedat.dilek@gmail.com>
Cc: bpf@vger.kernel.org
Link: http://lore.kernel.org/lkml/20220622181918.ykrs5rsnmx3og4sv@alap3.anarazel.de
Link: https://lore.kernel.org/r/20220801013834.156015-2-andres@anarazel.de
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[sw0312.kim: cherry-pick stable linux-5.15.y commit 51b99dc38c1a to resolve gcc-12 build issue]
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
Change-Id: I68d3e7bb522e3d6d5bb7c534b5a203d9ee03eb34

dm-bow: Fix 5.15 compatibility issue

https://patchwork.kernel.org/project/linux-block/patch/20210804094147.459763-8-hch@lst.de/

delays registering the gendisk, so move creating our sysfs nodes until
resume.

Orignal-Author: Paul Lawrence <paullawrence@google.com>
Origin: https://android.googlesource.com/kernel/common/+/88e27b17aab604fb2d486e538b2ef55cd967a430%5E%21/#F0
Signed-off-by: Paul Lawrence <paullawrence@google.com>
Change-Id: Ib328a4b1f989cdd7359c186668417f85d633b29a
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

ARM/ARM64: config: enable DRM_LOAD_EDID_FIRMWARE

Enable CONFIG_DRM_LOAD_EDID_FIRMWARE from tizen defconfigs to
support drm.edid_firmware paremeter.
Adding "drm.edid_firmware=edid/1920x1080.bin" to cmdline makes
all connected display connector has the 1920x1080 mode.

Kernel has prebuilt edids, 800x600.bin, 1024x768.bin,
1280x1024.bin, 1600x1200.bin, 1680x1050.bin and 1920x1080.bin and
to use other mode edids, put custom edid files into path
/lib/firmware/edid/.

Note: to build custom edid binary, please refer tools/edid/.

Change-Id: I7b80f1aa5a0422f4cb8ff8d99584d0cbdbc8ae1e
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

ARM/ARM64: config: enable DM_INIT configuration

To use "dm-mod.create=", enable DM_INIT configuration.

Change-Id: I22da617243d0ecafab3048a3aa970ef53b8712c5
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

dm init: add dm-mod.waitfor to wait for asynchronously probed block devices

Just calling wait_for_device_probe() is not enough to ensure that
asynchronously probed block devices are available (E.G. mmc, usb), so
add a "dm-mod.waitfor=<device1>[,..,<deviceN>]" parameter to get
dm-init to explicitly wait for specific block devices before
initializing the tables with logic similar to the rootwait logic that
was introduced with commit  cc1ed7542c8c ("init: wait for
asynchronously scanned block devices").

E.G. with dm-verity on mmc using:
dm-mod.waitfor="PARTLABEL=hash-a,PARTLABEL=root-a"

[    0.671671] device-mapper: init: waiting for all devices to be available before creating mapped devices
[    0.671679] device-mapper: init: waiting for device PARTLABEL=hash-a ...
[    0.710695] mmc0: new HS200 MMC card at address 0001
[    0.711158] mmcblk0: mmc0:0001 004GA0 3.69 GiB
[    0.715954] mmcblk0boot0: mmc0:0001 004GA0 partition 1 2.00 MiB
[    0.722085] mmcblk0boot1: mmc0:0001 004GA0 partition 2 2.00 MiB
[    0.728093] mmcblk0rpmb: mmc0:0001 004GA0 partition 3 512 KiB, chardev (249:0)
[    0.738274]  mmcblk0: p1 p2 p3 p4 p5 p6 p7
[    0.751282] device-mapper: init: waiting for device PARTLABEL=root-a ...
[    0.751306] device-mapper: init: all devices available
[    0.751683] device-mapper: verity: sha256 using implementation "sha256-generic"
[    0.759344] device-mapper: ioctl: dm-0 (vroot) is ready
[    0.766540] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Signed-off-by: Mike Snitzer <snitzer@kernel.org>
[jh80.chung: cherry picked from commit 035641b01e72af4f6c6cf22a4bdb5d7dfc4e8e8e]
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
Change-Id: Ib918a6f474842b1ae633225a7781839e7ffaade4

ARM: tizen_bcm2711_defconfig: Add enable mt7921u defconfig

Enable mt7921u defconfig for wifi-6e usb interface.

Change-Id: Ia129eb71bc3b71788d3647be02b9f8b260e0b599
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

mt76-6e-usb: mac80211: Use less restrictive channel usage rules

Fixed an issue where Wi-Fi 6e could not be scanned. Use less
restrictive channel usage rules.

Signed-off-by: astsam <info@no-problem.cc>
Change-Id: Iafba1ceb9b3275ad1bc71f0d16c48492215d48dd
[Patch url: https://github.com/astsam/mt7921/commit/ec4206ea938037f07cbff516260c9f5706ffa9f7]
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

mt76-6e-usb: mt7921: Avoid throughput drop in VO streaming, enable TX BA by default.

Avoid throughput drop in VO streaming, enable TX BA by default.

From: Deren Wu <deren.wu@mediatek.com>
From: YN Chen <YN.Chen@mediatek.com>

Change-Id: Id0f3ffffda64ce5e408936d82e26a3518a353c4e
[Patch url: https://patchwork.kernel.org/project/linux-wireless/patch/889fc1f28a8402f82cb83243af4916c3311c3eb1.1628072837.git.deren.wu@mediatek.com/]
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

arm64: tizen_bcm2711_defconfig: Add enable mt7921u defconfig

Enable mt7921u defconfig for wifi-6e usb interface.

Change-Id: I8bc6b0731cf1257603e683ffe385d42a0c488b37
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

mt76-6e-usb: mt7921u: Add support Netgear AXE3000(A8000) device

Added Netgear AXE3000 (A8000) usb_device_id to mt7921u_device_table[]

Issue: Though the Netgear AXE3000 (A8000) is based on the mt7921
chipset because of the unique USB VID:PID combination this device
does not initialize/register. Thus making it not plug and play.

Fix: Adds support for the Netgear AXE3000 (A8000) based on the Mediatek
mt7921au chipset. The method of action is adding the USD VID/PID
pair to the mt7921u_device_table[] array.

Notes: A retail sample of the Netgear AXE3000 (A8000) yeilds the following
from lsusb D 0846:9060 NetGear, Inc. Wireless_Device. This pair
0846:9060 VID:PID has been reported by other users on Github.

Signed-off-by: Reese Russell <git@qrsnap.io>
Change-Id: I321a0753c80563da4dab97cf69e319e901cbf7f7
[Patch url: https://patchwork.kernel.org/project/linux-wireless/patch/20230123090555.21415-1-git@qrsnap.io/]
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

mediatek: mt76-6e-usb Fix to build error

Copied entire code from v5.18.y, fix build error that occurred.

Signed-off-by: astsam <info@no-problem.cc>
Change-Id: Icb2c24cc3d81cb14a2dc8db6e1208d2ba42cec17
[Patch url: https://github.com/astsam/mt7921/commit/98007d648b31581e2fa99069c4319f820cbbc30a\]
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

mediatek: Add version option to support wifi-6e usb

Add version kconfig and makefile option to support wifi-6e usb.

Change-Id: I9cf0b7035942fd62018ec6c104f9371b03bf1099
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

mediatek: mt76-6e-usb: Copied entire code from v5.18.y

Copied entire code to 'mt76-6e-usb' from kernel v5.18.y
'drivers/net/wireless/mediatek/mt76', for support wifi-6e usb
interface.

repo: https://github.com/raspberrypi/linux.git
kernel version: 5.18.19
last commit: d83fb0cdf903 media: i2c: arducam-pivariety: Add custom controls

Change-Id: I60f7382cd84bc47fbebc899a82d4c46c2e14e628
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

ARM: tizen_bcm2711_*defconfig: Enable USB_GSPCA_ZC3XX defconfig

To support GSPCA family usb webcam, enable CONFIG_USB_GSPCA_ZC3XX.

Change-Id: I471d6c079b2bb802248028219ba2c585149a1532
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

drm/vc4: Workaround for crtc scanout device problem

Currently, the crtc device does not start a scanout, the time of
vblank is always calculated as future value. As a workaround, always
change vpos to a positive number.

Change-Id: I9d9efa473f530b519637a7497c6a41f5e3c9b541
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

tizen_bcm2711_defconfig: Enable dm-bow

This enables device mapper driver to allow checkpoint & restore on ext4
partitions.

Signed-off-by: Mateusz Moscicki <m.moscicki2@samsung.com>
[sw0312.kim: sync with savedefconfig]
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
[mszyprow: added changes to *_rt_defconfig]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Iba3831159515bffa387210111a3fbbe733b62eef

device-mapper: Add dm-bow

dm-bow is a device mapper driver that allows to create a checkpoint on
the volume so that it is possible to restore the state if necessary.
This is needed to protect the ext4 partition during a system upgrade in
case of a power failure.

Originally-by: Paul Lawrence <paullawrence@google.com>
Origin: https://android.googlesource.com/kernel/common/+/refs/heads/android-mainline/drivers/md/dm-bow.c
Signed-off-by: Mateusz Moscicki <m.moscicki2@samsung.com>
[mszyprow: fixed compile issue]
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Change-Id: Id521bd9f609fdc4a55837da8e1388800f375e8a5

rpi4: boot: Update the firmwares for kernel v5.15.82 (fix booting issue)

When connected to 4k hdmi, the issue of not reading the emmc
intermittently during booting has been resolved this firmware version.

The updated files comes from https://github.com/raspberrypi/firmware.git
master branch, commit(0a7ea7028461 firmware: arm_loader: PWM1 is not available on GPIO 45)

Change-Id: Ie03b4d2f6f9d72774458254d9e5a330d28b28928
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

packaging: enable NBD module

This will allow for booting with a remote NBD device for development
purposes with a special initrd stage (will be introduced in a separate
package).

Change-Id: I6149f3eaed4b9fb2fd61b5e471b4882efd66f9ae
Signed-off-by: Marek Pikuła <m.pikula@partner.samsung.com>

Partially Revert "brcmfmac: p2p: Deal with set but unused variables"

This partially reverts commit 2de64ca7c9fadd32b261530592db4a6adbfcb53f.

The commit 61325dc073e2 ("Revert "brcmfmac: move configuration of
probe request IEs"") requires vif set with p2p interface, but commit
2de64ca7c9fa removes setting. Partially revert the commit to support
p2p usage with p2p interface.

Change-Id: Iaa3a6c57bb9e14c80ef9f4714eea0cfc447d6adc
Reported-by: Jiung Yu <jiung.yu@samsung.com>
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

Bluetooth: Add LE connection parameter update

Add support for BT_LE_CONN_PARAM in l2cap socket.

Change-Id: I2ed693da26ba2d3464b9997bf1880c6c136055cd
Signed-off-by: Anuj Jain <anuj01.jain@samsung.com>

drm/vc4: Add gem_info node via debugfs for vc5

The memps requires gem_info with gem_names to analyze graphics shared
memory, so this patch adds gem_info node via common helpers for
debugfs.

Let's save pid/tgid in private file data only once when gem object is
created or prime_fd is imported and use them on gem_info. This is to
solve the wrong pid problem of gem_info created as different processes
share fd of drm device node.

The prime fd created in vc4, but handled in v3d, modified to hanle
this in vc4.

Change-Id: Ideab3ecf282b77247f9b3706ee7e46747b2d0762
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

drm/vc4: hdmi: Fix hotplug extcon uevent to works

There is a problem that extcon uevent does not work hdmi hotplug, so
fixed to works.

Change-Id: Ic22bfd25c6ebf951832c6687b68dfcda286a833d
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

AsoC: ac108: revert use of fallthrough pseudo-keywoard

This reverts commit 6a9dc5fd6170 ("lib: Revert use of fallthrough pseudo-keyword in lib/")
Now, use the fallthrough instead of /* fall through */

Change-Id: I1199d05f5830aa169f393c51310d4cbd699c79b1
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

script: build-rpi4: Update script to clarify build errors

Update script to clarify build errors, also do not remove dtb files to
eliminate unnecessary rebuilds.

Change-Id: I34685c2b0dfa25d79a79795b24d18a64465ed4a3
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

rpi4: boot: Update the firmwares for kernel v5.15.79

The updated files comes from https://github.com/raspberrypi/firmware.git
master branch, commit(b8a7365c70c6 kernel: Bump to 5.15.79)

Change-Id: I610b9a125231a79e423a29cc2033203c7c9b262a
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

packaging: Change the kernel version of the spec file

Change the kernel version to 5.15.79

Change-Id: I962339d32b22bc8eee4c7e3da37a834f8a406bb2
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

scripts: mkbootimg_rpi4: Fix url path for u-boot of rpi4

Fix url path for u-boot-rpi4.

Change-Id: I786de5c89da600d84cd48849cfd0def6806893c5
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

packaging: add perf package for perf tool and traceevent plugins

Add perf package for perf tool and its traceevent plugins.

Note: they are built from below directories.
- perf: tools/perf
- traceevent plugins: tools/lib/traceevent

Change-Id: Ia154b6fd85dbc65f2ca3c5af018cc86cd6061f9d
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

brd: Support for BLKFLSBUF

To support brd flush to free ramdisk brd_mutex is required. also to
free ramdisk memory, BLKFLSBUF support is required. this commit has
been modified to match the interface of the kernel v5.15.

This reverts commit 15f7b41f70ddcca3b555bd0fdc7c8da7466b517e.
This reverts commit ff26956875c2f05e12ecec9938411a2c7dfc767d.

Change-Id: Idde4b352924a0d8bd1c606b6da171f333dfb4f70
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

brd: Support discard

To support ramdisk flush, discard is required. So, revert the commit.
Also, this commit has been modified to match the interface of the
kernel v5.15.

This reverts commit f09a06a193d942a12c1a33c153388b3962222006.

Change-Id: Ic66d8331b63e96ed35ae7ca48cb7c7349559ea58
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

Revert "block: don't call into the driver for BLKFLSBUF"

Revert that commit for use with the blkdev_flushbuf ioctl.

This reverts commit 4a9d6d667f0bafed55a9e9f5ae8bceb3680749d7.

Change-Id: Ibba5ecdff7c0d3402a220005856a28783c36cc86
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

Revert "block: don't call into the driver for BLKROSET"

Revert that commit for use with the blkdev_flushbuf ioctl.

This reverts commit 732e12d805a77f74c907c0a28ece271ef1e81e01.

Change-Id: Ic0f44db39cc4bfd68a69a677949c3913763f2b88
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

Revert "block: remove __blkdev_driver_ioctl"

Revert that commit for use with the blkdev_flushbuf ioctl.

This reverts commit a7cb3d2f09c8405aed59d97a7d02cebea43cd3c7.

Change-Id: Idd8b165ea6c83ecbacdb697afa0532414b330360
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

ASoC: seeed-voicecard: Fix to not use asoc_simple_parse_xxx()

Interface changed since kernel v5.13, modified to not use
asoc_simple_parse_xxx().

Ref patch:
Link: https://lore.kernel.org/r/87pmz0wf9u.wl-kuninori.morimoto.gx@renesas.com
Change-Id: I6131e214b44427f4e9a79e53e36947270599b72e
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

ARM: tizen_bcm2711_defconfig: Add AC108 and SEEED configs

Add support 4channels mic volume.

Change-Id: I69cea4e7fe731dbe84a490aa4872dfc08d6ccbaa
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

arm64: tizen_bcm2711_defconfig: Add AC108 and SEEED configs

Add support 4channels mic volume.

Change-Id: Ib8e132a0d225143b7479b50ceeb2f79bc82e9ff0
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

arm: dts: bcm2711-rpi-4-b: Adds buttons for speaker profile

Tizen Speaker Profile uses a keypad that consists of 5 buttons for
up/down/left/right/center. The buttons are connected to GPIO pins as
follows.

GPIO16 : KEY_VOLUMEUP
GPIO13 : KEY_VOLUMEDOWN
GPIO6 : KEY_FASTFORWARD
GPIO12 : KEY_REWIND
GPIO25 : KEY_PLAYPAUSE

Signed-off-by: Jaechul Lee <jcsing.lee@samsung.com>
 Conflicts:
arch/arm/boot/dts/bcm2711-rpi-4-b.dts

Change-Id: I25bffde7c669c0572496ec3adbd4240fb2ed49cd
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

arm: dts: bcm2711-rpi-4-b: Adds respeaker 4mic nodes

adds respeaker 4mic nodes.

Change-Id: I79bf8b7860d53e7c88fa1b37ef2af5cdc0532840
Signed-off-by: Jaechul Lee <jcsing.lee@samsung.com>

ASoC: ac108: Fix changed interface

Fix changed interface and incorrectly used structure member names.

Change-Id: Ic22bf7d6651537d63f85ad8ba54e429a44874311
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

ASoC: ac108: fix build warning about '-Wimplict-fallthrough'

Fix build warning about '-Wimplicit-fallthrough'.

In file included from ./include/linux/acpi.h:15,
                 from ./include/linux/i2c.h:13,
                 from sound/soc/codecs/ac108.c:21:
sound/soc/codecs/ac108.c: In function 'ac108_set_fmt':
./include/linux/device.h:1758:5: warning: this statement may fall through [-Wimplicit-fallthrough=]

Change-Id: I89c995e338d2c2afbcc61d49495b406df76e17ab
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

ASoC: seeed-voicecard: Fix init and parse func

When we rebase the kernel version to v5.x, the interface changed and
a build error occurred. Modify the interface for card init and parse.

This patch is already been reviewd from [1].

[1]
  "Commit: ASoC: ac108: Adds ac108 codec and machine code"
  "Change-Id: Idd1fd85a461c3f2ac03192ec49bf527601d797b7"

Change-Id: Ib90e267e665fa910c1b4b7038375155dbea14d1f
Signed-off-by: Jaechul Lee <jcsing.lee@samsung.com>
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

ASoC: ac108: Fixes kernel bug message when starting to capture

The code in the trigger function is moved to prepare function that is
called right before trigger function. clock operation would be ran by
parepare function without disabling preemption.

BUG: scheduling while atomic: arecord/1244/0x00000004
Preemption disabled at:
[<ffffff80087c4a08>] snd_pcm_stream_lock+0x30/0x68

Call trace:
[<ffffff800808b250>] dump_backtrace+0x0/0x270
[<ffffff800808b4e4>] show_stack+0x24/0x30
[<ffffff8008ae87c4>] dump_stack+0xac/0xe8
[<ffffff80080cc814>] __schedule_bug+0x7c/0xd8
[<ffffff8008afb558>] __schedule+0x718/0x880
[<ffffff8008afb6fc>] schedule+0x3c/0xa0
[<ffffff8008aff028>] schedule_timeout+0x190/0x408
[<ffffff8008afc4b8>] wait_for_common+0xa8/0x150
[<ffffff8008afc5c4>] wait_for_completion_timeout+0x2c/0x38
[<ffffff80086e5a0c>] bcm2835_i2c_xfer+0x16c/0x400
[<ffffff80086deedc>] __i2c_transfer+0x12c/0x570
[<ffffff80086df38c>] i2c_transfer+0x6c/0xc0
[<ffffff80086df430>] i2c_master_send+0x50/0x68
[<ffffff8008584454>] regmap_i2c_write+0x34/0x70
[<ffffff800857fe34>] _regmap_raw_write+0x7cc/0x7e0
[<ffffff800857feb8>] _regmap_bus_raw_write+0x70/0x88
[<ffffff800857ea48>] _regmap_write+0x70/0x160
[<ffffff800857ec10>] _regmap_update_bits+0xd8/0xf8
[<ffffff80085800b0>] regmap_update_bits_base+0x68/0x98
[<ffffff8008805838>] ac10x_update_bits+0x48/0x88
[<ffffff8008805c00>] ac108_trigger+0x118/0x130

Change-Id: Ib0f5edc86d363005abd75f989d732e917617f3fe
Signed-off-by: Jaechul Lee <jcsing.lee@samsung.com>

ASoC: ac108: Adds default 4channels mic volume

It needs to be set default volume to max value.

Change-Id: Ibee68a2885925ec8a3c1ce12c6fa0f7ff8c98dfb
Signed-off-by: Jaechul Lee <jcsing.lee@samsung.com>

ASoC: ac108: Adds ac108 codec and machine code

adds respeaker machine code and ac101/ac108 codec code.

ReSpeaker driver
https://github.com/respeaker/seeed-voicecard

Change-Id: I30e687bef34f1e579d1646db43d9835a470df16f
Signed-off-by: Jaechul Lee <jcsing.lee@samsung.com>

packaging: remove headers_check in spec file

Remove headers_check in spec file.
When build the current version, WARNING message is displayed.

[   64s] =================== WARNING ===================
[   64s] Since Linux 5.5, 'make headers_check' is no-op,
[   64s] and will be removed after Linux 5.15 release.
[   64s] Please remove headers_check from your scripts.
[   64s] ===============================================

Change-Id: I62aebbe5dae0d5909eefb518ff26dd99ce91ee3e
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

rpi4: boot: config: Add dwc2-tizen driver config

Add dwc2-tizen driver config for using dwc2-tizen dts by overlays dtb.

Alwo, If dwc2 mode is set to otg, forcing dwc2 mode as peripheral is
proceeded in the early boot time, but since tizen configures the gadget
with configfs after system is prepared. It causes enumeration problem.
To prevent it, default mode will be fixed as peripheral. Actully, since
type-c usb port is only used as power-source and peripheral port, it is
more precise setting though.

Change-Id: I53266309475c397db14f212d81ee64ec1d933a45
Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com>
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

overlays: Add dwc2-tizen-overlay

Add g-extcon-always-on value,
Set extcon state for dwc2 cable as always true.

Change-Id: Ibfdeb4a022f3be3e584ceaf1ac2f3f7e2fd88499
Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com>
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

misc: tizen-inform_reboot: Fix to use kernel_write function

Fixed to use kernel_write instead of vfs_write. When using vfs_write,
there is a problem that the user buffer cannot be accessed.

Change-Id: Idb549b9c833188c585395af8191090dda8a5dc4c
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

misc: tizen-inform-reboot: Remove force_uaccess begin and end func

Configuration SET_FS is disabled, so this feature is not required.

Change-Id: I349afbd8d2a97aada87080d477cf5ca38d7016c9
Link: https://lore.kernel.org/r/20201202131558.39270-10-mark.rutland@arm.com
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

ARM/arm64: tizen_bcm2711_rt_defconfig: Enable NOP_USB_XCEIV defconfig

Enable NOP_USB_XCEIV defconfig for UBS_PHY defconfig.

Change-Id: I1e39da1a7d915e241f542edb87019f9ed649e8c3
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

ARM: tizen_bcm2711_defconfig: Enable NOP_USB_XCEIV defconfig

Enable NOP_USB_XCEIV defconfig for UBS_PHY defconfig.

Change-Id: I49f8c93e403d333b9aba54239807aa5ef740ebc9
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

arm64: tizen_bcm2711_defconfig: Enable NOP_USB_XCEIV defconfig

Enable NOP_USB_XCEIV defconfig for UBS_PHY defconfig.

Change-Id: Ib87795a3296000710a1d2724d9b2816a8680e414
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

rpi4: boot: config: Add display_auto_detect config for mipi dsi

Automatically load overlays for detected DSI displays.
Support touchscreen panel(mipi dsi vc4-kms-dsi-7inch).

Change-Id: I479d7bf8c371237b69d7901ec16c12cb714eb1d9
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

packaging: Add kernel dtb overlays

Add kernel dtb overlays into boot partition.

Change-Id: I81449ca04ed865a2eb7e846a70fac23e9ab1d9e1
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

rpi4: boot: config: Add vc4-kms-v3d-pi4 dtoverlays

Add vc4-kms-v3d-pi4 dtoverlays.

Change-Id: I7c3fdb210e61b436925d6541c668f60a6feb64c2
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

scripts: mkbootimg_rpi4: Add overlays dtbo

Add overlays dtbo into boot partition.

Change-Id: Ifb1b01c2e48119492ee16971249e15bf768ba74a
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

ARM: tizen_bcm2711_defconfig: Sync with savedefconfig

With kernel v5.15.73.

Change-Id: I78ef64316bea6f9862be9005b73866c4d429a226
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

arm64: tizen_bcm2711_defconfig: Sync with savedefconfig

With kernel v5.15.73.

Change-Id: I0f1457b382c0119f3b6bd968afda2aa0e9d65aa5
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

ARM/arm64: tizen_bcm2711_rt_defconfig: Sync with savedefconfig

With kernel v5.15.73.

Change-Id: Ia555ce50808a02335811544335514101c6218ac9
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

usb: serial: cp210x: Fix return type to void

Fix return type to void for fix build error.

Change-Id: I507ea7aa5566ccdda17e69a60cc86ff756f0830a
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

drm/v3d: Add gpu_gem_info node via debugfs

Add gpu_gem_info node via debugfs of dri debug sysfs for each
process with pid/tgid and its gem objects. Same gem object can be
opened from multiple processes, so from the gpu_gem_info node,
it can print same gem in multiple lines.

Ported from the commit dea4ace78ec7 ("drm/vc4: Add gem_info node
via debugfs") to v3d.

NOTE: From Raspberry Pi 4 board, v3d gpu is card0 and also render node
in dri card128, so accessing can be from both nodes. For render fixed
node, it is /sys/kernel/debug/dri/128/gpu_gem_info.
Also, Raspberry Pi 4 board gives entire gem count and total size with
/sys/kernel/debug/dri/128/bo_stats.

Change-Id: Ica09a3b92010e15dddc0a7ca117d4544106757f7
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

mm: LKSM: fix a bug in the filter length calculation

Since type of a size variable in the calculation of the
filter length is signed integer, it can make a buggy
situation when the size of a vma is bigger than a range
of a signed integer variable. In this case, the size is
treated as a negative number. As a result, it incurs a
kernel bug at BUG_ON(size < 0).

This patch changes types of variables and members in
lksm_region data structure from signed integer to unsigned
long. Additionally, remove an assertion BUG_ON(size < 0)
because the size never be a negative number.

Change-Id: I822a2ba5d372596ee55dcbec90a019fdf1dc2416
Signed-off-by: Sung-hun Kim <sfoon.kim@samsung.com>

ARM/ARM64: tizen_bcm2711: enable CONFIG_RTL8192CU_VENDOR

Enable CONFIG_RTL8192CU_VENDOR as module.

Change-Id: Ic3e8954b432bafda47b50dbc1f30c922035435b1
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

net: rtl8192cu: fix wrong configuration in Makefile

RTL8192CU_VENDOR is to distinguish with mainline and non-mainlne.
RTL8192CU_VENDOR is for non-mainline. So it needs to use
CONFIG_RTL8192CU_VENDOR instead of CONFIG_RTL8182CU.

It's why rtl8192cu dongle doesn't work in RPI4 target.

Change-Id: I93a50f5db3a965fdb4d8ee1e5a70d3956d5f6679
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

ARM64: tizen_bcm2711_defconfig: enable configs reelvant to RT2800USB

To use USB Wifi, enable configs relevant to RT2800USB.

Change-Id: Ib0b0f6f65d0e2a6420e2fd220a29fcccbce68c94
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

ARM/ARM64: tizen_bcm2711_defconfig: Enable RT_GROUP_SCHED config

Enable RT_GROUP_SCHED configuration to use the cgroup scheduling.

Change-Id: Iab166b7ab312a780b77316118194af1999abc4fb
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

USB: serial: cp210x: add cp210x-stlink driver

Support usb st-link device and its application, add fixed
version of cp210x driver.

Change-Id: Ic1d1a54723697cabf55545d708e2e92f8caddee2
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

ARM/ARM64: tizen_bcm2711_defconfig: Enable BT_HCIBTUSB config

Enable CONFIG_BT_HCIBTUSB config.
Tizen GHI image is using the USB BT device. To test BT, it needs to enable.

Change-Id: Ic1a233dd10978ee6cd7b9535c4cf240352605bd6
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

script: update build-rpi4 script to support RT kernel build

Update build-rpi4 script to support RT kernel build.

Change-Id: I6f6e8e7579b4ae10defc4110949135f0459871ed
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

packaging: change a file name to _localversion-rt

Change a file name from localversion-rt to _localversion-rt.

Change-Id: I3a8663aa8f3baab6006c554aafaa13b090b72471
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

spec: Build rt packages

Build a second set of packages with PREEMPT_RT enabled

Change-Id: I1c0ec964f68eda41d6c628b0476a5246045171ad
Signed-off-by: Łukasz Stelmach <l.stelmach@samsung.com>

Add tizen_bcm2711_rt_defconfig for arm and arm64

Add defconfigfiles with PREEMPT_RT enabled

Change-Id: I58b17d42cfa35ba9bd24c8109cd71f33fe3cd7be
Signed-off-by: Łukasz Stelmach <l.stelmach@samsung.com>

printk: suppress printing less important messages to console

Suppress printing to console messages with loglevel above the
console_loglevel via print_sync().

Change-Id: Ia8d53fd2fadb74e323d776f053c91f7832402021
Fixes: 5d6a5a2378db ("patch-5.10.100-rt62.patch")
Signed-off-by: Łukasz Stelmach <l.stelmach@samsung.com>

patches-5.15.92-rt57

Apply PREEMPT_RT patches-5.15.92-rt57.tar.gz.

Change-Id: If9209d9d4856aac47d3ac54111e1348c941bbbc6
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

usb: gadget: f_fs: Prevent panic due to failure of huge size buffer allocation

The f_fs daemons usually use large size buffer for increasing transfer
performance, but it can cause memory allocation failure in case of
that buddy space is fragmented. Since this, instead of just returning
error in this case, give the chance to retry to allocate memory with
a half length in order to prevent daemon crash due to failure of
buffer allocation.

Change-Id: I4df1987a6f07e558772dcc5f6f020cc550fb1b13
Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com>
 Conflicts:
drivers/usb/gadget/function/f_fs.c

Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

WORKAROUND: Revert "staging: bcm2835-codec: Format changed should trigger drain"

This reverts commit b7e6b495eff31298ba4665f71b2414cc9a8f99c2.

When setting last buffer done on format changed event, bcm2835-codec does not
work for decoding because it recognizes there is no queued buffer even it is
not well fit for v4l2 codec spec. Maybe it is because v4l2 codec gst plugin
v4l2 usage is not up to date in tizen. Until properly fixing it, revert it
to support video h/w decoding on rpi4 in tizen.

Change-Id: Id7d77ee57e58d42eab5a080d63eb8eb1518e6f7a
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

Revert "cgroup: Disable cgroup "memory" by default"

This reverts commit 2b13c54592135b6fab269517ed687fa9f80bf8e5.

The feature is used for saving memory which is consumed by memcg-related
structure (32bytes per 4K page), but now it is no longer merged on the
latest raspberry pi kernel. So instead of enabling memory cgroup by
adding command to cmdline.txt while preserving this feature, in order to
enable memory cgroup by default, this reverts commit '2b13c5459213
("cgroup: Disable cgroup "memory" by default")'

Change-Id: I1830129125fb44b36bfe64f97fddf329ea795c3c
Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com>
Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>

kdbus: export needed symbols for out-of-tree support

We have been asked to move kdbus out-of-tree. It uses a couple
unexported symbols, so we need to (grudgingly) export them.

Change-Id: Ide04c46bbc71f8fffbdefca68959e1048af1c905
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>

kdbus: Revert "fs: unexport poll_schedule_timeout"

This reverts commit 8f546ae1fc5ce8396827d4868c7eee1f1cc6947a.

Change-Id: I5429471eeb092c55a50e37c0b642d50d69daebc7
Signed-off-by: Łukasz Stelmach <l.stelmach@samsung.com>

packaging: Added '.gbs.conf' for partial build

Added gbs configuration file for enhanced building.
it makes gbs build faster than before.

https://source.tizen.org/documentation/reference/git-build-system/maintenance-models-supported-gbs

Change-Id: I79d57aa5eb49d0fbfa9a3744ec2acb032a274e5e
Signed-off-by: Jaechul Lee <jcsing.lee@samsung.com>
Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>

ARM: tizen_bcm2711_defconfig: Enable defconfig for touchscreen

Required defconfig for 7inch touchscreen operation.

Change-Id: I428d3569ec09e20a8cc44df2b41c00446710059a
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

arm64: tizen_bcm2711_defconfig: Enable defconfig for touchscreen

Required defconfig for 7inch touchscreen operation.

Change-Id: I19a35976e0e7782a79275f56c14ebdba82099ec3
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

packaging: Change the kernel version of the spec file

Change the kernel version to 5.10.95

Change-Id: Ia92dc3b1750e4cc693608bdc06f8bb32efcc8722
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

ARM: tizen_bcm2711_defconfig: Enable vc4_hdmi_cec

CEC driver is required for hdmi operation.

Change-Id: I4f6333945affe0230c78d38e456f5daee91883f2
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>

arm64: tizen_bcm2711_defconfig: Enable vc4_hdmi_cec

CEC driver is required for hdmi operation.

Change-Id: I2b63797641163a4da088b492c05c3d957fbaa208
Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>