pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
A new function pm_runtime_resume_and_get is introduced in
[0] to keep usage counter balanced. So We fix the reference
leak by replacing it with new funtion.
Hi Linus,
Here is a set of small, straight-forward fixes for platform-drivers-x86 for
5.10:
- thinkpad_acpi fixes: 2 bug-fixes and 3 model specific quirks
- fixes for misc. other drivers: 2 bug-fixes and 3 model specific quirks
Regards,
Hans
The following changes since commit
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
A new function pm_runtime_resume_and_get is introduced in
[0] to keep usage counter balanced. So We fix the reference
leak by replacing it with new funtion.
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
A new function pm_runtime_resume_and_get is introduced in
[0] to keep usage counter balanced. So We fix the reference
leak by replacing it with new funtion.
We need to always set ->need_cache_sync_on_prepare and
->need_cache_sync_on_finish when we initialize vb2 buffer.
Currently these flags are set/adjusted only in V4L2's
vb2_queue_or_prepare_buf(), which means that for the code
paths that don't use V4L2 vb2 will always tell videobuf2
core to skip
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
Use pm_runtime_resume_and_get to fix it.
Qinglang Miao (2):
crypto: stm32/cryp - fix reference leak in stm32_cryp_remove
crypto: stm32/hash - fix
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
A new function pm_runtime_resume_and_get is introduced in
[0] to keep usage counter balanced. So We fix the reference
leak by replacing it with new funtion.
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
A new function pm_runtime_resume_and_get is introduced in
[0] to keep usage counter balanced. So We fix the reference
leak by replacing it with new funtion.
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
Use pm_runtime_resume_and_get to fix it.
Qinglang Miao (3):
crypto: sun4i - fix reference leak in sun4i-ss
crypto: sun8i - fix reference leak in sun8i-ce
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
A new function pm_runtime_resume_and_get is introduced in
[0] to keep usage counter balanced. So We fix the reference
leak by replacing it with new funtion.
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
A new function pm_runtime_resume_and_get is introduced in
[0] to keep usage counter balanced. So We fix the reference
leak by replacing it with new funtion.
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
A new function pm_runtime_resume_and_get is introduced in
[0] to keep usage counter balanced. So We fix the reference
leak by replacing it with new funtion.
Hello Lee,
On Fri, 2020-11-27 at 08:32 +, Lee Jones wrote:
> On Mon, 23 Nov 2020, Matti Vaittinen wrote:
>
> > Add core support for ROHM BD9576MUF and BD9573MUF PMICs which are
> > mainly used to power the R-Car series processors.
> >
> > Signed-off-by: Matti Vaittinen
> > ---
> >
On Fri, Nov 27, 2020 at 05:44:46PM +0800, Qinglang Miao wrote:
> pm_runtime_get_sync will increment pm usage counter even it
> failed. Forgetting to putting operation will result in a
> reference leak here.
>
> A new function pm_runtime_resume_and_get is introduced in
> [0] to keep usage counter
On Fri, Nov 27, 2020 at 09:22:24AM +0100, Christophe Leroy wrote:
> Le 27/11/2020 à 06:06, Anshuman Khandual a écrit :
> > This adds validation tests for dirtiness after write protect conversion for
> > each page table level. This is important for platforms such as arm64 that
> > removes the
On (20/11/27 18:41), Sergey Senozhatsky wrote:
> We need to always set ->need_cache_sync_on_prepare and
> ->need_cache_sync_on_finish when we initialize vb2 buffer.
>
> Currently these flags are set/adjusted only in V4L2's
> vb2_queue_or_prepare_buf(), which means that for the code
> paths that
Daeho,
How about updating this patch based on below patch?
f2fs: introduce a new per-sb directory in sysfs
On 2020/10/22 10:53, Daeho Jeong wrote:
Yep, It sounds good to me.
2020년 10월 21일 (수) 오후 3:08, Chao Yu 님이 작성:
On 2020/10/16 13:14, Daeho Jeong wrote:
From: Daeho Jeong
Added
> Hi Peter,
>
> On 25/11/2020 14:49, Roger Quadros wrote:
> > Hardware based role switch is broken as the driver always skips it.
> > Fix this by registering for SW role switch only if 'usb-role-switch'
> > property is present in the device tree.
> >
> > Fixes: 50642709f659 ("usb: cdns3: core:
On Tuesday 24 Nov 2020 at 15:50:32 (+), Will Deacon wrote:
> Asymmetric systems may not offer the same level of userspace ISA support
> across all CPUs, meaning that some applications cannot be executed by
> some CPUs. As a concrete example, upcoming arm64 big.LITTLE designs do
> not feature
On Tuesday 24 Nov 2020 at 15:50:36 (+), Will Deacon wrote:
> Reject explicit requests to change the affinity mask of a task via
> set_cpus_allowed_ptr() if the requested mask is not a subset of the
> mask returned by arch_task_cpu_possible_mask(). This ensures that the
> 'cpus_mask' for a
To support playback continuation after hard suspend(bypass powerd)
and resume:
Prepare device in platform trigger callback.
Make I2s and DMA control registers as non volatile.
Signed-off-by: V Sujith Kumar Reddy
Signed-off-by: Srinivasa Rao Mandadapu
---
Changes Since v1 and v2:
-- Subject
On 2020-11-26 16:52, John Garry wrote:
Hi Marc,
https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=irq/hacks
ok, I'll have a look
I tried that and it doesn't look to work.
I find that for the its_msi_prepare() call, its_dev->shared does not
get set, as
On Fri, Nov 20, 2020 at 03:48:47PM +0800, Qinglang Miao wrote:
> kfree(dev) has been called inside put_device so anther
> kfree would cause a use-after-free bug/
>
> Fixes: 8286ae03308c ("MIPS: Add CDMM bus support")
> Reported-by: Hulk Robot
> Signed-off-by: Qinglang Miao
> ---
>
On Wed, Nov 25, 2020 at 06:11:30PM +0800, Tiezhu Yang wrote:
> After commit 9cce844abf07 ("MIPS: CPU#0 is not hotpluggable"),
> c->hotpluggable is 0 for CPU 0 and it will not generate a control
> file in sysfs for this CPU:
>
> [root@linux loongson]# cat /sys/devices/system/cpu/cpu0/online
> cat:
On Wed, Nov 25, 2020 at 06:06:52PM +0800, Jinyang He wrote:
> Abandon the third patch in v1. There are many other factors that should
> be considered. If possible, I'll fix it later.
>
> Jinyang He (2):
> MIPS: KASLR: Correcte valid bits in apply_r_mips_26_rel()
> MIPS: Loongson64: Add KASLR
On Fri, 27 Nov 2020 09:33:08 +0800, Lu Baolu wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/iommu/intel/iommu.c:5643:27: warning: variable 'last_pfn' set but not
> used [-Wunused-but-set-variable]
> 5643 | unsigned long start_pfn, last_pfn;
> |
On Wed, Nov 25, 2020 at 03:51:20PM +0100, Jessica Yu wrote:
> I've queued up patches 3, 4, 6, 7, 8 for testing before pushing them
> out to modules-next.
Thanks, Jessica.
Perhaps you can consider taking also the one for setup parameters (patch
5/8) through your tree since its related to the
Hi Christoph,
On Fri, 27 Nov 2020 10:21:37 +0100 Christoph Hellwig wrote:
>
> On Fri, Nov 27, 2020 at 05:58:01PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the dma-mapping tree, today's linux-next build (powerpc64
> > allnoconfig) failed like this:
>
> I'm looking into
Losing arbitration is normal in a CAN-bus network, it means that a
higher priority frame is being send and the pending message will be
retried later. Hence most driver only increment arbitration_lost, but
the sja1000 and sun4i driver also incremeant tx_error, causing errors
to be reported on a
On Tuesday 24 Nov 2020 at 15:50:33 (+), Will Deacon wrote:
> When exec'ing a 32-bit task on a system with mismatched support for
> 32-bit EL0, try to ensure that it starts life on a CPU that can actually
> run it.
>
> Signed-off-by: Will Deacon
> ---
> arch/arm64/kernel/process.c | 42
On 27/11/2020 09:44, Qinglang Miao wrote:
pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here.
A new function pm_runtime_resume_and_get is introduced in
[0] to keep usage counter balanced. So We fix the
On 11/27/20 9:56 AM, Halil Pasic wrote:
> On Thu, 26 Nov 2020 18:00:37 +0100
> Alexander Gordeev wrote:
>
>> The directed MSIs are delivered to CPUs whose address is
>> written to the MSI message data. The current code assumes
>> that a CPU logical number (as it is seen by the kernel)
>> is
On Thu, Nov 26, 2020 at 05:54:52PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 18 Nov 2020 16:29:34 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the v4l-dvb tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > Documentation/output/lirc.h.rst:6:
* Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> kernel/smp.c: In function 'csd_lock_wait_getcpu':
> kernel/smp.c:133:13: error: 'call_single_data_t' {aka 'struct
> __call_single_data'} has no member
On Thu, Nov 26, 2020 at 03:54:14PM +, David Brazdil wrote:
> Forward the following PSCI SMCs issued by host to EL3 as they do not
> require the hypervisor's intervention. This assumes that EL3 correctly
> implements the PSCI specification.
>
> Only function IDs implemented in Linux are
From: Alexander Sverdlin
Give uartlite a chance to be probed when IRQ controller will be finally
available and return potential -EPROBE_DEFER as-is. The condition "<="
has been changed to "<" to follow the recommendation in the header of
platform_get_irq().
Signed-off-by: Alexander Sverdlin
[ Again, please do not top-post. Quoting Greg:
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is
From: Mauro Carvalho Chehab
Fix the name of the enum on its kernel-doc markup:
enum slim_ch_aux_fmt -> enum slim_ch_aux_bit_fmt
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Srinivas Kandagatla
---
drivers/slimbus/slimbus.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Thanks Michal!!
On 11/26/2020 2:48 PM, Michal Hocko wrote:
> On Wed 25-11-20 16:18:06, Charan Teja Kalla wrote:
>>
>>
>> On 11/24/2020 1:11 PM, Michal Hocko wrote:
>>> On Mon 23-11-20 20:40:40, Charan Teja Kalla wrote:
Thanks Michal!
On 11/23/2020 7:43 PM, Michal Hocko wrote:
>
From: Bjorn Andersson
Attempting to send a power request during PM operations, when the QMI
handle isn't initialized results in a NULL pointer dereference. So check
if the QMI handle has been initialized before attempting to post the
power requests.
Fixes: 917809e2280b ("slimbus: ngd: Add qcom
Add support to protection domain restart. Protection domain restart
would also restart the service just like SSR.
Signed-off-by: Srinivas Kandagatla
---
drivers/slimbus/Kconfig | 1 +
drivers/slimbus/qcom-ngd-ctrl.c | 24
2 files changed, 25 insertions(+)
diff
Failure of dma_alloc_coherent will already throw a error message,
so addition message is really redundant here. Remove it!
Signed-off-by: Srinivas Kandagatla
---
drivers/slimbus/qcom-ngd-ctrl.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/slimbus/qcom-ngd-ctrl.c
This patch adds SSR(SubSystem Restart) support which includes, synchronisation
between SSR and QMI server notifications. Also with this patch now NGD is taken
down by SSR instead of QMI server down notification.
NGD up path now relies on both SSR and QMI notifications and particularly
sequence of
From: Rikard Falkeborn
qcom_slim_qmi_msg_handlers[] and qcom_slim_ngd_qmi_svc_event_ops are
only used as input arguments to qmi_handle_init() which accepts const
pointers to both qmi_ops and qmi_msg_handler. Make them const to allow
the compiler to put them in read-only memory.
Signed-off-by:
On 2020-11-24 15:50, Will Deacon wrote:
When confronted with a mixture of CPUs, some of which support 32-bit
applications and others which don't, we quite sensibly treat the system
as 64-bit only for userspace and prevent execve() of 32-bit binaries.
Unfortunately, some crazy folks have decided
From: "Gustavo A. R. Silva"
In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
by explicitly adding a break statement instead of letting the code fall
through to the next case.
Link: https://github.com/KSPP/linux/issues/115
Signed-off-by: Gustavo A. R. Silva
Hi Greg,
Here are some slimbus patches for 5.11 which includes
- ngd controller has added PDR and SSR support along with a trival fixes.
- few doc and clang warning fixes in slimbus
Can you please queue them up for 5.11.
thanks for you help,
srini
Bjorn Andersson (1):
slimbus: qcom-ngd-ctrl:
On 2020-11-24 15:50, Will Deacon wrote:
If a vCPU is caught running 32-bit code on a system with mismatched
support at EL0, then we should kill it.
Acked-by: Marc Zyngier
Signed-off-by: Will Deacon
---
arch/arm64/kvm/arm.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
Hi Greg,
Here are some nvmem patches for 5.11 which includes
- adding support to keepout regions in nvmem core
- support for unaligned word count in imx provider
- imx and qfprom new compatible strings.
Can you please queue them up for 5.11.
thanks for you help,
srini
Evan Green (3):
nvmem:
From: Evan Green
Some fuse ranges are protected by the XPU such that the AP cannot
access them. Attempting to do so causes an SError. Use the newly
introduced per-soc compatible string, and the newly introduced
nvmem keepout support to attach the set of regions
we should not access.
From: Peng Fan
When offset is not 4 bytes aligned, directly shift righty by 2 bits
will cause reading out wrong data. Since imx ocotp only supports
4 bytes reading once, we need handle offset is not 4 bytes aligned
and enlarge the bytes to 4 bytes aligned. After reading finished,
copy the needed
From: Fabien Parent
Add binding documentation for MT8516 SoCs.
Signed-off-by: Fabien Parent
Acked-by: Rob Herring
Signed-off-by: Srinivas Kandagatla
---
Documentation/devicetree/bindings/nvmem/mtk-efuse.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Evan Green
Introduce support into the nvmem core for arrays of register ranges
that should not result in actual device access. For these regions a
constant byte (repeated) is returned instead on read, and writes are
quietly ignored and returned as successful.
This is useful for instance
On Thu, Nov 26, 2020 at 7:00 PM Robert Foss wrote:
>
> On Wed, 25 Nov 2020 at 08:32, Tomasz Figa wrote:
> >
> > Hi Bingbu,
> >
> > On Wed, Nov 25, 2020 at 1:15 PM Bingbu Cao
> > wrote:
> > >
> > >
> > >
> > > On 11/24/20 6:20 PM, Robert Foss wrote:
> > > > On Tue, 24 Nov 2020 at 10:42, Bingbu
From: Evan Green
Add SoC-specific compatible strings so that data can be attached
to it in the driver.
Signed-off-by: Evan Green
Reviewed-by: Rob Herring
Signed-off-by: Srinivas Kandagatla
---
.../devicetree/bindings/nvmem/qcom,qfprom.yaml | 17 ++---
1 file changed, 14
Hi Will
Thanks a lot for your detailed review of my v3 below and sorry for the delay of
my answer : those last months were rather focused on the pmu driver using
than its improvement.
I prepared a v4 on kernel 5.10, taking into account most of your remarks below
but I still have some open
On 11/10/20 12:45 PM, Anshuman Khandual wrote:
perf handle structure needs to be shared with the TRBE IRQ handler for
capturing trace data and restarting the handle. There is a probability
of an undefined reference based crash when etm event is being stopped
while a TRBE IRQ also getting
Hi ALex,
On 11/26/20 7:32 PM, Alejandro Colomar wrote:
> The current Linux kernel only provides a definition of 'spu_create()'.
> It has 4 parameters, the last being 'int neighbor_fd'.
>
> Before Linux 2.6.23, there was an older prototype,
> which didn't have this last parameter.
>
> Move that
From: Thierry Reding
These were just some minor typos that have crept in recently and are
easily fixed.
Signed-off-by: Thierry Reding
---
drivers/base/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index
Dear all,
The following patches add the required nodes to enable dsi and display
support for MT8183 based boards. The patches were tested on a Lenovo
Ideapad Duet with an out-of-tree patch that enables the display for that
board.
The patches depends on [1].
[1]
Add iommu and larb nodes to the MT8183.
Signed-off-by: Enric Balletbo i Serra
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 79
1 file changed, 79 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
index
From: Jitao Shi
Add dsi and mipitx nodes to the MT8183.
Signed-off-by: Jitao Shi
Signed-off-by: Enric Balletbo i Serra
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 31
1 file changed, 31 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
Add display subsystem device nodes to allow video output.
Signed-off-by: Enric Balletbo i Serra
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 114 +++
1 file changed, 114 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
On 2020/11/27 16:17, Zheng Zengkai wrote:
> Hello Tetsuo,
>> On 2020/11/26 15:33, Zheng Zengkai wrote:
>>> As your say, I found the function tomoyo_assign_namespace( )
>>>
>>> in security/tomoyo/domain.c has the similar situation,
>>>
>>> Can I add __GFP_NOWARN for both and remove the null check
On Thu, Nov 26, 2020 at 08:31:51PM +, Mel Gorman wrote:
> > > and it is reasonable behaviour but it should be tunable.
> >
> > Only if there is no way to cover all of the relevant use cases in a
> > generally acceptable way without adding more module params etc.
> >
> > In this particular
Hi Michael,
On 11/27/20 11:43 AM, Michael Kerrisk (man-pages) wrote:
> Hi ALex,
>
> On 11/26/20 7:32 PM, Alejandro Colomar wrote:
>> The current Linux kernel only provides a definition of 'spu_create()'.
>> It has 4 parameters, the last being 'int neighbor_fd'.
>>
>> Before Linux 2.6.23, there
Hyvä asiakas
Freedom Market Investments on erikoistunut minkä tahansa määrän lainojen
järjestämiseen, joiden takaisinmaksuaika on pidempi. Tarjoamme yrityslainoja,
asuntolainoja, henkilökohtaisia ??lainoja, autolainoja, opintolainoja,
konsolidointiosastoa, Business Start -lainoja. Onko sinulla
default to 1 message per transfer (requested by Helen)
- Move -EIO error reporting to transfer function to cleanup transfer() itself
and its R/W callers
- Remove magic value hardcodings and introduce enum force_release.
Applies on next-20201127, tested on Chromebook EVE.
---
drivers/cha
Aliases property name must include only lowercase and '-', so fix this
in the driver, so we're not tempted to do "ovl_2l0 = _2l0" in the
device-tree instead of the right one which is "ovl-2l0 = _2l0".
Fixes: dd8feb2262d9 ("drm/mediatek: add component OVL_2L1")
Fixes: b17bdd0d7a73 ("drm/mediatek:
On Fri, Nov 27, 2020 at 08:11:05AM +0100, Uwe Kleine-König wrote:
> Hello Jonathan,
>
> On Fri, Nov 27, 2020 at 12:19:31AM +0100, Jonathan Neuschäfer wrote:
> > On Tue, Nov 24, 2020 at 09:20:19AM +0100, Uwe Kleine-König wrote:
> > > On Sun, Nov 22, 2020 at 11:27:36PM +0100, Jonathan Neuschäfer
On Tue, Nov 24, 2020 at 08:09:19PM +0200, Julian Anastasov wrote:
>
> Hello,
>
> On Tue, 24 Nov 2020, Wang Hai wrote:
>
> > kmemleak report a memory leak as follows:
> >
> > BUG: memory leak
> > unreferenced object 0x8880759ea000 (size 256):
> > backtrace:
> > []
Em Sat, 30 May 2020 10:41:17 +0800
Jia-Ju Bai escreveu:
> The value hdev->sfr.kva is stored in DMA memory, and it is assigned to
> sfr, so sfr->buf_size can be modified at anytime by malicious hardware.
> In this case, a buffer overflow may happen when the code
> "sfr->data[sfr->buf_size - 1]"
From: Alexander Sverdlin
Allocate the IRQ descriptors where necessary before configuring them via
irq_set_chip_and_handler(). Fixes the following soft lockup:
watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [modprobe:72]
Modules linked in:
irq event stamp: 33288
hardirqs last enabled at
On Wed, 25 Nov 2020, Shihlun Lin wrote:
> AHC1EC0 is the embedded controller driver for Advantech industrial
> products. This provides sub-devices such as hwmon and watchdog, and also
> expose functions for sub-devices to read/write the value to embedded
> controller.
>
> Signed-off-by: Shihlun
From: Lars-Peter Clausen
If no platform data is supplied use a dummy platform data that configures
the device in GPIO only mode. This change adds a adp5589_kpad_pdata_get()
helper that returns the default platform-data. This can be later extended
to load configuration from device-trees or ACPI.
This change wraps the devices supported by the adp5589 driver into a chip
info struct. With this, a device table can be created, and the probed
device can be selected based on the enum value provided by the i2c driver
data.
Signed-off-by: Alexandru Ardelean
---
From: Lars-Peter Clausen
Add very basic devicetree suppport to the adp5589 allowing the device to be
registered from devicetree and ACPI via PRP0001.
Signed-off-by: Lars-Peter Clausen
Signed-off-by: Alexandru Ardelean
---
drivers/input/keyboard/adp5589-keys.c | 30 ++-
This change adds the device-tree entries for the Analog Devices ADP5585 and
ADP5589 devices to the trivial devices list.
Signed-off-by: Alexandru Ardelean
---
Documentation/devicetree/bindings/trivial-devices.yaml | 6 ++
1 file changed, 6 insertions(+)
diff --git
From: Rafał Miłecki
It's a trivial reset controller. One register with bit per PCIe core.
Signed-off-by: Rafał Miłecki
---
drivers/reset/Kconfig| 2 +-
drivers/reset/reset-simple.c | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/reset/Kconfig
From: Rafał Miłecki
BCM4908 was built using older PCIe hardware block that requires using
external reset block controlling PERST# signals.
Signed-off-by: Rafał Miłecki
---
.../reset/brcm,bcm4908-misc-pcie-reset.yaml | 39 +++
1 file changed, 39 insertions(+)
create mode
On Wed, Nov 25, 2020 at 06:11:02PM +0800, Jinyang He wrote:
> Reserve memory from &_text to &_end. Otherwise if kernel address
> was modified, the memory range of start_pfn to kernel_start_pfn
> would be reserved. Then we could not use this range.
>
> Signed-off-by: Jinyang He
> ---
>
On 30/10/2020 12:36, Enric Balletbo i Serra wrote:
Dear all,
This is a new driver with the aim to deprecate the mtk-scpsys driver.
The problem with that driver is that, in order to support more Mediatek
SoCs you need to add some logic to handle properly the power-up
sequence of newer
On 25/11/2020 11:24, Enric Balletbo i Serra wrote:
Hi Hsin-Yi,
Thank you for your patch.
On 24/11/20 5:12, Hsin-Yi Wang wrote:
Add pwm to mt8183 and backlight to mt8183-kukui.
Signed-off-by: Hsin-Yi Wang
---
Picked the patch and checked that pwm for the backlight is working as expected
This is my take on the split irqchip bug that David reported. It's a
much more complicated patch, but I think it really gets to the bottom
of the issue and the code is clearer.
Paolo
Paolo Bonzini (2):
KVM: x86: handle !lapic_in_kernel case in kvm_cpu_*_extint
KVM: x86: Fix split-irqchip vs
Centralize handling of interrupts from the userspace APIC
in kvm_cpu_has_extint and kvm_cpu_get_extint, since
userspace APIC interrupts are handled more or less the
same as ExtINTs are with split irqchip. This removes
duplicated code from kvm_cpu_has_injectable_intr and
kvm_cpu_has_interrupt, and
kvm_cpu_accept_dm_intr and kvm_vcpu_ready_for_interrupt_injection are
a hodge-podge of conditions, hacked together to get something that
more or less works. But what is actually needed is much simpler;
in both cases the fundamental question is, do we have a place to stash
an interrupt if
On Fri, Nov 27, 2020 at 8:35 AM Yonghong Song wrote:
>
>
>
> On 11/26/20 8:57 AM, Florent Revest wrote:
> > This helper exposes the kallsyms_lookup function to eBPF tracing
> > programs. This can be used to retrieve the name of the symbol at an
> > address. For example, when hooking into
From: Bongsu Jeon
Extract the common phy blocks to reuse it.
The UART module will use the common blocks.
Signed-off-by: Bongsu Jeon
---
Changes in v2:
- remove the common function's definition in common header file.
- make the common phy_common.c file to define the common function.
- wrap
On 27/11/2020 11:49, Enric Balletbo i Serra wrote:
Dear all,
The following patches add the required nodes to enable dsi and display
support for MT8183 based boards. The patches were tested on a Lenovo
Ideapad Duet with an out-of-tree patch that enables the display for that
board.
Applied
From: Andrew Cooper
> Sent: 26 November 2020 23:52
>
> On 26/11/2020 19:15, Andy Lutomirski wrote:
> > On Thu, Nov 26, 2020 at 11:07 AM Lukas Bulwahn
> > wrote:
> >> On Thu, Nov 26, 2020 at 6:16 PM Andrew Cooper
> >> wrote:
> >>> On 26/11/2020 11:54, Lukas Bulwahn wrote:
> Commit
On Fri, Nov 20, 2020 at 12:46:21PM +0100, Juergen Gross wrote:
> SWAPGS is used only for interrupts coming from user mode or for
> returning to user mode. So there is no reason to use the PARAVIRT
> framework, as it can easily be replaced by an ALTERNATIVE depending
> on X86_FEATURE_XENPV.
>
>
On Fri, Nov 27, 2020 at 10:21 AM Lee Jones wrote:
>
> It's a per-subsystem convention thing.
I think some allow both, too. For people that send tree-wide patches,
it would be if we agreed on the convention...
Cheers,
Miguel
Hi Linus,
Here are some arm64 fixes for -rc6. The main changes are relating to our
handling of access/dirty bits, where our low-level page-table helpers
could lead to stale young mappings and loss of the dirty bit in some
cases (the latter has not been observed in practice, but could happen
when
Hi,
On 11/24/20 11:27 AM, Christoph Hellwig wrote:
> On Mon, Nov 23, 2020 at 03:49:09PM +0100, Hans de Goede wrote:
>> Hi,
>>
>> +Cc Christoph Hellwig
>>
>> Christoph, this is still an issue, so I've been looking around a bit and
>> think this
>> might have something to do with the
On 2020/11/27 16:45, Chen Huang wrote:
When a function doesn't have a callee, then it will not push ra
into the stack, such as lkdtm_BUG() function:
addisp,sp,-16
sd s0,8(sp)
addis0,sp,16
ebreak
Then we use pt_regs as a parameter to walk_stackframe(), for the
struct stackframe
Hi again, Linus,
Here's another round of IOMMU fixes for -rc6 consisting mainly of a
bunch of independent driver fixes. Thomas agreed for me to take the
x86 'tboot' fix here, as it fixes a regression introduced by a vt-d
change.
Please pull,
Will
--->8
The following changes since commit
On 27/11/2020 01:17, Ivaylo Dimitrov wrote:
> Hi Tomi,
>
> On 26.11.20 г. 16:11 ч., Tomi Valkeinen wrote:
>> Hi Aaro, Ivaylo,
>>
>> On 24/11/2020 23:03, Ivaylo Dimitrov wrote:
>>
>>> Is there any progress on the issue? I tried 5.9.1 and still nothing
>>> displayed.
>>
>> Can you test the
On Fri, Nov 27, 2020 at 10:25:06AM +, Marc Zyngier wrote:
> On 2020-11-24 15:50, Will Deacon wrote:
> > When confronted with a mixture of CPUs, some of which support 32-bit
> > applications and others which don't, we quite sensibly treat the system
> > as 64-bit only for userspace and prevent
On Fri, Nov 27, 2020 at 06:39:24PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> include/linux/kernel.h
>
> between commit:
>
> 74d862b682f5 ("sched: Make migrate_disable/enable() independent of RT")
>
> from the tip
On Fri, Nov 27, 2020 at 10:26:47AM +, Marc Zyngier wrote:
> On 2020-11-24 15:50, Will Deacon wrote:
> > If a vCPU is caught running 32-bit code on a system with mismatched
> > support at EL0, then we should kill it.
> >
> > Acked-by: Marc Zyngier
> > Signed-off-by: Will Deacon
> > ---
> >
101 - 200 of 742 matches
Mail list logo
