Hi Tobias
On 8/14/20 8:11 PM, Tobias Schramm wrote:
Previously the FIFO on the stm32h743 usart was not utilized, because
the stm32f7 compatible configures it without FIFO support.
Signed-off-by: Tobias Schramm
---
arch/arm/boot/dts/stm32h743.dtsi | 4 ++--
1 file changed, 2 insertions(+),
+ Daniel
> > Commit 17a8f868ae3e ("opp: Return genpd virtual devices from
> > dev_pm_opp_attach_genpd()"):
> > "The cpufreq drivers don't need to do runtime PM operations on
> > the virtual devices returned by dev_pm_domain_attach_by_name() and so
> > the virtual devices weren't shared with
On Fri, 14 Aug 2020 14:47:22 -0700
Atish Patra wrote:
> pcibus_to_node is used only when numa is enabled and does not depend
> on ISA. Thus, it can be moved the generic numa implementation.
>
> Signed-off-by: Atish Patra
>From a more general unification point of view, there seem to
be two
Hi!
On Fri, Aug 21, 2020 at 04:10:42PM +0900, Hoegeun Kwon wrote:
> Hi everyone,
>
> There is a problem that the output does not work at a resolution
> exceeding FHD. To solve this, we need to adjust the bvb clock at a
> resolution exceeding FHD.
>
> Rebased on top of next-20200708 and [1].
>
On Sun, Aug 23, 2020 at 6:16 PM Krzysztof Kozlowski wrote:
> DTSes with new i.MX 8 SoCs introduce their own compatibles so add them
> to fix dtbs_check warnings like:
>
> arch/arm64/boot/dts/freescale/imx8mm-evk.dt.yaml: gpio@3020:
> compatible:0: 'fsl,imx8mm-gpio' is not one of
On Fri 28-08-20 11:07:29, pet...@infradead.org wrote:
> On Fri, Aug 28, 2020 at 02:07:12PM +0800, Xianting Tian wrote:
> > As the normal aio wait path(read_events() ->
> > wait_event_interruptible_hrtimeout()) doesn't account iowait time, so use
> > this patch to make it to account iowait time,
On 2020-08-28 09:03, Krzysztof Kozlowski wrote:
> On Fri, 28 Aug 2020 at 08:58, Peter Rosin wrote:
I'm not a huge fan of adding *one* odd line breaking the 80 column
recommendation to any file. I like to be able to fit multiple
windows side by side in a meaningful way. Also, I
On Fri, Aug 28, 2020 at 12:30:18PM +0300, Andy Shevchenko wrote:
> >
> > > > Cc: Hartmut Knaack
> > >
> > > ...and this?!
> >
> > Since email is not bouncing, he might still receive it.
>
> Hmm... I'm a bit puzzled now. It seems gmx.net has some policies in
> places that make my replies to your
On 2020-08-28 10:25, Andy Shevchenko wrote:
> On Fri, Aug 28, 2020 at 12:46 AM Peter Rosin wrote:
>> On 2020-08-27 21:26, Krzysztof Kozlowski wrote:
>
> ...
>
>> I'm not a huge fan of adding *one* odd line breaking the 80 column
>> recommendation to any file. I like to be able to fit multiple
On Thu, Aug 27, 2020 at 10:51:43PM +0800, ChiYuan Huang wrote:
> Heikki Krogerus 於 2020年8月27日 週四 下午10:00寫道：
> >
> > On Thu, Aug 27, 2020 at 07:18:55PM +0800, cy_huang wrote:
> > > From: ChiYuan Huang
> > >
> > > Mediatek MT6360 is a multi-functional IC that includes USB Type-C.
> > > It works
On Fri, 14 Aug 2020 14:47:21 -0700
Atish Patra wrote:
> As we are using generic numa implementation code, modify the init function
> name to indicate that generic implementation.
>
> Signed-off-by: Atish Patra
> ---
> arch/arm64/mm/init.c | 4 ++--
> drivers/base/arch_numa.c | 8
On Fri, 28 Aug 2020 at 11:22, Naresh Kamboju wrote:
>
> On Thu, 27 Aug 2020 at 17:06, Naresh Kamboju
> wrote:
> >
> > On Thu, 27 Aug 2020 at 15:42, Viresh Kumar wrote:
> > >
> > > On 27-08-20, 11:48, Arnd Bergmann wrote:
> > > > > > [3.680477] dev_pm_opp_put_clkname+0x30/0x58
> > > > > >
Hi Marcin,
On 8/9/20 6:44 PM, Marcin Sloniewski wrote:
Add support for Seeed Studio's stm32mp157c odyssey board.
Board consists of SoM with stm32mp157c with 4GB eMMC and 512 MB DDR3 RAM
and carrier board with USB and ETH interfaces, SD card connector,
wifi and BT chip AP6236.
In this patch
On Fri, Aug 28, 2020 at 12:00 PM Krzysztof Kozlowski wrote:
> On Fri, Aug 28, 2020 at 11:20:58AM +0300, Andy Shevchenko wrote:
> > On Thu, Aug 27, 2020 at 11:25 PM Krzysztof Kozlowski
> > wrote:
> > >
> > > Hartmut Knaack was an active reviewer and contributor to the IIO
> > > subsystem and
On Fri, Aug 28, 2020 at 10:59:38AM +0200, pet...@infradead.org wrote:
> On Fri, Aug 28, 2020 at 03:07:09AM +0200, Ahmed S. Darwish wrote:
> > +#define __SEQ_RT IS_ENABLED(CONFIG_PREEMPT_RT)
> > +
> > +SEQCOUNT_LOCKTYPE(raw_spinlock, raw_spinlock_t, false,s->lock,
> > raw_spin,
On Thu, 20 Aug 2020, Daniel Thompson wrote:
> On Thu, Aug 20, 2020 at 08:49:16AM +0100, Lee Jones wrote:
> > On Thu, 20 Aug 2020, dinghao@zju.edu.cn wrote:
> >
> > > > On Thu, 20 Aug 2020, dinghao@zju.edu.cn wrote:
> > > >
> > > > > > On Wed, 19 Aug 2020, Markus Elfring wrote:
> > > > >
On Fri, Aug 28, 2020 at 11:06:21AM +0200, Linus Walleij wrote:
> On Fri, Aug 14, 2020 at 12:04 PM Thomas Preston
> wrote:
>
> > - Fix a typo where mcp23x17 configs are referred to as mcp23x16.
> > - Fix precious range to include INTCAP{A,B}, which clear on read.
> > - Fix precious range to
On Fri, 28 Aug 2020 at 06:24, Christoph Hellwig wrote:
>
> On Thu, Aug 27, 2020 at 10:11:53PM -0400, Rich Felker wrote:
> > > This change broke SD card support on J2 because MMC_SPI spuriously
> > > depends on HAS_DMA. It looks like it can be fixed just by removing
> > > that dependency from
In the original process of dma_map/unmap pages for VFIO-devices,
to make sure the pages are contiguous, we have to check them one by one.
As a result, dma_map/unmap could spend a long time.
Using the hugetlb pages, we can avoid this problem.
All pages in hugetlb pages are contiguous.And the
From: ChiYuan Huang
Add a devicetree binding documentation for the MT6360 Type-C driver.
usb typec: mt6360: Rename DT binding doument from mt6360 to mt636x
Signed-off-by: ChiYuan Huang
---
.../bindings/usb/mediatek,mt6360-tcpc.yaml | 73 ++
1 file changed, 73
From: ChiYuan Huang
Mediatek MT6360 is a multi-functional IC that includes USB Type-C.
It works with Type-C Port Controller Manager to provide USB PD
and USB Type-C functionalities.
Signed-off-by: ChiYuan Huang
---
v1 to v2
1. Add fix to Prevent the race condition from interrupt and tcpci port
-a016-20200827
i386 randconfig-a015-20200827
i386 randconfig-a014-20200827
i386 randconfig-a013-20200828
i386 randconfig-a012-20200828
i386 randconfig-a011-20200828
i386 randconfig-a016-20200828
i386
On Tue, 25 Aug 2020, Julien Thierry wrote:
> Implementation of ORC requires some definitions that are currently
> provided by the target architecture headers. Do not depend on these
> definitions when the orc subcommand is not implemented.
>
> This avoid requiring arches with no orc
On Fri, 14 Aug 2020 14:47:20 -0700
Atish Patra wrote:
> ARM64 numa implementation is generic enough that RISC-V can reuse that
> implementation with very minor cosmetic changes. This will help both
> ARM64 and RISC-V in terms of maintanace and feature improvement
>
> Move the numa
On Wed, Aug 26, 2020 at 01:56:43PM +, Maoming (maoming, Cloud
Infrastructure Service Product Dept.) wrote:
> > + /*
> > +* Unlike THP, the splitting should not happen for hugetlb pages.
> > +* Since PG_reserved is not relevant for compound pages, and the pfn of
> > +* PAGE_SIZE
Hi,
Thanks for taking a look.
Some replies below:
On Fri, 14 Aug 2020 10:37:29 +0800
Ming Mao wrote:
> In the original process of pinning/unpinning pages for VFIO-devices,
> to make sure the pages are contiguous, we have to check them one by one.
> As a result, dma_map/unmap could spend a
On Thu, 27 Aug 2020 at 17:06, Naresh Kamboju wrote:
>
> On Thu, 27 Aug 2020 at 15:42, Viresh Kumar wrote:
> >
> > On 27-08-20, 11:48, Arnd Bergmann wrote:
> > > > > [3.680477] dev_pm_opp_put_clkname+0x30/0x58
> > > > > [3.683431] sdhci_msm_probe+0x284/0x9a0
> > >
> > >
Hi Stefan & Hoegeun
On Wed, 26 Aug 2020 at 11:04, Stefan Wahren wrote:
>
> Hi Hoeguen,
>
> Am 21.08.20 um 09:10 schrieb Hoegeun Kwon:
> > There is a problem that the output does not work at a resolution
> > exceeding FHD. To solve this, we need to adjust the bvb clock at a
> > resolution
On Thu 27-08-20 14:28:43, Dinghao Liu wrote:
> When ext4_journal_get_write_access() fails, we should release
> n_group_desc, iloc.bh, dind and gdb_bh to prevent memleak.
> It's the same when ext4_handle_dirty_super() fails, but we
> don't need to release dind here because it has been released
>
Hi Lee,
On 28/08/2020 10:50, Lee Jones wrote:
> When testing with !OF, the build system reports:
>
>>> drivers/mfd/khadas-mcu.c:125:34: warning: unused variable
>>> 'khadas_mcu_of_match' [-Wunused-const-variable]
>static const struct of_device_id khadas_mcu_of_match[] = {
>
randconfig-a001-20200827
x86_64 randconfig-a005-20200827
x86_64 randconfig-a006-20200827
x86_64 randconfig-a004-20200827
i386 randconfig-a002-20200828
i386 randconfig-a005-20200828
i386 randconfig-a003-20200828
i386
On Fri, Aug 28, 2020 at 06:13:41PM +0900, Masami Hiramatsu wrote:
> On Fri, 28 Aug 2020 10:48:51 +0200
> pet...@infradead.org wrote:
>
> > On Thu, Aug 27, 2020 at 06:12:44PM +0200, Peter Zijlstra wrote:
> > > struct kretprobe_instance {
> > > union {
> > > + /*
> > > + * Dodgy
//lore.kernel.org/linux-spdx/alpine.DEB.2.21.2008270740140.31123@felia
>
> Suggested-by: Greg Kroah-Hartman
> Signed-off-by: Lukas Bulwahn
> ---
> applies cleanly on current master and next-20200828
>
> James, Martin, please pick this minor non-urgent patch.
>
> Anil,
There are too many technical terms at the media subsystem, and sometimes
the same thing is refered differently at the documentation and on the ML
and IRC discussions.
Let's add a glossary to the uAPI documentation, in order to start using
a common vocabulary at the subsystem's discussion and to
When we added support for omap3, back in 2010, we added a new
type of V4L2 devices that aren't fully controlled via the V4L2
device node.
Yet, we have never clearly documented in the V4L2 specification
the differences between the two types.
Let's document them based on the the current
Right now, only kAPI documentation describes the device naming.
However, such description is needed at the uAPI too. Add it,
and describe how to get an unique identifier for a given device.
Acked-by: Hans Verkuil
Reviewed-by: Sakari Ailus
Signed-off-by: Mauro Carvalho Chehab
---
minor numbers use to range between 0 to 255, but that
was changed a long time ago. While it still applies when
CONFIG_VIDEO_FIXED_MINOR_RANGES, when the minor number is
dynamically allocated, this may not be true. In any case,
this is not relevant, as udev will take care of it.
So, remove this
Add a glossary of terms used within the media userspace API
documentation, as several concepts are complex enough to cause
misunderstandings.
Signed-off-by: Mauro Carvalho Chehab
---
.../userspace-api/media/glossary.rst | 216 ++
On Fri, 28 Aug 2020 at 01:57, Naresh Kamboju wrote:
>
> On Thu, 27 Aug 2020 at 21:03, Douglas Anderson wrote:
> >
> > The commit d05a7238fe1c ("mmc: sdhci-msm: Unconditionally call
> > dev_pm_opp_of_remove_table()") works fine in the case where there is
> > no OPP table. However, if there is an
On Fri, 10 Jul 2020, Lubomir Rintel wrote:
> This driver provides access to the EC RAM of said embedded controller
> attached to the I2C bus as well as optionally supporting its slightly weird
> power-off/restart protocol.
>
> A particular implementation of the EC firmware can be identified by a
On Fri, 21 Aug 2020 14:58:22 -0700
Atish Patra wrote:
> On Wed, Aug 19, 2020 at 8:20 PM Anshuman Khandual
> wrote:
> >
> >
> >
> > On 08/20/2020 12:48 AM, Atish Patra wrote:
> > > On Tue, Aug 18, 2020 at 8:19 PM Anshuman Khandual
> > > wrote:
> > >>
> > >>
> > >>
> > >> On 08/15/2020 03:17
On Fri, 10 Jul 2020, Lubomir Rintel wrote:
> Add binding document for the ENE KB3930 Embedded Controller.
>
> Signed-off-by: Lubomir Rintel
> Reviewed-by: Rob Herring
>
> ---
> Changes since v5:
> - s/a I2C bus/an I2C bus/
>
> Changes since v4:
> - Collected Rob's Reviewed-by
>
> Changes
On Fri, 28 Aug 2020 10:48:51 +0200
pet...@infradead.org wrote:
> On Thu, Aug 27, 2020 at 06:12:44PM +0200, Peter Zijlstra wrote:
> > struct kretprobe_instance {
> > union {
> > + /*
> > +* Dodgy as heck, this relies on not clobbering freelist::refs.
> > +*
Hi Rob,
On Tue, Aug 18, 2020 at 4:12 AM Rob Herring wrote:
> On Wed, 12 Aug 2020 15:52:21 +0800, Anson Huang wrote:
> > Convert the vf610 gpio binding to DT schema format using json-schema.
> >
> > Signed-off-by: Anson Huang
> > ---
> > changes since V1:
> > - fix reg property to pass
Hi Holger
On 8/7/20 5:03 PM, Holger Assmann wrote:
The KSZ9031 PHY skew timings for rxc/txc, originally set to achieve
the desired phase shift between clock- and data-signal, now trigger a
kernel warning when used in rgmii-id mode:
*-skew-ps values should be used only with phy-mode = "rgmii"
On Tue, 25 Aug 2020, Julien Thierry wrote:
> Now that the objtool_file can be obtained outside of the check function,
> orc generation builtin no longer requires check to explicitly call its
> orc related functions.
>
> Signed-off-by: Julien Thierry
Reviewed-by: Miroslav Benes
M
On Fri, Aug 28, 2020 at 3:25 AM Greg Kroah-Hartman
wrote:
>
> On Fri, Aug 28, 2020 at 02:59:25AM -0500, Qiushi Wu wrote:
> > Hi Greg,
> > Thanks for your response!
> >
> > > You responded in html format which got rejected by the public list,
> > > please resend in text-only and I will be glad to
On Fri, Aug 28, 2020 at 10:45:40AM +0200, Ulf Hansson wrote:
> On Tue, 25 Aug 2020 at 21:37, Krzysztof Kozlowski wrote:
> >
> > The i.MX 8 DTSes use two compatibles so update the binding to fix
> > dtbs_check warnings like:
> >
> > arch/arm64/boot/dts/freescale/imx8mn-evk.dt.yaml: mmc@30b4:
Hi Stefan,
On Thu, Aug 27, 2020 at 11:49:34AM +0200, Stefan Wahren wrote:
> Am 27.08.20 um 06:35 schrieb Hoegeun Kwon:
> > Hi Stefan,
> >
> > Thank you for your review.
> >
> >
> > On 8/26/20 7:04 PM, Stefan Wahren wrote:
> >> Hi Hoeguen,
> >>
> >> Am 21.08.20 um 09:10 schrieb Hoegeun Kwon:
> >>>
Em Thu, 27 Aug 2020 14:08:11 +0300
Sakari Ailus escreveu:
> > +MC-centric
> > + :term:`V4L2 hardware` that requires a :term:`MC API`.
> > +
> > + Such hardware have ``V4L2_CAP_IO_MC`` device_caps field set
> > + (see :ref:`VIDIOC_QUERYCAP`).
> > +
> > + See
On Fri, Aug 28, 2020 at 10:50:33AM +0200, Sylwester Nawrocki wrote:
> On 28.08.2020 08:48, Krzysztof Kozlowski wrote:
> >> diff --git a/sound/soc/codecs/wm8994.c b/sound/soc/codecs/wm8994.c
> >> index b3ba053..fc9ea19 100644
> >> --- a/sound/soc/codecs/wm8994.c
> >> +++ b/sound/soc/codecs/wm8994.c
On 8/27/20 10:33 PM, Bjorn Helgaas wrote:
> On Thu, Aug 27, 2020 at 01:17:48PM -0600, Alex Williamson wrote:
>> On Thu, 27 Aug 2020 13:31:38 -0500
>> Bjorn Helgaas wrote:
>>
>>> Re the subject line, this patch does a lot more than just "introduce a
>>> flag"; AFAICT it actually enables important
Hi Greg,
On Fri, Aug 28, 2020 at 09:43:59AM +0200, Greg Kroah-Hartman wrote:
> I still find this crazy that a whole separate driver is created just to
> read a single 32bit value.
>
> Why not put this logic in the driver that wants to read that value?
> That would be much simpler, smaller, and
On Fri, Aug 28, 2020 at 02:07:12PM +0800, Xianting Tian wrote:
> As the normal aio wait path(read_events() ->
> wait_event_interruptible_hrtimeout()) doesn't account iowait time, so use
> this patch to make it to account iowait time, which can truely reflect
> the system io situation when using a
On Fri, Aug 14, 2020 at 12:04 PM Thomas Preston
wrote:
> - Fix a typo where mcp23x17 configs are referred to as mcp23x16.
> - Fix precious range to include INTCAP{A,B}, which clear on read.
> - Fix precious range to include GPIOB, which clears on read.
> - Fix volatile range to include GPIOB, to
On Tue, Jul 28, 2020 at 10:43:59PM +1000, Alexey Kardashevskiy wrote:
> At the moment opening a serial device node (such as /dev/ttyS3)
> succeeds even if there is no actual serial device behind it.
> Reading/writing/ioctls (most) expectantly fail as the uart port is not
> initialized (the type is
Commit cc9aec03e58f ("x86/numa_emulation: Introduce uniform split
capability") uses "-1" as the starting node ID, which causes the
strange kernel log as following, when "numa=fake=32G" is added to the
kernel command line.
Faking node -1 at [mem 0x-0x000893ff] (35136MB)
On Fri, 28 Aug 2020 03:00:59 +0900
Masami Hiramatsu wrote:
> On Thu, 27 Aug 2020 18:12:40 +0200
> Peter Zijlstra wrote:
>
> > +static void invalidate_rp_inst(struct task_struct *t, struct kretprobe *rp)
> > +{
> > + struct invl_rp_ipi iri = {
> > + .task = t,
> > + .rp =
On 2020/8/28 8:35, Dave Chinner wrote:
> On Thu, Aug 27, 2020 at 05:58:07PM +0800, Li, Hao wrote:
>> On 2020/8/27 14:37, Dave Chinner wrote:
>>> On Fri, Aug 21, 2020 at 09:59:53AM +0800, Hao Li wrote:
Currently, DCACHE_REFERENCED prevents the dentry with DCACHE_DONTCACHE
set from being
On Fri, Aug 28, 2020 at 11:20:58AM +0300, Andy Shevchenko wrote:
> On Thu, Aug 27, 2020 at 11:25 PM Krzysztof Kozlowski wrote:
> >
> > Hartmut Knaack was an active reviewer and contributor to the IIO
> > subsystem and drivers. However last message on LKML from him was sent
> > in October 2015.
>
From: Vincent Donnefort
rq->cpu_capacity is a key element in several scheduler parts, such as EAS
task placement and load balancing. Tracking this value enables testing
and/or debugging by a toolkit.
Signed-off-by: Vincent Donnefort
diff --git a/include/linux/sched.h b/include/linux/sched.h
Hi Mathieu and CS maintainers,
> Hi Liu,
>
> On Wed, Aug 19, 2020 at 04:06:37PM +0800, Qi Liu wrote:
> > When too much trace information is generated on-chip, the ETM will
> > overflow, and cause data loss. This is a common phenomenon on ETM
> > devices.
> >
> > But sometimes we do not want to
Ondrej Zary writes:
> On Thursday 27 August 2020 09:49:12 Kalle Valo wrote:
>> Ondrej Zary writes:
>>
>> > On Monday 17 August 2020 20:27:06 Jesse Brandeburg wrote:
>> >> On Mon, 17 Aug 2020 16:27:01 +0300
>> >> Kalle Valo wrote:
>> >>
>> >> > I was surprised to see that someone was using
On Fri, Aug 28, 2020 at 03:07:09AM +0200, Ahmed S. Darwish wrote:
> +#define __SEQ_RT IS_ENABLED(CONFIG_PREEMPT_RT)
> +
> +SEQCOUNT_LOCKTYPE(raw_spinlock, raw_spinlock_t, false,s->lock,
> raw_spin, raw_spin_lock(s->lock))
> +SEQCOUNT_LOCKTYPE(spinlock, spinlock_t,
On Fri, Aug 28, 2020 at 10:27:54AM +0200, pet...@infradead.org wrote:
> On Fri, Aug 28, 2020 at 03:07:07AM +0200, Ahmed S. Darwish wrote:
> > Differentiate the first group by using "__seqcount_t_" as prefix. This
> > also conforms with the rest of seqlock.h naming conventions.
>
> > #define
On Fri, Aug 28, 2020 at 03:07:09AM +0200, Ahmed S. Darwish wrote:
> +/*
> + * Automatically disable preemption for seqcount_LOCKTYPE_t writers, if the
> + * associated lock does not implicitly disable preemption.
> + *
> + * Don't do it for PREEMPT_RT. Check __SEQ_LOCK().
> + */
> +#define
Good morning Linus,
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-fixes-5.9
for you to fetch changes up to
On Fri 28-08-20 14:07:12, Xianting Tian wrote:
> As the normal aio wait path(read_events() ->
> wait_event_interruptible_hrtimeout()) doesn't account iowait time, so use
> this patch to make it to account iowait time, which can truely reflect
> the system io situation when using a tool like 'top'.
The nested VMX controls MSRs can be initialized by the global capability
values stored in vmcs_config.
Signed-off-by: Chenyi Qiang
Reviewed-by: Xiaoyao Li
---
arch/x86/kvm/vmx/vmx.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/x86/kvm/vmx/vmx.c
When setting the nested VMX MSRs, verify it with the values in
vmcs_config.nested_vmx_msrs, which reflects the global capability of
VMX controls MSRs.
Signed-off-by: Chenyi Qiang
---
arch/x86/kvm/vmx/nested.c | 71 ---
1 file changed, 51 insertions(+), 20
A minor fix for the update of VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL field
in exit_ctls_high.
Fixes: 03a8871add95 ("KVM: nVMX: Expose load IA32_PERF_GLOBAL_CTRL
VM-{Entry,Exit} control")
Signed-off-by: Chenyi Qiang
Reviewed-by: Xiaoyao Li
---
arch/x86/kvm/vmx/nested.c | 2 +-
1 file changed, 1
Update the fields (i.e. VM_{ENTRY_LOAD, EXIT_CLEAR}_BNDCFGS and
VM_{ENTRY, EXIT}_LOAD_IA32_PERF_GLOBAL_CTRL) in
nested MSR_IA32_VMX_TRUE_{ENTRY, EXIT}_CTLS according to guest CPUID
when user space initializes the features MSRs. Regardless of the order
of SET_CPUID and SET_MSRS from the user space,
KVM supports the nested VM_{EXIT, ENTRY}_LOAD_IA32_PERF_GLOBAL_CTRL and
VM_{ENTRY_LOAD, EXIT_CLEAR}_BNDCFGS, but they doesn't expose during
the setup of nested VMX controls MSR.
Signed-off-by: Chenyi Qiang
---
arch/x86/kvm/vmx/nested.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
The first three patches fix a issue for the nested VMX controls MSRs. The
issue happens when I use QEMU to run nested VM. The VM_{ENTRY,
EXIT}_LOAD_IA32_PERF_GLOBAL_CTRL and VM_{ENTRY_LOAD, EXIT_CLEAR}_BNDCFGS
in L1 MSR_IA32_VMX_TRUE_{ENTRY, EXIT}_CTLS MSR are always cleared
regardless of whether
__chk_user_ptr() & __chk_io_ptr() are dummy extern functions which
only exist to enforce the typechecking of __user or __iomem pointers
in macros when using sparse.
This typechecking is done by inserting a call to these functions.
But the presence of these calls can inhibit some simplifications
On Thu, 27 Aug 2020 at 17:22, Veerabhadrarao Badiganti
wrote:
>
> On sc7180 target, issues are observed with HS400 mode due to a
> hardware limitation. If sdcc clock is dynamically gated and ungated,
> the very next command is failing with command CRC/timeout errors.
>
> To mitigate this issue,
On 28.08.2020 08:48, Krzysztof Kozlowski wrote:
>> diff --git a/sound/soc/codecs/wm8994.c b/sound/soc/codecs/wm8994.c
>> index b3ba053..fc9ea19 100644
>> --- a/sound/soc/codecs/wm8994.c
>> +++ b/sound/soc/codecs/wm8994.c
>> @@ -3514,6 +3514,8 @@ int wm8994_mic_detect(struct snd_soc_component
>>
When testing with !OF, the build system reports:
>> drivers/mfd/khadas-mcu.c:125:34: warning: unused variable
>> 'khadas_mcu_of_match' [-Wunused-const-variable]
static const struct of_device_id khadas_mcu_of_match[] = {
^
Cc: Neil Armstrong
Reported-by:
Hi, Pei,
On Thu, Aug 27, 2020 at 4:05 PM Tiezhu Yang wrote:
>
> According to the user's manual chapter 8.2.1 of Loongson 3A2000 CPU [1]
> and 3A3000 CPU [2], we should take some event IDs such as 274, 358, 359
> and 360 as valid in the check condition, otherwise they are recognized
> as "not
On Thu, Aug 27, 2020 at 06:12:44PM +0200, Peter Zijlstra wrote:
> struct kretprobe_instance {
> union {
> + /*
> + * Dodgy as heck, this relies on not clobbering freelist::refs.
> + * llist: only clobbers freelist::next.
> + * rcu: clobbers
On Tue, 25 Aug 2020 at 21:37, Krzysztof Kozlowski wrote:
>
> The i.MX 8 DTSes use two compatibles so update the binding to fix
> dtbs_check warnings like:
>
> arch/arm64/boot/dts/freescale/imx8mn-evk.dt.yaml: mmc@30b4:
> compatible: ['fsl,imx8mn-usdhc', 'fsl,imx7d-usdhc'] is too long
>
On Thu, 27 Aug 2020 at 19:21, Sowjanya Komatineni
wrote:
>
> Tegra210/Tegra186/Tegra194 has incorrectly enabled
> SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK from the beginning of their support.
>
> Tegra210 and later SDMMC hardware default uses sdmmc_legacy_tm (TMCLK)
> all the time for hardware data
On Mon, 24 Aug 2020 at 19:20, Alex Dewar wrote:
>
> There seems to be no particular reason to only test for ARM, so allow
> for build-testing on other platforms to increase coverage.
Agree.
>
> Build-tested on x86 with allyesconfig.
>
> Signed-off-by: Alex Dewar
I have applied this for next,
On Fri, 28 Aug 2020 at 08:08, 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.
>
>
On Fri, Aug 28, 2020 at 03:00:59AM +0900, Masami Hiramatsu wrote:
> On Thu, 27 Aug 2020 18:12:40 +0200
> Peter Zijlstra wrote:
>
> > +static void invalidate_rp_inst(struct task_struct *t, struct kretprobe *rp)
> > +{
> > + struct invl_rp_ipi iri = {
> > + .task = t,
> > +
On Mon, 24 Aug 2020 at 03:04, Tian Tao wrote:
>
> Use kobj_to_dev() instead of container_of()
>
> Signed-off-by: Tian Tao
Applied for next, thanks!
Kind regards
Uffe
> ---
> drivers/mmc/core/sd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/core/sd.c
On Tue, 25 Aug 2020 at 19:00, Faiz Abbas wrote:
>
> There is a one time delay because of a card detect debounce timer in the
> controller IP. This timer runs as soon as power is applied to the module
> regardless of whether a card is present or not and any writes to
> SDHCI_POWER_ON will return 0
On Fri, 28 Aug 2020 at 07:09, Viresh Kumar wrote:
>
> On 27-08-20, 08:33, Douglas Anderson wrote:
> > The commit d05a7238fe1c ("mmc: sdhci-msm: Unconditionally call
> > dev_pm_opp_of_remove_table()") works fine in the case where there is
> > no OPP table. However, if there is an OPP table then
>
On Wed, 26 Aug 2020 at 15:01, Lars Povlsen wrote:
>
> This changes the "mmc0@60080" node name to "mmc@60080" to be
> compliant with devicetree naming rules.
>
> Signed-off-by: Lars Povlsen
Applied, but squashing this into the original commit, thanks!
Kind regards
Uffe
> ---
>
On Thu, 27 Aug 2020 at 10:23, Matthias Brugger wrote:
>
>
>
> On 24/08/2020 11:50, Ulf Hansson wrote:
> > On Fri, 14 Aug 2020 at 03:44, Wenbin Mei wrote:
> >>
> >> This commit adds reset node for mmc device.
> >>
> >> Cc: # v5.4+
> >> Fixes: 966580ad236e ("mmc: mediatek: add support for MT7622
No users left in the kernel, it can be removed.
Signed-off-by: Peter Ujfalusi
---
include/linux/dmaengine.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
index 6fbd5c99e30c..011371b7f081 100644
--- a/include/linux/dmaengine.h
+++
Hi Sakari,
On Wed, Aug 26, 2020 at 02:54:27PM +0300, Sakari Ailus wrote:
> Enable drivers to tell ACPI that there's no need to power on a device for
> probe. Drivers should still perform this by themselves if there's a need
> to. In some cases powering on the device during probe is undesirable,
On Fri, Aug 28, 2020 at 10:30:22AM +0200, pet...@infradead.org wrote:
> On Fri, Aug 28, 2020 at 03:07:08AM +0200, Ahmed S. Darwish wrote:
> > #define __read_seqcount_begin(s) \
> > +({ \
> > +
Hi Lucas,
I was wondering about the plans to merge this series. Since not many
people can test it properly due to lack of DCSS support in the upstream
NWL driver (which I heard it's coming soon) and a completely nonexistent
HDP driver, are we going to take a leap of faith and merge it as is? Or
Em Thu, 27 Aug 2020 13:36:28 -0700
Steve deRosier escreveu:
> Hi Mauro,
>
> On Thu, Aug 27, 2020 at 10:42 AM Mauro Carvalho Chehab
> wrote:
> >
> > Em Thu, 27 Aug 2020 08:48:30 -0700
> > Steve deRosier escreveu:
> >
> > > On Tue, Aug 25, 2020 at 10:49 PM Mauro Carvalho Chehab
> > > wrote:
On Fri, Aug 28, 2020 at 03:07:08AM +0200, Ahmed S. Darwish wrote:
> #define __read_seqcount_begin(s) \
> +({ \
> + unsigned seq; \
> +
28.08.2020 04:47, Chanwoo Choi пишет:
> Hi,
...
>> Hence the NULL-checking is unnecessary.
>>
>> When I first encountered the of_device_get_match_data(), I was also
>> thinking that adding the NULL-checks is a good idea, but later on
>> somebody pointed out to me (maybe Thierry) that it's
On Fri, Aug 28, 2020 at 03:07:07AM +0200, Ahmed S. Darwish wrote:
> Differentiate the first group by using "__seqcount_t_" as prefix. This
> also conforms with the rest of seqlock.h naming conventions.
> #define __seqprop_case(s, locktype, prop)\
>
On 28.08.20 09:47, Vignesh Raghavendra wrote:
> Buffers need to mapped to DMA channel's device pointer instead of SPI
> controller's device pointer as its system DMA that actually does data
> transfer.
> Data inconsistencies have been reported when reading from flash
> without this fix.
>
>
On Fri, Aug 28, 2020 at 02:59:25AM -0500, Qiushi Wu wrote:
> Hi Greg,
> Thanks for your response!
>
> > You responded in html format which got rejected by the public list,
> > please resend in text-only and I will be glad to reply.
> >
> Sorry about this!
>
>
> > > 1. Linux allows anyone to
801 - 900 of 1034 matches
Mail list logo
