ARM: tegra: Add WiFi/BT support for ASUS TF701T #106

gcc warns about a couple of instances in which a sanity check exists but the author wasn't sure how to react to it failing, which makes it look like a possible bug: fs/hfsplus/inode.c: In function 'hfsplus_cat_read_inode': fs/hfsplus/inode.c:503:37: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body] 503 | /* panic? */; | ^ fs/hfsplus/inode.c:524:37: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body] 524 | /* panic? */; | ^ fs/hfsplus/inode.c: In function 'hfsplus_cat_write_inode': fs/hfsplus/inode.c:582:37: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body] 582 | /* panic? */; | ^ fs/hfsplus/inode.c:608:37: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body] 608 | /* panic? */; | ^ fs/hfs/inode.c: In function 'hfs_write_inode': fs/hfs/inode.c:464:37: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body] 464 | /* panic? */; | ^ fs/hfs/inode.c:485:37: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body] 485 | /* panic? */; | ^ panic() is probably not the correct choice here, but a WARN_ON seems appropriate and avoids the compile-time warning. Link: https://lkml.kernel.org/r/[email protected] Link: https://lore.kernel.org/all/[email protected]/ Signed-off-by: Arnd Bergmann <[email protected]> Reviewed-by: Christian Brauner <[email protected]> Cc: Alexander Viro <[email protected]> Cc: Christian Brauner <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Cc: Jan Kara <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

Fix the following out-of-bounds warnings by enclosing structure members file and finder into new struct info: fs/hfsplus/xattr.c:300:5: warning: 'memcpy' offset [65, 80] from the object at 'entry' is out of the bounds of referenced subobject 'user_info' with type 'struct DInfo' at offset 48 [-Warray-bounds] fs/hfsplus/xattr.c:313:5: warning: 'memcpy' offset [65, 80] from the object at 'entry' is out of the bounds of referenced subobject 'user_info' with type 'struct FInfo' at offset 48 [-Warray-bounds] Refactor the code by making it more "structured." Also, this helps with the ongoing efforts to enable -Warray-bounds and makes the code clearer and avoid confusing the compiler. Matthew said: : The offending line is this: : : - memcpy(&entry.file.user_info, value, : + memcpy(&entry.file.info, value, : file_finderinfo_len); : : what it's trying to do is copy two structs which are adjacent to each : other in a single call to memcpy(). gcc legitimately complains that : the memcpy to this struct overruns the bounds of the struct. What : Gustavo has done here is introduce a new struct that contains the two : structs, and now gcc is happy that the memcpy doesn't overrun the : length of this containing struct. Link: KSPP/linux#109 Link: https://lkml.kernel.org/r/20210330145226.GA207011@embeddedor Signed-off-by: Gustavo A. R. Silva <[email protected]> Reported-by: kernel test robot <[email protected]> Cc: Matthew Wilcox <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

'linux/string.h' included in 'signal.h' is duplicated. it's also included at line 7. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Ye Guojin <[email protected]> Reported-by: Zeal Robot <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

Move seq_escape() to the header as inliner, for a small kernel text size reduction. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Andy Shevchenko <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

Use swap() instead of reimplementing it. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Ran Xiaokai <[email protected]> Cc: Gabriel Krisman Bertazi <[email protected]> Cc: Peter Zijlstra <[email protected]> Cc: Eric W. Biederman <[email protected]> Cc: Jens Axboe <[email protected]> Cc: Alexey Gladkov <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

There were runtime checks about sizes of struct v7_super_block and struct sysv_inode. If one of these checks fail the kernel will panic. Since these values are known at compile time let's use BUILD_BUG_ON(), because it's a standard mechanism for validation checking at build time Link: https://lkml.kernel.org/r/[email protected] Fixes: 1da177e ("Linux-2.6.12-rc2") Signed-off-by: Pavel Skripkin <[email protected]> Cc: Christoph Hellwig <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

Patch series "kcov: PREEMPT_RT fixup + misc", v2. The last patch in series is follow-up to address the PREEMPT_RT issue within in kcov reported by Clark [1]. Patches 1-3 are smaller things that I noticed while staring at it. Patch 4 is small change which makes replacement in grate-driver#5 simpler / more obvious. [1] https://lkml.kernel.org/r/[email protected] This patch (of 5): The first example code has includes at the top, the following two example share that part. The last example (remote coverage collection) requires the linux/types.h header file due its __aligned_u64 usage. Add the linux/types.h to the top most example and a comment that the header files from above are required as it is done in the second example. Link: https://lkml.kernel.org/r/[email protected] Link: https://lore.kernel.org/r/[email protected] Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Sebastian Andrzej Siewior <[email protected]> Acked-by: Dmitry Vyukov <[email protected]> Acked-by: Marco Elver <[email protected]> Tested-by: Marco Elver <[email protected]> Reviewed-by: Andrey Konovalov <[email protected]> Cc: Steven Rostedt <[email protected]> Cc: Clark Williams <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

The example code uses the variable `ip' but never declares it. Declare `ip' as a 64bit variable which is the same type as the array from which it loads its value. Link: https://lkml.kernel.org/r/[email protected] Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Sebastian Andrzej Siewior <[email protected]> Acked-by: Dmitry Vyukov <[email protected]> Acked-by: Marco Elver <[email protected]> Tested-by: Marco Elver <[email protected]> Reviewed-by: Andrey Konovalov <[email protected]> Cc: Clark Williams <[email protected]> Cc: Steven Rostedt <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

During boot kcov allocates per-CPU memory which is used later if remote/ softirq processing is enabled. Allocate the per-CPU memory on the CPU local node to avoid cross node memory access. Link: https://lkml.kernel.org/r/[email protected] Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Sebastian Andrzej Siewior <[email protected]> Acked-by: Dmitry Vyukov <[email protected]> Acked-by: Marco Elver <[email protected]> Tested-by: Marco Elver <[email protected]> Reviewed-by: Andrey Konovalov <[email protected]> Cc: Clark Williams <[email protected]> Cc: Steven Rostedt <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

kcov_remote_start() may need to allocate memory in the in_task() case (otherwise per-CPU memory has been pre-allocated) and therefore requires enabled interrupts. The interrupts are enabled before checking if the allocation is required so if no allocation is required then the interrupts are needlessly enabled and disabled again. Enable interrupts only if memory allocation is performed. Link: https://lkml.kernel.org/r/[email protected] Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Sebastian Andrzej Siewior <[email protected]> Acked-by: Dmitry Vyukov <[email protected]> Acked-by: Marco Elver <[email protected]> Tested-by: Marco Elver <[email protected]> Reviewed-by: Andrey Konovalov <[email protected]> Cc: Clark Williams <[email protected]> Cc: Steven Rostedt <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

The kcov code mixes local_irq_save() and spin_lock() in kcov_remote_{start|end}(). This creates a warning on PREEMPT_RT because local_irq_save() disables interrupts and spin_lock_t is turned into a sleeping lock which can not be acquired in a section with disabled interrupts. The kcov_remote_lock is used to synchronize the access to the hash-list kcov_remote_map. The local_irq_save() block protects access to the per-CPU data kcov_percpu_data. There is no compelling reason to change the lock type to raw_spin_lock_t to make it work with local_irq_save(). Changing it would require to move memory allocation (in kcov_remote_add()) and deallocation outside of the locked section. Adding an unlimited amount of entries to the hashlist will increase the IRQ-off time during lookup. It could be argued that this is debug code and the latency does not matter. There is however no need to do so and it would allow to use this facility in an RT enabled build. Using a local_lock_t instead of local_irq_save() has the befit of adding a protection scope within the source which makes it obvious what is protected. On a !PREEMPT_RT && !LOCKDEP build the local_lock_irqsave() maps directly to local_irq_save() so there is overhead at runtime. Replace the local_irq_save() section with a local_lock_t. Link: https://lkml.kernel.org/r/[email protected] Link: https://lore.kernel.org/r/[email protected] Reported-by: Clark Williams <[email protected]> Signed-off-by: Sebastian Andrzej Siewior <[email protected]> Acked-by: Dmitry Vyukov <[email protected]> Acked-by: Marco Elver <[email protected]> Tested-by: Marco Elver <[email protected]> Reviewed-by: Andrey Konovalov <[email protected]> Cc: Steven Rostedt <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

Patch series "virtio-mem: disallow mapping virtio-mem memory via /dev/mem", v5. Let's add the basic infrastructure to exclude some physical memory regions marked as "IORESOURCE_SYSTEM_RAM" completely from /dev/mem access, even though they are not marked IORESOURCE_BUSY and even though "iomem=relaxed" is set. Resource IORESOURCE_EXCLUSIVE for that purpose instead of adding new flags to express something similar to "soft-busy" or "not busy yet, but already prepared by a driver and not to be mapped by user space". Use it for virtio-mem, to disallow mapping any virtio-mem memory via /dev/mem to user space after the virtio-mem driver was loaded. This patch (of 3): We end up traversing subtrees of ranges we are not interested in; let's optimize this case, skipping such subtrees, cleaning up the function a bit. For example, in the following configuration (/proc/iomem): 00000000-00000fff : Reserved 00001000-00057fff : System RAM 00058000-00058fff : Reserved 00059000-0009cfff : System RAM 0009d000-000fffff : Reserved 000a0000-000bffff : PCI Bus 0000:00 000c0000-000c3fff : PCI Bus 0000:00 000c4000-000c7fff : PCI Bus 0000:00 000c8000-000cbfff : PCI Bus 0000:00 000cc000-000cffff : PCI Bus 0000:00 000d0000-000d3fff : PCI Bus 0000:00 000d4000-000d7fff : PCI Bus 0000:00 000d8000-000dbfff : PCI Bus 0000:00 000dc000-000dffff : PCI Bus 0000:00 000e0000-000e3fff : PCI Bus 0000:00 000e4000-000e7fff : PCI Bus 0000:00 000e8000-000ebfff : PCI Bus 0000:00 000ec000-000effff : PCI Bus 0000:00 000f0000-000fffff : PCI Bus 0000:00 000f0000-000fffff : System ROM 00100000-3fffffff : System RAM 40000000-403fffff : Reserved 40000000-403fffff : pnp 00:00 40400000-80a79fff : System RAM ... We don't have to look at any children of "0009d000-000fffff : Reserved" if we can just skip these 15 items directly because the parent range is not of interest. Link: https://lkml.kernel.org/r/[email protected] Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: David Hildenbrand <[email protected]> Reviewed-by: Dan Williams <[email protected]> Cc: Arnd Bergmann <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Cc: "Michael S. Tsirkin" <[email protected]> Cc: Jason Wang <[email protected]> Cc: "Rafael J. Wysocki" <[email protected]> Cc: Hanjun Guo <[email protected]> Cc: Andy Shevchenko <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

virtio-mem dynamically exposes memory inside a device memory region as system RAM to Linux, coordinating with the hypervisor which parts are actually "plugged" and consequently usable/accessible. On the one hand, the virtio-mem driver adds/removes whole memory blocks, creating/removing busy IORESOURCE_SYSTEM_RAM resources, on the other hand, it logically (un)plugs memory inside added memory blocks, dynamically either exposing them to the buddy or hiding them from the buddy and marking them PG_offline. In contrast to physical devices, like a DIMM, the virtio-mem driver is required to actually make use of any of the device-provided memory, because it performs the handshake with the hypervisor. virtio-mem memory cannot simply be access via /dev/mem without a driver. There is no safe way to: a) Access plugged memory blocks via /dev/mem, as they might contain unplugged holes or might get silently unplugged by the virtio-mem driver and consequently turned inaccessible. b) Access unplugged memory blocks via /dev/mem because the virtio-mem driver is required to make them actually accessible first. The virtio-spec states that unplugged memory blocks MUST NOT be written, and only selected unplugged memory blocks MAY be read. We want to make sure, this is the case in sane environments -- where the virtio-mem driver was loaded. We want to make sure that in a sane environment, nobody "accidentially" accesses unplugged memory inside the device managed region. For example, a user might spot a memory region in /proc/iomem and try accessing it via /dev/mem via gdb or dumping it via something else. By the time the mmap() happens, the memory might already have been removed by the virtio-mem driver silently: the mmap() would succeeed and user space might accidentially access unplugged memory. So once the driver was loaded and detected the device along the device-managed region, we just want to disallow any access via /dev/mem to it. In an ideal world, we would mark the whole region as busy ("owned by a driver") and exclude it; however, that would be wrong, as we don't really have actual system RAM at these ranges added to Linux ("busy system RAM"). Instead, we want to mark such ranges as "not actual busy system RAM but still soft-reserved and prepared by a driver for future use." Let's teach iomem_is_exclusive() to reject access to any range with "IORESOURCE_SYSTEM_RAM | IORESOURCE_EXCLUSIVE", even if not busy and even if "iomem=relaxed" is set. Introduce EXCLUSIVE_SYSTEM_RAM to make it easier for applicable drivers to depend on this setting in their Kconfig. For now, there are no applicable ranges and we'll modify virtio-mem next to properly set IORESOURCE_EXCLUSIVE on the parent resource container it creates to contain all actual busy system RAM added via add_memory_driver_managed(). Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: David Hildenbrand <[email protected]> Reviewed-by: Dan Williams <[email protected]> Cc: Andy Shevchenko <[email protected]> Cc: Arnd Bergmann <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Cc: Hanjun Guo <[email protected]> Cc: Jason Wang <[email protected]> Cc: "Michael S. Tsirkin" <[email protected]> Cc: "Rafael J. Wysocki" <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

We don't want user space to be able to map virtio-mem device memory directly (e.g., via /dev/mem) in order to have guarantees that in a sane setup we'll never accidentially access unplugged memory within the device-managed region of a virtio-mem device, just as required by the virtio-spec. As soon as the virtio-mem driver is loaded, the device region is visible in /proc/iomem via the parent device region. From that point on user space is aware of the device region and we want to disallow mapping anything inside that region (where we will dynamically (un)plug memory) until the driver has been unloaded cleanly and e.g., another driver might take over. By creating our parent IORESOURCE_SYSTEM_RAM resource with IORESOURCE_EXCLUSIVE, we will disallow any /dev/mem access to our device region until the driver was unloaded cleanly and removed the parent region. This will work even though only some memory blocks are actually currently added to Linux and appear as busy in the resource tree. So access to the region from user space is only possible a) if we don't load the virtio-mem driver. b) after unloading the virtio-mem driver cleanly. Don't build virtio-mem if access to /dev/mem cannot be restricticted -- if we have CONFIG_DEVMEM=y but CONFIG_STRICT_DEVMEM is not set. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: David Hildenbrand <[email protected]> Reviewed-by: Dan Williams <[email protected]> Acked-by: Michael S. Tsirkin <[email protected]> Cc: Andy Shevchenko <[email protected]> Cc: Arnd Bergmann <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Cc: Hanjun Guo <[email protected]> Cc: Jason Wang <[email protected]> Cc: "Rafael J. Wysocki" <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

This commit removes the requirement to be root to modify sem_next_id, msg_next_id and shm_next_id and checks checkpoint_restore_ns_capable instead. Since those files are specific to the IPC namespace, there is no reason they should require root privileges. This is similar to ns_last_pid, which also only checks checkpoint_restore_ns_capable. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Michal Clapinski <[email protected]> Reviewed-by: Davidlohr Bueso <[email protected]> Reviewed-by: Manfred Spraul <[email protected]> Cc: "Eric W. Biederman" <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

ipc/ipc_sysctl.c needs capability.h for checkpoint_restore_ns_capable() Cc: Davidlohr Bueso <[email protected]> Cc: "Eric W. Biederman" <[email protected]> Cc: Manfred Spraul <[email protected]> Cc: Michal Clapinski <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

Compilation of ipc/ipc_sysctl.c is controlled by obj-$(CONFIG_SYSVIPC_SYSCTL) [see ipc/Makefile] And CONFIG_SYSVIPC_SYSCTL depends on SYSCTL [see init/Kconfig] An SYSCTL is selected by PROC_SYSCTL. [see fs/proc/Kconfig] Thus: #ifndef CONFIG_PROC_SYSCTL in ipc/ipc_sysctl.c is impossible, the fallback can be removed. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Manfred Spraul <[email protected]> Reviewed-by: "Eric W. Biederman" <[email protected]> Acked-by: Davidlohr Bueso <[email protected]> Cc: Manfred Spraul <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

# Conflicts: # arch/parisc/include/asm/bitops.h

Memory allocators may disable interrupts or preemption as part of the allocation and freeing process. For PREEMPT_RT it is important that these sections remain deterministic and short and therefore don't depend on the size of the memory to allocate/ free or the inner state of the algorithm. Until v3.12-RT the SLAB allocator was an option but involved several changes to meet all the requirements. The SLUB design fits better with PREEMPT_RT model and so the SLAB patches were dropped in the 3.12-RT patchset. Comparing the two allocator, SLUB outperformed SLAB in both throughput (time needed to allocate and free memory) and the maximal latency of the system measured with cyclictest during hackbench. SLOB was never evaluated since it was unlikely that it preforms better than SLAB. During a quick test, the kernel crashed with SLOB enabled during boot. Disable SLAB and SLOB on PREEMPT_RT. [[email protected]: commit description] Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Ingo Molnar <[email protected]> Signed-off-by: Thomas Gleixner <[email protected]> Signed-off-by: Sebastian Andrzej Siewior <[email protected]> Acked-by: Vlastimil Babka <[email protected]> Cc: Christoph Lameter <[email protected]> Cc: Pekka Enberg <[email protected]> Cc: David Rientjes <[email protected]> Cc: Joonsoo Kim <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

… its mapping Patch series "Some cleanup for page migration", v3. This patchset does some cleanups and improvements for page migration. This patch (of 4): There is no need to validate the file-backed page's refcount before trying to freeze the page's expected refcount, instead we can rely on the folio_ref_freeze() to validate if the page has the expected refcount before migrating its mapping. Moreover we are always under the page lock when migrating the page mapping, which means nowhere else can remove it from the page cache, so we can remove the xas_load() validation under the i_pages lock. Link: https://lkml.kernel.org/r/[email protected] Link: https://lkml.kernel.org/r/df4c129fd8e86a95dbc55f4663d77441cc0d3bd1.1629447552.git.baolin.wang@linux.alibaba.com Signed-off-by: Baolin Wang <[email protected]> Suggested-by: Matthew Wilcox <[email protected]> Cc: Yang Shi <[email protected]> Cc: Alistair Popple <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

Patch series "unexport memcg locking helpers". Neither the old page-based nor the new folio-based memcg locking helpers are used in modular code at all, so drop the exports. This patch (of 2): folio_memcg_{,un}lock are only used in built-in core mm code. Link: https://lkml.kernel.org/r/[email protected] Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Christoph Hellwig <[email protected]> Cc: Johannes Weiner <[email protected]> Cc: Michal Hocko <[email protected]> Cc: Vladimir Davydov <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

These are only used in built-in core mm code. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Christoph Hellwig <[email protected]> Acked-by: Johannes Weiner <[email protected]> Cc: Michal Hocko <[email protected]> Cc: Vladimir Davydov <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

There are multiple kasan modes. It makes sense that we add some messages to know which kasan mode is when booting up. see [1]. Link: https://bugzilla.kernel.org/show_bug.cgi?id=212195 [1] Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Kuan-Ying Lee <[email protected]> Reviewed-by: Marco Elver <[email protected]> Cc: Andrey Ryabinin <[email protected]> Cc: Alexander Potapenko <[email protected]> Cc: Andrey Konovalov <[email protected]> Cc: Dmitry Vyukov <[email protected]> Cc: Catalin Marinas <[email protected]> Cc: Will Deacon <[email protected]> Cc: Matthias Brugger <[email protected]> Cc: Chinwen Chang <[email protected]> Cc: Yee Lee <[email protected]> Cc: Nicholas Tang <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

…alloc() - fixup3 Due to cd06ab2 ("drm/locking: add backtrace for locking contended locks without backoff") landing recently to -next adding a new stack depot user in drivers/gpu/drm/drm_modeset_lock.c we need to add an appropriate call to stack_depot_init() there as well. Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Vlastimil Babka <[email protected]> Cc: Jani Nikula <[email protected]> Cc: Naresh Kamboju <[email protected]> Cc: Marco Elver <[email protected]> Cc: Vijayanand Jitta <[email protected]> Cc: Maarten Lankhorst <[email protected]> Cc: Maxime Ripard <[email protected]> Cc: Thomas Zimmermann <[email protected]> Cc: David Airlie <[email protected]> Cc: Daniel Vetter <[email protected]> Cc: Andrey Ryabinin <[email protected]> Cc: Alexander Potapenko <[email protected]> Cc: Andrey Konovalov <[email protected]> Cc: Dmitry Vyukov <[email protected]> Cc: Geert Uytterhoeven <[email protected]> Cc: Oliver Glitta <[email protected]> Cc: Imran Khan <[email protected]> Cc: Stephen Rothwell <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Stephen Rothwell <[email protected]>

Signed-off-by: Stephen Rothwell <[email protected]>

Add blocking_notifier_call_chain_empty() that returns true if call chain is empty and false otherwise. Signed-off-by: Dmitry Osipenko <[email protected]>

Add atomic/blocking_notifier_has_unique_priority() helpers which return true if given handler has unique priority in the notifier chain. Signed-off-by: Dmitry Osipenko <[email protected]>

Correct s/implemenations/implementations/ in <reboot.h>. Signed-off-by: Dmitry Osipenko <[email protected]>

It doesn't make sense to register restart handlers with the same priority, normally it's a direct sign of a problem. Add sanity check which ensures that there are no two restart handlers registered with the same priority. Signed-off-by: Dmitry Osipenko <[email protected]>

Emit warning if unregister_restart_handler() fails since it never should fail. This will ease further API development by catching dumb mistakes. Signed-off-by: Dmitry Osipenko <[email protected]>

There is no need to annotate function prototypes with 'extern', it makes code less readable. Remove unnecessary annotations from <reboot.h>. Signed-off-by: Dmitry Osipenko <[email protected]>

SoC platforms often have multiple options for performing of system's power-off and restart operations. Meanwhile today's kernel is limited to a single option. Add combined power-off+restart handler call chain API, which is inspired by the restart API. The new API provides both power-off and restart functionality, it's designed with reliability, simplicity and extensibility in mind. The old pm_power_off method will be kept around till all users are converted to the new API. Current restart API will be replaced with the new unified API since new API is its superset. The restart functionality of the power-handler API is built upon the existing restart-notifier APIs. In order to ease conversion to the new API, convenient helpers are added for the common use-cases. They will reduce amount of boilerplate code and remove global variables. These helpers preserve old behaviour where only one power-off handler was executed. Users of the new API should explicitly opt-in to allow power-off chaining by enabling the corresponding flag of power_handler structure. Signed-off-by: Dmitry Osipenko <[email protected]>

Kernel now supports chained power-off handlers. Use do_kernel_power_off() that invokes chained power-off handlers. It also invokes legacy pm_power_off() for now, which will be removed once all drivers will be converted to the new power-off API. Signed-off-by: Dmitry Osipenko <[email protected]>

Kernel now supports chained power-off handlers. Use register_power_off_handler() that registers power-off handlers and do_kernel_power_off() that invokes chained power-off handlers. Legacy pm_power_off() will be removed once all drivers will be converted to the new power-off API. Normally arch code should adopt only the do_kernel_power_off() at first, but m68k is a special case because it uses pm_power_off() "inside out", i.e. it assigns machine_power_off() to pm_power_off, while it's machine_power_off() that should invoke the pm_power_off(), and thus, we can't convert platforms to the new API separately. There are only two platforms changed here, so it's not a big deal. Signed-off-by: Dmitry Osipenko <[email protected]>

Replace legacy pm_power_off with kernel_can_power_off() helper that is aware about chained power-off handlers. Signed-off-by: Dmitry Osipenko <[email protected]>

Switch to power-handler API that replaces legacy pm_power_off callbacks. Signed-off-by: Dmitry Osipenko <[email protected]>

Use devm_register_power_handler() that replaces global pm_power_off_prepare variable and allows to register multiple power-off handlers. Signed-off-by: Dmitry Osipenko <[email protected]>

All pm_power_off_prepare() users were converted to power-handler API. Remove the obsolete callback. Signed-off-by: Dmitry Osipenko <[email protected]>

Nexus 7 Android tablet can be turned off using a special bootloader command which is conveyed to bootloader by putting magic value into specific scratch register and then rebooting normally. This power-off method should be invoked if USB cable is connected. Bootloader then will display battery status and power off the device. This behaviour is borrowed from downstream kernel and matches user expectations, otherwise it looks like device got hung during power-off and it may wake up on USB disconnect. Switch PMC driver to power-handler API, which provides drivers with combined power-off+restart call chains functionality, replacing the restart-only call chain API. Signed-off-by: Dmitry Osipenko <[email protected]>

Use devm_register_power_handler() that replaces global pm_power_off variable and allows to register multiple power-off handlers. It also provides restart-handler support, i.e. all in one API. Signed-off-by: Dmitry Osipenko <[email protected]>

Use register_simple_power_off_handler() that replaces global pm_power_off variable and allows to register multiple power-off handlers. Signed-off-by: Dmitry Osipenko <[email protected]>

Use devm_register_simple_power_off_handler() that replaces global pm_power_off variable and allows to register multiple power-off handlers. Signed-off-by: Dmitry Osipenko <[email protected]>

Use devm_register_simple_power_off_handler() that replaces global pm_power_off variable and allows to register multiple power-off handlers. Nexus 7 Android tablet can be powered off using MAX77663 PMIC and using a special bootloader command. At first the bootloader option should be tried, it will have a higher priority than of PMIC that uses default priority. Signed-off-by: Dmitry Osipenko <[email protected]>

Use devm_register_trivial_power_off_handler() that replaces global pm_power_off variable and allows to register multiple power-off handlers. Signed-off-by: Dmitry Osipenko <[email protected]>

Use devm_register_simple_restart_handler() helper that reduces boilerplate code. Signed-off-by: Dmitry Osipenko <[email protected]>

Use devm_register_prioritized_restart_handler() helper that reduces boilerplate code. Signed-off-by: Dmitry Osipenko <[email protected]>

After updating to Ubuntu 20.04, I found that all chromium-based software got broken. This happens because Ubuntu 20.04 updated GLIBC to 2.31, which now uses clock_gettime64 by default, but chromium doesn't whitelist this syscall for seccomp. The clock_gettime64 is a VDSO function on ARM, and thus, there is no good reason to fail software that is not ready for a newer GLIBC versions. Falkon and Akregator are now working on Ubuntu 20.04 without a need to disable seccomp by software, which isn't always possible (like in a case of Akregator). Signed-off-by: Dmitry Osipenko <[email protected]>

Chromium browser crashes sometime because it doesn't whitelist the clock_nanosleep_time64 syscall. This is a problem crated by GLIBC, it won't be fixed until all userspace software that uses seccomp will update its syscall filtering rules. Signed-off-by: Dmitry Osipenko <[email protected]>

GENPD core now can set up domain's performance state properly while device is RPM-suspended. Runtime PM of a device must be enabled during setup because GENPD checks whether device is suspended and check doesn't work while RPM is disabled. Instead of replicating the boilerplate RPM-enable code around OPP helper for each driver, let's make OPP helper to take care of enabling it. Signed-off-by: Dmitry Osipenko <[email protected]>

Only couple drivers need to get the -ENODEV error code and majority of drivers need to explicitly initialize the performance state. Add new common helper which sets up OPP table for these drivers. Signed-off-by: Dmitry Osipenko <[email protected]>

Previously we assumed that devm_tegra_core_dev_init_opp_table() will be used only by drivers that will always have device with OPP table, but this is not true anymore. For example now Tegra30 will have OPP table for PWM, but Tegra20 not and both use the same driver. Hence let's not print the error message about missing OPP table in the common helper, we can print it elsewhere. Signed-off-by: Dmitry Osipenko <[email protected]>

Document sub-nodes which describe Tegra SoC clocks that require a higher voltage of the core power domain in order to operate properly on a higher clock rates. Each node contains a phandle to OPP table and power domain. The root PLLs and system clocks don't have any specific device dedicated to them, clock controller is in charge of managing power for them. Reviewed-by: Rob Herring <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

The Clock-and-Reset controller resides in a core power domain on NVIDIA Tegra SoCs. In order to support voltage scaling of the core power domain, we hook up DVFS-capable clocks to the core GENPD for managing of the GENPD's performance state based on the clock changes. Some clocks don't have any specific physical hardware unit that backs them, like root PLLs and system clock and they have theirs own voltage requirements. This patch adds new clk-device driver that backs the clocks and provides runtime PM functionality for them. A virtual clk-device is created for each such DVFS-capable clock at the clock's registration time by the new tegra_clk_register() helper. Driver changes clock's device GENPD performance state based on clk-rate notifications. In result we have this sequence of events: 1. Clock driver creates virtual device for selective clocks, enables runtime PM for the created device and registers the clock. 2. Clk-device driver starts to listen to clock rate changes. 3. Something changes clk rate or enables/disables clk. 4. CCF core propagates the change through the clk tree. 5. Clk-device driver gets clock rate-change notification or GENPD core handles prepare/unprepare of the clock. 6. Clk-device driver changes GENPD performance state on clock rate change. 7. GENPD driver changes voltage regulator state change. 8. The regulator state is committed to hardware via I2C. We rely on fact that DVFS is not needed for Tegra I2C and that Tegra I2C driver already keeps clock always-prepared. Hence I2C subsystem stays independent from the clk power management and there are no deadlock spots in the sequence. Currently all clocks are registered very early during kernel boot when the device driver core isn't available yet. The clk-device can't be created at that time. This patch splits the registration of the clocks in two phases: 1. Register all essential clocks which don't use RPM and are needed during early boot. 2. Register at a later boot time the rest of clocks. This patch adds power management support for Tegra20 and Tegra30 clocks. Tested-by: Peter Geis <[email protected]> # Ouya T30 Tested-by: Paul Fertser <[email protected]> # PAZ00 T20 Tested-by: Nicolas Chauvet <[email protected]> # PAZ00 T20 and TK1 T124 Tested-by: Matt Merhar <[email protected]> # Ouya T30 Signed-off-by: Dmitry Osipenko <[email protected]>

Document new DVFS OPP table and power domain properties of the Host1x bus and devices sitting on the bus. Reviewed-by: Rob Herring <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

…d GR3D Memory Client should be blocked before hardware reset is asserted in order to prevent memory corruption and hanging of memory controller. Document Memory Client resets of Host1x, GR2D and GR3D hardware units. Reviewed-by: Rob Herring <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

Add runtime PM and OPP support to the Host1x driver. For the starter we will keep host1x always-on because dynamic power management require a major refactoring of the driver code since lot's of code paths are missing the RPM handling and we're going to remove some of these paths in the future. Tested-by: Peter Geis <[email protected]> # Ouya T30 Tested-by: Paul Fertser <[email protected]> # PAZ00 T20 Tested-by: Nicolas Chauvet <[email protected]> # PAZ00 T20 and TK1 T124 Tested-by: Matt Merhar <[email protected]> # Ouya T30 Signed-off-by: Dmitry Osipenko <[email protected]>

Add host1x_channel_stop() which waits till channel becomes idle and then stops the channel hardware. This is needed for supporting suspend/resume by host1x drivers since the hardware state is lost after power-gating, thus the channel needs to be stopped before client enters into suspend. Tested-by: Peter Geis <[email protected]> # Ouya T30 Tested-by: Paul Fertser <[email protected]> # PAZ00 T20 Tested-by: Nicolas Chauvet <[email protected]> # PAZ00 T20 and TK1 T124 Tested-by: Matt Merhar <[email protected]> # Ouya T30 Signed-off-by: Dmitry Osipenko <[email protected]>

Add OPP and SoC core voltage scaling support to the display controller driver. This is required for enabling system-wide DVFS on pre-Tegra186 SoCs. Tested-by: Peter Geis <[email protected]> # Ouya T30 Tested-by: Paul Fertser <[email protected]> # PAZ00 T20 Tested-by: Nicolas Chauvet <[email protected]> # PAZ00 T20 and TK1 T124 Tested-by: Matt Merhar <[email protected]> # Ouya T30 Signed-off-by: Dmitry Osipenko <[email protected]>

The HDMI on Tegra belongs to the core power domain and we're going to enable GENPD support for the core domain. Now HDMI driver must use OPP API for driving the controller's clock rate because OPP API takes care of reconfiguring the domain's performance state based on HDMI clock rate. Add OPP support to the HDMI driver. Signed-off-by: Dmitry Osipenko <[email protected]>

Add runtime power management and support generic power domains. Tested-by: Peter Geis <[email protected]> # Ouya T30 Tested-by: Paul Fertser <[email protected]> # PAZ00 T20 Tested-by: Nicolas Chauvet <[email protected]> # PAZ00 T20 and TK1 T124 Tested-by: Matt Merhar <[email protected]> # Ouya T30 Signed-off-by: Dmitry Osipenko <[email protected]>

CDMA must be stopped before hardware is suspended. Add channel stopping to RPM suspend callback. Add system level suspend-resume callbacks. Runtime PM initialization is moved to host1x client init phase because RPM callback now uses host1x channel that is available only when host1x client is registered. Signed-off-by: Dmitry Osipenko <[email protected]>

Runtime PM is now universally available, make it mandatory by removing the pm_runtime_enabled() checks. Signed-off-by: Dmitry Osipenko <[email protected]>

Runtime PM auto-suspension doesn't work without pm_runtime_mark_last_busy(), add it. Signed-off-by: Dmitry Osipenko <[email protected]>

The Tegra USB controller belongs to the core power domain and we're going to enable GENPD support for the core domain. Now USB controller must be resumed using runtime PM API in order to initialize the USB power state. We already support runtime PM for the CI device, but CI's PM is separated from the RPM managed by tegra-usb driver. Add runtime PM and OPP support to the driver. Acked-by: Peter Chen <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

The GMI bus on Tegra belongs to the core power domain and we're going to enable GENPD support for the core domain. Now GMI must be resumed using runtime PM API in order to initialize the GMI power state. Add runtime PM and OPP support to the GMI driver. Signed-off-by: Dmitry Osipenko <[email protected]>

The PWM on Tegra belongs to the core power domain and we're going to enable GENPD support for the core domain. Now PWM must be resumed using runtime PM API in order to initialize the PWM power state. The PWM clock rate must be changed using OPP API that will reconfigure the power domain performance state in accordance to the rate. Add runtime PM and OPP support to the PWM driver. Signed-off-by: Dmitry Osipenko <[email protected]>

The SDHCI on Tegra belongs to the core power domain and we're going to enable GENPD support for the core domain. Now SDHCI must be resumed using runtime PM API in order to initialize the SDHCI power state. The SDHCI clock rate must be changed using OPP API that will reconfigure the power domain performance state in accordance to the rate. Add runtime PM and OPP support to the SDHCI driver. Signed-off-by: Dmitry Osipenko <[email protected]>

The NAND on Tegra belongs to the core power domain and we're going to enable GENPD support for the core domain. Now NAND must be resumed using runtime PM API in order to initialize the NAND power state. Add runtime PM and OPP support to the NAND driver. Acked-by: Miquel Raynal <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

The SPI on Tegra belongs to the core power domain and we're going to enable GENPD support for the core domain. Now SPI driver must use OPP API for driving the controller's clock rate because OPP API takes care of reconfiguring the domain's performance state in accordance to the rate. Add OPP support to the driver. Acked-by: Mark Brown <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

Convert NVIDIA Tegra video decoder binding to schema. Reviewed-by: Rob Herring <[email protected]> Acked-by: Hans Verkuil <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

Document new OPP table and power domain properties of the video decoder hardware. Reviewed-by: Rob Herring <[email protected]> Acked-by: Hans Verkuil <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

Currently driver supports legacy power domain API, this patch adds generic power domain support. This allows us to utilize a modern GENPD API for newer device-trees. Tested-by: Peter Geis <[email protected]> # Ouya T30 Tested-by: Paul Fertser <[email protected]> # PAZ00 T20 Tested-by: Nicolas Chauvet <[email protected]> # PAZ00 T20 and TK1 T124 Tested-by: Matt Merhar <[email protected]> # Ouya T30 Acked-by: Hans Verkuil <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

The FUSE controller is enabled at a boot time. Reset it in order to put hardware and clock into clean and disabled state. Signed-off-by: Dmitry Osipenko <[email protected]>

Use resource-managed helpers to make code cleaner and more correct, properly releasing all resources in case of driver probe error. Signed-off-by: Dmitry Osipenko <[email protected]>

Depending on hardware version, Tegra SoC may require a higher voltages during resume from system suspend, otherwise hardware will crash. Set SoC voltages to a nominal levels during suspend. Signed-off-by: Dmitry Osipenko <[email protected]>

Device-tree schema doesn't allow domain name to start with a number. We don't use 3d domain yet in device-trees, so rename it to the name used by Tegra TRMs: TD, TD2. Reported-by: David Heidelberg <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

CORE power domain uses name of device-tree node, which is inconsistent with the names of PMC domains. Set the name to "core" to make it consistent. Signed-off-by: Dmitry Osipenko <[email protected]>

All device drivers got runtime PM and OPP support. Flip the core domain support status for Tegra20 and Tegra30 SoCs. Signed-off-by: Dmitry Osipenko <[email protected]>

OPP table name now should start with "opp-table" and OPP entries shouldn't contain commas and @ signs in accordance to the new schema requirement. Reorganize CPU and EMC OPP table device-tree nodes. Signed-off-by: Dmitry Osipenko <[email protected]>

Extend memory OPPs with 500MHz entry. This clock rate is used by ASUS Transformer tablets. Signed-off-by: Dmitry Osipenko <[email protected]>

Add OPP tables and power domains to all peripheral devices which support power management on Tegra20 SoC. Tested-by: Paul Fertser <[email protected]> # PAZ00 T20 Tested-by: Nicolas Chauvet <[email protected]> # PAZ00 T20 Signed-off-by: Dmitry Osipenko <[email protected]>

Add OPP tables and power domains to all peripheral devices which support power management on Tegra30 SoC. Tested-by: Peter Geis <[email protected]> # Ouya T30 Tested-by: Matt Merhar <[email protected]> # Ouya T30 Signed-off-by: Dmitry Osipenko <[email protected]>

Memory access must be blocked before hardware reset is asserted and before power is gated, otherwise a serious hardware fault is inevitable. Add reset for memory clients to the GR2D, GR3D and Host1x nodes. Tested-by: Paul Fertser <[email protected]> # PAZ00 T20 Tested-by: Nicolas Chauvet <[email protected]> # PAZ00 T20 Signed-off-by: Dmitry Osipenko <[email protected]>

Memory access must be blocked before hardware reset is asserted and before power is gated, otherwise a serious hardware fault is inevitable. Add reset for memory clients to the GR2D, GR3D and Host1x nodes. Tested-by: Peter Geis <[email protected]> # Ouya T30 Tested-by: Matt Merhar <[email protected]> # Ouya T30 Signed-off-by: Dmitry Osipenko <[email protected]>

MPE, VI, EPP and ISP were never used and we don't have drivers for them. Since these modules are enabled by default in a device-tree, a device is created for them, blocking voltage scaling because there is no driver to bind, and thus, state of PMC driver is never synced. Disable them. Signed-off-by: Dmitry Osipenko <[email protected]>

The device-tree of AC97 codecs need to be parsed differently from I2S codecs, plus codec device may need to be created. This was missed by the patch that unified machine drivers into a single driver, fix it. It should restore audio on Toradex Colibri board. Cc: <[email protected]> Fixes: cc8f70f ("ASoC: tegra: Unify ASoC machine drivers") Signed-off-by: Dmitry Osipenko <[email protected]>

The default card name for Trimslice device should be "tegra-trimslice". It got lost by accident during unification of machine sound drivers, fix it. Cc: <[email protected]> Fixes: cc8f70f ("ASoC: tegra: Unify ASoC machine drivers") Signed-off-by: Dmitry Osipenko <[email protected]>

Driver was upstreamed in 2013 and never got a user, remove it. Signed-off-by: Dmitry Osipenko <[email protected]>

Name clocks and regulators according to DT-schema to fix warnings such as: arch/arm/boot/dts/tegra20-acer-a500-picasso.dt.yaml: /: clock@0: 'anyOf' conditional failed, one must be fixed: 'reg' is a required property 'ranges' is a required property From schema: /home/runner/.local/lib/python3.8/site-packages/dtschema/schemas/root-node.yaml Signed-off-by: David Heidelberg <[email protected]>

Add HannStar HSD101PWW2 10.1" WXGA (1280x800) TFT-LCD LVDS panel to the list of compatibles. Signed-off-by: Svyatoslav Ryhel <[email protected]>

Add definition of the HannStar HSD101PWW2 Rev0-A00/A01 LCD SuperIPS+ HD panel. Signed-off-by: Svyatoslav Ryhel <[email protected]>

Document Tegra20/30-based ASUS Transformer Series tablet devices. This group includes EeePad TF101, Prime TF201, Pad TF300T, TF300TG and Infinity TF700T. Signed-off-by: David Heidelberg <[email protected]> Signed-off-by: Svyatoslav Ryhel <[email protected]>

Document Pegatron Chagall, which is Tegra30-based tablet device. Signed-off-by: David Heidelberg <[email protected]>

Add device-tree for Tegra20-based ASUS Transformer EeePad TF101. Co-developed-by: David Heidelberg <[email protected]> Co-developed-by: Dmitry Osipenko <[email protected]> Co-developed-by: Svyatoslav Ryhel <[email protected]> Co-developed-by: Antoni Aloy Torrens <[email protected]> Signed-off-by: David Heidelberg <[email protected]> Signed-off-by: Svyatoslav Ryhel <[email protected]> Signed-off-by: Antoni Aloy Torrens <[email protected]> Signed-off-by: Nikola Milosavljević <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

Add device-tree for ASUS Transformer Prime TF201, which is NVIDIA Tegra30-based tablet device. Co-developed-by: Ion Agorria <[email protected]> Signed-off-by: Ion Agorria <[email protected]> Signed-off-by: Svyatoslav Ryhel <[email protected]>

Add device-tree for ASUS Transformer Pad TF300T, which is NVIDIA Tegra30-based tablet device. Tested-by: <Ihor Didenko [email protected]> Tested-by: <Andreas Westman Dorcsak [email protected]> Co-developed-by: Ion Agorria <[email protected]> Signed-off-by: Ion Agorria <[email protected]> Co-developed-by: Svyatoslav Ryhel <[email protected]> Signed-off-by: Svyatoslav Ryhel <[email protected]> Signed-off-by: Michał Mirosław <[email protected]>

Add device-tree for ASUS Transformer Pad TF300TG, which is NVIDIA Tegra30-based tablet device, a variant of TF300T that has 3g modem. Co-developed-by: Ion Agorria <[email protected]> Signed-off-by: Ion Agorria <[email protected]> Signed-off-by: Svyatoslav Ryhel <[email protected]>

Add device-tree for ASUS Transformer Infinity TF700T, which is NVIDIA Tegra30-based tablet device. Tested-by: Andreas Westman Dorcsak <[email protected]> Tested-by: Jasper Korten <[email protected]> Co-developed-by: Ion Agorria <[email protected]> Co-developed-by: Maxim Schwalm <[email protected]> Signed-off-by: Ion Agorria <[email protected]> Signed-off-by: Maxim Schwalm <[email protected]> Signed-off-by: Svyatoslav Ryhel <[email protected]>

Add device-tree for Pegatron Chagall, which is NVIDIA Tegra30-based Android tablet. Co-developed-by: Raffaele Tranquillini <[email protected]> Signed-off-by: Raffaele Tranquillini <[email protected]> Co-developed-by: Ion Agorria <[email protected]> Signed-off-by: Ion Agorria <[email protected]> Signed-off-by: Svyatoslav Ryhel <[email protected]>

pm_runtime_disable() cancels all pending power requests, while they should be completed for the Tegra SPI driver. Otherwise SPI clock won't be disabled ever again because clk refcount will become unbalanced. Enforce runtime PM suspension to put device into expected state before driver is unbound and device's RPM state is reset by driver's core. Signed-off-by: Dmitry Osipenko <[email protected]>

Change debugfs directory name to "smmu", which is a much more obvious name than the generic name of the memory controller device-tree node. Signed-off-by: Dmitry Osipenko <[email protected]>

All consumer-grade Android and Chromebook devices show a splash screen on boot and then display is left enabled when kernel is booted. This behaviour is unacceptable in a case of implicit IOMMU domains to which devices are attached during kernel boot since devices, like display controller, may perform DMA at that time. We can work around this problem by deferring the enable of SMMU translation for a specific devices, like a display controller, until the first IOMMU mapping is created, which works good enough in practice because by that time h/w is already stopped. Signed-off-by: Dmitry Osipenko <[email protected]>

…mebook The previous commit fixes problem where display client was attaching too early to IOMMU during kernel boot in a multi-platform kernel configuration which enables CONFIG_ARM_DMA_USE_IOMMU=y. The workaround that helped to defer the IOMMU attachment for Nyan Big Chromebook isn't needed anymore, revert it. Signed-off-by: Dmitry Osipenko <[email protected]>

The case of CONFIG_ARM_DMA_USE_IOMMU=y was found to be broken for host1x driver. Add back the workaround using arm_iommu_detach_device() as a temporary solution. Cc: [email protected] Fixes: af1cbfb ("gpu: host1x: Support DMA mapping of buffers" Signed-off-by: Dmitry Osipenko <[email protected]>

The case of CONFIG_ARM_DMA_USE_IOMMU=y was found to be broken for DRM driver. Add back the workaround using arm_iommu_detach_device() as a temporary solution. Cc: [email protected] Fixes: fa6661b ("drm/tegra: Optionally attach clients to the IOMMU") Signed-off-by: Dmitry Osipenko <[email protected]>

Tiling modifier can't be applied to YV12 video overlay by userspace because all tiling modifiers are filtered out for multi-plane formats. AFAIK, all modifiers should work with all of formats, hence the checking is incorrect. Fixes: e90124c ("drm/tegra: plane: Support format modifiers") Signed-off-by: Dmitry Osipenko <[email protected]>

Debug messages create too much CPU and memory activity by themselves, so it's difficult to debug lower rates and catch unwanted interrupts that happen rarely. Tracepoints are ideal in that regards because they do not contribute to the sampled date at all. This allowed me to catch few problems which are fixed by the followup patches, without tracepoints it would be much harder to do. Signed-off-by: Dmitry Osipenko <[email protected]>

Currently Memory Controller informs about erroneous memory accesses done by memory clients and that's it. Let's make it to block whole HW unit that corresponds to the misbehaving memory client in order to try to avoid memory corruptions and to stop deliberate attempts of manipulation by a misbehaving client. Signed-off-by: Dmitry Osipenko <[email protected]>

Enable IOMMU support for Host1x clients. Signed-off-by: Dmitry Osipenko <[email protected]>

This quirk is required in order to detect EMMC partitions on some Tegra20 devices. Signed-off-by: Dmitry Osipenko <[email protected]>

This reverts commit 828663c674099f5b2f831e1281913c762a6f61e8. It makes some T20 devices to see eMMC partitions, but breaks the others.

This enables IOMMU for Terga20 GPU. The patch will be removed after updating DRM WIP patch to support IOMMU in a different way. Signed-off-by: Dmitry Osipenko <[email protected]>

Device-tree should contain the ram-console node, example: /memreserve/ 0xbeb00000 0x100000; ram-console { compatible = "android,ram-console"; reg = <0xbeb00000 0x100000>; };

Add support for the gpt_sector cmdline parameter which will be used for looking up GPT entry on internal eMMC storage of NVIDIA Tegra20+ devices. This parameter is used by a stock downstream bootloader of Android devices. Signed-off-by: Dmitry Osipenko <[email protected]>

All NVIDIA Tegra devices use a special partition table format for the internal storage partitioning. Most of Tegra devices have GPT partition in addition to TegraPT, but some older Android consumer-grade devices do not or GPT is placed in a wrong sector, and thus, the TegraPT is needed in order to support these devices properly by the upstream kernel. This patch adds support for NVIDIA Tegra Partition Table format that is used at least by all NVIDIA Tegra20 and Tegra30 devices. Tested-by: Nils Östlund <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

It's quite useful to have unencrypted BCT exposed to userspace for debugging purposes, so let's expose it via sysfs. The BCT data will be present in '/sys/tegra/boot_config_table' binary file if BCT is available. Suggested-by: Michał Mirosław <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

The debug messages are useful for a WIP devices, so let's enable them. Signed-off-by: Dmitry Osipenko <[email protected]>

Downstream bootloader of Tegra20/30 doesn't support device-tree, so compiled DTB needs to be manually appended to the kernel's zImage. Signed-off-by: Dmitry Osipenko <[email protected]>

This patch disable the use of nv_msi_ht_cap_quirk_leaf quirk on arm and arm64 NVIDIA devices such as Tegra This fixes the following output: "pci 0000:00:01.0: nv_msi_ht_cap_quirk didn't locate host bridge" as experienced on a Trimslice device with PCI host bridge enabled v3: exclude the quirk for arm and arm64 instead of only for x86 v2: use __maybe_unused to avoid a warning on nv_msi_ht_cap_quirk_leaf Signed-off-by: Nicolas Chauvet <[email protected]> Reviewed-by: Manikanta Maddireddy <[email protected]> Acked-by: Thierry Reding <[email protected]>

The BO tiling isn't respected since the time when DRM modifiers became supported and in a result older userspace can't set tiling mode. This patch restores the legacy BO tiling flag support, which is useful for developing purposes. Signed-off-by: Dmitry Osipenko <[email protected]>

Color keying is the action of replacing pixels matching a given color (or range of colors) with transparent pixels in an overlay when performing blitting. Depending on the hardware capabilities, the matching pixel can either become fully transparent or gain adjustment of the pixels component values. Color keying is found in a large number of devices whose capabilities often differ, but they still have enough common features in range to standardize color key properties. This commit adds new generic DRM plane properties related to the color keying, providing initial color keying support. Signed-off-by: Laurent Pinchart <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

The new drivers and UAPI provide all features that are necessary for implementing of a proper userspace driver. The new driver takes a different approach in regards to working with sync points by making each submitted job to take an individual sync point, this solves the problem with the sync point recovery that old driver suffered from. The new Host1x driver and v2 UAPI are optimized for performance and minimal resources consumption. The new v2 UAPI exposes to userspace the HW cmdstream-related features that are necessary for a proper HW fencing. The staging v1 UAPI is kept functional and all of current userspace will continue to work with the new driver, note that some of the never-really-used features of v1 UAPI have been removed (like sync point increment IOCTL) and will return EPERM. The goal is to merge new features into the main driver once they are ready. Key moments of v2 UAPI: - Raw sync points are not exposed to userspace. - Job descriptors are embedded into the commands stream. Kernel driver parses the stream and patches the descriptors in-place. - Commands buffer is copied from userspace via usrptr (no BO allocation and uncached-reading overhead). - Channel is not restricted to a single client, thus 3d channel can take a multi-client job that uses 2d / 3d. - Supports explicit jobs fencing. DRM sync object and DRM scheduler are utilized to provide the fencing support. - Allows to use host1x gather opcode, which is restricted to data-upload usecase only. This allows userspace to pre-allocate a gather buffer, put shaders code / data there, and use two-word "gather" opcode to upload data from the buffer without pushing that data into the commands stream on each submission. Signed-off-by: Dmitry Osipenko <[email protected]>

Add SMB345 charger node to Nexus 7 2013 DTS. Proper charger configuration prevents battery from overcharging. Original author: Vinay Simha BN <[email protected]> Signed-off-by: David Heidelberg <[email protected]>

… to yaml Convert Tegra audio complex with the * ALC5632 * MAX98090 * RT5640 * RT5677 * SGTL5000 * TrimSlice * WM8753 * WM8903 * WM9712 codec to the YAML format. Signed-off-by: David Heidelberg <[email protected]>

ASUS Transformer and other tablets use RT5631 codec. Add RT5631 compatible to the tegra-audio binding. Signed-off-by: Svyatoslav Ryhel <[email protected]> Signed-off-by: Ion Agorria <[email protected]> Signed-off-by: David Heidelberg <[email protected]>

Add Realtek ALC5631/RT5631 codec support to the Tegra ASoC machine driver. The RT5631 codec is found on devices like ASUS Transformer TF201, TF700T and other Tegra-based Android tablets. Signed-off-by: Svyatoslav Ryhel <[email protected]> Signed-off-by: Ion Agorria <[email protected]>

Pins DATA_ENABLE, H_SYNC, V_SYNC, PIXEL_CLOCK are low polarity, set this in the registers to make the panel working. Signed-off-by: Sergey Larin <[email protected]>

Pixel format of the panel on this device is ABGR, not the typical RGBA format. There's no way to switch the pixel format in panel as there's no documenation, so do this in DRM driver instead. The proper solution would require checking MEDIA_BUS_FMT_* values in DRM driver and setting this value correctly in panel driver. Signed-off-by: Sergey Larin <[email protected]>

Low part of GTCON(IFCTL) register is responsible for flipping/rotation. This commit disables default rotation by 180 degrees. Signed-off-by: Sergey Larin <[email protected]>

Original timings cause issues on Tegra hardware - image is shifted and colors are wrong. Signed-off-by: Sergey Larin <[email protected]>

The panel driver gets probed before PMIC, so the regulator_bulk_get() call fails with EPROBE_DEFER, making the driver to probe later in the boot process. However, the screen gets corrupted in some time with noise displayed. To resolve this, reset GPIO is now requested before the regulator, setting the panel to the reset state. Signed-off-by: Sergey Larin <[email protected]>

This should be input/ driver, it has nothing to do with LED. (cherry picked from commit e510fd2c344d8f1967e186a3fa030ccee201a4d6) Signed-off-by: Sergey Larin <[email protected]>

Signed-off-by: David Heidelberg <[email protected]>

This chip variant differs from others - it has different register map and swapped rows/columns. Signed-off-by: Sergey Larin <[email protected]>

Add the binding for MELFAS MCS-5000 and MCS-5080 touchscreen controllers. Signed-off-by: David Heidelberg <[email protected]>

Add device-tree support to MCS touchkey driver. Signed-off-by: Beomho Seo <[email protected]> Signed-off-by: Seung-Woo Kim <[email protected]>

Tis patch use the devm_* managed functions to allocate resources. Change-Id: I9351869922b481a6791ca98f6dd3328d84424906 Signed-off-by: Beomho Seo <[email protected]>

This commit adds support for LED found on this touchkey controller. Signed-off-by: Sergey Larin <[email protected]>

(cherry picked from commit d58c0084b16491251b3871bfacbc070105eb9356) Signed-off-by: Sergey Larin <[email protected]> ASoC: tegra_wm8994: cleanup Remove unnecessary functions. Also, S/PDIF support is not needed. Signed-off-by: Sergey Larin <[email protected]> ASoC: tegra_wm8994: New driver based on WM8903 This fully routed driver resolves issues with suspend/resume state not being correctly restored. It also provides headphone detection and internal/external mic switching (however, mic detection is probably broken). Signed-off-by: Sergey Larin <[email protected]> ASoC: tegra_wm8994: Fix codec name The codec name in wm8994 driver is 'wm8994-aif1', not the 'wm8994-hifi' as there are 2 interfaces. Signed-off-by: Sergey Larin <[email protected]> ASoC: tegra_wm8994: Set mclk ID value The mclk_id value wasn't set, so setting clocks in wm8994_set_dai_sysclk failed with an error. This led to other failures in output configuration. Signed-off-by: Sergey Larin <[email protected]>

Support WM8994 inside the Tegra audio complex. Signed-off-by: David Heidelberg <[email protected]>

When OTG cable is inserted, the host needs to enable VBUS in order to supply power to the connected device. However, the charger detects that and starts charging the battery, draining the supplied power. Avoid this by using an optional regulator subnode which disables charging when enabled. Signed-off-by: Sergey Larin <[email protected]> power: supply: max8903: OTG disable fix The GPIO value wasn't changed after GPIO API changes - the GPIO is now ACTIVE_LOW in device tree instead of ACTIVE_HIGH. Signed-off-by: Sergey Larin <[email protected]>

Add device-tree for Tegra20-based Samsung SGH-I927 smartphone. Signed-off-by: Sergey Larin <[email protected]>

Document Samsung I927 Captivate Glide board. Signed-off-by: David Heidelberg <[email protected]>

The DMA subsystem could be entirely disabled in Kconfig and then the TEGRA20_APB_DMA option isn't available too. Hence kernel configuration fails if DMADEVICES Kconfig option is disabled due to the unsatisfiable dependency. The FUSE driver isn't a critical driver and currently it only provides NVMEM interface to userspace which isn't known to be widely used, and thus, it's fine if FUSE driver fails to load. Let's remove the erroneous Kconfig dependency and let the FUSE driver to fail the probing if DMA is unavailable. Fixes: 19d41e5 ("soc/tegra: fuse: Add APB DMA dependency for Tegra20") Reported-by: Necip Fazil Yildiran <[email protected]> Link: https://bugzilla.kernel.org/show_bug.cgi?id=209301 Signed-off-by: Dmitry Osipenko <[email protected]>

Signed-off-by: Dmitry Osipenko <[email protected]>

Add legacy `/sys/kernel/debug/tegra_pinmux` which allows to compare applied pinctrl configuration to the debug info of a downstream kernel.

All Tegra SoCs require an intermediate step for CPU clock rate transition. The clk driver takes care of switching the CPU clock to a backup parent during transition. But if there is a need to change CPU voltage for the transition, then going from a low freq to a high freq may take dozen milliseconds, which could be unacceptably long transition time for some applications which require CPU to run at a reasonable performance immediately, like audio playback for example. In order to mitigate the potentially long transition time, we will switch CPU to a faster backup frequency upfront, i.e. before the voltage change is initiated. Signed-off-by: Dmitry Osipenko <[email protected]>

…tion" This reverts commit 6fdbd8979fc9.

…roller This eases writing new device-trees. Signed-off-by: Dmitry Osipenko <[email protected]>

This removes a need to have bleeding edge userspace that knows how to work with the rotated planes. Only Opentegra driver supports planes rotation today, everything else is upside-down without the universal rotation support. The plan is to teach DRM core about the CRTC rotation capabilities and then this hack won't be needed, for now it's not obvious how to implement that. Signed-off-by: Dmitry Osipenko <[email protected]>

Assert DSI reset before power-up in order to ensure that hardware is properly re-initialized. This fixes occasional DSI panel initialization failures on boot if panel and DSI controller are left ON after bootloader. Signed-off-by: Dmitry Osipenko <[email protected]>

Speedo IDs are a valuable information, especially for bringing up new devices. These IDs should be printed out regardless of debugging state of the fuse driver. Signed-off-by: Dmitry Osipenko <[email protected]>

Signed-off-by: Svyatoslav Ryhel <[email protected]>

Implement driver for hot-plugged I2C busses: where some devices on a bus are hot-pluggable and their presence is indicated by GPIO line. Co-developed-by: Ion Agorria <[email protected]> Signed-off-by: Ion Agorria <[email protected]> Signed-off-by: Michał Mirosław <[email protected]>

Add binding document for the embedded controller found in Asus Transformer devices. Signed-off-by: Svyatoslav Ryhel <[email protected]>

Signed-off-by: Svyatoslav Ryhel <[email protected]>

Add support for accessing Embedded Controller RAM of Asus Transformer devices. This will be used by the EC MFD drivers. Signed-off-by: Michał Mirosław <[email protected]>

Support Nuvoton NPCE795-based ECs as used in Asus Transformer TF201, TF300T, TF300TG, TF300TL and TF700T pad and dock, as well as TF101 dock and TF701T pad. This is a glue driver handling detection and common operations for EC's functions. Co-developed-by: Svyatoslav Ryhel <[email protected]> Signed-off-by: Svyatoslav Ryhel <[email protected]> Signed-off-by: Michał Mirosław <[email protected]>

Add input driver for Asus Transformer dock keyboard and touchpad. Signed-off-by: Michał Mirosław <[email protected]>

Some keys in Asus Dock report keycodes that don't make sense according to their position, this patch modifies the incoming data that is sent to serio to send proper scancodes. This enables normal keyboard keys to become available by default unless AltGr is pressed, which sends the multimedia keys sent originally. Pressing ScreenLock + AltGr switches the default choice between 2 type of keys. Since this only modifies codes sent by asus-ec keys ext it doesn't affect normal keyboards at all. Co-developed-by: Ion Agorria <[email protected]> Signed-off-by: Ion Agorria <[email protected]> Signed-off-by: Michał Mirosław <[email protected]>

Add driver for Asus Transformer built-in LEDs. Signed-off-by: Michał Mirosław <[email protected]>

Driver contains one battery cell per EC controller and supports reading of battery status for Asus Transformer and its mobile dock. The voltage and charge values need to be multiplied by 1000 in order to be reported correctly, fix them. Co-developed-by: Dmitry Osipenko <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]> Co-developed-by: Svyatoslav Ryhel <[email protected]> Signed-off-by: Svyatoslav Ryhel <[email protected]> Signed-off-by: Michał Mirosław <[email protected]>

Unlike Pad, Asus Transformer Dock AC event is detected by reading embedded controller. Although, this is only known way to detect AC plug, driver uses polling with 1-2 sec interval and may cause warnings from other devices which use similar method, like keyboard. Signed-off-by: Svyatoslav Ryhel <[email protected]>

Signed-off-by: Svyatoslav Ryhel <[email protected]>

Add battery driver for Pegatron Chagall Android tablet. Signed-off-by: Svyatoslav Ryhel <[email protected]>

Signed-off-by: Dmitry Osipenko <[email protected]>

…10f004b00" This reverts commit f8286fe.

The p4wifi USB connector reads the STMPE811 ADC to determine if USB or AC cable is plugged in.

TODO: drop cmc623_initialize_clks and clocks from DTS v2: - fix drm_connector (David) - drop vrefresh (David) - drop return value from drm_panel_add (Max Buchholz) v3: - incorporated fixes and improvements from Dmitry Signed-off-by: David Heidelberg <[email protected]>

Broken wakeup_source, FIXME later.

- system_rev - reboot mode - charging mode v2: - disable write to hardcoded eMMC, to prevent possible corruption

Convert to a proper platform driver. Squash h/w initialization and reboot notifier to the driver. Signed-off-by: Dmitry Osipenko <[email protected]>

… for p4wifi

Signed-off-by: David Heidelberg <[email protected]>

Add device-tree for Samsung Galaxy Tab 10.1 (p4wifi) NVIDIA Tegra20-based tablet. Signed-off-by: David Heidelberg <[email protected]>

Document Samsung Galaxy Tab 10.1 p4wifi board. Signed-off-by: David Heidelberg <[email protected]>

it's a merged defconfig from postmarketos (kernel 5.0) and tegra_defconfig from grate-driver/linux (kernel 5.11-next). Disabled BIGSYS, which is used in postmarketos as a hack to combine system and cache partitions. v2: - dropped some PCIe Intel network adapters

Vendor prefix shouldn't start with capital letter. The Elpida Memory compatible was never used in practice, hence just correct the compatible. Signed-off-by: Dmitry Osipenko <[email protected]>

This is the same tables as ram-code 0 Signed-off-by: Nicolas Chauvet <[email protected]>

Add device-tree for Tegra30-based Lenovo IdeaTab A2109A. Primary things left to do: - LVDS bridge (for now we will assume it's always ON) - Sound - Power key Signed-off-by: Kai Jan Schmidt-Brauns <fix@me>

Document Lenovo IdeaTab A2109A board. Signed-off-by: David Heidelberg <[email protected]>

BCM4329 doesn't support BRCMF_C_GET_ASSOCLIST firmware call and WiFi eventually stop to work properly on Acer A500 during the FW call. Don't use that FW command on unsupported hardware to work around the problem. Signed-off-by: Dmitry Osipenko <[email protected]>

Ensure that clock is disabled on suspend to catch LPM programming bugs.

DMA flushing may fail if hardware unit is power-gated. We need to reset hardware unit and its memory clients in a certain order, but it becomes complicated when we need to power-up hardware domain for the first time since resets are requested in a special order. We assumed that power domains are initially turned on all devices, but this could be a wrong assumption. Signed-off-by: Dmitry Osipenko <[email protected]>

…ansmitter LVDS transmitter used in Surface RT. Signed-off-by: David Heidelberg <[email protected]>

Right now ACPI isn't implemented, so parsing the MADT/APIC table is not possible. Its contents have to be hardcoded. The current hardcoded table is for Mircrosoft Surface RT. Signed-off-by: Leander Wollersberger <[email protected]>

Add phandle names for memory/I2C/SPI/USB/SDMMC controller nodes to allow for cleaner device descriptions. Signed-off-by: Michał Mirosław <[email protected]>

Signed-off-by: Anton Bambura <[email protected]> Signed-off-by: Jonas Schwöbel <[email protected]>

Battery and Charger support for UEFI and APX boot. use CONFIG_BATTERY_CHARGER_SURFACE_RT to enable support Signed-off-by: Jonas Schwöbel <[email protected]>

Added audio output support. Internal speakers and headphones work. No internal mic's and no headset mic support. Signed-off-by: Jonas Schwöbel <[email protected]>

Trackpad right/left click correctly send BTN_LEFT/RIGHT but additionally sends KEY_F23. KEY_F23 is linked to some special actions: pmOS -> trackpad disabled notifitcation raspiOS -> open new terminal This problem is fixed now. Signed-off-by: Jonas Schwöbel <[email protected]>

Document Microsoft Surface RT board. Signed-off-by: David Heidelberg <[email protected]>

This device-tree is intended to be used with kernel running on https://github.com/digetx/tegra2_qemu Signed-off-by: Dmitry Osipenko <[email protected]>

Document Tegra20 QEMU board. Signed-off-by: David Heidelberg <[email protected]>

Create tuxmake builds for each push on master branch and run checkpatch.pl Each time is generated tagged release which overwrites previous. This tagged release contains tuxmake archive (zImage, dtbs, vmlinux etc.) Based on: https://gitlab.com/okias/kernel-simpleci Signed-off-by: David Heidelberg <[email protected]>

Enable options needed by Transformers, GalaxyTab, SGH-I927 and SurfaceRT devices. Signed-off-by: Dmitry Osipenko <[email protected]>

Supported devices: - acer-picasso; - microsoft surface-rt; - transformers; - pegatron chagall; - grouper / tilapia; - samsung-i927 glide; Link: grate-driver#69 (comment) Signed-off-by: Anton Bambura <[email protected]>

besides generic needed options: - built-in stuff needed for cryptsetup - anbox support (is broken on armv7, but we hope it will be fixed) - waydroid support - nftables - containers (docker, lxc) - zram Link: grate-driver#69 (comment) Signed-off-by: Anton Bambura <[email protected]>

NVIDIA Tegra30 thermal sensor driver has a hardware-controlled CPU cooling feature that halves CPU frequency once a specified trip point is breached. In order to account the hardware state transitions, which are reported by interrupt, the sensor driver needs to report the cooling state transition and this is done by thermal_cooling_device_stats_update(). The sensor driver could be compiled as a loadable driver module, but this API function isn't exported, hence export it. Signed-off-by: Dmitry Osipenko <[email protected]>

Expose Tegra30 thermal sensor as a cooling device and enable hardware-assisted DIV2 CPU frequency throttling. The DIV2 cooling is activated by hardware while the breach of hot temperature trip is detected by sensor. Signed-off-by: Dmitry Osipenko <[email protected]>

Tegra I2C device isn't guaranteed to be suspended after removal of the driver since driver uses pm_runtime_put() that is asynchronous and pm_runtime_disable() cancels pending power-change requests. This means that potentially refcount of the clocks may become unbalanced after removal of the driver. This a very minor problem which unlikely to happen in practice and won't cause any visible problems, nevertheless let's replace pm_runtime_disable() with pm_runtime_force_suspend() and use pm_runtime_put_sync() which disables RPM of the device and puts it into suspend before driver is removed. Signed-off-by: Dmitry Osipenko <[email protected]>

Not all OPP entries fit into a single word. In particular NVIDIA Tegra OPP tables use multi-word names. Allow OPP entry to have multi-worded name separated by hyphen. This silences DT checker warnings about wrong naming scheme. Reviewed-by: David Heidelberg <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

The clock-frequency property was never used and is deprecated now. Remove it from Nexus 7 device-tree. Signed-off-by: David Heidelberg <[email protected]>

Older device-trees don't specify padctrl interrupt and xhci-tegra driver now fails to probe with -EINVAL using those device-trees. Check interrupt presence and disallow runtime PM suspension if it's missing to fix the trouble. Fixes: 971ee24 ("usb: xhci: tegra: Enable ELPG for runtime/system PM") Reported-by: Nicolas Chauvet <[email protected]> Tested-by: Nicolas Chauvet <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

The current default is to leave the VDE clock's parent at the default, which is clk_m. However, that is not a configuration that will allow the VDE to function. Reparent it to pll_p instead to make sure the hardware can actually decode video content. Signed-off-by: Dmitry Osipenko <[email protected]>

Tegra114 and Tegra124 support reference picture marking, which will cause BSEV to write picture marking data to SDRAM. Make sure there is a valid destination address for that data to avoid error messages from the memory controller. [[email protected]: added BO support and moved secure BO allocation to kernel] Tested-by: Anton Bambura <[email protected]> # T114 ASUS TF701T Signed-off-by: Thierry Reding <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

Entries in the reference picture list are marked as invalid by setting the frame ID to 0x3f. Signed-off-by: Thierry Reding <[email protected]> Signed-off-by: Dmitry Osipenko <[email protected]>

Register misc device in the end of driver's probing since device should become visible to userspace once driver is fully prepared. Do the opposite in case of driver removal. This is a minor improvement that doesn't solve any problem. Signed-off-by: Dmitry Osipenko <[email protected]>

Add Video Decoder Engine node to Tegra114 device-tree. Signed-off-by: Anton Bambura <[email protected]>

LQ101R1SX03 is compatible with LQ101R1SX01, document it. Signed-off-by: Anton Bambura <[email protected]>

LQ101R1SX03 is compatible with LQ101R1SX01, add compatible to the driver. Signed-off-by: Anton Bambura <[email protected]>

Document Tegra114-based Asus Transformer Pad TF701T (asus-tf701t). Signed-off-by: Anton Bambura <[email protected]>

Add more labels in order to use label reference in device-specific dts files. Signed-off-by: Anton Bambura <[email protected]>

Add device-tree for Tegra114-based Asus Transformer Pad TF701T (K00C) tablet. Signed-off-by: Anton Bambura <[email protected]>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ARM: tegra: Add WiFi/BT support for ASUS TF701T #106

ARM: tegra: Add WiFi/BT support for ASUS TF701T #106

Commits on Oct 25, 2021

ARM: tegra: Add WiFi/BT support for ASUS TF701T #106

Are you sure you want to change the base?

ARM: tegra: Add WiFi/BT support for ASUS TF701T #106

Commits on Oct 25, 2021