On Wed, Oct 21, 2020 at 10:33:25PM +0200, Jernej Skrabec wrote:
> If scaling matrix control is present, VPU should not use default matrix.
> Fix that.
>
> Fixes: b3a23db0e2f8 ("media: cedrus: Use H264_SCALING_MATRIX only when
> required")
> Signed-off-by: Jernej Skrabec
Acked-by: Maxime Ripard
On Wed, Oct 21, 2020 at 11:15:54PM -0700, Prashant Malani wrote:
> A PD-capable device can return up to 3 Product Type VDOs as part of its
> DiscoverIdentity Response (USB PD Spec, Rev 3.0, Version 2.0, Section
> 6.4.4.3.1). Add a sysfs attribute to expose these to userspace.
>
> Cc: Benson Leung
On Wed, 2020-10-21 at 16:19 -0600, Jonathan Corbet wrote:
> CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you can confirm the sender
> and know the content is safe.
>
>
>
> On Thu, 22 Oct 2020 08:55:42 +1100
> Stephen Rothwell w
On Wed, Oct 21, 2020 at 11:49:07PM +0200, Łukasz Stelmach wrote:
> Add bindings for AX88796C SPI Ethernet Adapter.
>
> Signed-off-by: Łukasz Stelmach
> ---
> .../bindings/net/asix,ax88796c.yaml | 69 +++
> 1 file changed, 69 insertions(+)
> create mode 100644 Documenta
From: Fam Zheng
Both seem overlooked while adding the section in the main content.
Signed-off-by: Fam Zheng
---
v2: Add sign-off.
---
Documentation/admin-guide/sysctl/vm.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/admin-guide/sysctl/vm.rst
b/Documentation/admin-
On Wed, Oct 21, 2020 at 11:27:57AM -0700, Dmitry Torokhov wrote:
> On Wed, Oct 21, 2020 at 12:56:14PM +0200, Oleksij Rempel wrote:
> >
> > As you can see, I would need to configure my dts with spi-cs-high flag,
> > even if the hardware is actually ACTIVE_LOW. If I will go this way, I
> > would ris
On Wed, Oct 21, 2020 at 11:49:06PM +0200, Łukasz Stelmach wrote:
> Add the prefix for ASIX Electronics Corporation
End the sentence with a full stop.
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
>
> > > Did you mean /dev/disk/by-[part]label/ symlink? It's quite reasonable to
> > > use them by udev in userspace such as initramfs but some cases does not
> > use
> > > initramfs or initrd. In that case, we need to load the root
> > > device(/dev/sda[N]) directly from kernel.
> >
> > Please us
Hi,
On Tue, Oct 20, 2020 at 10:59:58AM -0400, Mathieu Desnoyers wrote:
> - On Oct 20, 2020, at 10:36 AM, Peter Zijlstra pet...@infradead.org wrote:
>
> > On Tue, Oct 20, 2020 at 09:47:13AM -0400, Mathieu Desnoyers wrote:
> >> +void membarrier_update_current_mm(struct mm_struct *next_mm)
> >>
Hi Daeho,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on f2fs/dev-test]
[also build test WARNING on linus/master v5.9 next-20201022]
[cannot apply to linux/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch
On Thu, Oct 22, 2020 at 01:53:15PM +0800, zhuoliang.zhang wrote:
>
> there are 2 related hash lists : net->xfrm.state_bydst and
> net->xfrm.state_byspi:
>
> 1. a new state x is alloced in xfrm_state_alloc() and added into the
> bydst hlist in __find_acq_core() on the LHS;
> 2. on the RHS, state_
- atomic_check removed
- video data input and output formats added
- bus formats read from drm_bridge_state.output_bus_cfg.format
and .atomic_get_input_bus_fmts() instead of connector
Signed-off-by: Vinay Simha BN
---
v1:
* Laurent Pinchart review comments incorporated
drm_bridge_state.out
From: Kai-Chuan Hsieh
Some Dell platforms rely on modalias to customize configuration,
the product sku can be more specific for the hardware.
Add product_sku to modalias for better utilization.
Signed-off-by: Kai-Chuan Hsieh
---
drivers/firmware/dmi-id.c | 31 ---
> Since WB feature has been added, WB related sysfs entries can be accessed
> even when an UFS device does not support WB feature. In that case, the
> descriptors which are not supported by the UFS device may be wrongly
> reported when they are accessed from their corrsponding sysfs entries.
> Fix
On Wed, 21 Oct 2020 14:32:52 -0700 Brendan Higgins
wrote:
> On Mon, Oct 12, 2020 at 3:27 AM SeongJae Park wrote:
> >
> > From: SeongJae Park
> >
> > 'kunit_kernel.kunittest_config' was constant at first, and therefore it
> > used UPPER_SNAKE_CASE naming convention that usually means it is
> >
On Wed, 21 Oct 2020 at 12:40, Arnd Bergmann wrote:
>
> On Wed, Oct 21, 2020 at 12:39 PM Joel Stanley wrote:
>
> >
> > diff --git a/drivers/net/ethernet/faraday/ftgmac100.c
> > b/drivers/net/ethernet/faraday/ftgmac100.c
> > index 331d4bdd4a67..15cdfeb135b0 100644
> > --- a/drivers/net/ethernet/fa
It is now possible to only build book3s/32 kernel for
CPUs without hash table.
Opt out hash related code when CONFIG_PPC_BOOK3S_604 is not selected.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_book3s_32.S | 12
arch/powerpc/mm/book3s32/Makefile| 4 +++-
2 file
flush_tlb_mm() and flush_tlb_page() handle both the MMU_FTR_HPTE_TABLE
case and the other case.
The non MMU_FTR_HPTE_TABLE case is trivial as it is only a call
to _tlbie()/_tlbia() which is not worth a dedicated function.
Make flush_tlb_mm() and flush_tlb_page() hash specific and call
them from t
early_mmu_init() is independent of MMU type and not
directly linked to tlb handling.
In a following patch, tlb.c will be restricted to HASH mmu.
Move early_mmu_init() into mmu.c which is common.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/book3s32/mmu.c | 4
arch/powerpc/mm/book3s
book3s/32 has two main families:
- CPU with 603 cores that don't have HASH PTE table and
perform SW TLB loading.
- Other CPUs based on 604+ cores that have HASH PTE table.
This leads to some complex logic and additionnal code to
support both. This makes sense for distribution kernels
that aim at r
As 601 is gone, CONFIG_PPC_BOO3S_6xx and CONFIG_PPC_BOOK3S_32
are dedundant.
Remove CONFIG_PPC_BOOK3S_6xx.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/cputable.c | 4 ++--
arch/powerpc/platforms/Kconfig.cputype | 6 +-
2 files changed, 3 insertions(+), 7 deletions(-)
di
flush_hash_entry() is a simple function calling
flush_hash_pages() if it's a hash MMU or doing nothing otherwise.
Inline it.
And use it also in __ptep_test_and_clear_young().
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/book3s/32/pgtable.h | 17 +++--
arch/powerpc/i
We now have an early hash table on hash MMU, so no need to check
Hash var to know if the Hash table is set of not.
Use mmu_has_feature(MMU_FTR_HPTE_TABLE) instead. This will allow
optimisation via jump_label.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/book3s32/mmu.c | 2 +-
arch/power
flush_range() handle both the MMU_FTR_HPTE_TABLE case and
the other case.
The non MMU_FTR_HPTE_TABLE case is trivial as it is only a call
to _tlbie()/_tlbia() which is not worth a dedicated function.
Make flush_range() a hash specific and call it from tlbflush.h based
on mmu_has_feature(MMU_FTR_H
flush_tlb_range() and flush_tlb_kernel_range() are trivial calls to
flush_range().
Make flush_range() global and inline flush_tlb_range()
and flush_tlb_kernel_range().
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/book3s/32/tlbflush.h | 15 --
arch/powerpc/mm/book3s32/tlb
In order to selectively build the kernel for 603 SW TLB handling,
regroup all 603 based CPUs together.
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/cputable.h | 14 +++---
arch/powerpc/kernel/cputable.c | 78 ++---
2 files changed, 47 insertions(+), 4
On non SMP, _tlbie() is just a tlbie plus a sync instruction.
Make it static inline.
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/book3s/32/tlbflush.h | 7 +++
arch/powerpc/mm/book3s32/hash_low.S | 7 ++-
2 files changed, 9 insertions(+), 5 deletions(-)
diff -
On book3s/32, tlb_flush() does nothing when the CPU has a hash table,
it calls _tlbia() otherwise.
Inline it.
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/book3s/32/tlbflush.h | 11 +++
arch/powerpc/mm/book3s32/tlb.c| 15 ---
2 files changed,
In order to use _tlbie() and _tlbia() directly
from asm/book3s/32/tlbflush.h, move their prototypes
from mm/mm_decl.h to there.
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/book3s/32/tlbflush.h | 4
arch/powerpc/mm/mmu_decl.h| 3 ---
2 files changed, 4 in
flush_tlb_page_nohash() was removed by
commit 703b41ad1a87 ("powerpc/mm: remove flush_tlb_page_nohash")
Remove stale prototype and comment.
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/book3s/32/tlbflush.h | 1 -
arch/powerpc/include/asm/nohash/tlbflush.h| 1 -
2 files chang
_tlbie() and _tlbia() are used only on 603 cores while the
other functions are used only on cores having a hash table.
Move them into a new file named nohash_low.S
Add mmu_hash_lock var is used by both, it needs to go
in a common file.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/book3s
This table is used only locally. Declare it static.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/book3s32/mmu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/mm/book3s32/mmu.c b/arch/powerpc/mm/book3s32/mmu.c
index a59e7ec98180..eceb55c12fe9 100644
--- a
On 8xx, we get the following features:
[0.00] cpu_features = 0x0100
[0.00] possible= 0x0120
[0.00] always = 0x
This is not correct. As CONFIG_PPC_8xx is mutually exclusive with all
other configurations, the
Hash var is used only locally in mmu.c now.
No need to set it in head_32.S anymore.
Make it static and initialises it to the early hash table.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_book3s_32.S | 5 -
arch/powerpc/mm/book3s32/mmu.c | 2 +-
arch/powerpc/mm/mmu_de
On the same principle as commit 773edeadf672 ("powerpc/mm: Add mask
of possible MMU features"), add mask for MMU features that are
always there in order to optimise out dead branches.
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/mmu.h | 25 +
1 file change
Hash related vars are used at init only.
Declare them in __initdata.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/book3s32/mmu.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/mm/book3s32/mmu.c b/arch/powerpc/mm/book3s32/mmu.c
index c0c0f2a50f86.
Hi David,
I love your patch! Yet something to improve:
[auto build test ERROR on c4d6fe7311762f2e03b3c27ad38df7c40c80cc93]
url:
https://github.com/0day-ci/linux/commits/David-Gow/fat-Add-KUnit-tests-for-checksums-and-timestamps/20201021-141819
base
As suspend_set_ops is exported in commit a5e4fd8783a2
("PM / Suspend: Export suspend_set_ops, suspend_valid_only_mem"),
exporting s2idle_set_ops to make kernel module setup s2idle ops too.
In this way, kernel module can hook platform suspend
functions regardless of Suspend-to-Ram(S2R) or
Suspend-t
> -Original Message-
> From: Z.q. Hou
> Sent: Wednesday, October 21, 2020 4:48 PM
> To: Lorenzo Pieralisi ; Richard Zhu
>
> Cc: Kishon Vijay Abraham I ; Bjorn Helgaas
> ; linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
> r...@kernel.org; bhelg...@google.com; gustavo.pimen...@syno
This series based on 5.9-rc1
As suspend_set_ops is exported in commit a5e4fd8783a2
("PM / Suspend: Export suspend_set_ops, suspend_valid_only_mem"),
exporting s2idle_set_ops to make kernel module setup s2idle ops too.
In this way, kernel module can hook platform suspend functions
regardless of Su
A PD-capable device can return up to 3 Product Type VDOs as part of its
DiscoverIdentity Response (USB PD Spec, Rev 3.0, Version 2.0, Section
6.4.4.3.1). Add a sysfs attribute to expose these to userspace.
Cc: Benson Leung
Cc: Heikki Krogerus
Signed-off-by: Prashant Malani
---
NOTE: I didn't i
>
> On Fri, 25 Sep 2020 at 03:57, wrote:
> >
> > From: Rui Feng
> >
> > RTS5261 support legacy SD mode and SD Express mode.
> > In SD7.x, SD association introduce SD Express as a new mode.
> > This patch makes RTS5261 support SD Express mode.
>
> As per patch 2, can you please add some more inf
Add support for the LTC4162-L Li-Ion battery charger. The driver allows
reading back telemetry and to set some charging options like the input
current limit.
Signed-off-by: Mike Looijmans
---
drivers/power/supply/Kconfig | 8 +
drivers/power/supply/Makefile| 1 +
driv
Christoph's set_fs base series + fixups. A few trivial conflicts
(arch/{ia64,m68k/s390}/Kconfig and arch/x86/lib/getuser.S); proposed
resolution in #merge-candidate, same as in -next.
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16
Since WB feature has been added, WB related sysfs entries can be accessed
even when an UFS device does not support WB feature. In that case, the
descriptors which are not supported by the UFS device may be wrongly
reported when they are accessed from their corrsponding sysfs entries.
Fix it by addi
On 10/21/20 4:10 PM, Sergei Shtepa wrote:
The 10/21/2020 16:31, Hannes Reinecke wrote:
I do understand where you are coming from, but then we already have a
dm-snap which does exactly what you want to achieve.
Of course, that would require a reconfiguration of the storage stack on
the machine, w
The param "irqflood_suppress" is helpful for capture kernel to survive irq
flood.
Signed-off-by: Pingfan Liu
Cc: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Jisheng Zhang
Cc: Andrew Morton
Cc: "Guilherme G. Piccoli"
Cc: Petr Mladek
Cc: Marc Zyngier
Cc: Linus Walleij
Cc: afzal mohammed
Cc: Lin
In kdump case, the capture kernel has no chance to shutdown devices, and
leave the devices in unstable state. Irq flood is one of the consequence.
When irq floods, the kernel is totally occupies by irq. Currently, there
may be nothing or just soft lockup warning showed in console. It is better
to
The capture kernel should try its best to save the crash info. Normally,
irq flood is caused by some trivial devices, which has no impact on saving
vmcore.
Introducing a parameter "irqflood_suppress" to enable suppress irq flood.
Signed-off-by: Pingfan Liu
Cc: Thomas Gleixner
Cc: Peter Zijlstra
I hit a irqflood bug on powerpc platform, and two years ago, on a x86 platform.
When the bug happens, the kernel is totally occupies by irq. Currently, there
may be nothing or just soft lockup warning showed in console. It is better
to warn users with irq flood info.
In the kdump case, the kernel
Hi Greg,
thanks for taking a look at this.
On Thu, Oct 22, 2020 at 07:31:43AM +0200, Greg Kroah-Hartman wrote:
> On Thu, Oct 22, 2020 at 11:23:24AM +0800, Chen Yu wrote:
> > Currently there are 4 driver flags to control system suspend/resume
> > behavior: DPM_FLAG_NO_DIRECT_COMPLETE, DPM_FLAG_SMART
On 2020/10/20 9:43, Joel Fernandes (Google) wrote:
> Core-scheduling prevents hyperthreads in usermode from attacking each
> other, but it does not do anything about one of the hyperthreads
> entering the kernel for any reason. This leaves the door open for MDS
> and L1TF attacks with concurrent ex
On 2020/10/21 下午10:45, Michael S. Tsirkin wrote:
On Wed, Jun 17, 2020 at 11:29:43AM +0800, Jason Wang wrote:
Hi All:
This series introduces API for reporing IOVA range. This is a must for
userspace to work correclty:
- for the process that uses vhost-vDPA directly to properly allocate
IOV
If some bits were cleared by i2c_dw_read_clear_intrbits_slave() in
i2c_dw_isr_slave() and not handled immediately, those cleared bits would
not be shown again by later i2c_dw_read_clear_intrbits_slave(). They
therefore were forgotten to be handled.
i2c_dw_read_clear_intrbits_slave() should be call
When rtnl_configure_link() fails, peer needs to be
freed just like when register_netdevice() fails.
Signed-off-by: Dinghao Liu
---
drivers/net/veth.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/net/veth.c b/drivers/net/veth.c
index 8c737668008a..6c68094399cc 100644
--- a/drivers
On Tue, Oct 6, 2020 at 5:48 AM Atish Patra wrote:
>
> Use the generic numa implementation to add NUMA support for RISC-V.
> This is based on Greentime's patch[1] but modified to use generic NUMA
> implementation and few more fixes.
>
> [1] https://lkml.org/lkml/2020/1/10/233
>
> Co-developed-by: G
On Tue, Oct 6, 2020 at 5:48 AM Atish Patra wrote:
>
> From: Greentime Hu
>
> These two functions are used to distinguish between PROT_NONENUMA
> protections and hinting fault protections.
>
> Signed-off-by: Greentime Hu
> ---
> arch/riscv/include/asm/pgtable.h | 20
> 1 fil
On Tue, Oct 6, 2020 at 5:48 AM Atish Patra wrote:
>
> Currently, we perform some memory init functions in paging init. But,
> that will be an issue for NUMA support where DT needs to be flattened
> before numa initialization and memblock_present can only be called
> after numa initialization.
>
>
Hi Greg,
Thanks for taking a look.
On Wed, Oct 21, 2020 at 10:30 PM Greg KH wrote:
>
> On Wed, Oct 21, 2020 at 02:18:02PM -0700, Prashant Malani wrote:
> > A PD-capable device can return up to 3 Product Type VDOs as part of its
> > DiscoverIdentity Response (USB PD Spec, Rev 3.0, Version 2.0, Se
On Thu, Oct 22, 2020 at 11:23:24AM +0800, Chen Yu wrote:
> Currently there are 4 driver flags to control system suspend/resume
> behavior: DPM_FLAG_NO_DIRECT_COMPLETE, DPM_FLAG_SMART_PREPARE,
> DPM_FLAG_SMART_SUSPEND and DPM_FLAG_MAY_SKIP_RESUME. Make these flags
> visible in sysfs as read-only to
On Wed, Oct 21, 2020 at 02:18:02PM -0700, Prashant Malani wrote:
> A PD-capable device can return up to 3 Product Type VDOs as part of its
> DiscoverIdentity Response (USB PD Spec, Rev 3.0, Version 2.0, Section
> 6.4.4.3.1). Add a sysfs attribute to expose these to userspace.
You forgot to add the
I've only as yet seen nouveau lockdep gripage when firing up one of my
full distro KVM's.
[ 91.655613] ==
[ 91.655614] WARNING: possible circular locking dependency detected
[ 91.655614] 5.9.1-rt18-rt #5 Tainted: G S E
[ 91.65561
>
> On 21.10.20 07:21, Dinghao Liu wrote:
> > When rtnl_configure_link() fails, peer needs to be
> > freed just like when register_netdevice() fails.
> >
> > Signed-off-by: Dinghao Liu
>
> Acked-by: Oliver Hartkopp
>
> Btw. as the vxcan.c driver bases on veth.c the same issue can be found
>
Greetings,
The gripe below is repeatable in two ways here, boot with nomodeset so
nouveau doesn't steal the lockdep show when I then fire up one of my
(oink) full distro VM's, or from an ltp directory ./runltp -f cpuset
with the attached subset of controllers file placed in ./runtest dir.
Method2
End users frequently want to know what features their processor
supports, independent of what the kernel supports.
/proc/cpuinfo is great. It is omnipresent and since it is provided by
the kernel it is always as up to date as the kernel. But, it could be
ambiguous about processor features which ca
On Wed, Oct 21, 2020 at 08:18:59AM -0700, Mark Salyzyn wrote:
> Mark Salyzyn (3):
> Add flags option to get xattr method paired to __vfs_getxattr
> overlayfs: handle XATTR_NOSECURITY flag for get xattr method
> overlayfs: override_creds=off option bypass creator_cred
>
> Mark Salyzyn + John
On 28-08-20, 11:37, Viresh Kumar wrote:
> dev_pm_opp_of_remove_table() doesn't report any errors when it fails to
> find the OPP table with error -ENODEV (i.e. OPP table not present for
> the device). And we can call dev_pm_opp_of_remove_table()
> unconditionally here.
>
> Reviewed-by: Qiang Yu
>
On 21-10-20, 09:58, Rob Clark wrote:
> On Wed, Oct 21, 2020 at 12:24 AM Viresh Kumar wrote:
> >
> > On 05-10-20, 11:56, Viresh Kumar wrote:
> > > On 28-08-20, 11:37, Viresh Kumar wrote:
> > > > dev_pm_opp_of_remove_table() doesn't report any errors when it fails to
> > > > find the OPP table with
On Thu, Oct 22, 2020 at 7:01 AM Atish Patra wrote:
>
> On Fri, Oct 16, 2020 at 11:24 AM Atish Patra wrote:
> >
> > On Tue, Oct 13, 2020 at 10:24 PM Atish Patra wrote:
> > >
> > > On Tue, Oct 13, 2020 at 6:21 PM Jim Wilson wrote:
> > > >
> > > > On Tue, Oct 13, 2020 at 3:25 PM Atish Patra
> >
Mapping kernel space memory to user space as noncached, since user space
need check the updates of avail_idx and device page flags timely.
Signed-off-by: Joakim Zhang
Signed-off-by: Sherry Sun
---
drivers/misc/mic/vop/vop_vringh.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
Allocate vrings use dma_alloc_coherent is a common way in kernel. As the
memory interacted between two systems should use consistent memory to
avoid caching effects, same as device page memory.
The orginal way use __get_free_pages and dma_map_single to allocate and
map vring, but not use dma_sync_
The device page and vring should use consistent memory which are
allocated by dma_alloc_coherent api, when user space wants to get its
physical address, virt_to_phys cannot be used, should simply return the
saved device page dma address by get_dp_dma callback and the vring dma
address saved in mic_
Changes in V3:
1. Change the device page allocation method of the Intel mic layer in Patch 1 to
align with the vring allocation.
2. Move the vring physical address changes in mmap callback from Prach 3 to 1.
3. Use must_be_zero instead of directly deleting used_address_updated in
Patch 2 to avoid
We don't need to allocate and reassign the used ring here and remove the
used_address_updated flag.Since RC has allocated the entire vring,
including the used ring. Simply add the corresponding offset can get the
used ring address.
If following the orginal way to reassign the used ring, will encou
The extra 0 only adds one point in the userspace visible range,
so this change is almost a noop with the current driver behavior.
We don't need the 0% point, userspace seems to handle this just fine
because it uses the bl_power property to turn off the display.
Furthermore after adding "backlight
The previous behavior was a little unexpected, its properties/problems:
1. It was designed to generate strictly increasing values (no repeats)
2. It had quantization errors when calculating step size. Resulting in
unexpected jumps near the end of some segments.
Example settings:
brightness
We want userspace to represent the human perceived brightness.
Since the led drivers and the leds themselves don't have a
linear response to the value we give them in terms of perceived
brightness, we'll bake the curve into the dts.
The panel also doesn't have a good response under 5%, so we'll av
I was trying to adjust the brightness-levels for the trogdor boards:
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/2291209
Like on a lot of panels, trogdor's low end needs to be cropped,
and now that we have the interpolation stuff I wanted to make use of it
and bake in
On Tue, Oct 20, 2020 at 04:39:56PM -0400, Arvind Sankar wrote:
> Unrolling the LOAD and BLEND loops improves performance by ~8% on x86_64
> (tested on Broadwell Xeon) while not increasing code size too much.
>
> Signed-off-by: Arvind Sankar
> ---
Looks good,
Reviewed-by: Eric Biggers
On Mon, Oct 19, 2020 at 8:38 AM estherbdf <603571...@qq.com> wrote:
>
> [Why] the func bios_parser_get_src_obj () is similar to
> bios_parser_get_dst_obj () which is fixed by the
> commit("drm/amd/display: Banch of smatch error and warning
> fixes in DC").
> the symbol 'id' is uninitialized an
On Tue, Oct 20, 2020 at 04:39:55PM -0400, Arvind Sankar wrote:
> This reduces code size substantially (on x86_64 with gcc-10 the size of
> sha256_update() goes from 7593 bytes to 1952 bytes including the new
> SHA256_K array), and on x86 is slightly faster than the full unroll
> (tesed on Broadwell
On Tue, Oct 20, 2020 at 04:39:54PM -0400, Arvind Sankar wrote:
> The temporary W[] array is currently zeroed out once every call to
> sha256_transform(), i.e. once every 64 bytes of input data. Moving it to
> sha256_update() instead so that it is cleared only once per update can
> save about 2-3% o
> > Did you mean /dev/disk/by-[part]label/ symlink? It's quite reasonable to
> > use them by udev in userspace such as initramfs but some cases does not
> use
> > initramfs or initrd. In that case, we need to load the root
> > device(/dev/sda[N]) directly from kernel.
>
> Please use udev or system
On Tue, Oct 20, 2020 at 04:39:53PM -0400, Arvind Sankar wrote:
> The assignments to clear a through h and t1/t2 are optimized out by the
> compiler because they are unused after the assignments.
>
> These variables shouldn't be very sensitive: t1/t2 can be calculated
> from a through h, so they do
Applied. Thanks!
Alex
On Mon, Oct 19, 2020 at 11:08 AM Harry Wentland wrote:
>
> On 2020-10-19 10:55 a.m., Christian König wrote:
> > Am 19.10.20 um 16:43 schrieb t...@redhat.com:
> >> From: Tom Rix
> >>
> >> A break is not needed if it is preceded by a return or break
> >>
> >> Signed-off-by:
On 21-10-20, 20:11, Rafael J. Wysocki wrote:
> On Wednesday, October 21, 2020 3:10:26 PM CEST Peter Zijlstra wrote:
> > On Wed, Oct 21, 2020 at 02:19:50PM +0200, Peter Zijlstra wrote:
> > > On Wed, Oct 21, 2020 at 01:56:55PM +0200, Julia Lawall wrote:
> > > > Prior to 5.8, my machine was using inte
Thanks,
Do you mean Megasas raid can be used in m68k arch?
-Original Message-
From: Finn Thain [mailto:fth...@telegraphics.com.au]
Sent: Thursday, October 22, 2020 10:25 AM
To: tianxianting (RD)
Cc: kashyap.de...@broadcom.com; sumit.sax...@broadcom.com;
shivasharan.srikanteshw...@broadc
GSMI driver uses dma_pool_* API functions for buffer allocation
because it requires that the SMI buffers are allocated within 32-bit
physical address space. However, this does not work well with IOMMU
since there is no real device and hence no domain associated with the
device.
Since this is not a
Hi Tomasz,
On 2020-10-13 19:09, Tomasz Figa wrote:
Hi Vikash,
On Tue, Oct 13, 2020 at 02:56:21PM +0530, vgaro...@codeaurora.org
wrote:
On 2020-10-08 19:51, Tomasz Figa wrote:
> On Wed, Oct 7, 2020 at 9:33 PM wrote:
> >
> > Hi Tomasz,
> >
> > On 2020-10-01 20:47, Tomasz Figa wrote:
> > > On
> The use of ?: here is a bit strange. How about:
>
> return algorithm < COMPRESS_MAX && f2fs_cops[algorithm] != NULL;
>
Ack
> Likewise, EINVAL tends to be over-used, which makes it ambiguous. Maybe use
> ENOPKG for the case where algorithm < COMPRESS_MAX but the algorithm wasn't
> comp
On Tue, Oct 20, 2020 at 04:39:52PM -0400, Arvind Sankar wrote:
> Without the barrier_data() inside memzero_explicit(), the compiler may
> optimize away the state-clearing if it can tell that the state is not
> used afterwards. At least in lib/crypto/sha256.c:__sha256_final(), the
> function can get
On Thu, Oct 22, 2020 at 1:00 AM Alexey Budankov
wrote:
>
>
> Introduce decompressor to trace reader object so that decompression
> could be executed on per trace file basis separately for every
> trace file located in trace directory.
I'm slightly uncomfortable with the word 'trace' here as it's
On Tue, Oct 20, 2020 at 04:39:57PM -0400, Arvind Sankar wrote:
> Putting the round constants and the message schedule arrays together in
> one structure saves one register, which can be a significant benefit on
> register-constrained architectures. On x86-32 (tested on Broadwell
> Xeon), this gives
On Thu, Oct 22, 2020 at 12:59 AM Alexey Budankov
wrote:
>
>
> Move definition of reader to session header file to be shared
> among different source files. Introduce reference to active
> reader object from session object.
>
> Signed-off-by: Alexey Budankov
Acked-by: Namhyung Kim
Thanks
Namhyu
On Thu, Oct 22, 2020 at 12:58 AM Alexey Budankov
wrote:
>
>
> Open files located at trace data directory in case read access
> mode is requested. File are opened and its fds assigned to
> perf_data dir files especially for loading data directories
> content in perf report mode.
>
> Signed-off-by:
Yep, it sounds more clear~
2020년 10월 22일 (목) 오후 1:22, Eric Biggers 님이 작성:
>
> On Thu, Oct 22, 2020 at 12:58:47PM +0900, Daeho Jeong wrote:
> > + if (!f2fs_compressed_file(inode)) {
> > + inode_unlock(inode);
> > + return -EINVAL;
> > + }
>
> How about using ENODATA
The legacy CPU cooling should ONLY be used when "#cooling-cells" is NOT
present in cpu node, current implementation for registering legacy cooling
always return -EPROBE_DEFER when cpufreq is NOT ready, that will cause
thermal driver probe failed when cpufreq failed to probe with a non
-EPROBE_DEFER
Hi,
On Thu, Oct 22, 2020 at 12:56 AM Alexey Budankov
wrote:
>
>
> Extend reader, ordered_event and decomp objects to contain path
> of a trace file being displayed.
>
> Signed-off-by: Alexey Budankov
Acked-by: Namhyung Kim
Thanks
Namhyung
> ---
> tools/perf/util/ordered-events.h | 1 +
> to
On Thu, Oct 22, 2020 at 12:57 AM Alexey Budankov
wrote:
>
>
> Print path and name of a trace file into raw dump (-D)
> @. Print offset of PERF_RECORD_COMPRESSED
> record instead of zero for decompressed records:
> 0x22...@perf.data [0x30]: event: 9
> or
> 0x15c...@perf.data/data.7 [0x30]: even
On Tue, Oct 20, 2020 at 6:35 PM Chris Down wrote:
>
> `hostname` may not be present on some systems as it's not mandated by
> POSIX/SUSv4. This isn't just a theoretical problem: on Arch Linux,
> `hostname` is provided by `inetutils`, which isn't part of the base
> distribution.
>
> ./scripts/m
1 - 100 of 905 matches
Mail list logo
