From: Hermes Zhang
The CHARGE_NOW is map to REG_NAC for all the gauge chips beofre. But for
some chips (e.g. bq27z561) which doesn't have the REG_NAC, we use REG_RC
(remaining capacity) for CHARGE_NOW.
Signed-off-by: Hermes Zhang
---
drivers/power/supply/bq27xxx_battery.c | 35
On Wed, Dec 16, 2020 at 04:40:51PM -0800, Nick Desaulniers wrote:
> With newer GNU binutils, linking with BFD produces warnings for vmlinux:
> aarch64-linux-gnu-ld: warning: -z norelro ignored
>
> BFD can produce this warning when the target emulation mode does not
> support RELRO relocation
On Thu, Dec 17, 2020 at 4:54 AM Geert Uytterhoeven wrote:
>
> Hi Adam,
>
> On Sun, Dec 13, 2020 at 7:38 PM Adam Ford wrote:
> > The SoC was expecting two clock sources with different frequencies.
> > One to support 44.1KHz and one to support 48KHz. With the newly added
> > ability to configure
Hi Pali,
From the TI spec (e.g.
https://www.ti.com/lit/ug/tidu077/tidu077.pdf?ts=1608206347022_url=https%253A%252F%252Fwww.google.com%252F)
, the NAC and RC (RemainingCapacity) are different:
4.5 NominalAvailableCapacity( ): 0x08/0x09
This read-only command pair returns the uncompensated (less
On Thu, Dec 17, 2020 at 05:26:07PM +0900, Masahiro Yamada wrote:
> On Thu, Dec 17, 2020 at 8:04 AM Joe Lawrence wrote:
> >
> > On 12/16/20 1:14 AM, Masahiro Yamada wrote:
> > > On Tue, Dec 8, 2020 at 11:31 PM Artem Savkov
> > > wrote:
> > >>
> > >> On Tue, Dec 08, 2020 at 05:20:35PM +0800, WANG
On Thu, Dec 17, 2020 at 01:15:10AM -0800, John Hubbard wrote:
> On 12/16/20 10:23 AM, Matthew Wilcox (Oracle) wrote:
> > Implement readahead_batch_length() to determine the number of bytes in
> > the current batch of readahead pages and use it in btrfs.
> >
> > Signed-off-by: Matthew Wilcox
Hi Yifei,
On Sun, Oct 11, 2020 at 8:08 PM YiFei Zhu wrote:
> From: YiFei Zhu
>
> Currently the kernel does not provide an infrastructure to translate
> architecture numbers to a human-readable name. Translating syscall
> numbers to syscall names is possible through FTRACE_SYSCALL
>
Hi all,
This patch series will free some vmemmap pages(struct page structures)
associated with each hugetlbpage when preallocated to save memory.
In order to reduce the difficulty of the first version of code review.
>From this version, we disable PMD/huge page mapping of vmemmap if this
feature
Move bootmem info registration common API to individual bootmem_info.c.
And we will use {get,put}_page_bootmem() to initialize the page for the
vmemmap pages or free the vmemmap pages to buddy in the later patch.
So move them out of CONFIG_MEMORY_HOTPLUG_SPARSE. This is just code
movement without
On 12/08/20 13:28, Will Deacon wrote:
> If the scheduler cannot find an allowed CPU for a task,
> cpuset_cpus_allowed_fallback() will widen the affinity to cpu_possible_mask
> if cgroup v1 is in use.
>
> In preparation for allowing architectures to provide their own fallback
> mask, just return
The HUGETLB_PAGE_FREE_VMEMMAP option is used to enable the freeing
of unnecessary vmemmap associated with HugeTLB pages. The config
option is introduced early so that supporting code can be written
to depend on the option. The initial version of the code only
provides support for x86-64.
Like
In the subsequent patch, we will allocate the vmemmap pages when free
HugeTLB pages. But update_and_free_page() is called from a non-task
context(and hold hugetlb_lock), so we can defer the actual freeing in
a workqueue to prevent from using GFP_ATOMIC to allocate the vmemmap
pages.
When we free a HugeTLB page to the buddy allocator, we should allocate the
vmemmap pages associated with it. We can do that in the __free_hugepage()
before freeing it to buddy.
Signed-off-by: Muchun Song
---
include/linux/mm.h | 1 +
mm/hugetlb.c | 2 ++
mm/hugetlb_vmemmap.c | 11
Because we reuse the first tail vmemmap page frame and remap it
with read-only, we cannot set the PageHWPosion on a tail page.
So we can use the head[4].private to record the real error page
index and set the raw error page PageHWPoison later.
Signed-off-by: Muchun Song
Reviewed-by: Oscar
Every HugeTLB has more than one struct page structure. We __know__ that
we only use the first 4(HUGETLB_CGROUP_MIN_ORDER) struct page structures
to store metadata associated with each HugeTLB.
There are a lot of struct page structures associated with each HugeTLB
page. For tail pages, the value
On Thu, Dec 17, 2020 at 4:41 AM Geert Uytterhoeven wrote:
>
> On Sun, Dec 13, 2020 at 7:38 PM Adam Ford wrote:
> > The Bluetooth chip is capable of operating at 4Mbps, but the
> > max-speed setting was on the UART node instead of the Bluetooth
> > node, so the chip didn't operate at the correct
We should flush work when dissolving a hugetlb page to make sure that
the hugetlb page is freed to the buddy.
Signed-off-by: Muchun Song
---
mm/hugetlb.c | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index
For HugeTLB page, there are more metadata to save in the struct page.
But the head struct page cannot meet our needs, so we have to abuse
other tail struct page to store the metadata. In order to avoid
conflicts caused by subsequent use of more tail struct pages, we can
gather these discrete
Add a kernel parameter hugetlb_free_vmemmap to enable the feature of
freeing unused vmemmap pages associated with each hugetlb page on boot.
Signed-off-by: Muchun Song
Reviewed-by: Oscar Salvador
Reviewed-by: Barry Song
---
Documentation/admin-guide/kernel-parameters.txt | 14 ++
From: Borislav Petkov
Add the targets which add Kconfig items to the .config so that the
kernel can be run as a guest, to the main 'make help' output so that
they can be found easier and there's no need to grep the tree each time
to remember what they should be called.
Signed-off-by: Borislav
All the infrastructure is ready, so we introduce nr_free_vmemmap_pages
field in the hstate to indicate how many vmemmap pages associated with
a HugeTLB page that can be freed to buddy allocator. And initialize it
in the hugetlb_vmemmap_init(). This patch is actual enablement of the
feature.
We cannot optimize if a "struct page" crosses page boundaries. If
it is true, we can optimize the code with the help of a compiler.
When free_vmemmap_pages_per_hpage() returns zero, most functions are
optimized by the compiler.
Signed-off-by: Muchun Song
---
include/linux/hugetlb.h | 3 ++-
When cpu is going offline, set q->offline as true
and interrupt happened. The interrupt may call the
quarantine_put. But quarantine_put do not free the
the object. The object will cause memory leak.
Add qlink_free() to free the object.
Changes since v2:
- Add Fixes in the commit message
When cpu is going offline, set q->offline as true
and interrupt happened. The interrupt may call the
quarantine_put. But quarantine_put do not free the
the object. The object will cause memory leak.
Add qlink_free() to free the object.
Fixes: 6c82d45c7f03 (kasan: fix object remaining in offline
On 17.12.20 13:12, Muchun Song wrote:
> Hi all,
>
> This patch series will free some vmemmap pages(struct page structures)
> associated with each hugetlbpage when preallocated to save memory.
>
> In order to reduce the difficulty of the first version of code review.
> From this version, we
On 17.12.20 12:45, Anshuman Khandual wrote:
>
>
> On 12/10/20 12:34 PM, David Hildenbrand wrote:
>>
>>> Am 10.12.2020 um 07:58 schrieb Heiko Carstens :
>>>
>>> On Thu, Dec 10, 2020 at 09:48:11AM +0530, Anshuman Khandual wrote:
>> Alternatively leaving __segment_load() and vmem_add_memory()
Add 2 missing 'icc_put()' calls in the error handling path of the probe
function, as already done in the remove function.
Fixes: 32f0a6ddc8c9 ("media: venus: Use on-chip interconnect API")
Signed-off-by: Christophe JAILLET
---
drivers/media/platform/qcom/venus/core.c | 31
Dear RT folks!
I'm pleased to announce the v5.10.1-rt19 patch set.
Changes since v5.10.1-rt18:
- The RCU related patches have been updated resulting in updated
documentation.
- The tracing infrastructure is able to recognize "serving softirq"
context with PREEMPT_RT enabled and
A CPU's current task can have its {closid, rmid} fields read locally while
they are being concurrently written to from another CPU. This can happen
anytime __resctrl_sched_in() races with either __rdtgroup_move_task() or
rdt_move_group_tasks().
Prevent load / store tearing for those accesses by
From: siyanteng
When building cma_heap the following error shows up:
drivers/dma-buf/heaps/cma_heap.c:195:10: error: implicit declaration of
function 'vmap'; did you mean 'kmap'? [-Werror=implicit-function-declaration]
195 | vaddr = vmap(buffer->pages, buffer->pagecount, VM_MAP, PAGE_KERNEL);
From: Stefan Chulski
During GoP port 2 Networking Complex Control mode of operation configurations,
also GoP port 3 mode of operation was wrongly set.
Patch removes these configurations.
GENCONF_CTRL0_PORTX naming also fixed.
Cc: sta...@vger.kernel.org
Fixes: f84bf386f395 ("net: mvpp2:
This patch series add support for Linkup/Linkdown suport for LAN8814 phy
and 1588 Driver support for the same phy.
v3->v4
-Changed call to MAC API in phy driver to phy_trigger_machine.
-Adding PTP maintainer to CC list for 1588 Driver.
v2->v3
-Split the patch into 2 patches, one is
This patch add supports for Link up and Link down interrupts
to LAN8814 phy.
Signed-off-by: Divya Koppera
---
v1 -> v2
* Fixed warnings
Reported-by: kernel test robot
v2 -> v3
* Splitting 1588 support patch to Link up/down patch
and 1588 support patch.
v3 -> v4
* Changed MAC API call to
This patch add supports for 1588 Hardware Timestamping support
to LAN8814 Quad Phy. It supports L2 and Ipv4 encapsulations.
Signed-off-by: Divya Koppera
---
v1 -> v2
* Fixed warnings
Reported-by: kernel test robot
v2 -> v3
* Split the patch to linkup/linkdown interrupt handling
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a003-20201217
x86_64
On Thu, Dec 17, 2020 at 09:44:31AM +0100, Nicolas Saenz Julienne wrote:
> On Thu, 2020-12-17 at 16:08 +0800, Peng Fan (OSS) wrote:
> > From: Peng Fan
> >
> > ZONE_DMA should not be disabled, otherwise arm64_dma_phys_limit is
> > left uninitialized and cause swiotlb have IO TLB above 4GB which
>
allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a003-20201217
x86_64 randconfig-a006-20201217
x86_64 randconfig-a002-20201217
x86_64
onfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a003-20201217
x86_64 randconfig-a002-20201
Instead of open coding DEVICE_ATTR(), use the
DEVICE_ATTR_RW(), DEVICE_ATTR_RO() and DEVICE_ATTR_WO()
macros wherever possible.
This required a few functions to be renamed but the
functionality itself is unchanged.
Signed-off-by: Dwaipayan Ray
---
Note: The patch is compiled tested only.
Merges
On Thu, Dec 17, 2020 at 9:18 PM Borislav Petkov wrote:
>
> From: Borislav Petkov
>
> Add the targets which add Kconfig items to the .config so that the
> kernel can be run as a guest, to the main 'make help' output so that
> they can be found easier and there's no need to grep the tree each time
On 16.12.20 19:23, Matthew Wilcox (Oracle) wrote:
> One of the great things about compound pages is that when you try to
> do various operations on a tail page, it redirects to the head page and
> everything Just Works. One of the awful things is how much we pay for
> that simplicity. Here's an
On 12/16/2020 11:16 PM, Arnaldo Carvalho de Melo wrote:
Em Wed, Dec 16, 2020 at 11:30:47AM -0300, Arnaldo Carvalho de Melo escreveu:
Em Wed, Dec 16, 2020 at 07:14:02PM +0800, Jiaxun Yang escreveu:
在 2020/12/16 下午6:05, Tiezhu Yang 写道:
Hi,
In the current upstream mainline kernel, perf record
Hi Hans,
On Thu, Dec 17, 2020 at 11:53:42AM +0100, Hans Verkuil wrote:
> On 17/12/2020 11:49, Maxime Ripard wrote:
> > Hi Hans,
> >
> > On Wed, Dec 16, 2020 at 01:35:43PM +0100, Hans Verkuil wrote:
> >> Hi Maxime,
> >>
> >> On 10/12/2020 14:46, Maxime Ripard wrote:
> >>> Hi,
> >>>
> >>> Here's a
On Fri, 11 Dec 2020 10:04:43 -0500
Matthew Rosato wrote:
> On 12/11/20 10:01 AM, Matthew Rosato wrote:
> > On 12/11/20 9:35 AM, Cornelia Huck wrote:
> >> Let me summarize this to make sure I understand this new region
> >> correctly:
> >>
> >> - some devices may have relaxed alignment/length
On Thu, 17 Dec 2020 09:17:24 +0100 SeongJae Park wrote:
> From: SeongJae Park
>
> Some code does not directly make 'xenbus_watch' object and call
> 'register_xenbus_watch()' but use 'xenbus_watch_path()' instead. This
> commit adds support of 'will_handle' callback in the
>
From: SeongJae Park
This commit adds a counter of pending messages for each watch in the
struct. It is used to skip unnecessary pending messages lookup in
'unregister_xenbus_watch()'. It could also be used in 'will_handle'
callback.
This is part of XSA-349
This is upstream commit
From: SeongJae Park
Some code does not directly make 'xenbus_watch' object and call
'register_xenbus_watch()' but use 'xenbus_watch_path()' instead. This
commit adds support of 'will_handle' callback in the
'xenbus_watch_path()' and it's wrapper, 'xenbus_watch_pathfmt()'.
This is part of
From: SeongJae Park
If handling logics of watch events are slower than the events enqueue
logic and the events can be created from the guests, the guests could
trigger memory pressure by intensively inducing the events, because it
will create a huge number of pending events that exhausting the
There is no check for the kcontrol against NULL and in some cases
it causes kernel to crash.
Fixes: 2d744ecf2b984 ("ASoC: Intel: Skylake: Automatic DMIC format
configuration according to information from NHLT")
Cc: # 5.4+
Signed-off-by: Lukasz Majczak
Reviewed-by: Mateusz Gorski
---
From: SeongJae Park
This commit adds support of the 'will_handle' watch callback for
'xen_bus_type' users.
This is part of XSA-349
This is upstream commit be987200fbaceaef340872841d4f7af2c5ee8dc3
Cc: sta...@vger.kernel.org
Signed-off-by: SeongJae Park
Reported-by: Michael Kurth
Reported-by:
From: SeongJae Park
Changes from v1
(https://lore.kernel.org/stable/20201217081727.8253-1-sjp...@amazon.com/)
- Remove wrong 'Signed-off-by' lines for 'Author Redacted'
SeongJae Park (5):
xen/xenbus: Allow watches discard events before queueing
xen/xenbus: Add 'will_handle' callback support
On Fri, Dec 11 2020 at 14:14, Andy Lutomirski wrote:
> On Mon, Nov 23, 2020 at 10:10 PM wrote:
> After contemplating this for a bit, I think this isn't really the
> right approach. It *works*, but we've mostly just created a bit of an
> unfortunate situation. Our stack, on a (possibly nested)
commit 367c820ef08082 ("arm64: Enable perf events based hard lockup detector")
reinitilizes lockup detector after arm64 PMU is initialized and provide
another chance for access smp_processor_id() in preemptible context.
Since hardlockup_detector_event_create() use many percpu relative variable,
I figured I would send a new version before going on vacation, so I can
work on it when I am back.
Changes from RFCv3 to Patchv1:
- Addressed feedback from David
- Re-order patches
Changes from v2 -> v3:
- Re-order patches (Michal)
- Fold "mm,memory_hotplug: Introduce MHP_MEMMAP_ON_MEMORY"
Let the caller check whether it can pass MHP_MEMMAP_ON_MEMORY by
checking mhp_supports_memmap_on_memory().
MHP_MEMMAP_ON_MEMORY can only be set in case
ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE is enabled, the architecture supports
altmap, and the range to be added spans a single memory block.
Let the caller check whether it can pass MHP_MEMMAP_ON_MEMORY by
checking mhp_supports_memmap_on_memory().
MHP_MEMMAP_ON_MEMORY can only be set in case
ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE is enabled, the architecture supports
altmap, and the range to be added spans a single memory block.
Physical memory hotadd has to allocate a memmap (struct page array) for
the newly added memory section. Currently, alloc_pages_node() is used
for those allocations.
This has some disadvantages:
a) an existing memory is consumed for that purpose
(eg: ~2MB per 128MB memory section on x86_64)
My employment with TI is ending tomorrow, so update the email address
entry in the maintainers file. Also, I don't expect to spend that much
time with maintaining TI code anymore, so downgrade the status level to
odd fixes only on areas where I remain as the main contact point for
now, and move
Self stored memmap leads to a sparse memory situation which is unsuitable
for workloads that requires large contiguous memory chunks, so make this
an opt-in which needs to be explicitly enabled.
To control this, let memory_hotplug have its own memory space, as suggested
by David, so we can add
On 17/12/2020 12:38, Srinivas Pandruvada wrote:
> On Thu, 2020-12-17 at 07:28 +0100, Daniel Lezcano wrote:
>> On 10/12/2020 13:15, Daniel Lezcano wrote:
>>> The acpi driver wants to do a netlink notification in case of a hot
>>> or
>>> critical trip point. Implement the corresponding ops to be
In order to use self-hosted memmap array, the platform needs to have
support for CONFIG_SPARSEMEM_VMEMMAP and altmap.
Currently, only arm64, PPC and x86_64 have the support, so enable those
platforms with ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE.
ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE will be checked later on
Hi Juergen,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.10]
[cannot apply to xen-tip/linux-next tip/x86/core tip/x86/asm next-20201217]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
On 12/17/20 12:06 PM, Takashi Iwai wrote:
On Thu, 17 Dec 2020 11:59:23 +0100,
Lars-Peter Clausen wrote:
On 12/17/20 10:55 AM, Takashi Iwai wrote:
On Thu, 17 Dec 2020 10:43:45 +0100,
Lars-Peter Clausen wrote:
On 12/17/20 5:15 PM, Robin Gong wrote:
Since mmap for userspace is based on page
On 12/16/20 4:45 PM, Jakub Kicinski wrote:
> On Tue, 15 Dec 2020 06:22:28 -0800 t...@redhat.com wrote:
>> From: Tom Rix
>>
>> See Documentation/core-api/printk-formats.rst.
>> h should no longer be used in the format specifier for printk.
>>
>> Signed-off-by: Tom Rix
> That's for new code I
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git
tags/fuse-update-5.11
- Improve performance of virtio-fs in mixed read/write workloads.
- Try to revalidate cache before returning EEXIST on exclusive create.
- Add a couple of miscellaneous bug
On Thu, Dec 17, 2020 at 02:07:01PM +0100, Thomas Gleixner wrote:
> On Fri, Dec 11 2020 at 14:14, Andy Lutomirski wrote:
> > On Mon, Nov 23, 2020 at 10:10 PM wrote:
> > After contemplating this for a bit, I think this isn't really the
> > right approach. It *works*, but we've mostly just created
Hi Tomasz,
Thanks for your comments, I have a few questions below.
On 12/16/20 12:13 AM, Tomasz Figa wrote:
> On Tue, Dec 15, 2020 at 11:37 PM Helen Koike
> wrote:
>>
>> Hi Tomasz,
>>
>> On 12/14/20 7:46 AM, Tomasz Figa wrote:
>>> On Fri, Dec 4, 2020 at 4:52 AM Helen Koike
>>> wrote:
On 12/16/20 9:44 PM, Xu Yilun wrote:
> The match ops allows dfl drivers have their own matching algorithem
> instead of the standard id_table matching.
>
> This is to support the DFL UIO driver. It intends to match any DFL
> device which could not be handled by other DFL drivers.
>
>
On Wed, Dec 16, 2020 at 08:25:18PM -0800, Stephen Boyd wrote:
> > spin_lock_irq(>lock);
> > + if (mas->cur_xfer) {
>
> How is it possible that cs change happens when cur_xfer is non-NULL?
We will set the initial chip select state during controller setup.
signature.asc
On Thu, Dec 17, 2020 at 12:40:00PM +0300, Dmitry Osipenko wrote:
> The PHY hardware needs the delay of 2ms after power up, otherwise initial
> interrupt may be lost if USB controller is accessed before PHY is settled
> down. Previously this issue was masked by implicit delays, but now it pops
> up
On 12/16/20 9:44 PM, Xu Yilun wrote:
> This patch supports the DFL drivers be written in userspace. This is
> realized by exposing the userspace I/O device interfaces.
>
> The driver leverages the uio_pdrv_genirq, it adds the uio_pdrv_genirq
> platform device with the DFL device's resources, and
On 12/16/20 9:44 PM, Xu Yilun wrote:
> This patch adds description for UIO support for dfl devices on DFL
> bus.
Thanks for the changes.
Reviewed-by: Tom Rix
> Signed-off-by: Xu Yilun
> ---
> v2: no doc in v1, add it for v2.
> v3: some documentation fixes.
> ---
>
Borislav Petkov writes:
> On Mon, Dec 14, 2020 at 10:27:09PM +0900, Punit Agrawal wrote:
>> IIUC, this suggests that Linux booting on anything prior to Zen3 is down
>> to pure luck - I hope that wasn't the case.
>
> WTF does this have to do with linux booting?!
I guess I misunderstood the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Linus,
Please pull powerpc updates for 5.11.
There's only one conflict I'm aware of, which is the three lkdtm files,
resolution is simply to take both sides.
Notable out of area changes:
drivers/misc/lkdtm/* # 3ba150fb2120
On Wed, 2020-12-16 at 14:31 +0100, Mike Galbraith wrote:
> When the below new to 5.11 cycle badness happens, it's time to reboot.
>
> ...
> [ 27.467260] NFSD: Using UMH upcall client tracking operations.
> [ 27.467273] NFSD: starting 90-second grace period (net f0a0)
> [ 27.965138]
On Thu, Dec 17, 2020 at 09:47:07PM +0900, Masahiro Yamada wrote:
> I do not want to touch scripts/kconfig/Makefile
> every time somebody adds a new file to
> kernel/configs/*.config or arch/$(ARCH)/configs/*.config
Because that happens so often and somehow burdens your maintenance
effort
On Thu, Dec 17, 2020 at 5:12 AM Geert Uytterhoeven wrote:
>
> Hi Adam,
>
> CC alsa-devel
>
> On Sun, Dec 13, 2020 at 7:38 PM Adam Ford wrote:
> > With the newly added configurable clock options, the audio CODEC can
> > configure the mclk automatically. Add the reference to the versaclock.
> >
On Thu, Dec 17, 2020 at 12:40:01PM +0300, Dmitry Osipenko wrote:
> Support programming of waking up from a low power mode by implementing the
> generic set_wakeup() callback of the USB PHY API.
>
> Tested-by: Matt Merhar
> Tested-by: Nicolas Chauvet
> Tested-by: Peter Geis
> Tested-by: Ion
On Thu, Dec 17, 2020 at 12:40:03PM +0300, Dmitry Osipenko wrote:
> Rename all occurrences in the code from "udc" to "usb" and change the
> Kconfig entry in order to show that this driver supports USB modes other
> than device-only mode. The follow up patch will add host-mode support and
> it will
On Thu, Dec 17, 2020 at 03:46:17PM +0800, Huaixin Chang wrote:
> In this patch, we introduce the notion of CFS bandwidth burst. Unused
> "quota" from pervious "periods" might be accumulated and used in the
> following "periods". The maximum amount of accumulated bandwidth is
> bounded by "burst".
On 12/16/20 9:44 PM, Xu Yilun wrote:
> This patchset supports some dfl device drivers written in userspace.
>
> In the patchset v1, the "driver_override" interface should be used to bind
> the DFL UIO driver to DFL devices. But there is concern that the
> "driver_override" interface is not OK
On Thu, Dec 17, 2020 at 12:40:04PM +0300, Dmitry Osipenko wrote:
> From: Peter Geis
>
> Add USB host mode to the Tegra HDRC driver. This allows us to benefit from
> support provided by the generic ChipIdea driver instead of duplicating the
> effort in a separate ehci-tegra driver.
>
>
On Thu, Dec 17, 2020 at 12:40:05PM +0300, Dmitry Osipenko wrote:
> Tegra PHY driver now supports waking up controller from a low power mode.
> Enable runtime PM in order to put controller into the LPM during idle.
>
> Tested-by: Matt Merhar
> Tested-by: Nicolas Chauvet
> Tested-by: Peter Geis
Currently checkpatch warns for long line in commit messages even for
URL lines.
An evaluation over v4.13..v5.8 showed that out of ~11000 warnings for
this class, around 790 are due to the line containing link.
E.g. running checkpatch on commit 3cde818cd02b ("ASoC: topology:
Consolidate how
On Thu, Dec 17, 2020 at 12:40:06PM +0300, Dmitry Osipenko wrote:
> The ChipIdea driver now provides USB2 host mode support for NVIDIA Tegra
> SoCs. The ehci-tegra driver is obsolete now, remove it and redirect the
> older Kconfig entry to the CI driver.
>
> Tested-by: Matt Merhar
> Tested-by:
On Thu, Dec 17, 2020 at 12:12:46PM +, Matthew Wilcox wrote:
> ehh ... probably an off-by-one. Does subtracting 1 from contig_end fix it?
> I'll spool up a test VM shortly and try it out.
Yes, this fixed it:
- u64 contig_end = contig_start + readahead_batch_length(rac);
+
17.12.2020 16:41, Thierry Reding пишет:
> On Thu, Dec 17, 2020 at 12:40:05PM +0300, Dmitry Osipenko wrote:
>> Tegra PHY driver now supports waking up controller from a low power mode.
>> Enable runtime PM in order to put controller into the LPM during idle.
>>
>> Tested-by: Matt Merhar
>>
On Thu, Dec 17, 2020 at 12:15:52PM +, Qais Yousef wrote:
> On 12/08/20 13:28, Will Deacon wrote:
> > If the scheduler cannot find an allowed CPU for a task,
> > cpuset_cpus_allowed_fallback() will widen the affinity to cpu_possible_mask
> > if cgroup v1 is in use.
> >
> > In preparation for
On Thu, Dec 17, 2020 at 12:40:07PM +0300, Dmitry Osipenko wrote:
> The ehci-tegra driver was superseded by the generic ChipIdea USB driver,
> update the tegra's defconfig accordingly.
>
> Signed-off-by: Dmitry Osipenko
> ---
> arch/arm/configs/tegra_defconfig | 3 ++-
> 1 file changed, 2
From: Borislav Petkov
Realign help text vertically and add spacing so that target help text
is properly separated.
No functional changes.
Signed-off-by: Borislav Petkov
---
arch/x86/Makefile | 29 +++--
1 file changed, 15 insertions(+), 14 deletions(-)
diff --git
From: Borislav Petkov
Add the targets which add Kconfig items to the .config so that the
kernel can be run as a guest, to the 'make help' output so that they
can be found easier and there's no need to grep the tree each time to
remember what they should be called.
Signed-off-by: Borislav Petkov
17.12.2020 16:33, Thierry Reding пишет:
>> +/* PHY won't resume if reset is asserted */
>> +if (phy->wakeup_enabled)
>> +goto chrg_cfg0;
>>
>> val = readl_relaxed(base + USB_SUSP_CTRL);
>> val |= UTMIP_RESET;
>> writel_relaxed(val, base + USB_SUSP_CTRL);
>>
Hi Rob,
On 15/12/20 9:42 pm, Aswath Govindraju wrote:
> Hi Rob,
> On 15/12/20 3:53 am, Rob Herring wrote:
>> On Fri, Dec 11, 2020 at 08:34:57PM +0530, Aswath Govindraju wrote:
>>> Hi,
>>> On 11/12/20 9:03 am, Rob Herring wrote:
On Wed, Dec 09, 2020 at 11:27:07PM +0530, Aswath Govindraju
On Thu, Dec 17, 2020 at 01:47:57PM +0100, David Hildenbrand wrote:
> On 16.12.20 19:23, Matthew Wilcox (Oracle) wrote:
> > One of the great things about compound pages is that when you try to
> > do various operations on a tail page, it redirects to the head page and
> > everything Just Works.
On Thu, Dec 17, 2020 at 11:44 AM Srinivas Pandruvada
wrote:
>
> This change tries to address an issue, when BIOS disabled turbo
> but HWP_CAP guaranteed is changed later and user space wants to take
> advantage of this increased guaranteed performance.
>
> The HWP_CAP.GUARANTEED value is not a
On Thu, Dec 17, 2020 at 02:51:58PM +0800, Yunfeng Ye wrote:
>
>
> On 2020/12/15 22:47, Frederic Weisbecker wrote:
> > On Tue, Dec 15, 2020 at 08:06:34PM +0800, Yunfeng Ye wrote:
> >> The idle_exittime field of tick_sched is used to record the time when
> >> the idle state was left. but currently
17.12.2020 16:36, Thierry Reding пишет:
> On Thu, Dec 17, 2020 at 12:40:03PM +0300, Dmitry Osipenko wrote:
>> Rename all occurrences in the code from "udc" to "usb" and change the
>> Kconfig entry in order to show that this driver supports USB modes other
>> than device-only mode. The follow up
>From QPIC version 2.0 onwards new register got added to
read last codeword. This change will update the same.
For first three code word READ_LOCATION_n register will be
use.For last code wrod READ_LOCATION_LAST_CW_n register will be
use.
Signed-off-by: Md Sadre Alam
---
> Do you think it's a fix that should be backported to stable branches?
> If yes, please add 'Fixes: ("commit title")' and it may be
> good to add 'Cc: sta...@vger.kernel.org' adjacent to the Signed-off-by
> tag.
netdev patches should not be Cc: sta...@vger.kernel.org. David and
Jakub handle
4k requires two dsi pipes, so don't report MODE_OK when only a
single pipe is configured. But rather report MODE_PANEL to
signal that requirements of the panel are not being met.
Reported-by: Peter Collingbourne
Suggested-by: Peter Collingbourne
Signed-off-by: Robert Foss
Tested-by: John
801 - 900 of 988 matches
Mail list logo
