Wed, Sep 02, 2020 at 05:30:25PM CEST, k...@kernel.org wrote:
>On Wed, 2 Sep 2020 11:46:27 +0200 Jiri Pirko wrote:
>> >? Do we need such change there too or keep it as is, each action by itself
>> >and return what was performed ?
>>
>> Well, I don't know. User asks for X, X should be performed,
On Wed, Sep 02, 2020 at 12:15:35AM +1000, Nicholas Piggin wrote:
> Cc: Yoshinori Sato
> Cc: Rich Felker
> Cc: linux...@vger.kernel.org
> Signed-off-by: Nicholas Piggin
> ---
>
> Please ack or nack if you object to this being mered via
> Arnd's tree.
Acked-by: Rich Felker
>
>
9495b7e92f71 ("driver core: platform: Initialize dma_parms for platform
devices") included dma_parms in platform_device. There's no need to
allocate again.
Fixes: 13483fc2f20f0e2db7ba9c39b095ac7ea46f8de8 ("media: mtk-vcodec: set dma
max segment size")
Suggested-by: Robin Murphy
Signed-off-by:
Addition of SECCOMP_FILTER exposed a longstanding bug in
do_syscall_trace_enter, whereby r0 (the 5th argument register) was
mistakenly used where r3 (syscall_nr) was intended. By overwriting r0
rather than r3 with -1 when attempting to block a syscall, the
existing code would instead have caused
On Wed, Sep 02, 2020 at 11:56:04PM -0400, Rich Felker wrote:
> On Sat, Aug 29, 2020 at 01:09:43PM +0200, John Paul Adrian Glaubitz wrote:
> > Hi!
> >
> > On 8/29/20 2:49 AM, Rich Felker wrote:
> > > This restored my ability to use strace
> >
> > I can confirm that. However ...
> >
> > > and
The 'imask' and 'bsize' are not used in dbg_dumpregs:
drivers/mmc/host/s3cmci.c:149:36: warning: variable 'imask' set but not used
[-Wunused-but-set-variable]
drivers/mmc/host/s3cmci.c:148:63: warning: variable 'bsize' set but not used
[-Wunused-but-set-variable]
Reported-by: kernel test
Add a littler helper to make the somewhat arcane bd_contains checks a
little more obvious.
Signed-off-by: Christoph Hellwig
---
block/blk-lib.c | 2 +-
block/ioctl.c | 4 ++--
block/scsi_ioctl.c | 2 +-
drivers/ide/ide-ioctls.c| 4 ++--
bd_disk is set on all block devices, including those for partitions.
Signed-off-by: Christoph Hellwig
---
drivers/block/drbd/drbd_receiver.c | 2 +-
drivers/block/drbd/drbd_worker.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/drbd/drbd_receiver.c
bd_disk is set on all block devices, including those for partitions.
Signed-off-by: Christoph Hellwig
---
drivers/md/md.c | 2 +-
drivers/md/md.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 3f33562d10d6f5..5a0fd93769a70e 100644
bd_contains is never NULL for an open block device. In addition ibd_bd
is always set to a block device that was exclusively opened by the
target code, so the holder is guranteed to be ib_dev as well.
Signed-off-by: Christoph Hellwig
---
drivers/target/target_core_iblock.c | 5 ++---
1 file
To check for partitions of the same disk bd_contains works as well, but
bd_disk is way more obvious.
Signed-off-by: Christoph Hellwig
---
drivers/md/md.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index
Hi Jens,
this series add a new helepr to check if a struct block_device represents
a parition, and removes most direct access to ->bd_contained from
drivers.
Diffstat:
Documentation/userspace-api/ioctl/hdio.rst | 24
block/blk-lib.c|2
No need to go through the hd_struct to find the partition number.
Signed-off-by: Christoph Hellwig
---
lib/vsprintf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index afb9521ddf9197..14c9a6af1b239a 100644
--- a/lib/vsprintf.c
+++
The ->bd_contains field is set by __blkdev_get and drivers have no
business manipulating it.
Signed-off-by: Christoph Hellwig
---
drivers/block/drbd/drbd_main.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/block/drbd/drbd_main.c b/drivers/block/drbd/drbd_main.c
index
No need to go through the hd_struct to find the partition number.
Signed-off-by: Christoph Hellwig
---
block/genhd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/genhd.c b/block/genhd.c
index 081f1039d9367f..771aa56b1a8c3d 100644
--- a/block/genhd.c
+++
bd_contains is an implementation detail and should not be mentioned in
a userspace API documentation.
Signed-off-by: Christoph Hellwig
---
Documentation/userspace-api/ioctl/hdio.rst | 24 +++---
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git
On Tue, Sep 1, 2020 at 3:10 PM Kim Phillips wrote:
>
> Later revisions of PPRs that post-date the original Family 17h events
> submission patch add these events.
>
> Specifically, they were not in this 2017 revision of the F17h PPR:
>
> Processor Programming Reference (PPR) for AMD Family 17h
On 10/08/20 3:07 PM, Wolfram Sang wrote:
> On Sun, Aug 09, 2020 at 07:24:44PM +0200, Stephen Kitt wrote:
>> The i2c probe functions here don't use the id information provided in
>> their second argument, so the single-parameter i2c probe function
>> ("probe_new") can be used instead.
>>
>> This
On Wed, Sep 02, 2020 at 11:32:27PM +0200, Michał Mirosław wrote:
> On Wed, Sep 02, 2020 at 09:36:58PM +0200, Krzysztof Kozlowski wrote:
> > Multiple MMC host controller driver can be compile tested as they do not
> > depend on architecture specific headers.
> [...]
> > ---
On Thu, Sep 3, 2020 at 11:42 AM Nicolin Chen wrote:
>
> On Thu, Sep 03, 2020 at 11:09:15AM +0800, Shengjiu Wang wrote:
> > Transmit data pins will output zero when slots are masked or channels
> > are disabled. In CHMOD TDM mode, transmit data pins are tri-stated when
> > slots are masked or
On Wed, Sep 02, 2020 at 05:06:40PM +0200, Krzysztof Kozlowski wrote:
> Common pattern of handling deferred probe can be simplified with
> dev_err_probe(). Less code and the error value gets printed.
>
> Signed-off-by: Krzysztof Kozlowski
Acked-by: Oleksij Rempel
> ---
>
On 2020-09-03 03:17, Joel Fernandes wrote:
On Wed, Sep 2, 2020 at 4:01 PM Nachammai Karuppiah
wrote:
Hi,
This patch series adds support to store trace events in pstore.
Storing trace entries in persistent RAM would help in understanding
what
happened just before the system went down. The
Add an I2C bus driver for virtio para-virtualization.
The controller can be emulated by the backend driver in
any device model software by following the virtio protocol.
This driver communicates with the backend driver through a
virtio I2C message structure which includes following parts:
-
在 2020/8/31 上午4:32, Alexander Duyck 写道:
>> Right that the different level to fix this problem, but narrow the cmpxchg
>> comparsion is still needed and helpful.
> What I was getting at though is that I am not sure that is the case.
> Normally I believe we are always holding the zone lock when
On 9/3/2020 10:14 AM, Rajendra Nayak wrote:
On 9/2/2020 9:02 PM, Doug Anderson wrote:
Hi,
On Tue, Sep 1, 2020 at 10:36 PM Rajendra Nayak wrote:
* In terms of the numbers here, I believe that you're claiming that we
can dissipate 768 mW * 6 + 1202 mW * 2 = ~7 Watts of power. My memory
On Thu, Sep 3, 2020 at 1:21 AM Arvind Sankar wrote:
>
> Changes from v2:
> - Clarify commit log and source comment some more
Much better now, thanks!
Reviewed-by: Miguel Ojeda
Cheers,
Miguel
On 9/2/20 7:11 PM, Martin K. Petersen wrote:
>
> Tyrel,
>
>> Fixup complier errors from neglected commit --amend
>
> Bunch of formatting-related checkpatch warnings. Please fix.
>
> Thanks!
>
So, I stuck to the existing style already in that header. If I'm going to fixup
to make
On Mon, Aug 31, 2020 at 4:03 PM Barret Rhoden wrote:
>
> The max_entries for a BPF map may depend on runtime parameters.
> Currently, we need to know the maximum value at BPF compile time. For
> instance, if you want an array map with NR_CPUS entries, you would hard
> code your architecture's
Hi Nishanth,
On 9/2/20 11:48 PM, Nishanth Menon wrote:
> On 11:51-20200902, Suman Anna wrote:
>> On 9/1/20 5:30 PM, Nishanth Menon wrote:
>>> Use adc@ naming for nodes following standard conventions of device
>>> tree (section 2.2.2 Generic Names recommendation
Hi all,
Today's linux-next merge of the scsi-mkp tree got a conflict in:
drivers/scsi/ufs/ufshcd.c
between commit:
b10178ee7fa8 ("scsi: ufs: Clean up completed request without interrupt
notification")
from Linus' tree and commit:
307348f6ab14 ("scsi: ufs: Abort tasks before clearing
On Tue, 1 Sep 2020 at 06:31, Ralph Campbell wrote:
>
> The user level OpenCL code shouldn't have to align start and end
> addresses to a page boundary. That is better handled in the nouveau
> driver. The npages field is also redundant since it can be computed
> from the start and end addresses.
>
On Wed, 2 Sep 2020 at 09:43, Lyude Paul wrote:
>
> Not entirely sure why this never came up when I originally tested this
> (maybe some BIOSes already have this setup?) but the ->caps_init vfunc
> appears to cause the display engine to throw an exception on driver
> init, at least on my ThinkPad
On 8/28/20 12:51 PM, Julien Desfossez wrote:
> +#ifndef find_next_or_bit
> +/**
> + * find_next_or_bit - find the next set bit in any memory regions
> + * @addr1: The first address to base the search on
> + * @addr2: The second address to base the search on
> + * @offset: The bitnumber to start
---
kernel: 4.4.235-rc2
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git branch: 4.4.235-rc2-hikey-20200902-803
git commit: 4e984a08e49b4aa772d7681bfaeb091bd7a7b4b9
git describe: 4.4.235-rc2-hikey-20200902-803
Test details:
https://qa-reports.linaro.org/lkft/linaro-hikey-stab
Hello, Kehuan
Can you test the attached one-line fix? I think we are overthinking,
probably all
we need here is a busy wait.
Thanks.
diff --git a/include/net/sch_generic.h b/include/net/sch_generic.h
index d60e7c39d60c..fc1bacdb102b 100644
--- a/include/net/sch_generic.h
+++
Hi Ingo,
On Thu, 3 Sep 2020 05:51:08 +0200 Ingo Molnar wrote:
>
> I've merged the old commit by mistake - it's removed now.
Ah, OK, thanks.
--
Cheers,
Stephen Rothwell
pgpqbzuw8G3mY.pgp
Description: OpenPGP digital signature
On 9/2/2020 9:02 PM, Doug Anderson wrote:
Hi,
On Tue, Sep 1, 2020 at 10:36 PM Rajendra Nayak wrote:
* In terms of the numbers here, I believe that you're claiming that we
can dissipate 768 mW * 6 + 1202 mW * 2 = ~7 Watts of power. My memory
of how much power we could dissipate in
Adding printouts to the i2c_hid_probe() function shows that it takes
quite some time. It used to take about 70 ms, but after commit
eef4016243e9 ("HID: i2c-hid: Always sleep 60ms after I2C_HID_PWR_ON
commands") it takes about 190 ms. This is not tons of time but it's
not trivial. Because we
On 02/09/2020 08:34, Leonardo Bras wrote:
On Mon, 2020-08-31 at 10:47 +1000, Alexey Kardashevskiy wrote:
Maybe testing with host 64k pagesize and IOMMU 16MB pagesize in qemu
should be enough, is there any chance to get indirect mapping in qemu
like this? (DDW but with smaller DMA window
> On Sep 2, 2020, at 7:53 PM, Yu, Yu-cheng wrote:
>
> On 9/2/2020 4:50 PM, Andy Lutomirski wrote:
On Sep 2, 2020, at 3:13 PM, Yu, Yu-cheng wrote:
>>>
>>> On 9/2/2020 1:03 PM, Jann Horn wrote:
> On Tue, Aug 25, 2020 at 2:30 AM Yu-cheng Yu wrote:
> Add REGSET_CET64/REGSET_CET32
On Wed, Sep 2, 2020 at 12:57 PM Dario Faggioli wrote:
>
> On Wed, 2020-09-02 at 09:53 +0200, Thomas Gleixner wrote:
> > On Tue, Sep 01 2020 at 21:29, Joel Fernandes wrote:
> > > On Tue, Sep 01, 2020 at 10:02:10PM +0200, Thomas Gleixner wrote:
> > > >
> > > Or, are you saying users may want 'core
On 02/09/2020 07:38, Leonardo Bras wrote:
On Mon, 2020-08-31 at 13:48 +1000, Alexey Kardashevskiy wrote:
Well, I created this TCE_RPN_BITS = 52 because the previous mask was a
hardcoded 40-bit mask (0xfful), for hard-coded 12-bit (4k)
pagesize, and on PAPR+/LoPAR also defines TCE as
dc1a9bf2c8169d9f607502162af1858a73a18cb8
config: i386-randconfig-m021-20200902 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
smatch warnings:
drivers/net/phy/dp83869.c:669 dp83869_config_init() warn
Now that protected-clocks is handled in the clk core, this
driver-specific implementation is redundant.
This reverts commit b181b3b801da8893c8eb706e448dd5111b02de60.
Signed-off-by: Samuel Holland
---
drivers/clk/qcom/common.c | 18 --
1 file changed, 18 deletions(-)
diff --git
Stephen, Maxime,
You previously asked me to implement the protected-clocks property in a
driver-independent way:
https://www.spinics.net/lists/arm-kernel/msg753832.html
I provided an implementation 6 months ago, which I am resending now:
https://patchwork.kernel.org/patch/11398629/
Do you
This is a generic implementation of the "protected-clocks" property from
the common clock binding. It allows firmware to inform the OS about
clocks that must not be disabled while the OS is running.
This implementation comes with some caveats:
1) Clocks that have CLK_IS_CRITICAL in their init
On Sat, Aug 29, 2020 at 01:09:43PM +0200, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 8/29/20 2:49 AM, Rich Felker wrote:
> > This restored my ability to use strace
>
> I can confirm that. However ...
>
> > and I've written and tested a minimal strace-like hack using
> >
* Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
>
> Caused by commit
>
> f670269a42bf ("x86: Fix early boot crash on gcc-10, next try")
>
> interacting with commit
>
> a9a3ed1eff36 ("x86: Fix
On 2020-09-02 22:00 +0800, Coiby Xu wrote:
> This fixes commit 0107635e15ac
> ("staging: qlge: replace pr_err with netdev_err") which introduced an
> build breakage of missing `struct ql_adapter *qdev` for some functions
> and a warning of type mismatch with dumping enabled, i.e.,
>
> $ make
On Wed, 2 Sep 2020 17:01:19 +0100
Lorenzo Pieralisi wrote:
> On Tue, Sep 01, 2020 at 02:33:56PM -0400, Samuel Dionne-Riel wrote:
>
> Please print a pointer as a pointer and print both bus and
> bus->parent.
Hopefully pointer as a pointer is %px. Not sure what else, if that's
wrong please tell.
Nicolin Chen writes:
> diff --git a/arch/powerpc/kernel/iommu.c b/arch/powerpc/kernel/iommu.c
> index 9704f3f76e63..cbc2e62db597 100644
> --- a/arch/powerpc/kernel/iommu.c
> +++ b/arch/powerpc/kernel/iommu.c
> @@ -236,15 +236,10 @@ static unsigned long iommu_range_alloc(struct device
> *dev,
>
Currently, all command packet structs used by this driver are packed.
However, only one (TW_SG_Entry) actually needs to be packed, because it
uses 64-bit addresses at 32-bit alignment. To improve the quality of
generated code, stop packing all of the other command packet structs.
This requires
The controller expects all data it sends/receives to be little-endian.
Therefore, the packet struct definitions should use the __le16/32/64
types. Once those are correct, sparse reports several issues with the
driver code, which are fixed here as well.
The main issue observed was at the call to
In preparation for removing the "#pragma pack(1)" from the driver, fix
all instances where a trailing array member could be replaced by a
flexible array member. Since a flexible array member has zero size, it
introduces no padding, whether or not the struct is packed.
Signed-off-by: Samuel
If calling mtdoops_write, don't also schedule work to be done later.
Although this appears to not be causing an issue, possibly because the
scheduled work will never get done, it is confusing.
Fixes: 016c1291ce70 ("mtd: mtdoops: do not use mtd->panic_write directly")
Signed-off-by: Mark
On Thu, Sep 03, 2020 at 11:09:15AM +0800, Shengjiu Wang wrote:
> Transmit data pins will output zero when slots are masked or channels
> are disabled. In CHMOD TDM mode, transmit data pins are tri-stated when
> slots are masked or channels are disabled. When data pins are tri-stated,
> there is
From: CK Hu
add support runtime pm feature
Signed-off-by: Zhanyong Wang
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 446 +++-
drivers/usb/host/xhci-mtk.h | 14 ++
2 files changed, 455 insertions(+), 5 deletions(-)
mode change 100644
From: Zhanyong Wang
After inserted the usb type-c 3.5mm dongle with headset, dmesg showed:
usb 1-1.1: new full-speed USB device number 5 using xhci-mtk
usb 1-1.1: New USB device found, idVendor=05ac, idProduct=110a, bcdDevice=26.11
usb 1-1.1: New USB device strings: Mfr=1, Product=2,
From: Zhanyong Wang
Add SSUSB related nodes for mt8192
Signed-off-by: Zhanyong Wang
Signed-off-by: Chunfeng Yun
---
Depends on:
https://patchwork.kernel.org/patch/11713559/
[v4,1/3] arm64: dts: Add Mediatek SoC MT8192 and evaluation board dts and
Makefile
---
From: Zhanyong Wang
need to add wakeup solution as V3
since not support presently.
Signed-off-by: Zhanyong Wang
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 9 +
1 file changed, 9 insertions(+)
mode change 100644 => 100755 drivers/usb/host/xhci-mtk.c
diff --git
From: Zhanyong Wang
Add SSUSB related nodes for mt8192
Signed-off-by: Zhanyong Wang
Signed-off-by: Chunfeng Yun
---
Depends on:
https://patchwork.kernel.org/patch/11713559/
[v4,1/3] arm64: dts: Add Mediatek SoC MT8192 and evaluation board dts and
Makefile
---
On Tue, Sep 01, 2020 at 07:01:08PM +0800, Shengjiu Wang wrote:
> One data channel is one data line. From imx7ulp, the SAI IP is
> enhanced to support multiple data channels.
>
> If there is only two channels input and slots is 2, then enable one
> data channel is enough for data transfer. So
From: CK Hu
add support runtime pm feature
Signed-off-by: Zhanyong Wang
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 446 +++-
drivers/usb/host/xhci-mtk.h | 14 ++
2 files changed, 455 insertions(+), 5 deletions(-)
mode change 100644
From: Zhanyong Wang
After inserted the usb type-c 3.5mm dongle with headset, dmesg showed:
usb 1-1.1: new full-speed USB device number 5 using xhci-mtk
usb 1-1.1: New USB device found, idVendor=05ac, idProduct=110a, bcdDevice=26.11
usb 1-1.1: New USB device strings: Mfr=1, Product=2,
From: Zhanyong Wang
need to add wakeup solution as V3
since not support presently.
Signed-off-by: Zhanyong Wang
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 9 +
1 file changed, 9 insertions(+)
mode change 100644 => 100755 drivers/usb/host/xhci-mtk.c
diff --git
On Wed, Sep 02, 2020 at 10:13:12AM +0200, Niklas Schnelle wrote:
> On 9/2/20 12:16 AM, Nicolin Chen wrote:
> > These two patches are to update default segment_boundary_mask.
> >
> > PATCH-1 fixes overflow issues in callers of dma_get_seg_boundary.
> > Previous version was a series:
This patch adds the binding documentation of camsys-raw,
camsys and imgsys for Mediatek MT8192.
Signed-off-by: Weiyi Lu
---
.../bindings/arm/mediatek/mediatek,camsys-raw.yaml | 54 ++
.../bindings/arm/mediatek/mediatek,camsys.txt | 1 +
In all MediaTek PLL design, bit0 of CON0 register is always
the enable bit.
However, there's a special case of usbpll on MT8192.
The enable bit of usbpll is moved to bit2 of other register.
Add configurable en_reg and pll_en_bit for enable control or
default 0 where pll data are static variables.
Add MT8192 clock dt-bindings, include topckgen, apmixedsys,
infracfg, pericfg and subsystem clocks.
Signed-off-by: Weiyi Lu
---
include/dt-bindings/clock/mt8192-clk.h | 592 +
1 file changed, 592 insertions(+)
create mode 100644
The en_mask actually is a combination of divider enable mask
and pll enable bit(bit0).
Before this patch, we enabled both divider mask and bit0 in prepare(),
but only cleared the bit0 in unprepare().
Now, setting the enable register(CON0) in 2 steps: first divider mask,
then bit0 during prepare(),
This patch adds the binding documentation of mdpsys, mmsys,
vdecsys-soc, vdecsys and vencsys for Mediatek MT8192.
Signed-off-by: Weiyi Lu
---
.../bindings/arm/mediatek/mediatek,mdpsys.yaml | 38 ++
.../bindings/arm/mediatek/mediatek,mmsys.txt | 1 +
This series is based on v5.9-rc1 and MT8192 dts[1].
[1] https://patchwork.kernel.org/cover/11713555/
changes since v2:
- update and split dt-binding documents by functionalities
- add error checking in probe() function
- fix incorrect clock relation and add critical clocks
- update license
This patch adds the binding documentation of audsys and scp-adsp
for Mediatek MT8192.
Signed-off-by: Weiyi Lu
---
.../bindings/arm/mediatek/mediatek,audsys.txt | 1 +
.../bindings/arm/mediatek/mediatek,scp-adsp.yaml | 38 ++
2 files changed, 39 insertions(+)
create
This patch adds the binding documentation of ipesys and mfgcfg
for Mediatek MT8192.
Signed-off-by: Weiyi Lu
---
Documentation/devicetree/bindings/arm/mediatek/mediatek,ipesys.txt | 1 +
Documentation/devicetree/bindings/arm/mediatek/mediatek,mfgcfg.txt | 1 +
2 files changed, 2 insertions(+)
This patch adds the binding documentation of apmixedsys, imp_iic_wrap,
infracfg, msdc, pericfg and topckgen for Mediatek MT8192.
Signed-off-by: Weiyi Lu
---
.../bindings/arm/mediatek/mediatek,apmixedsys.txt | 1 +
.../arm/mediatek/mediatek,imp_iic_wrap.yaml| 78 ++
On Sun, Aug 30, 2020 at 05:10:10PM -0700, Guenter Roeck wrote:
> On Mon, Aug 31, 2020 at 12:36:21AM +0300, Laurent Pinchart wrote:
> > Hi Guenter,
> >
> [ ... ]
>
> > I'll try to prototype what I envision would be a good solution in the
> > V4L2 core. If stars align, I may even try to push it
On Wed, Sep 02, 2020 at 02:06:13PM -0400, Zi Yan wrote:
> When depositing page table pages for 1GB THPs, we need 512 PTE pages +
> 1 PMD page. Instead of counting and depositing 513 pages, we can use the
> PMD page as a leader page and chain the rest 512 PTE pages with ->lru.
> This, however,
Transmit data pins will output zero when slots are masked or channels
are disabled. In CHMOD TDM mode, transmit data pins are tri-stated when
slots are masked or channels are disabled. When data pins are tri-stated,
there is noise on some channels when FS clock value is high and data is
read while
config: mips-randconfig-r033-20200902 (attached as .config)
compiler: mips64el-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout
Commit c4f382930145 (power: supply: sbs-battery: don't assume
i2c errors as battery disconnect) overwrites the original error code
returned from internal functions. On such a sporadic i2c error,
a user will get a wrong value without errors.
Fixes: c4f382930145 (power: supply: sbs-battery: don't
From: Daeho Jeong
writepages() can be concurrently invoked for the same file by different
threads such as a thread fsyncing the file and a kworker kernel thread.
So, changing i_compr_blocks without protection is racy and we need to
protect it by changing it with atomic type value. Plus, we don't
The number of distinct CMA areas is limited by the constant
CONFIG_CMA_AREAS. In most environments, this was set to a default
value of 7. Not too long ago, support was added to allocate hugetlb
gigantic pages from CMA. More recent changes to make dma_alloc_coherent
NUMA-aware on arm64 added
On Wed, 26 Aug 2020 15:24:26 +0800, Luo Jiaxing wrote:
> We found that it will fail every time when set feature to SATA disk by
> "sdparm -s WCE=0 /dev/sde".
>
> After checking protocol, we know that MODE SELECT is the SCSI command for
> setting WCE, and it do not exist in the SATA protocol.
On Sun, 23 Aug 2020 17:14:53 +0800, Dinghao Liu wrote:
> When pm8001_tag_alloc() fails, task should be freed just
> like what we've done in the subsequent error paths.
Applied to 5.9/scsi-fixes, thanks!
[1/1] scsi: pm8001: Fix memleak in pm8001_exec_internal_task_abort
On 9/2/2020 4:50 PM, Andy Lutomirski wrote:
On Sep 2, 2020, at 3:13 PM, Yu, Yu-cheng wrote:
On 9/2/2020 1:03 PM, Jann Horn wrote:
On Tue, Aug 25, 2020 at 2:30 AM Yu-cheng Yu wrote:
Add REGSET_CET64/REGSET_CET32 to get/set CET MSRs:
IA32_U_CET (user-mode CET settings) and
On 9/2/2020 5:33 PM, Jann Horn wrote:
On Thu, Sep 3, 2020 at 12:13 AM Yu, Yu-cheng wrote:
On 9/2/2020 1:03 PM, Jann Horn wrote:
On Tue, Aug 25, 2020 at 2:30 AM Yu-cheng Yu wrote:
Add REGSET_CET64/REGSET_CET32 to get/set CET MSRs:
IA32_U_CET (user-mode CET settings) and
On Wed, Sep 2, 2020 at 7:22 PM Yunsheng Lin wrote:
>
> On 2020/9/3 9:48, Cong Wang wrote:
> > On Wed, Sep 2, 2020 at 6:22 PM Yunsheng Lin wrote:
> >>
> >> On 2020/9/3 8:35, Cong Wang wrote:
> >>> On Tue, Sep 1, 2020 at 11:35 PM Yunsheng Lin
> >>> wrote:
>
> On 2020/9/2 12:41, Cong
Sometimes firmware sizes can be in ten's of MB's and reading
all the memory during coredump can consume lot of time and
memory.
Introducing support for mini-dumps. Mini-dump contains smallest
amount of useful information, that could help to debug subsystem
crashes.
During bootup memory is
This patch adds support for collecting minidump in the
event of remoteproc crash. Parse the minidump table
based on remoteproc's unique minidump-id, read all
memory regions from the remoteproc's minidump table
entry and expose the memory to userspace.
The remoteproc platform driver can choose to
Add minidump id for modem in sm8150 chipset.
Signed-off-by: Rishabh Bhatnagar
Signed-off-by: Gurbir Arora
---
drivers/remoteproc/qcom_q6v5_pas.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/remoteproc/qcom_q6v5_pas.c
b/drivers/remoteproc/qcom_q6v5_pas.c
index 19873d1..d35a502
Each remoteproc might have different requirements for coredumps and might
want to choose the type of dumps it wants to collect. This change allows
remoteproc drivers to specify their own custom dump function to be executed
in place of rproc_coredump. If the coredump op is not specified by the
Hello,
syzbot found the following issue on:
HEAD commit:4d41ead6 Merge tag 'block-5.9-2020-08-28' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=174adf4990
kernel config: https://syzkaller.appspot.com/x/.config?x=891ca5711a9f1650
On 9/2/20 5:58 PM, Nícolas F. R. A. Prado wrote:
> In order to cross-reference C types in the documentation, Sphinx
> requires the syntax :c:type:`type_name`, or even :c:type:`struct
> type_name ` in order to have the link text different from the
> target text.
> This patch series removes the need
On Thu, Sep 3, 2020 at 11:18 AM Nathan Royce wrote:
>
> Heard, but all the same if it isn't important (which I'm assuming),
> I'd just as soon be left out of it. That's just the way I am in
> general, not wanting to be seen unless I have to be seen. Thanks
> though.
OK, I will drop your tag.
Hi all,
After merging the tip tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
Caused by commit
f670269a42bf ("x86: Fix early boot crash on gcc-10, next try")
interacting with commit
a9a3ed1eff36 ("x86: Fix early boot crash on gcc-10, third try")
from Linus'
On Wed, 2 Sep 2020 18:03:23 +0200
pet...@infradead.org wrote:
>
> During the LPC RCU BoF Paul asked how come the "USED" <- "IN-NMI"
> detector doesn't trip over rcu_read_lock()'s lockdep annotation.
>
> Looking into this I found a very embarrasing typo in
> verify_lock_unused():
>
> - if
When CONFIG_RETPOLINE is disabled, Clang uses a jump table for the
switch statement in cmdline_find_option (jump tables are disabled when
CONFIG_RETPOLINE is enabled). This function is called very early in boot
from sme_enable() if CONFIG_AMD_MEM_ENCRYPT is enabled. At this time,
the kernel is
To recovery non-fatal errors, no full reset is required, err_handler only
clears those pending TRs/TMRs so that scsi layer can re-issue them. In
current err_handler, TRs are directly cleared from UFS host's doorbell but
not aborted from device side. However, according to the UFSHCI JEDEC spec,
the
PA Layer issues a LINERESET to the PHY at the recovery step in the Power
Mode change operation. If it happens during auto or mannual hibern8 enter,
even if hibern8 enter succeeds, UFS power mode shall be set to PWM-G1 mode
and kept in that mode after exit from hibern8, leading to bad performance.
Hi Peter,
On Wed, Sep 02, 2020 at 03:48:05PM +0200, Peter Zijlstra wrote:
> On Wed, Sep 02, 2020 at 02:21:27PM +0100, Leo Yan wrote:
> > The system register CNTVCT_EL0 can be used to retrieve the counter from
> > user space. Add rdtsc() for Arm64.
>
> > +u64 rdtsc(void)
> > +{
> > + u64 val;
1 - 100 of 1333 matches
Mail list logo
