The mainline device trees lack the "st,syscfg-pdds", so probing the
driver always throws the warning. As the property is optional per binding
and the driver can deal with its absence, demote the warning to info log
level.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Link: https://lore.kernel.org/r/20200224172519.15315-1-a.fatoum@pengutronix.de
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Clang errors:
drivers/remoteproc/mtk_scp.c:364:14: error: incompatible function
pointer types initializing 'void *(*)(struct rproc *, u64, size_t)' (aka
'void *(*)(struct rproc *, unsigned long long, unsigned int)') with an
expression of type 'void *(struct rproc *, u64, int)' (aka 'void
*(struct rproc *, unsigned long long, int)')
[-Werror,-Wincompatible-function-pointer-types]
.da_to_va = scp_da_to_va,
^~~~~~~~~~~~
1 error generated.
Make the same change as commit 0fcbb369f052 ("remoteproc: Use size_t
type for len in da_to_va"), which was not updated for the acceptance of
commit 63c13d61ea ("remoteproc/mediatek: add SCP support for mt8183").
Fixes: 0fcbb369f052 ("remoteproc: Use size_t type for len in da_to_va")
Link: https://github.com/ClangBuiltLinux/linux/issues/927
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
Link: https://lore.kernel.org/r/20200310211514.32288-1-natechancellor@gmail.com
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Now that remoteproc can load an elf64, coredump elf class should be
the same as the loaded elf class. In order to do that, add a
elf_class field to rproc with default values. If an elf is loaded
successfully, this field will be updated with the loaded elf class.
Then, the coredump core code has been modified to use the generic elf
macro in order to create an elf file with correct class.
Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Clement Leger <cleger@kalray.eu>
Link: https://lore.kernel.org/r/20200302093902.27849-9-cleger@kalray.eu
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Now that rproc_elf_sanity_check can be used by external drivers, allow
to only overwrite the sanity_check member of rproc_ops. This will allow
drivers to handle elf32 and elf64 by overwriting sanity_check with
rproc_elf_sanity_check function.
Signed-off-by: Clement Leger <cleger@kalray.eu>
Link: https://lore.kernel.org/r/20200302093902.27849-8-cleger@kalray.eu
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
In order to support elf64, use macros from remoteproc_elf_helpers.h
to access elf headers depending on elf class.
To allow new drivers to support elf64, add rproc_elf_sanity_check
function which make more sense than adding a elf64 named one since
it will support both elf versions.
Driver which need to support both elf32/elf64 should use this new
function for elf sanity check instead of the elf32 one.
Signed-off-by: Clement Leger <cleger@kalray.eu>
Tested-by: Arnaud POULIQUEN <arnaud.pouliquen@st.com>
Link: https://lore.kernel.org/r/20200302093902.27849-7-cleger@kalray.eu
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Since this function will be modified to support both elf32 and elf64,
rename the existing one to elf32 (which is the only supported format
at the moment). This will allow not to introduce possible side effect
when adding elf64 support (ie: all backends will still support only
elf32 if not requested explicitely using rproc_elf_sanity_check).
Signed-off-by: Clement Leger <cleger@kalray.eu>
Link: https://lore.kernel.org/r/20200302093902.27849-6-cleger@kalray.eu
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
elf32 and elf64 mainly differ by their types. In order to avoid
copy/pasting the whole loader code, generate static inline functions
which will access values according to the elf class. It allows to
keep a common loader basis.
In order to accommodate both elf types sizes, the maximum size for a
elf header member is chosen using the maximum value of the field for
both elf class.
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Signed-off-by: Clement Leger <cleger@kalray.eu>
Link: https://lore.kernel.org/r/20200302093902.27849-5-cleger@kalray.eu
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
elf64 entry is defined as a u64. Since boot_addr is used to store the
elf entry point, change boot_addr type to u64 to support both elf32
and elf64. In the same time, fix users that were using this variable.
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Clement Leger <cleger@kalray.eu>
Link: https://lore.kernel.org/r/20200302093902.27849-4-cleger@kalray.eu
[bjorn: Fixes up return type of rproc_get_boot_addr()]
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Now that rproc_da_to_va uses a size_t for length, use a size_t for len
field of rproc_mem_entry. Function used to create such structures now
takes a size_t instead of int to allow full size range to be handled.
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Signed-off-by: Clement Leger <cleger@kalray.eu>
Link: https://lore.kernel.org/r/20200302093902.27849-3-cleger@kalray.eu
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
With upcoming changes in elf loader for elf64 support, section size will
be a u64. When used with da_to_va, this will potentially lead to
overflow if using the current "int" type for len argument. Change
da_to_va prototype to use a size_t for len and fix all users of this
function.
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Signed-off-by: Clement Leger <cleger@kalray.eu>
Link: https://lore.kernel.org/r/20200302093902.27849-2-cleger@kalray.eu
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Fix the following warnings when documentation is built:
drivers/remoteproc/remoteproc_virtio.c:330: warning: Function parameter
or member 'id' not described in 'rproc_add_virtio_dev'
drivers/remoteproc/remoteproc_core.c:243: warning: Function parameter
or member 'name' not described in 'rproc_find_carveout_by_name'
drivers/remoteproc/remoteproc_core.c:473: warning: Function parameter
or member 'offset' not described in 'rproc_handle_vdev'
drivers/remoteproc/remoteproc_core.c:604: warning: Function parameter
or member 'offset' not described in 'rproc_handle_trace'
drivers/remoteproc/remoteproc_core.c:678: warning: Function parameter
or member 'offset' not described in 'rproc_handle_devmem'
drivers/remoteproc/remoteproc_core.c:873: warning: Function parameter
or member 'offset' not described in 'rproc_handle_carveout'
drivers/remoteproc/remoteproc_core.c:1029: warning: cannot understand function
prototype: 'rproc_handle_resource_t rproc_loading_handlers[RSC_LAST] = '
drivers/remoteproc/remoteproc_core.c:1693: warning: Function parameter
or member 'work' not described in 'rproc_crash_handler_work'
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Link: https://lore.kernel.org/r/20200212161956.10358-1-arnaud.pouliquen@st.com
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
On secure devices after a wdog/fatal interrupt, the mba region has to be
refreshed in order to prevent the following errors during mba load.
Err Logs:
remoteproc remoteproc2: stopped remote processor 4080000.remoteproc
qcom-q6v5-mss 4080000.remoteproc: PBL returned unexpected status -284031232
qcom-q6v5-mss 4080000.remoteproc: PBL returned unexpected status -284031232
....
qcom-q6v5-mss 4080000.remoteproc: PBL returned unexpected status -284031232
qcom-q6v5-mss 4080000.remoteproc: MBA booted, loading mpss
Fixes: 7dd8ade24d ("remoteproc: qcom: q6v5-mss: Add custom dump function for modem")
Cc: stable@vger.kernel.org
Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
Tested-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Link: https://lore.kernel.org/r/20200304194729.27979-4-sibis@codeaurora.org
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
The code used to sync with the MBA after each segment loaded and this is
still what's done downstream. So reduce the delta towards downstream by
switching to a model where the content is iteratively validated.
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
Tested-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Link: https://lore.kernel.org/r/20200304194729.27979-3-sibis@codeaurora.org
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Trying to reclaim mpss memory while the mba is not running causes the
system to crash on devices with security fuses blown, so leave it
assigned to the remote on shutdown and recover it on a subsequent boot.
Fixes: 6c5a9dc248 ("remoteproc: qcom: Make secure world call for mem ownership switch")
Cc: stable@vger.kernel.org
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
Tested-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Link: https://lore.kernel.org/r/20200304194729.27979-2-sibis@codeaurora.org
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Overlapping header include additions in macsec.c
A bug fix in 'net' overlapping with the removal of 'version'
string in ena_netdev.c
Overlapping test additions in selftests Makefile
Overlapping PCI ID table adjustments in iwlwifi driver.
Signed-off-by: David S. Miller <davem@davemloft.net>
The imx SC api strongly assumes that messages are composed out of
4-bytes words but some of our message structs have odd sizeofs.
This produces many oopses with CONFIG_KASAN=y.
Fix by marking with __aligned(4).
Fixes: 666aed2d13 ("clk: imx: scu: add set parent support")
Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
Link: https://lkml.kernel.org/r/aad021e432b3062c142973d09b766656eec18fde.1582216144.git.leonard.crestez@nxp.com
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
The imx SC api strongly assumes that messages are composed out of
4-bytes words but some of our message structs have odd sizeofs.
This produces many oopses with CONFIG_KASAN=y.
Fix by marking with __aligned(4).
Fixes: fe37b48204 ("clk: imx: add scu clock common part")
Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
Link: https://lkml.kernel.org/r/10e97a04980d933b2cfecb6b124bf9046b6e4f16.1582216144.git.leonard.crestez@nxp.com
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
I copy/pasted these macros and forgot to update the argument
names and where they're passed to. Fix it so that these macros make
sense.
Reported-by: Maxime Ripard <maxime@cerno.tech>
Fixes: 194efb6e26 ("clk: gate: Add support for specifying parents via DT/pointers")
Signed-off-by: Stephen Boyd <sboyd@kernel.org>
Link: https://lkml.kernel.org/r/20200325022257.148244-1-sboyd@kernel.org
Tested-by: Maxime Ripard <mripard@kernel.org>
At present, on Power systems with Protected Execution Facility
hardware and an ultravisor, a KVM guest can transition to being a
secure guest at will. Userspace (QEMU) has no way of knowing
whether a host system is capable of running secure guests. This
will present a problem in future when the ultravisor is capable of
migrating secure guests from one host to another, because
virtualization management software will have no way to ensure that
secure guests only run in domains where all of the hosts can
support secure guests.
This adds a VM capability which has two functions: (a) userspace
can query it to find out whether the host can support secure guests,
and (b) userspace can enable it for a guest, which allows that
guest to become a secure guest. If userspace does not enable it,
KVM will return an error when the ultravisor does the hypercall
that indicates that the guest is starting to transition to a
secure guest. The ultravisor will then abort the transition and
the guest will terminate.
Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Ram Pai <linuxram@us.ibm.com>
The current codebase makes use of the zero-length array language
extension to the C90 standard, but the preferred mechanism to declare
variable-length types such as these ones is a flexible array member[1][2],
introduced in C99:
struct foo {
int stuff;
struct boo array[];
};
By making use of the mechanism above, we will get a compiler warning
in case the flexible array does not occur last in the structure, which
will help us prevent some kind of undefined behavior bugs from being
inadvertently introduced[3] to the codebase from now on.
Also, notice that, dynamic memory allocations won't be affected by
this change:
"Flexible array members have incomplete type, and so the sizeof operator
may not be applied. As a quirk of the original implementation of
zero-length arrays, sizeof evaluates to zero."[1]
This issue was found with the help of Coccinelle.
[1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html
[2] https://github.com/KSPP/linux/issues/21
[3] commit 7649773293 ("cxgb3/l2t: Fix undefined behaviour")
Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
Link: https://lore.kernel.org/r/20200319195046.GA452@embeddedor.com
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Moving to support aarch32 mode on aarch64 hardware, need to drop
the dependency on ARM64 to make the driver could be selected for
ARM32.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
Link: https://lore.kernel.org/r/1584070036-26447-2-git-send-email-peng.fan@nxp.com
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
For each prog/btf load we allocate and free 16 megs of verifier buffer.
On production systems it doesn't really make sense because the
programs/btf have gone through extensive testing and (mostly) guaranteed
to successfully load.
Let's assume successful case by default and skip buffer allocation
on the first try. If there is an error, start with BPF_LOG_BUF_SIZE
and double it on each ENOSPC iteration.
v3:
* Return -ENOMEM when can't allocate log buffer (Andrii Nakryiko)
v2:
* Don't allocate the buffer at all on the first try (Andrii Nakryiko)
Signed-off-by: Stanislav Fomichev <sdf@google.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: Andrii Nakryiko <andriin@fb.com>
Link: https://lore.kernel.org/bpf/20200325195521.112210-1-sdf@google.com
Has been unused since commit ef99b02b23 ("libbpf: capture value in BTF
type info for BTF-defined map defs").
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Reviewed-by: Quentin Monnet <quentin@isovalent.com>
Acked-by: Andrii Nakryiko <andriin@fb.com>
Link: https://lore.kernel.org/bpf/20200325113655.19341-1-tklauser@distanz.ch
It's a follow-up for discussion in [1].
drgn tool bpf_inspect.py was merged to drgn repo in [2]. Document it
in kernel tree to make BPF developers aware that the tool exists and
can help with getting BPF state unavailable via UAPI.
For now it's just one tool but the doc is written in a way that allows
to cover more tools in the future if needed.
Please refer to the doc itself for more details.
The patch was tested by `make htmldocs` and sanity-checking that
resulting html looks good.
v2 -> v3:
- two sections: "Description" and "Getting started" (Daniel);
- add examples in "Getting started" section (Daniel);
- add "Customization" section to show how tool can be customized.
v1 -> v2:
- better "BPF drgn tools" section (Alexei)
[1] https://lore.kernel.org/bpf/20200228201514.GB51456@rdna-mbp/T/#mefed65e8a98116bd5d07d09a570a3eac46724951
[2] https://github.com/osandov/drgn/pull/49
Signed-off-by: Andrey Ignatov <rdna@fb.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Link: https://lore.kernel.org/bpf/20200324185135.1431038-1-rdna@fb.com
The default handling of the gpio-line-names property by the
gpiolib-of implementation does not work with the multiple
gpiochip banks per device structure used by the gpio-brcmstb
driver.
This commit adds driver level support for the device tree
property so that GPIO lines can be assigned friendly names.
Signed-off-by: Doug Berger <opendmb@gmail.com>
Link: https://lore.kernel.org/r/1583780521-45702-1-git-send-email-opendmb@gmail.com
Acked-by: Gregory Fong <gregory.0xf0@gmail.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Remove some of the outmoded "Why KUnit" rationale, and move some
UML-specific information to the kunit_tool page. Also update the Getting
Started guide to mention running tests without the kunit_tool wrapper.
Signed-off-by: David Gow <davidgow@google.com>
Reviewed-by: Frank Rowand <frank.rowand@sony.com>
Acked-by: Shuah Khan <skhan@linuxfoundation.org>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
A few of the lists used in the linked-list KUnit tests (the
for_each_entry{,_reverse} tests) are declared 'static', and so are
not-reinitialised if the test runs multiple times. This was not a
problem when KUnit tests were run once on startup, but when tests are
able to be run manually (e.g. from debugfs[1]), this is no longer the
case.
Making these lists no longer 'static' causes the lists to be
reinitialised, and the test passes each time it is run. While there may
be some value in testing that initialising static lists works, the
for_each_entry_* tests are unlikely to be the right place for it.
Signed-off-by: David Gow <davidgow@google.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Pull 5.7 NVMe updates from Keith.
* 'nvme-5.7-rc1' of git://git.infradead.org/nvme: (42 commits)
nvme: cleanup namespace identifier reporting in nvme_init_ns_head
nvme: rename __nvme_find_ns_head to nvme_find_ns_head
nvme: refactor nvme_identify_ns_descs error handling
nvme-tcp: Add warning on state change failure at nvme_tcp_setup_ctrl
nvme-rdma: Add warning on state change failure at nvme_rdma_setup_ctrl
nvme: Fix controller creation races with teardown flow
nvme: Make nvme_uninit_ctrl symmetric to nvme_init_ctrl
nvme: Fix ctrl use-after-free during sysfs deletion
nvme-pci: Re-order nvme_pci_free_ctrl
nvme: Remove unused return code from nvme_delete_ctrl_sync
nvme: Use nvme_state_terminal helper
nvme: release ida resources
nvme: Add compat_ioctl handler for NVME_IOCTL_SUBMIT_IO
nvmet-tcp: optimize tcp stack TX when data digest is used
nvme-fabrics: Use scnprintf() for avoiding potential buffer overflow
nvme-multipath: do not reset on unknown status
nvmet-rdma: allocate RW ctxs according to mdts
nvmet-rdma: Implement get_mdts controller op
nvmet: Add get_mdts op for controllers
nvme-pci: properly print controller address
...
Report event FAN_DIR_MODIFY with name in a variable length record similar
to how fid's are reported. With name info reporting implemented, setting
FAN_DIR_MODIFY in mark mask is now allowed.
When events are reported with name, the reported fid identifies the
directory and the name follows the fid. The info record type for this
event info is FAN_EVENT_INFO_TYPE_DFID_NAME.
For now, all reported events have at most one info record which is
either FAN_EVENT_INFO_TYPE_FID or FAN_EVENT_INFO_TYPE_DFID_NAME (for
FAN_DIR_MODIFY). Later on, events "on child" will report both records.
There are several ways that an application can use this information:
1. When watching a single directory, the name is always relative to
the watched directory, so application need to fstatat(2) the name
relative to the watched directory.
2. When watching a set of directories, the application could keep a map
of dirfd for all watched directories and hash the map by fid obtained
with name_to_handle_at(2). When getting a name event, the fid in the
event info could be used to lookup the base dirfd in the map and then
call fstatat(2) with that dirfd.
3. When watching a filesystem (FAN_MARK_FILESYSTEM) or a large set of
directories, the application could use open_by_handle_at(2) with the fid
in event info to obtain dirfd for the directory where event happened and
call fstatat(2) with this dirfd.
The last option scales better for a large number of watched directories.
The first two options may be available in the future also for non
privileged fanotify watchers, because open_by_handle_at(2) requires
the CAP_DAC_READ_SEARCH capability.
Link: https://lore.kernel.org/r/20200319151022.31456-15-amir73il@gmail.com
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
For FAN_DIR_MODIFY event, allocate a variable size event struct to store
the dir entry name along side the directory file handle.
At this point, name info reporting is not yet implemented, so trying to
set FAN_DIR_MODIFY in mark mask will return -EINVAL.
Link: https://lore.kernel.org/r/20200319151022.31456-14-amir73il@gmail.com
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
The signed 1 bit bitfields should be unsigned, so make them unsigned.
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
Link: https://lore.kernel.org/r/20200325132913.110115-1-colin.king@canonical.com
Signed-off-by: Mark Brown <broonie@kernel.org>
This adds Bluetooth support on Nexus 5, USB on Xperia Z1 and defines
gpio-ranges throughout the various gpio-controllers.
-----BEGIN PGP SIGNATURE-----
iQJPBAABCAA5FiEEBd4DzF816k8JZtUlCx85Pw2ZrcUFAl5xpGUbHGJqb3JuLmFu
ZGVyc3NvbkBsaW5hcm8ub3JnAAoJEAsfOT8Nma3FPNUQALMV/qh54J3eHFrqfNDv
rGWO2jpYXKftCHeg46DQ/Mi8nswZHNqa7zGbFvIlooVHZFELfKs4bAU8ndgDa+gj
DCSXZO7SoUmn5Vd+WfkKzqsPOP2tPK8eTyQPNTdyKHPqi9q+8zA93fJOZuqg2lRE
CdQiEpg+y1WuKCJriXK0Qwtxe066DpyGM4I72vQhTf/f9Sv1ltCuqNhRMxw8gpjM
wR5LhZC9fAmUGPUt4QTHgzygkHvou+mRKCfQi1cRbWBnN9+aKgnBMi+JwuKrarT7
gsP9Ja1g9YlKCXSVIEpjVYWM+bovyMRvy79InZd1BQW5+pAZlE+rH5zOXd6rU1Ks
9JBiWGESy6McEo1TFi8APMUddGnYktwWAtMeHWrVFAczbU6hdnrhcediKR7Mer/y
UTu7U1kwvqOcZ0F85kXNnpqYteno3cG/J2J5BVc03k0lb2DxnkMuO1lQtROLjkuI
fqo84xtG2hpuJkKFVcJbG8GewniC3Xy52esPf5bnzkw1kU4HGS/hvpEg+mIWlBbT
5+l9wE1pBm0hEbT4GyIIXmBaEKGe4PfVGhZiaxY8P6d7RyjF3iHiaITQ6UzBbBBH
NKNJVk7AtFRFqpfLQVhPCf/yi7qh6pzOeTtBKTq+wEzUHsk7GVRXrglAIsk1YTuf
qclhE/zuP7xngMAcscUoEBdg
=1cGm
-----END PGP SIGNATURE-----
Merge tag 'qcom-dts-for-5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into arm/dt
Qualcomm ARM dts updates for v5.7
This adds Bluetooth support on Nexus 5, USB on Xperia Z1 and defines
gpio-ranges throughout the various gpio-controllers.
* tag 'qcom-dts-for-5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux:
ARM: dts: qcom: add gpio-ranges property
ARM: dts: qcom: msm8974-hammerhead: add support for bluetooth
ARM: dts: qcom: msm8974: add blsp2_uart10
ARM: dts: qcom: msm8974-honami: Add USB node.
Link: https://lore.kernel.org/r/20200318044305.GE470201@yoga
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Recent series of patches targeting broadwell boards, while enabling
SOF, changed behavior for non-SOF solutions. In essence replacing
platform 'dummy' with actual 'platform' causes redundant stream
initialization to occur during audio start. hw_params for haswell-pcm
destroys initial stream right after its creation - only to recreate it
again from proceed from there.
While harmless so far, this flow isn't right and should be corrected.
The actual need for dummy components for SSP0 link is questionable but
that issue is subject for another series.
Fixes: a40acc6bfc ("ASoC: Intel: bdw-rt5650: change cpu_dai and platform components for SOF")
Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Link: https://lore.kernel.org/r/20200325131611.545-4-cezary.rojewski@intel.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Recent series of patches targeting broadwell boards, while enabling
SOF, changed behavior for non-SOF solutions. In essence replacing
platform 'dummy' with actual 'platform' causes redundant stream
initialization to occur during audio start. hw_params for haswell-pcm
destroys initial stream right after its creation - only to recreate it
again from proceed from there.
While harmless so far, this flow isn't right and should be corrected.
The actual need for dummy components for SSP0 link is questionable but
that issue is subject for another series.
Fixes: 4865bde187 ("ASoC: Intel: bdw-rt5677: change cpu_dai and platform components for SOF")
Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Link: https://lore.kernel.org/r/20200325131611.545-3-cezary.rojewski@intel.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Recent series of patches targeting broadwell boards, while enabling
SOF, changed behavior for non-SOF solutions. In essence replacing
platform 'dummy' with actual 'platform' causes redundant stream
initialization to occur during audio start. hw_params for haswell-pcm
destroys initial stream right after its creation - only to recreate it
again from proceed from there.
While harmless so far, this flow isn't correct and should be corrected.
The actual need for dummy components for SSP0 link is questionable but
that issue is subject for another series.
Link to first message in conversation:
https://lkml.org/lkml/2020/3/18/54
Fixes: 64df6afa0d ("ASoC: Intel: broadwell: change cpu_dai and platform components for SOF")
Reported-by: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Link: https://lore.kernel.org/r/20200325131611.545-2-cezary.rojewski@intel.com
Signed-off-by: Mark Brown <broonie@kernel.org>
- Rename the IDE nodes to match the YAML schema
- Add a temperature zone to the DIR-685, use hard drive
as sensor and cool the case using the fan.
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEElDRnuGcz/wPCXQWMQRCzN7AZXXMFAl51Qf4ACgkQQRCzN7AZ
XXOCuQ//V2YDq/C1Xlq3+ffUoAvdXV4iiJHjdpASkCfrUA97AJYD8beHkZ3GMJI+
yYpclrvr1yfVeI5X9zGKKJ81driivFDUx0wmVzb9OMw1AiQHIIbKznqpA6UWCzsj
2mZlILSPLZs9BixLLiE72PP7xWb3xkycT/s6TOuY8IzpweMuhFtsS4Z/YqYyWODI
UNIrRUG6LPhCkPngfqAkl0EzCvp9mqcus/fiBBm0RSwEUP4V5k26JpGTmW2ZCbOS
Opxw97xKMzHHhhAIOGoV0cDpYXZ/dCBwPXA7oNKXXXSrv78oVoB9+A31nEBks73o
IC+XPT+V1LGsgQksXv1bIrtTrRqIa+ay1oAB+cMnVNCJ9q/Ya4fIenYjvikjExvY
P9NLZKuYRL1jxlzscL+X7hEDUszzSLkrl/Od8X8D4J8Dt0saPfvM09nlfnOY4ZxM
bBiNB9mwZZTeHZH09cGkBK0e+j1NCmue8jDXy4X//u0bQqAue/gncRwLh7t9p1YP
92l11vJuhZOHs3DeLnqLK6ynzLuyf7lPBop2FsBYN17UyR1BnlG2TWC+60hikpt1
aG0At5MwGzCurcwRPtUEBmD1TsNgZPvKbM+UusldpsK1Wx0mV8bJwgf4dXHLx9Ap
67CchCbdTvRsmufoTyZouGGSx+WQp0GPBPdZ2rd4iLgoqqXztCs=
=/Tw7
-----END PGP SIGNATURE-----
Merge tag 'gemini-dts-v5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik into arm/dt
Gemini DTS changes for v5.7:
- Rename the IDE nodes to match the YAML schema
- Add a temperature zone to the DIR-685, use hard drive
as sensor and cool the case using the fan.
* tag 'gemini-dts-v5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik:
ARM: dts: gemini: Add thermal zone to DIR-685
ARM: dts: gemini: Rename IDE nodes
Link: https://lore.kernel.org/r/CACRpkdbvgqCVuoMCHJrCZ0J+3NrwdrBnwBz+BJrSE=hqYh2j+Q@mail.gmail.com
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
- add real time clock node
mt8173:
- mark arch timer invalid in suspend
mt8183:
- add CPU idle states
- add watchdog node
- add dynamic power coefficient and cooling cells for all CPUs
mt8516:
- add basic support for the SoC
- add basic support for the pumpkin board
-----BEGIN PGP SIGNATURE-----
iQJLBAABCAA1FiEEUdvKHhzqrUYPB/u8L21+TfbCqH4FAl50pDsXHG1hdHRoaWFz
LmJnZ0BnbWFpbC5jb20ACgkQL21+TfbCqH5Wqg/+LWQAEdCFKwCscc/t6L7J1FoI
oywTgYJe4sO8VjPQu0AiVvpgLw8lZf73+om0g5zsG04CzuZEK44vR4P3g8hZ7bhv
qpFj1YEiV7QK9dMuqDRGbSUg6gFf5zlwjHgEEhYV7GRkLV5L5IsxbUwUWRDnxtrC
p4bHbyPIy88y00IdpCSZaKP+5uTxl2K4LE1AvYOpyY9usNM2fHU8Mb6+fEpd/Ai2
9bVxM8B6a861D7fNXrbHBG13H2wZDcPS8QkTlp/IfoWQnGvj3ZaE5KfO/fbdHIJQ
xAqjZWk60RiWGDJFPFOl1uVuMxgTGcGnBXedW5UzpahdH+9HmPEElzxnt8NasNNB
17ZcJLhYnBfg5pl3FUQ7utwzC+8OaXOON6ZWvBG7avgJ2xumAM8B8hVXA6dyIjUp
RGPCqUAZj6x+yBO42YFS6BT+SbjImPc3WmdCqjpGLeueeXsLEQ55H1YkXjMMGrkx
q52avNWrUHrJrH8mJDhWN0lzW5yltzVlyUTle0g7joFX3ux5uCGnwTE14OmYyAYf
IHi2D8TCj3N1zZdp8wz4nwFzIjsc538vjS1how331azjjYC4DCMFIB6sX4kBALqV
Rss7HII6szBjKQY9wf7eDs4D5n4Gxtq1RN8tm78qVjo5NXZirLiyW4d2mn4moAM6
8eL5IcBN1/XUrDLIBjU=
=8cRs
-----END PGP SIGNATURE-----
Merge tag 'v5.6-next-dts64' of git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux into arm/dt
mt2712:
- add real time clock node
mt8173:
- mark arch timer invalid in suspend
mt8183:
- add CPU idle states
- add watchdog node
- add dynamic power coefficient and cooling cells for all CPUs
mt8516:
- add basic support for the SoC
- add basic support for the pumpkin board
* tag 'v5.6-next-dts64' of git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux:
arm64: dts: add RTC nodes for MT2712
arm64: dts: mediatek: add pumpkin board dts
arm64: dts: mediatek: add dtsi for MT8516
arm64: dts: mt8183: Add #cooling-cells to CPU nodes
arm64: dts: mt8183: add/update dynamic power coefficients
arm64: dts: mediatek: rename scpsys nodes to power-controller
amr64: dts: mt8183: Add watchdog node
arm64: dts: mt8173: add arm,no-tick-in-suspend in timer
arm64: dts: mt8183: Enable CPU idle-states
Link: https://lore.kernel.org/r/c512b5cb-e639-1429-64db-9c1a53378c49@gmail.com
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
- Add missing clocks to dwc3 nodes on am65x (fixes USB)
- Add DMA entries for main_spi0 on am65x
- Add phy-gmii-sel nodes for both am65x and j721e (towards ethernet
support)
- Add DMA entries for ADC for both am65x and j721e
- Add MCU system control module on j721e (needed by phy-gmii-sel)
-----BEGIN PGP SIGNATURE-----
iQJEBAABCgAuFiEEtQ6szHmfiBT7fujkyvq9MXlQGhEFAl50ha0QHHQta3Jpc3Rv
QHRpLmNvbQAKCRDK+r0xeVAaESy8D/9suvz/dcJ1CLavA2goT3PTmBHvmkmPNi4r
DoiNHZ6D4RDLcJwqLHerJ0cuSMHFvyQFcM5tGV3x0c7p1imqJuyTYGm6tYexrHHJ
f+sVzF+xOGxgc95+AuZ19SAM9VFwziCbKLaBdUKKJUS2pYrHvZcGQsh16cRZ1jfh
yy1GDtBNd75MWPH8NPoal2NKHFJrWsohsawMQ+3UsU9OEoJl2fQkD6Pf0xy7ag+R
tVLmtgb8EfWfZq9/7vxzZDUDpOZgmbtF9NsAaQ6a3l9BVf5yOv6bUg9reo5tj5dF
xLqDs/4gAAhowyDcpeb6zUDqhAQuz6rQXnfACg718cbbu+ATQW4CfDCf5E0fpL7i
a6zSQkCJdaM6UM16S6FG4Ovyh4/MSiNbgpUdOnA11s5dAqCHzmZL4KnWcl9MRV+q
R/bfAr9dC9950RYexzpYpky59LY+OjxtoZGUMCWIOEXJOLS/PR/iMuPYNBRH919Z
qOGpS/7nIFRa9mvxlBIUwOAtFYmhbRVvFHeOfdOqF4VjYaHBrZY5mHtTXXauVHzS
MyrufvbquhSF+mSktmYUd2Fd8DAs5T6tRqRdj7g51Cwq1Lt+0wDy5jlDEho9J3ui
BIWgV/cb1B2+0Ql6XQWhf5gPIJ76+QiHR6s6Tf1EwVCG+HOS2w3Xi2Je2uFIfmZ5
h+jNEo9vaA==
=XbCt
-----END PGP SIGNATURE-----
Merge tag 'ti-k3-soc-for-v5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/kristo/linux into arm/dt
Texas Instruments K3 SoC family changes for v5.7
- Add missing clocks to dwc3 nodes on am65x (fixes USB)
- Add DMA entries for main_spi0 on am65x
- Add phy-gmii-sel nodes for both am65x and j721e (towards ethernet
support)
- Add DMA entries for ADC for both am65x and j721e
- Add MCU system control module on j721e (needed by phy-gmii-sel)
* tag 'ti-k3-soc-for-v5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/kristo/linux:
arm64: dts: ti: k3-j721e-mcu: add scm node and phy-gmii-sel nodes
arm64: dts: ti: k3-am65-mcu: add phy-gmii-sel node
arm64: dts: ti: k3-am65-mcu: Add DMA entries for ADC
arm64: dts: ti: k3-am65-main: Add DMA entries for main_spi0
arm64: dts: ti: k3-j721e-mcu-wakeup: Add DMA entries for ADC
arm64: dts: ti: k3-am65: Add clocks to dwc3 nodes
Link: https://lore.kernel.org/r/4b6b7804-4bcb-07ba-5e76-6a411e1f457f@ti.com
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
- New support for Kontron LS1028A based boards and NXP i.MX8MP EVK.
- Add Ethernet PHY reset GPIO for imx8mm-evk and imx8mq-evk board.
- Add gpio-fan, thermal and Ethernet support for imx8mq-phanbell board.
- Add SNVS clock description to pwrkey device for i.MX8 SoCs.
- A number of updates on librem5-devkit board to add audio, proximity
sensor, lsm9ds1 mount matrix support, and improve WoWWAN, DVFS, SD
devices as well.
- A series of patches from Anson Huang to update i.MX8 EVK boards
for support of I2C PCA6416, thermal, GPIO LED, OPP table etc.
- Add PCIe device nodes for LX2160A and LS1028A SoC.
- Add FSPI deivce support for LX2160A evaluation boards.
- Add EEPROM and LTC3882 regulator support for lx2160a-cex7 board.
- Other small and random updates on LS1028A and i.MX8 support.
-----BEGIN PGP SIGNATURE-----
iQFIBAABCgAyFiEEFmJXigPl4LoGSz08UFdYWoewfM4FAl5xmGAUHHNoYXduZ3Vv
QGtlcm5lbC5vcmcACgkQUFdYWoewfM7hcggAituxUHoAgPgEmEp7h+7C0dAkD8tL
G21IEi1xL608qIeKgVsyhPqbIze84+CrxzWhhUDJD+EUoVYwc78mGwOebDPBT+bE
U/VP0GU3oaHUOe0zApSf+4uWWHxmx2tqBut6qwgKp9h/nmXQKZ39yivAifrQgyn5
jckrN+gtGoCWLPUVF4baqUBJ7383A2gCpGsdTodNg95e903PYRDFORoez/8q4Hdo
r86YbIZca+tQxDrG00tpKgb0n0iIFsR139YTQtSjUQhzw9nRUcF2AuxtYGYl96mo
ZTyW82fLf+t9Av416cHFi8EL9DKQxVV6stSL6OCrVosll9zWoN/dTuNiOw==
=nTfu
-----END PGP SIGNATURE-----
Merge tag 'imx-dt64-5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into arm/dt
i.MX arm64 DTS update for 5.7:
- New support for Kontron LS1028A based boards and NXP i.MX8MP EVK.
- Add Ethernet PHY reset GPIO for imx8mm-evk and imx8mq-evk board.
- Add gpio-fan, thermal and Ethernet support for imx8mq-phanbell board.
- Add SNVS clock description to pwrkey device for i.MX8 SoCs.
- A number of updates on librem5-devkit board to add audio, proximity
sensor, lsm9ds1 mount matrix support, and improve WoWWAN, DVFS, SD
devices as well.
- A series of patches from Anson Huang to update i.MX8 EVK boards
for support of I2C PCA6416, thermal, GPIO LED, OPP table etc.
- Add PCIe device nodes for LX2160A and LS1028A SoC.
- Add FSPI deivce support for LX2160A evaluation boards.
- Add EEPROM and LTC3882 regulator support for lx2160a-cex7 board.
- Other small and random updates on LS1028A and i.MX8 support.
* tag 'imx-dt64-5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux: (63 commits)
arm64: dts: ls1028a: disable the felix switch by default
arm64: dts: imx8mp: Add snvs clock to powerkey
arm64: dts: imx8mn: Add snvs clock to powerkey
arm64: dts: ls1028a: Add PCIe controller DT nodes
arm64: dts: ls1028a: sl28: add support for variant 2
arm64: dts: ls1028a: sl28: expose switch ports in KBox A-230-LS
arm64: dts: ls1028a: sl28: fix on-board EEPROMS
arm64: dts: freescale: sl28: add SPI flash
arm64: dts: imx8m: fix aips dts node
arm64: dts: imx8mn: Add CPU thermal zone support
arm64: dts: imx8mm: Add thermal zone support
arm64: dts: imx8mq-phanbell: Fix Ethernet PHY post-reset duration
arm64: dts: enable fspi in imx8mm dts
arm64: dts: imx8mn: align name for crypto child nodes
arm64: dts: lx2160aqds: Add FSPI node properties
arm64: dts: lx2160ardb: Update FSPI node properties
arm64: dts: imx8mq-phanbell: Add gpio-fan/thermal support
arm64: dts: layerscape: add iommu-map property to pci nodes
arm64: dts: imx8mp-evk: Enable pca6416 on i2c3 bus
arm64: dts: imx8mp-evk: Add i2c3 support
...
Link: https://lore.kernel.org/r/20200318051918.32579-5-shawnguo@kernel.org
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
- New support for i.MX6/7 based PICO devices and Toradex i.MX7 based
Aster boards.
- Add voltage monitor device node for vf610-zii boards.
- Improve UART pins macro defines for i.MX6SX SoC and switch related
boards to use the new names.
- Use generic node name for devices like GPT, KPP, CCM, WDOG, OCOTP and
IOMUXC in i.MX DTS files.
- Switch imx6ul-pico device tree to DRM bindings.
- Use SPDX-License-Identifier for all Toradex i.MX6/7 based boards.
- Add proper rgmii PHY description for imx6dl-riotboard and
imx6q-marsboard.
- Add capture-subsystem device support for i.MX51.
- Kill off "simple-panel" compatibles which has never been an accepted
as an upstream compatible string.
- Random device addition to various boards.
-----BEGIN PGP SIGNATURE-----
iQFIBAABCgAyFiEEFmJXigPl4LoGSz08UFdYWoewfM4FAl5xkLsUHHNoYXduZ3Vv
QGtlcm5lbC5vcmcACgkQUFdYWoewfM5UZwgAh4EMxfFHTvfIO3Pobcax9qTnwQfX
A1cNE5VcZFhIt93FHV9H4k/rd/28v1QArs18X2PsdYk9NChzmEXSH1fPUQj7aMxT
NnDMDrkPaVGezWZbtoUEcpYr9sCxS6c0eMXq/VI2TTZS0pWPTzBBtsyqWiPbx3ZN
4h12SjS8T3M81VI90En1QStFAlg0YnDXYdEHNS3c/0rBcXLenkfPMlAeBJw6Rti2
9simCtJEDYnJpN77JUfFz8Lkm1bc7np4Fr56diKOrOmCeXD9VQ/qyy/KyBu99oRN
SL404Y7ACFc1OG9MMTkCKrbSCCQqa5ZseNyvV7PJEZImZ3XNb59+ICidRQ==
=42du
-----END PGP SIGNATURE-----
Merge tag 'imx-dt-5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into arm/dt
i.MX arm DTS changes for 5.7:
- New support for i.MX6/7 based PICO devices and Toradex i.MX7 based
Aster boards.
- Add voltage monitor device node for vf610-zii boards.
- Improve UART pins macro defines for i.MX6SX SoC and switch related
boards to use the new names.
- Use generic node name for devices like GPT, KPP, CCM, WDOG, OCOTP and
IOMUXC in i.MX DTS files.
- Switch imx6ul-pico device tree to DRM bindings.
- Use SPDX-License-Identifier for all Toradex i.MX6/7 based boards.
- Add proper rgmii PHY description for imx6dl-riotboard and
imx6q-marsboard.
- Add capture-subsystem device support for i.MX51.
- Kill off "simple-panel" compatibles which has never been an accepted
as an upstream compatible string.
- Random device addition to various boards.
* tag 'imx-dt-5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux: (55 commits)
ARM: dts: imx6q-marsboard: properly define rgmii PHY
ARM: dts: imx6dl-riotboard: properly define rgmii PHY
ARM: dts: imx51-zii-rdu1: set name prefix for TPA6130A2
ARM: dts: imx6: RDU2: assign video PLL as input to LDB
ARM: dts: vf: toradex: SPDX tags and copyright cleanup
ARM: dts: imx7: toradex: use SPDX-License-Identifier
ARM: dts: imx6: toradex: use SPDX-License-Identifier
ARM: dts: imx51: add capture-subsystem device
ARM: dts: imx: add nvmem property for cpu0
ARM: dts: imx6qdl: Add imx6qdl-pico support
ARM: dts: imx6ul-pico: Add support for the dwarf baseboard
ARM: dts: imx7d-pico: Add support for the nymph baseboard
ARM: dts: imx7d-pico: Add support for the dwarf baseboard
ARM: dts: imx23: introduce mmc0_sck_cfg
ARM: dts: imx25-pinfunc: add config for kpp rows 4 to 7
ARM: dts: imx: align name for crypto node and child nodes
ARM: dts: imx6qdl-gw5910: add CC1352 UART
ARM: dts: imx6qdl-sr-som-ti: indicate powering off wifi is safe
ARM: dts: imx6: phycore-som: add da9062 gpio support
ARM: dts: imx6: phycore-som: explicit disable pmic watchdog during suspend
...
Link: https://lore.kernel.org/r/20200318051918.32579-4-shawnguo@kernel.org
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
- Rename nodes to avoid dt-schema warnings
- Add a generic compatible to EEPROM so that it matches OF table
- Add USB controller nodes to Pro5 SoC
- Fix clock and reset of SPI nodes
-----BEGIN PGP SIGNATURE-----
iQJSBAABCgA8FiEEbmPs18K1szRHjPqEPYsBB53g2wYFAl5xBVMeHHlhbWFkYS5t
YXNhaGlyb0Bzb2Npb25leHQuY29tAAoJED2LAQed4NsGImYP/i/iwslPTSeha2U0
j1HJIgd0LhSW/bdn4HoA1yJGPRWHy2n0/1cwccT6bZAVhpPzBdzY76A49bYKLoa3
hP0ye0hiihcLxOhxQXflSmRt/9xMOx0/n2akxvd97YBq9XakRDUgOuaThJhEPhWk
0u//IUgpmoYPII5r4J5plD51MYjUP+QiPdnB3CeaFbBeghKGKIqJSPDon4hP17Dl
uxuKljVI3HRX8mLMYTvc/Pc+A32RjuEvwEaiMo5yHCy0sGGuWfNfMEcbTw7WyF9K
PCLSE/pnxaD3yXh90U6Ea6e197EVjSATrblrlUunWL/R4nlQo/4o3cUYskmtsSTW
aVrVFmhFlbK1bYma3dzSNSc+bzg3dy9N/Bqu7ugKNYGKvjKdOuddxXshWu2AceSj
YNDmKUaPXNGscfs468ChArBLPW/FEU/gS+osB5PK74NOGbsaZfPBHo0G59WrrVBk
7rFAea5W06nA+PkK/c3b7K9fyHPdtty67sbSKOuaBAJ6ofPU/JrlGhzmoHrtJ7AS
XU5ckltBjf32XLIvFYK/2b8rEm8/lW/OZljtaq8JG/qopXQS6fdzOkpduq+M6LZi
+l4US6yK7aUqmnJzl4RAcjdZl6me9sew7ZFaeeU++1kk6BVebwIicjwMuAdaBCH5
ZiYF2zeXwZrYN1aiS+2EAhUi/nS+
=posG
-----END PGP SIGNATURE-----
Merge tag 'uniphier-dt-v5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier into arm/dt
UniPhier ARM SoC DT updates for v5.7
- Rename nodes to avoid dt-schema warnings
- Add a generic compatible to EEPROM so that it matches OF table
- Add USB controller nodes to Pro5 SoC
- Fix clock and reset of SPI nodes
* tag 'uniphier-dt-v5.7' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier:
ARM: dts: uniphier: Set SCSSI clock and reset IDs for each channel
ARM: dts: uniphier: Add USB3 controller nodes for Pro5
ARM: dts: uniphier: Add one more generic compatible string for I2C EEPROM
ARM: dts: uniphier: rename cache controller nodes to follow json-schema
ARM: dts: uniphier: rename NAND node names to follow json-schema
ARM: dts: uniphier: rename aidet node names to follow json-schema
ARM: dts: uniphier: change SD/eMMC node names to follow json-schema
Link: https://lore.kernel.org/r/CAK7LNAQ-AOTyqpV1E_S-hksjqexHfVauwGV9rrfDvjRVnu8-UQ@mail.gmail.com
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
This uses the DEFER_SETUP flag to group channels with
L2CAP_CREDIT_BASED_CONNECTION_REQ.
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
