Create fixup.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: I0af333fc5985734696edc1674bb30506ad6b003a

Change-Id: I1f9a33e9d94ee7d458fc1178a8d6549be93da61d

Create fixup.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: I170eb5df215ffbae4b4399b4b1e209fc7ab59de3

Create fixup.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: Id75b3ef1421713b67ba747f1287fb7e28100c355

Add files required for check metadata script.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: I220b9d920980ac56cca9f1353ab17a4577db1d10

Create fixup.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: I4ba3dd0932fdd44e5b6860fd885cc45a6ee4b7ae

Create fixup.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: Iaeaa46c4f8dbe49668804c0697b45a87b970aebd

Create fixup.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: I94bcefbfbf32b6be896c0e88f3e70b84fbfa42dc

Create fixup.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: I2a6cdfc3906285d21e7f38c55f949cbc2c7f5849

Create fixup.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: I7ceb963d73839c9d14d63e882871d5e179898a83

mt8183-kukui-jacuzzi has an anx7625 bridge connected to the output of
its DSI host. However, after commit fd0310b6 ("drm/bridge: anx7625:
add MIPI DPI input feature"), a bus-type property started being required
in the endpoint node by the driver to indicate whether it is DSI or DPI.

Add the missing bus-type property and set it to 5
(V4L2_FWNODE_BUS_TYPE_PARALLEL) so that the driver has its input
configured to DSI and the display pipeline can probe correctly.

While at it, also set the data-lanes property that was also introduced
in that same commit, so that we don't rely on the default value.

Fixes: fd0310b6 ("drm/bridge: anx7625: add MIPI DPI input feature")
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Link: https://lore.kernel.org/r/20220214200507.2500693-1-nfraprado@collabora.com


Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
(cherry picked from commit 32568ae3)

BUG=b:209930699
TEST=check display on kingler

Signed-off-by: Linux Patches Robot <linux-patches-robot@chromeos-missing-patches.google.com.iam.gserviceaccount.com>
Change-Id: Ibd3a204ac550914168c6dc4586f6c71b8a307c68

We need to compile mediatek soc thermal driver.

Generated by:

cat <<EOF | tee -a \
   chromeos/config/arm64/chromiumos-arm64.flavour.config
   chromeos/config/arm64/chromiumos-mediatek.flavour.config

CONFIG_MTK_THERMAL=y
CONFIG_MTK_SOC_THERMAL=y

EOF

./chromeos/scripts/kernelconfig olddefconfig

BUG=b:206305724
TEST=boot kukui and check thermal reading is normal

Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
Change-Id: I716fbd1562fc0c5b514c3250b8cebcf494840d7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/3279174


Commit-Queue: Tzung-Bi Shih <tzungbi@chromium.org>
Reviewed-by: Tzung-Bi Shih <tzungbi@chromium.org>

This reverts commit 2d4bcf88.

This reverts commit 2873cd31.

Create fixup.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: I8be1a57c3db6612a7f8b32f6cbcee1fb70c14acb

Create fixup.

Signed-off-by: Łukasz Bartosik <ukaszb@google.com>
Change-Id: Id97577c8160a966dd0371e25bab4cf8343f47938

cpuinfo_x86.x86_max_dies is introduced in commit 7745f03e
("x86/topology: Add CPUID.1F multi-die/package support") and then
removed in commit 14d96d6c
("x86/topology: Create topology_max_die_per_package()").

Remove the obsolete cpuinfo_x86.x86_max_dies description.

Fixes: 14d96d6c ("x86/topology: Create topology_max_die_per_package()")
Reviewed-by: Len Brown <len.brown@intel.com>
Signed-off-by: Zhang Rui <rui.zhang@intel.com>
(am from https://patchwork.kernel.org/patch/12944427/)
(also found at https://lore.kernel.org/r/20220816051633.17775-9-rui.zhang@intel.com

)

BUG=b:239519025
TEST=None

Signed-off-by: Srihari Uttanur <srihari.uttanur@intel.corp-partner.google.com>
Change-Id: Ic3278d07fbb67b5910fcdd595b6e762e5795f19f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/3832289


Commit-Queue: Victor Ding <victording@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Tested-by: Altaf Basha <altaf.basha@intel.com>
Reviewed-by: Sean Paul <sean@poorly.run>
Reviewed-by: Victor Ding <victording@chromium.org>
Commit-Queue: Sam McNally <sammc@chromium.org>

smp_num_siblings/cpuinfo_x86.x86_max_cores are retrieved via CPUID EAX
bit_shift value, and they represent the maximum possible number of threads
in a core, and the maximum possible number of cores in a package.

Update the smp_num_siblings/cpuinfo_x86.x86_max_cores description in the
documentation.

Reviewed-by: Len Brown <len.brown@intel.com>
Signed-off-by: Zhang Rui <rui.zhang@intel.com>
(am from https://patchwork.kernel.org/patch/12944432/)
(also found at https://lore.kernel.org/r/20220816051633.17775-8-rui.zhang@intel.com

)

BUG=None
TEST=None

Signed-off-by: Srihari Uttanur <srihari.uttanur@intel.corp-partner.google.com>
Change-Id: Ib41b0163d88205f061ed88062d9eaa380c4f7c76
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/3832288


Reviewed-by: Sean Paul <sean@poorly.run>
Tested-by: Altaf Basha <altaf.basha@intel.com>
Commit-Queue: Victor Ding <victording@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: Victor Ding <victording@chromium.org>
Commit-Queue: Sam McNally <sammc@chromium.org>

This patch adds the specification for /sys/devices/.../coredump_disabled
attribute which allows the userspace to enable/disable devcoredump for a
particular device and drivers can use it to enable/disable functionality
accordingly. It is available when the CONFIG_DEV_COREDUMP is enabled and
driver has implemented the .coredump() callback.

Signed-off-by: Manish Mandlik <mmandlik@google.com>
Reviewed-by: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
(am from https://patchwork.kernel.org/patch/12940739

)

BUG=b:154866409
TEST=Build

Change-Id: I5622b2a92dca4d2703a0f747e24f3ef19303e6df
Signed-off-by: Manish Mandlik <mmandlik@google.com>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/3763750


Reviewed-by: Abhishek Pandit-Subedi <abhishekpandit@google.com>
Tested-by: Manish Mandlik <mmandlik@chromium.org>
Reviewed-by: Sean Paul <sean@poorly.run>
Commit-Queue: Manish Mandlik <mmandlik@chromium.org>

BUG=b:230648523
TEST=none

Signed-off-by: Brian Norris <briannorris@chromium.org>
Change-Id: I6dc03aded7234a0459f4750a7c0c5e3693434d4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/3615720


Reviewed-by: Guenter Roeck <groeck@chromium.org>

0-day reports:

ld: kernel/watchdog.o: in function `set_sample_period':
kernel/watchdog.c:250: undefined reference to `watchdog_update_hrtimer_threshold'

watchdog_update_hrtimer_threshold is only declared if both
CONFIG_HARDLOCKUP_CHECK_TIMESTAMP and CONFIG_HARDLOCKUP_DETECTOR_PERF
are enabled. Fix dependencies.

BUG=None
TEST=Test builds

Change-Id: Ibe575dfbc7f3eca86c4a96d20f945857fa96cd6f
Disallow-Recycled-Builds: test-failures
Signed-off-by: Guenter Roeck <groeck@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/3335762


Reviewed-by: Martin Faltesek <mfaltesek@google.com>
Commit-Queue: Martin Faltesek <mfaltesek@google.com>

This is the final patch in FUTEX_SWAP patchset. It
adds a test/benchmark to validate behavior and
compare performance of a new FUTEX_SWAP futex operation.

Detailed API design and behavior considerations are provided
in the commit messages of the previous two patches.

Signed-off-by: Peter Oskolkov <posk@google.com>
(am from https://lore.kernel.org/patchwork/patch/1277906/)
(also found at https://lore.kernel.org/r/20200722234538.166697-4-posk@posk.io

)

BUG=b:170967073
TEST=eve-kernelnext and manual verification with selftests

Signed-off-by: Brian Geffon <bgeffon@chromium.org>
Change-Id: I2b5b87a7f7ba3d4a7f604fc2e127941822090fe6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/2476742


Reviewed-by: Sean Paul <seanpaul@chromium.org>
Reviewed-by: Joel Fernandes <joelaf@google.com>

This tree is generated by gentoo tools and should be ignored by git.

Tested by observing that git does ignore the top level build/ tree,
but does report build/ subtrees within the kernel tree.

Review URL: http://codereview.chromium.org/2512002

Change-Id: Ic631c4f151f3ecaa1112b0129bf5841e9e1b3ba0

The Linux kernel codebase currently doesn't come close to following
Google's "inclusive language" terminology guidelines. Rather than trip
up the pre-upload checks on preexisting terminology, let's just opt out
for now.

BUG=none
TEST=pre-upload.py

Change-Id: Id83ed8aa4b0698eae0e593a5558dc9e0cfac3bfb
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/3027437


Reviewed-by: Dmitry Torokhov <dtor@chromium.org>

Change-Id: I5cdb716f4f1a0c65107930023790edbd9cb73ead

Send notifications when the label becomes active after an idle period.
Send netlink message notifications in addition to sysfs notifications.
Using a uevent with
  subsystem=xt_idletimer
  INTERFACE=...
  STATE={active,inactive}

This is backport from common android-3.0
commit: beb914e987cbbd368988d2b94a6661cb907c4d5a
with uevent support instead of a new netlink message type.

[CPNOTE: 20/07/21] Lee: Pinged the bug

Bug: 120445672
Change-Id: I31677ef00c94b5f82c8457e5bf9e5e584c23c523
Signed-off-by: Ashish Sharma <ashishsharma@google.com>
Signed-off-by: JP Abgrall <jpa@google.com>
[adelva: Folded the following changes into this patch:
         ee0b238fada5 ("netfilter: xt_IDLETIMER: time-stamp and suspend/resume handling.")
         728c058a495e ("netfilter: xt_IDLETIMER: Adds the uid field in the msg")
         5ebea489d44c ("netfilter: xt_IDLETIMER: Fix use after free condition during work")
         5ab69d7ba2c5 ("netfilter: xt_IDLETIMER: Use fullsock when querying uid")]
Signed-off-by: Alistair Delva <adelva@google.com>
[maennich: Folded the following changes into this patch:
           03f7b06dd871 ("ANDROID: nf: IDLETIMER: Fix possible use before initialization in idletimer_resume")]
Signed-off-by: Matthias Maennich <maennich@google.com>

Before 5.10-rc1, the upstream kernel blocked any compat calls into XFRM
code with EOPNOTSUPP, however Android kernels had been patching this
check out and made userspace match the 64-bit kernel netlink format
instead.

When the new XFRM_USER_COMPAT feature landed, it added a similar check
in two places which returns EOPNOTSUPP only if the XFRM_USER_COMPAT
feature is disabled, however that is currently always the case for
Android kernels and we do not want to filter these callers.

While we work to remove the userspace compatibility mess, disable the
filtering of compat calls when XFRM_USER_COMPAT is disabled. If the
XFRM_USER_COMPAT feature is enabled, nothing changes.

[CPNOTE: 20/07/21] Lee: Pinged the author via the bug

Bug: 163141236
Bug: 172541864
Signed-off-by: Alistair Delva <adelva@google.com>
Change-Id: Ifbea109070650dfcb4f93a3cc692c18a8d11ab44

Currently, IPv6 router discovery always puts routes into
RT6_TABLE_MAIN. This causes problems for connection managers
that want to support multiple simultaneous network connections
and want control over which one is used by default (e.g., wifi
and wired).

To work around this connection managers typically take the routes
they prefer and copy them to static routes with low metrics in
the main table. This puts the burden on the connection manager
to watch netlink to see if the routes have changed, delete the
routes when their lifetime expires, etc.

Instead, this patch adds a per-interface sysctl to have the
kernel put autoconf routes into different tables. This allows
each interface to have its own autoconf table, and choosing the
default interface (or using different interfaces at the same
time for different types of traffic) can be done using
appropriate ip rules.

The sysctl behaves as follows:

- = 0: default. Put routes into RT6_TABLE_MAIN as before.
- > 0: manual. Put routes into the specified table.
- < 0: automatic. Add the absolute value of the sysctl to the
       device's ifindex, and use that table.

The automatic mode is most useful in conjunction with
net.ipv6.conf.default.accept_ra_rt_table. A connection manager
or distribution could set it to, say, -100 on boot, and
thereafter just use IP rules.

[CPNOTE: 20/07/21] Lee: Asked Lorenzo for status via the bug

Signed-off-by: Lorenzo Colitti <lorenzo@google.com>
[AmitP: Refactored original changes to align with
        the changes introduced by upstream commits
        830218c1 ("net: ipv6: Fix processing of RAs in presence of VRF"),
        8d1c802b ("net/ipv6: Flip FIB entries to fib6_info").

        Also folded following android-4.9 commit changes into this patch
        be65fb01da4d ("ANDROID: net: ipv6: remove unused variable ifindex in")]
Bug: 120445791
Change-Id: I82d16e3737d9cdfa6489e649e247894d0d60cbb1
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>

Explicitly set what is visible to userspace

Bug: 196046570
Test: passed netd test suites
Signed-off-by: Todd Kjos <tkjos@google.com>
Change-Id: Iacec0ef8ae290e01f1b60508d8abcd40a3653c83

Initialize message buffer for quota2_log to avoid sending
random data.

Bug: 196046570
Test: passed netd test suites
Fixes: 10cda83a ("ANDROID: netfilter: xt_quota2: adding the
original quota2 from xtables-addons")
Signed-off-by: Todd Kjos <tkjos@google.com>
Change-Id: Ic9f34aaa2593809b375fc649b74567190c99dc62

Make sure string only contains the characters specified by userspace.

Fix cherry-picked from xtables-extensions project

Signed-off-by: Sam Liddicott <sam@liddicott.com>
Bug: 196046570
Test: passed netd test suites
Fixes: 10cda83a ("ANDROID: netfilter: xt_quota2: adding the
original quota2 from xtables-addons")
Signed-off-by: Todd Kjos <tkjos@google.com>
(cherry picked from https://git.code.sf.net/p/xtables-addons/xtables-addons
bc2bcc383c70b293bd816c29523a952ca8736fb5)
Change-Id: I965448564906e5fbf0fe6d6414f44d9e257ea195

xt_quota in the kernel is plain broken:
  - counts quota at a per CPU level
    (was written back when ubiquitous SMP was just a dream)
  - provides no way to count across IPV4/IPV6.

Therefore this patch adds xt_quota2, derived from
"extensions/xt_quota2.c" from xtables-addons
(https://sourceforge.net/projects/xtables-addons

)
at commit e84391ce665cef046967f796dd91026851d6bbf3.

[CPNOTE: 20/07/21] Lee: Poked the bug

Bug: 120445421
Change-Id: I19d49858840effee9ecf6cff03c23b45a97efdeb
Signed-off-by: JP Abgrall <jpa@google.com>
[adelva: Folded 4d33aa305871 ("netfilter: xt_quota2: fixup the quota2,
         and enable.") into this patch]
Signed-off-by: Alistair Delva <adelva@google.com>
[maennich: Folded eab89421 ("ANDROID: fix kernelci build-break")
           into this patch]
Signed-off-by: Matthias Maennich <maennich@google.com>
[ebiggers: Folded in the following commits:
           8a35207f ("ANDROID: fix up xt_quota2 for proc_ops changes")
           91e5e077 ("ANDROID: move up spin_unlock_bh() ahead of remove_proc_entry()").
           b20eacd8 ("ANDROID: fix a bug in quota2")
           Also updated the commit message.]
Signed-off-by: Eric Biggers <ebiggers@google.com>

When using the PF_KEY interface, SHA-256 hashes are hardcoded to
use 96-bit truncation. This is a violation of RFC4868, which
specifies 128-bit truncation, but will not be fixed upstream due
to backwards compatibility concerns and because the PF_KEY
interface is deprecated in favour of netlink XFRM (which allows
the app to specify an arbitrary truncation length).

Change the hardcoded truncation length from 96 to 128 so that
PF_KEY apps such as racoon will work with standards-compliant VPN
servers.

[CPNOTE: 20/07/21] Lee: Rejected upstream due to backward capability issues

Bug: 34114242
Bug: 120440497
Signed-off-by: Lorenzo Colitti <lorenzo@google.com>
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I8ee2ac9bb577b5078e8565a5b1f5fd84c2b3f74f

Allows a file system to provide its own fs-verity implementation
but still to hook into the signature check and control file from
fs-verity

[CPNOTE: 20/07/21] Lee: Requested an update from Paul via the OoT bug
[CPNOTE: 21/07/21] Lee: Depends on upstreaming of IncFS

Bug: 160634504
Bug: 170978993
Test: incfs_test running on this + subsequent changes
Signed-off-by: Paul Lawrence <paullawrence@google.com>
Change-Id: I02020af460d62fa5eb459a083419208e175005e8

Avoid waking up every thread sleeping in an epoll_wait call during
suspend and resume by calling a freezable blocking call.  Previous
patches modified the freezer to avoid sending wakeups to threads
that are blocked in freezable blocking calls.

This call was selected to be converted to a freezable call because
it doesn't hold any locks or release any resources when interrupted
that might be needed by another freezing task or a kernel driver
during suspend, and is a common site where idle userspace tasks are
blocked.

[CPNOTE: 20/07/21] Lee: Pinged the bug for status

Bug: 77139736
Bug: 120440023
[ccross: This was upstream (https://lkml.org/lkml/2013/5/6/823), but
         reverted because it reportedly caused memory corruption on
         32-bit x86 (https://patchwork.kernel.org/patch/3162301/).

]
Acked-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Colin Cross <ccross@android.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
[gregkh: add this back after the 5.11-rc1 merge mess]
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: Ia8268d310c00f0cfa6c01f36f3fa528e04f206e0

Increase drm property count from 24 to 64 to make
room for custom properties of drm plane and drm
crtc objects.

[CPNOTE: 19/07/21] Lee: Pinged for status on the bug
[CPNOTE: 21/07/21] Lee: Code only supports vendor's features - no upstream user

Signed-off-by: Shashank Babu Chinta Venkata <sbchin@codeaurora.org>
Bug: 139653858
Change-Id: I3e42c1fc684d7d7cea828fc35b96673bdef598f4

Minigbm uses dumb ioctls when the virtio gpu is in 2D mode. This
changes allows those calls to pass the permission checks in
drm_ioctl_permit().

[CPNOTE: 19/07/21] Lee: This was due for removal - pinged the bug for an update

Bug: b/123764798
Test: booted cuttlefish on drm stack w/o 3d
Change-Id: I872ba8f6d0a284127178dd60f8a2048e5e7397fb
Signed-off-by: Jason Macnak <natsu@google.com>
Signed-off-by: Alistair Delva <adelva@google.com>

This driver presents a standard USB audio class interface to the host
and an ALSA PCM device to userspace

[CPNOTE: 19/07/21] Lee: Should be re-written to use upstream APIs - pinged Badhri

Bug: 78114713
Bug: 120441124
[badhri: f_audio_source is being migrated to userspace.]
Change-Id: If16b14a5ff27045f9cb2daaf1ae9195c5eeab7d0
Signed-off-by: Mike Lockwood <lockwood@google.com>
[AmitP: Folded following android-4.9 commit changes into this patch
        Parts of e27543931009 ("ANDROID: usb: gadget: Fixes and hacks to make android usb gadget compile on 3.8")
        i6d9285e2574a ("ANDROID: usb: gadget: f_audio_source:replace deprecated API")]
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
[adelva: Folded the following changes into this patch:
         ddfd0c4070c1 ("ANDROID: usb: gadget: f_audio_source: Move to USB_FUNCTION API")
         a3ab81aaa19e ("ANDROID: usb: gadget: f_audio_source: Move gadget functions code")
         2095c953d894 ("ANDROID: usb: gadget: f_audio_source: change max ISO packet size")
         8671b3e53638 ("ANDROID: usb: gadget: f_audio_source: Fixed USB Audio Class Interface Descriptor")
         af98f36edbe2 ("ANDROID: usb: gadget: f_audio_source: disable the CPU C-states upon playback")
         a830751a338e ("CHROMIUM: usb: gadget: f_audio_source: add .free_func callback")]
Signed-off-by: Alistair Delva <adelva@google.com>

Android frameworks relies on the alsa
config reported by the f_midi device.

[CPNOTE: 19/07/21] Lee: Should be re-written to use upstream APIs - pinged Badhri

Bug: 111003288
Bug: 120441124
Change-Id: I0695e00b166fd953f50acea93802245b0d5a5240
[badhri: The framework should be moved away from this]
Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>

USB accessory mode allows users to connect USB host hardware
specifically designed for Android-powered devices. The accessories
must adhere to the Android accessory protocol outlined in the
http://accessories.android.com

 documentation. This allows
Android devices that cannot act as a USB host to still interact with
USB hardware. When an Android device is in USB accessory mode, the
attached Android USB accessory acts as the host, provides power
to the USB bus, and enumerates connected devices.

[CPNOTE: 19/07/21] Lee: Should be re-written to use upstream APIs - pinged Badhri

Bug: 63740241
Bug: 120441124
Bug: 223101878
Change-Id: I67964b50d278f3c0471d47efbb7b0973a3502681
[badhri: f_accessory is being migrated to userspace.]
Signed-off-by: Mike Lockwood <lockwood@android.com>
[AmitP: Folded following android-4.9 commit changes into this patch
        ceb2f0aac624 ("ANDROID: usb: gadget: accessory: Fix section mismatch")
        Parts of e27543931009 ("ANDROID: usb: gadget: Fixes and hacks to make android usb gadget compile on 3.8")
        1b07ec751563 ("ANDROID: drivers: usb: gadget: 64-bit related type fixes")]
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
[adelva: Folded the following changes into this patch:
         9d5891d516e2 ("ANDROID: usb: gadget: f_accessory: Add ACCESSORY_SET_AUDIO_MODE control request and ioctl")
         dc66cfce9622 ("ANDROID: usb: gadget: f_accessory: Add support for HID input devices")
         5f1ac9c2871b ("ANDROID: usb: gadget: f_accessory: move userspace interface to uapi")
         9a6241722cd8 ("ANDROID: usb: gadget: f_accessory: Enabled Zero Length Packet (ZLP) for acc_write")
         31a0ecd5a825 ("ANDROID: usb: gadget: f_accessory: check for accessory device before disconnecting HIDs")
         580721fa6cbc ("ANDROID: usb: gadget: f_accessory: Migrate to USB_FUNCTION API")
         7f407172fb28 ("ANDROID: usb: gadget: f_accessory: Fix for UsbAccessory clean unbind.")
         ebc98ac5a22f ("ANDROID: usb: gadget: f_accessory: fix false disconnect due to a signal sent to the reading process")
         71c6dc5ffdab ("ANDROID: usb: gadget: f_accessory: assign no-op request complete callbacks")
         675047ee68e9 ("ANDROID: usb: gadget: f_accessory: Move gadget functions code")
         b2bedaa5c7df ("CHROMIUM: usb: gadget: f_accessory: add .raw_request callback")]
Signed-off-by: Alistair Delva <adelva@google.com>
[maennich: Folded the following patch in this patch:
           f4f6f40e ("ANDROID: usb: gadget: Fix dependency for f_accessory")]
Signed-off-by: Matthias Maennich <maennich@google.com>
[ebiggers: Folded in the following commit:
           fd734b5e ("ANDROID: USB: f_accessory: Check dev pointer before decoding ctrl request")]
Signed-off-by: Eric Biggers <ebiggers@google.com>
         ANDROID: usb: gadget: f_accessory: add compat_ioctl support