On Sun, Oct 04, 2020 at 12:08:47AM -0700, Nathan Chancellor wrote:
> On Fri, Oct 02, 2020 at 03:15:24PM -0700, Kees Cook wrote:
> > Instead of doing if/endif blocks with cc-option calls in the UBSAN
> > Makefile, move all the tests into Kconfig and use the Makefile to
> > collect the results.
> >
Chris Chiu writes:
> On Mon, Oct 5, 2020 at 11:01 PM Chris Chiu wrote:
>
> From: Chris Chiu
>
> The legacy_httxpowerdiff in rtl8192se is pretty much the same as
> the legacy_ht_txpowerdiff for other chips. Use the same name to
> keep the consistency.
>
>
On Sun, Oct 04, 2020 at 12:16:14AM -0700, Nathan Chancellor wrote:
> On Fri, Oct 02, 2020 at 03:15:26PM -0700, Kees Cook wrote:
> > Clang handles 'maybe-uninitialized' better in the face of using UBSAN,
> > so do not make this universally disabled for UBSAN builds.
> >
> > Signed-off-by: Kees
On Mon, Oct 05, 2020 at 10:03:13PM -0700, Josh Triplett wrote:
> On Mon, Oct 05, 2020 at 11:18:34PM -0400, Theodore Y. Ts'o wrote:
> > What Josh is proposing I'm pretty sure would also break "e2fsck -E
> > unshare_blocks", so that's another reason not to accept this as a
> > valid format change.
>
Hi all,
FIXME: Add owner of second tree to To:
Add author(s)/SOB of conflicting commits.
Today's linux-next merge of the devicetree tree got a conflict in:
Documentation/devicetree/bindings/arm/samsung/sysreg.yaml
between commit:
18394297562a ("dt-bindings: mfd: syscon: Merge
On Fri, Oct 02, 2020 at 05:23:03PM +0200, Christian Eggers wrote:
> According to the "VFxxx Controller Reference Manual" (and the comment
> block starting at line 97), Vybrid requires writing a one for clearing
> an interrupt flag. Syncing the method for clearing I2SR_IIF in
> i2c_imx_isr().
>
>
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/x86/kernel/setup.c
between commit:
f47e22d65d08 ("dma-mapping: split ")
from the dma-mapping tree and commit:
a945c8345ec0 ("static_call: Allow early init")
from the tip tree.
I fixed it up (see below) and can
Martin Ågren writes:
> Minor comments follow.
> ...
> s/used // (without 'g' flag!)
Thanks.
--
Dear,
Did you receive the message i sent to you?
Regards,
Peter Joe
On Fri, Oct 02, 2020 at 01:17:00PM -0700, Si-Wei Liu wrote:
> + Eli.
>
> On Thu, Oct 1, 2020 at 2:02 PM Si-Wei Liu wrote:
> >
> > A VM with mlx5 vDPA has below warnings while being reset:
> >
> > vhost VQ 0 ring restore failed: -1: Resource temporarily unavailable (11)
> > vhost VQ 1 ring
On Tue, Oct 6, 2020 at 1:41 AM Jason Gunthorpe wrote:
>
> On Tue, Oct 06, 2020 at 12:43:31AM +0200, Daniel Vetter wrote:
>
> > > iow I think I can outright delete the frame vector stuff.
> >
> > Ok this doesn't work, because dma_mmap always uses a remap_pfn_range,
> > which is a VM_IO | VM_PFNMAP
Hi,
I would like to verify this series along with the other series "PCI:
dwc: fix two MSI issues" on Tegra194. I tried to apply these series on
both linux-next and Lorenzo's pci/dwc branches but there seem to be non
trivial conflicts. Could you please tell me which branch I can use and
apply
On 09/30/2020 04:31 PM, Ard Biesheuvel wrote:
> On Wed, 30 Sep 2020 at 10:03, Anshuman Khandual
> wrote:
>>
>>
>> On 09/29/2020 08:52 PM, Will Deacon wrote:
>>> On Tue, Sep 29, 2020 at 01:34:24PM +0530, Anshuman Khandual wrote:
On 09/29/2020 02:05 AM, Will Deacon wrote:
> On
Hi Geert,
On Fri, Sep 25, 2020 at 2:48 PM Geert Uytterhoeven wrote:
>
> Hi Mateusz,
>
> On Wed, Sep 23, 2020 at 12:09 PM Mateusz Holenko
> wrote:
> > From: Pawel Czarnecki
> >
> > Add documentation for LiteX SoC Controller bindings.
> >
> > Signed-off-by: Pawel Czarnecki
> > Signed-off-by:
Hi,
On 10/6/20 4:44 AM, Anant Thazhemadam wrote:
On 05-10-2020 14:48, Hans de Goede wrote:
To fully fix the memleak you also need to add a kfree_skb(h5->rx_skb);
call to the end of h5_serdev_remove(), because in the hu->serdev case
that is where the h5 struct will be free-ed (it is free-ed
Currently driver only retries to download FW if FW downloading
is failed. Sometimes observed command timeout for version request
command, if this happen on some platforms during boot time, then
a reboot is needed to turn ON BT. Instead to avoid a reboot, now
extended retry logic for version
Hi Jonathan,
thanks for your review!
On Wed, Sep 23, 2020 at 1:58 PM Jonathan Cameron
wrote:
>
> On Wed, 23 Sep 2020 12:09:06 +0200
> Mateusz Holenko wrote:
>
> > From: Pawel Czarnecki
> >
> > This commit adds driver for the FPGA-based LiteX SoC
> > Controller from LiteX SoC builder.
> >
> >
Hello Jeff,
Am Dienstag, 6. Oktober 2020, 04:17:29 CEST schrieb Jeff LaBundy:
> Hi Alexander,
>
> On Mon, Oct 05, 2020 at 10:34:42PM +0200, Alexander Dahl wrote:
> > The node names for devices using the pwm-leds driver follow a certain
> > naming scheme (now). Parent node name is not enforced,
On 09/30/2020 01:32 PM, Anshuman Khandual wrote:
> But if __is_lm_address() checks against the effective linear range instead
> i.e [_PAGE_OFFSET(vabits_actual)..(PAGE_END - 1)], it can be used for hot
> plug physical range check there after. Perhaps something like this, though
> not tested
Hi Linus,
Daniel queued these up last week and I took a long weekend so didn't
get them out, but fixing the OOB access on get font seems like
something we should land and it's cc'ed stable as well. The other big
change is a partial revert for a regression on android on the clcd
fbdev driver, and
On Tue, 6 Oct 2020 11:56:34 +0530 Vidya Sagar wrote:
>
>
> Hi,
Hi,
> I would like to verify this series along with the other series "PCI:
> dwc: fix two MSI issues" on Tegra194. I tried to apply these series on
> both linux-next and Lorenzo's pci/dwc branches but there seem to be non
>
DeepSleep is a UFS v3.1 feature that achieves the lowest power consumption
of the device, apart from power off.
In DeepSleep mode, no commands are accepted, and the only way to exit is
using a hardware reset or power cycle.
This patch assumes that if a power cycle was an option, then power off
> -Original Message-
> From: Namhyung Kim [mailto:namhy...@kernel.org]
> Sent: Tuesday, October 6, 2020 2:26 PM
> To: Song Bao Hua (Barry Song)
> Cc: Andi Kleen ; linux-kernel@vger.kernel.org; Linuxarm
> ; Peter Zijlstra ; Ingo Molnar
> ; Arnaldo Carvalho de Melo ; Mark
> Rutland ;
On Wed, Sep 30, 2020 at 9:48 PM Pavel Machek wrote:
>
> Hi!
>
> > +static int iei_wt61p803_puzzle_led_brightness_set_blocking(struct
> > led_classdev *cdev,
> > + enum led_brightness brightness)
> > +{
> > + struct iei_wt61p803_puzzle_led *priv =
> >
Em Mon, 5 Oct 2020 10:17:36 -0600
Jonathan Corbet escreveu:
> On Sun, 4 Oct 2020 10:02:03 +0200
> Mauro Carvalho Chehab wrote:
>
> > When kernel-doc is called via kerneldoc.py, there's no need to
> > auto-detect the Sphinx version, as the Sphinx module already
> > knows it. So, add an
On Tue, Oct 06, 2020 at 02:22:15AM -0400, Michael S. Tsirkin wrote:
Acked-by: Eli Cohen
> On Fri, Oct 02, 2020 at 01:17:00PM -0700, Si-Wei Liu wrote:
> > + Eli.
> >
> > On Thu, Oct 1, 2020 at 2:02 PM Si-Wei Liu wrote:
> > >
> > > A VM with mlx5 vDPA has below warnings while being reset:
> > >
On 5/10/20 6:46 pm, Bean Huo wrote:
> Hi Adrian
>
> thanks for submitting your patch. this patch looks fine to me.
>
>
> do you think the new deepsleep PM level aslo should be added in
> "rpm_lvl" description in Documentation/ABI/testing/sysfs-driver-ufs?
Thanks for looking at this. Yes, I
Hi all,
I'm running a single-CPU Linux VM on Hyper-V. The Linux kernel is v5.9-rc7
and I have CONFIG_NR_CPUS=256.
The Hyper-V Host (Version 17763-10.0-1-0.1457) provides a guest firmware,
which always reports 128 Local APIC entries in the ACPI MADT table. Here
only the first Local APIC entry's
Use per_cpu_ptr_to_phys() instead of virt_to_phys() for per-cpu
address conversion.
In xen_starting_cpu(), per-cpu xen_vcpu_info address is converted
to gfn by virt_to_gfn() macro. However, since the virt_to_gfn(v)
assumes the given virtual address is in linear mapped kernel memory
area, it can
> -Original Message-
> From: Jiri Olsa [mailto:jo...@redhat.com]
> Sent: Friday, October 2, 2020 10:00 PM
> To: Namhyung Kim ; liwei (GF)
>
> Cc: Mark Rutland ; Andi Kleen ;
> Alexander Shishkin ; Alexey Budankov
> ; Adrian Hunter
> ; Arnaldo Carvalho de Melo ;
> linux-kernel ; Peter
On Fri, 2020-09-25 at 16:04 +0200, Matthias Brugger wrote:
>
> On 25/09/2020 12:06, Weiyi Lu wrote:
> > On Thu, 2020-09-10 at 19:28 +0200, 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
On Mon, Oct 5, 2020 at 10:47 PM Alexander Mikhalitsyn
wrote:
>
> Hi Amir,
>
> On Mon, 5 Oct 2020 10:56:50 +0300
> Amir Goldstein wrote:
>
> > On Sun, Oct 4, 2020 at 10:25 PM Alexander Mikhalitsyn
> > wrote:
> > >
> > > Some time ago we discussed about the problem of Checkpoint-Restoring
> > >
On Mon, 05 Oct 2020, Michael Brunner wrote:
> On Fri, 2020-10-02 at 08:01 +0100, Lee Jones wrote:
> > On Thu, 01 Oct 2020, Michael Brunner wrote:
> >
> > > The Intel 0-DAY CI Kernel Test Service reports an unused variable
> > > warning when compiling with clang for PowerPC:
> > >
> > > > >
On Tue, 06 Oct 2020, Kalle Valo wrote:
> Lee Jones writes:
>
> > On Thu, 10 Sep 2020, Lee Jones wrote:
> >
> >> This is a rebased/re-worked set of patches which have been
> >> previously posted to the mailing list(s).
> >>
> >> This set is part of a larger effort attempting to clean-up W=1
>
On Mon, Oct 05, 2020 at 11:49:10AM -0700, Paul E. McKenney wrote:
> On Mon, Oct 05, 2020 at 08:38:42PM +0200, Sedat Dilek wrote:
> > On Mon, Oct 5, 2020 at 8:29 PM 'Nick Desaulniers' via Clang Built
> > Linux wrote:
> > >
> > > On Fri, Oct 2, 2020 at 1:51 PM Paul E. McKenney
> > > wrote:
> > >
On Mon, 05 Oct 2020, Rob Herring wrote:
> In order to add meta-schema checks for additional/unevaluatedProperties
> being present, all schema need to make this explicit. As common/shared
> schema are included by other schemas, they should always allow for
> additionalProperties.
Acked-by: Lee
On (20/10/05 20:35), Guenter Roeck wrote:
> On a side note, I don't see the problem presumably fixed with this
> patch in any of my tests.
Hmm. This is rather interesting. Empty console= certainly oops-es my laptop,
but not the cros board I just tested this on. Do we carry around any chromeos
On Mon, 05 Oct 2020, Rob Herring wrote:
> In cases where we don't reference another schema, 'additionalProperties'
> can be used instead. This is preferred for now as 'unevaluatedProperties'
> support isn't implemented yet.
>
> In a few cases, this means adding some missing property definitions
On Fri, 02 Oct 2020, Rob Herring wrote:
> Another round of wack-a-mole. The json-schema default is additional
> unknown properties are allowed, but for DT all properties should be
> defined.
Acked-by: Lee Jones
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open
Hi Geert,
On Fri, Sep 25, 2020 at 3:16 PM Geert Uytterhoeven wrote:
>
> Hi Mateusz,
>
> On Wed, Sep 23, 2020 at 12:10 PM Mateusz Holenko
> wrote:
> > From: Filip Kokosinski
> >
> > Add documentation for LiteUART devicetree bindings.
> >
> > Signed-off-by: Filip Kokosinski
> > Signed-off-by:
On Mon, Oct 05, 2020 at 02:07:23PM +0200, Wilken Gottwalt wrote:
> On Mon, 5 Oct 2020 18:36:36 +0700 Lars Melin wrote:
> > On 10/5/2020 18:06, Johan Hovold wrote:
> > > Do you remember the interface layout and why you blacklisted interface
> > > 1?
> > It is very likely that Cellient has
On Thu, 1 Oct 2020 21:07:51 -0700
Guenter Roeck wrote:
> On 10/1/20 3:22 PM, Andreas Kemnade wrote:
> > On Wed, 30 Sep 2020 22:00:09 +0200
> > Arnd Bergmann wrote:
> >
> >> On Wed, Sep 30, 2020 at 6:44 PM Guenter Roeck wrote:
> >>>
> >>> On Wed, Sep 30, 2020 at 10:54:42AM +0200, Andreas
On 05/10/2020 21:47:01-0400, Peter Geis wrote:
> On Mon, Oct 5, 2020 at 6:29 PM Alexandre Belloni
> wrote:
> >
> > On 05/10/2020 09:13:08-0400, Peter Geis wrote:
> > > Good Morning,
> > >
> > > While testing suspend to ram on the Ouya, I encountered an interesting
> > > issue with the
On 24-09-20, 13:30, Ionela Voinescu wrote:
> Compared to other arch_* functions, arch_set_freq_scale() has an atypical
> weak definition that can be replaced by a strong architecture specific
> implementation.
>
> The more typical support for architectural functions involves defining
> an empty
Hi Mateusz,
On Tue, Oct 6, 2020 at 9:01 AM Mateusz Holenko wrote:
> On Fri, Sep 25, 2020 at 3:16 PM Geert Uytterhoeven
> wrote:
> > On Wed, Sep 23, 2020 at 12:10 PM Mateusz Holenko
> > wrote:
> > > From: Filip Kokosinski
> > >
> > > Add documentation for LiteUART devicetree bindings.
> > >
Hi Alain
On 8/30/20 9:57 PM, Alain Volmat wrote:
> Update the sti platform LL_UART support to rely on
> CONFIG_DEBUG_UART_PHYS and CONFIG_DEBUG_UART_VIRT from Kconfig
>
> Signed-off-by: Alain Volmat
> ---
> arch/arm/Kconfig.debug | 23 ---
>
On Mon, Sep 28, 2020 at 03:17:34PM -0700, David Miller wrote:
> From: Christoph Hellwig
> Date: Sat, 26 Sep 2020 09:00:49 +0200
>
> > ->sendpage is only called from generic_splice_sendpage. The only user of
> > generic_splice_sendpage is socket_file_ops, which is also the only
> > instance that
On Tue, 6 Oct 2020 at 06:12, wrote:
>
> The order in which 'users' counter is decremented vs calling drivers'
> close() method is implementation specific, and we should not rely on
> it. Let's introduce driver private flag and use it to signal ISR
> to exit when device is being closed.
>
> This
Hi Alain
On 8/30/20 9:57 PM, Alain Volmat wrote:
> Add the entry for the STiH418 SBC UART0 low level uart.
>
> Signed-off-by: Alain Volmat
> ---
> arch/arm/Kconfig.debug | 19 +--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/Kconfig.debug
Lee Jones writes:
> On Tue, 06 Oct 2020, Kalle Valo wrote:
>
>> Lee Jones writes:
>>
>> > On Thu, 10 Sep 2020, Lee Jones wrote:
>> >
>> >> This is a rebased/re-worked set of patches which have been
>> >> previously posted to the mailing list(s).
>> >>
>> >> This set is part of a larger effort
On 24-09-20, 13:30, Ionela Voinescu wrote:
> big.LITTLE switching complicates the setting of a correct cpufreq-based
> frequency invariance scale factor due to (as observed in
> drivers/cpufreq/vexpress-spc-cpufreq.c):
> - Incorrect current and maximum frequencies as a result of the
>exposure
Towards removing the mode specific @dax_kmem_res attribute from the
generic 'struct dev_dax', and preparing for multi-range support, move
resource tracking to driver data. The memory for the resource name
needs to have its own lifetime separate from the device bind lifetime
for cases where the
Make the device-dax 'size' attribute writable to allow capacity to be
split between multiple instances in a region. The intended consumers of
this capability are users that want to split a scarce memory resource
between device-dax and System-RAM access, or users that want to have
multiple
Use sysfs_streq() in device_find_child_by_name() to allow it to use a
sysfs input string that might contain a trailing newline.
The other "device by name" interfaces,
{bus,driver,class}_find_device_by_name(), already account for sysfs
strings.
Link:
In preparation for introducing seed devices the dax-bus core needs to be
able to intercept ->probe() and ->remove() operations. Towards that end
arrange for the bus and drivers to switch from raw 'struct device'
driver operations to 'struct dev_dax' typed operations.
Cc: Jason Yan
Cc: Vishal
The 'struct resource' in 'struct dev_pagemap' is only used for holding
resource span information. The other fields, 'name', 'flags', 'desc',
'parent', 'sibling', and 'child' are all unused wasted space.
This is in preparation for introducing a multi-range extension of
devm_memremap_pages().
The
Towards removing the mode specific @dax_kmem_res attribute from the
generic 'struct dev_dax', and preparing for multi-range support, teach
the driver to calculate the hotplug range from the device range. The
hotplug range is the trivially calculated memory-block-size aligned
version of the device
Changes since v5 [1]:
- (David) Introduce range_len() to include/linux/range.h immediately in
"device-dax: make pgmap optional for instance creation" rather than
wait until "mm/memremap_pages: convert to 'struct range'" to move it.
- (David) David points out that release_mem_region() can not
;In preparation for a facility that enables dax regions to be sub-divided,
introduce infrastructure to track and allocate region capacity.
The new dax_region/available_size attribute is only enabled for volatile
hmem devices, not pmem devices that are defined by nvdimm namespace
boundaries. This
Add a seed device concept for dynamic dax regions to be able to split the
region amongst multiple sub-instances. The seed device, similar to
libnvdimm seed devices, is a device that starts with zero capacity
allocated and unbound to a driver. In contrast to libnvdimm seed devices
explicit
The passed in dev_pagemap is only required in the pmem case as the
libnvdimm core may have reserved a vmem_altmap for dev_memremap_pages() to
place the memmap in pmem directly. In the hmem case there is no agent
reserving an altmap so it can all be handled by a core internal default.
Pass the
Break the requirement that device-dax instances are physically contiguous.
With this constraint removed it allows fragmented available capacity to
be fully allocated.
This capability is useful to mitigate the "noisy neighbor" problem with
memory-side-cache management for virtual machines, or any
In support of device-dax growing the ability to front physically
dis-contiguous ranges of memory, update devm_memremap_pages() to track
multiple ranges with a single reference counter and devm instance.
Convert all [devm_]memremap_pages() users to specify the number of
ranges they are mapping in
On Tue, 6 Oct 2020 at 06:27, Yong Wu wrote:
>
> On Fri, 2020-10-02 at 13:08 +0200, Krzysztof Kozlowski wrote:
> > On Wed, Sep 30, 2020 at 03:06:25PM +0800, Yong Wu wrote:
> > > Convert MediaTek SMI to DT schema.
> > >
> > > Signed-off-by: Yong Wu
> > > ---
> > > .../mediatek,smi-common.txt
On Wed, Sep 30, 2020 at 03:06:41PM +0800, Yong Wu wrote:
> After extending v7s, our pagetable already support iova reach
> 16GB(34bit). the master got the iova via dma_alloc_attrs may reach
> 34bits, but its HW register still is 32bit. then how to set the
> bit32/bit33 iova? this depend on a SMI
On Tue, 6 Oct 2020 07:45:10 +0200
Heiner Kallweit wrote:
>
> On 05.10.2020 18:00, Florian Fainelli wrote:
> >
> >
> > On 10/5/2020 8:54 AM, Heiner Kallweit wrote:
> >> On 05.10.2020 17:41, Florian Fainelli wrote:
> >>>
> >>>
> >>> On 10/5/2020 1:53 AM, Jisheng Zhang wrote:
> On Wed,
On Tue, Oct 06, 2020 at 12:26:45PM +0800, Yong Wu wrote:
> Hi Krzysztof,
>
> On Fri, 2020-10-02 at 13:10 +0200, Krzysztof Kozlowski wrote:
> > On Wed, Sep 30, 2020 at 03:06:29PM +0800, Yong Wu wrote:
> > > This patch adds decriptions for mt8192 IOMMU and SMI.
> > >
> > > mt8192 also is MTK IOMMU
Hi Geert,
On Fri, Sep 25, 2020 at 3:41 PM Geert Uytterhoeven wrote:
>
> Hi Mateusz,
>
> On Wed, Sep 23, 2020 at 12:12 PM Mateusz Holenko
> wrote:
> > From: Filip Kokosinski
> >
> > This commit adds driver for the FPGA-based LiteUART serial controller
> > from LiteX SoC builder.
> >
> > The
On Mon, Oct 05, 2020 at 11:19:02PM +, Harley A.W. Lorenzo wrote:
> On Monday, October 5, 2020 5:31 PM, Sudip Mukherjee
> wrote:
>
> > find_tt() can return NULL or the error value in ERR_PTR() and
> > dereferencing the return value without checking for the error can
> > lead to a possible
On 24-09-20, 10:53, Nicola Mazzucato wrote:
> I am seeking some feedback/comments on the following approach.
>
> Intro:
> Info of performance depency for cpus will be beneficial for systems
> where f/w description of the CPU performance control domain is different
> from the clock domain, e.g.
This patch is against to mkp's 5.10/scsi-staging.
1. fix warning: right shift count >= width of type.
---
On Mon, Oct 05, 2020 at 10:35:43AM -0400, Jonathan Marek wrote:
> The cache synchronization doesn't have anything to do with IOMMU (for
> example: cache synchronization would be useful in cases where drm/msm
> doesn't use IOMMU).
It has to do with doing DMA. And we have two frameworks for doing
a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Jeremy-Linton/arm64-bti-fix-BTI-to-handle-local-indirect-branches/20201006-021958
base: https://git.kernel.org/pub/scm/linux
On Mon, Oct 05, 2020 at 04:57:20PM +0200, Peter Zijlstra wrote:
> +static inline void balance_switch(struct rq *rq)
> +{
> + if (unlikely(rq->balance_flags)) {
> + /*
> + * Run the balance_callbacks, except on hotplug
> + * when we need to push the current
Alex Dewar writes:
> ath11k_peer_create() is called without its return value being checked,
> meaning errors will be unhandled. Add missing check and, as the mutex is
> unconditionally unlocked on leaving this function, simplify the exit
> path.
>
> Addresses-Coverity-ID: 1497531 ("Code
From: ching Huang
Fix warning: right shift count >= width of type.
Reported-by: kernel test robot
Signed-off-by: ching Huang
---
diff --git a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
index be6fb72..d13d672 100644
--- a/drivers/scsi/arcmsr/arcmsr_hba.c
+++
On 10/4/2020 3:56 AM, Kuogee Hsieh wrote:
Set link rate by using OPP set rate api so that CX level will be set
accordingly based on the link rate.
Changes in v2:
-- remove dev from dp_ctrl_put() parameters
-- address review comments
This needs to go below '---' and should not be part of the
By the way I just realized that the DT binding in this driver seems
incorrect to me.
The controller logically supports 3 LED strings, each having
configurable control bank.
But the DT binding supports 2 DT nodes, one for each control bank
(identified by the `reg` property) and then `led-sources`
On Tue, 2020-10-06 at 08:42 +0200, Mauro Carvalho Chehab wrote:
> Em Mon, 5 Oct 2020 10:17:36 -0600
> Jonathan Corbet escreveu:
[]
> Sure. It should be easy to make the third argument optional, although
> the regex will be a little more harder to understand.
>
> Something like this should do the
Hi all,
Today's linux-next merge of the char-misc tree got a conflict in:
drivers/misc/ocxl/Kconfig
between commit:
dde6f18a8779 ("ocxl: Don't return trigger page when allocating an interrupt")
from the powerpc tree and commit:
4b53a3c72116 ("ocxl: fix kconfig dependency warning for
Hi Rob,
On Mon, Oct 5, 2020 at 8:39 PM Rob Herring wrote:
> This doesn't yet do anything in the tools, but make it explicit so we can
> check either 'unevaluatedProperties' or 'additionalProperties' is present
> in schemas.
>
> 'unevaluatedProperties' is appropriate when including another schema
Hi Marc,
On Tue, Aug 25, 2020 at 3:21 AM Rob Herring wrote:
>
> On Sun, 16 Aug 2020 20:07:31 +0100, Lad Prabhakar wrote:
> > Document RZ/G1H (r8a7742) SoC specific bindings. The R8A7742 CAN module
> > is identical to R-Car Gen2 family.
> >
> > No driver change is needed due to the fallback
On Mon, Oct 05, 2020 at 05:57:36PM -0700, Ricardo Neri wrote:
> On Sat, Oct 03, 2020 at 10:53:45AM +0200, Greg Kroah-Hartman wrote:
> > On Fri, Oct 02, 2020 at 06:17:42PM -0700, Ricardo Neri wrote:
> > > Hybrid CPU topologies combine CPUs of different microarchitectures in the
> > > same die.
On Thu, Oct 01, 2020 at 11:48:40PM +0800, Ming Lei wrote:
> Hi,
>
> The 1st patch removes memory footprint of percpu_ref in fast path
> from 7 words to 2 words, since it is often used in fast path and
> embedded in user struct.
>
> The 2nd patch moves .q_usage_counter to 1st cacheline of
>
On Mon, Oct 5, 2020 at 8:39 PM Rob Herring wrote:
> In order to add meta-schema checks for additional/unevaluatedProperties
> being present, all schema need to make this explicit. As the top-level
> board/SoC schemas always have additional properties, add
> 'additionalProperties: true'.
>
>
On Mon, Oct 5, 2020 at 8:39 PM Rob Herring wrote:
> In order to add meta-schema checks for additional/unevaluatedProperties
> being present, all schema need to make this explicit. As common/shared
> schema are included by other schemas, they should always allow for
> additionalProperties.
>
>
+ Jes
On 10/5/2020 4:12 PM, Kalle Valo wrote:
Greg Kroah-Hartman writes:
On Fri, Oct 02, 2020 at 01:53:58PM +0200, Sebastian Andrzej Siewior wrote:
On 2020-10-02 13:37:25 [+0200], Greg Kroah-Hartman wrote:
Is it possible to end up here in softirq context or is this a relic?
I think it's
Sean Christopherson writes:
> On Mon, Oct 05, 2020 at 05:29:47PM +0200, Vitaly Kuznetsov wrote:
>> Tianjia Zhang writes:
>>
>> > Original KVM_SET_CPUID has removed NX on non-NX hosts as it did
>> > before. but KVM_SET_CPUID2 does not. The two should be consistent.
>> >
>> > Signed-off-by:
On Tue 06-10-20 08:26:35, Anshuman Khandual wrote:
>
>
> On 10/05/2020 11:35 AM, Michal Hocko wrote:
> > On Mon 05-10-20 07:59:12, Anshuman Khandual wrote:
> >>
> >>
> >> On 10/02/2020 05:34 PM, Michal Hocko wrote:
> >>> On Wed 30-09-20 11:30:49, Anshuman Khandual wrote:
> Add following new
Use dma_alloc_coherent() for bounce buffer instead of kmalloc() to
make sure the bounce buffer to be allocated within its DMAable range.
Signed-off-by: Ikjoon Jang
---
drivers/spi/spi-mtk-nor.c | 94 ++-
1 file changed, 52 insertions(+), 42 deletions(-)
Dear Rafael,
On 10/1/20 12:56 AM, Rafael J. Wysocki wrote:
> On Tue, Sep 29, 2020 at 10:56 AM Chanwoo Choi wrote:
>>
>> Dear Rafael,
>>
>> This is devfreq-next pull request for v5.10-rc1. I add detailed description
>> of
>> this pull request on the following tag. Please pull devfreq with
The ASUS D700SA desktop's audio (1043:2390) with ALC887 cannot detect
the headset microphone and another headphone jack until
ALC887_FIXUP_ASUS_HMIC and ALC887_FIXUP_ASUS_AUDIO quirks are applied.
The NID 0x15 maps as the headset microphone and NID 0x19 maps as another
headphone jack. Also need
Add MT8192 spi-nor controller support.
Signed-off-by: Ikjoon Jang
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/spi/mediatek,spi-mtk-nor.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/mediatek,spi-mtk-nor.yaml
in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Konrad-Dybcio/pm8994-msm8992-4-DT-updates/20201006-003302
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm64-allyesconfig (attached as .config)
compiler: aarch64
Hi all,
Today's linux-next merge of the staging tree got a conflict in:
Documentation/devicetree/bindings/iio/adc/samsung,exynos-adc.yaml
between commit:
41fb845621ea ("dt-bindings: Another round of adding missing
'additionalProperties'")
from the devicetree tree and commit:
On Mon, Oct 05, 2020 at 04:57:32PM +0200, Peter Zijlstra wrote:
> +static inline struct task_struct *get_push_task(struct rq *rq)
> +{
> + struct task_struct *p = rq->curr;
> +
> + lockdep_assert_held(>lock);
> +
> + if (rq->push_busy)
> + return NULL;
> +
> + if
This patch adds dev_pm_ops to mtk-nor to support suspend/resume,
auto suspend delay is set to -1 by default.
Accessing registers are only permitted after its clock is enabled
to deal with unknown state of operating clk at probe time.
Signed-off-by: Ikjoon Jang
---
drivers/spi/spi-mtk-nor.c |
This patchset adds 36bit dma address and power management
supports for mt8192-nor.
Changes in v5:
- Rebase from merge conflict
Changes in v4:
- Drop two patches from a list, addressed by an another series
- Fix 0-day ci 'shift-count-overflow' warning
Changes in v3:
- Fix a bugfix of v2 in
This patch enables 36bit dma address support to spi-mtk-nor.
Currently this is enabled only for mt8192-nor.
Signed-off-by: Ikjoon Jang
---
drivers/spi/spi-mtk-nor.c | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/drivers/spi/spi-mtk-nor.c
Hi Geert,
On Fri, Sep 25, 2020 at 3:16 PM Geert Uytterhoeven wrote:
>
> Hi Mateusz,
>
> On Wed, Sep 23, 2020 at 12:10 PM Mateusz Holenko
> wrote:
> > From: Pawel Czarnecki
> >
> > This commit adds driver for the FPGA-based LiteX SoC
> > Controller from LiteX SoC builder.
> >
> >
1 - 100 of 1071 matches
Mail list logo
