The Documentation/DMA-API-HOWTO.txt states that the dma_map_sg() function
returns the number of the created entries in the DMA address space.
However the subsequent calls to the dma_sync_sg_for_{device,cpu}() and
dma_unmap_sg must be called with the original number of the entries
passed to the
Provide basic helpers, KVM_FEATURE and a hypercall.
Host side doesn't provide the feature yet, so it is a dead code for now.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/include/asm/kvm_para.h | 5 +
arch/x86/include/uapi/asm/kvm_para.h | 3 ++-
arch/x86/kernel/kvm.c
On Thu, May 14, 2020 at 01:53:16AM +0530, Souptick Joarder wrote:
> First, when memory allocation for sg_list_unaligned failed, there
> is no point of calling put_pages() as we haven't pinned any pages.
>
> Second, if get_user_pages_fast() failed we should unpinned num_pinned
> pages, no point of
New helpers copy_from_guest()/copy_to_guest() to be used if KVM memory
protection feature is enabled.
Signed-off-by: Kirill A. Shutemov
---
include/linux/kvm_host.h | 4 +++
virt/kvm/kvm_main.c | 78 ++--
2 files changed, 72 insertions(+), 10
Add infrastructure that handles protected memory extension.
Arch-specific code has to provide hypercalls and define non-zero
VM_KVM_PROTECTED.
Signed-off-by: Kirill A. Shutemov
---
include/linux/kvm_host.h | 4 ++
mm/mprotect.c| 1 +
virt/kvm/kvm_main.c | 131
The user mapping doesn't have the page mapping for protected memory.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/kvm/mmu/paging_tmpl.h | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/mmu/paging_tmpl.h b/arch/x86/kvm/mmu/paging_tmpl.h
index
VirtIO for KVM is a primary way to provide IO. All memory that used for
communication with the host has to be marked as shared.
The easiest way to archive that is to use DMA API that already knows how
to deal with shared memory.
Signed-off-by: Kirill A. Shutemov
---
The new VMA flag that indicate a VMA that is not accessible to userspace
but usable by kernel with GUP if FOLL_KVM is specified.
The FOLL_KVM is only used in the KVM code. The code has to know how to
deal with such pages.
Signed-off-by: Kirill A. Shutemov
---
include/linux/mm.h | 8
If the protected memory feature enabled, unmap guest memory from
kernel's direct mappings.
Migration and KSM is disabled for protected memory as it would require a
special treatment.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/mm/pat/set_memory.c | 1 +
include/linux/kvm_host.h | 3 ++
struct kvm_steal_time is shared between guest and host. Mark it as
shared.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/kernel/kvm.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c
index f50d65df4412..b0f445796ed1 100644
We cannot access protected pages directly. Use ioremap() to
create a temporary mapping of the page. The mapping is destroyed
on __kvm_unmap_gfn().
The new interface gfn_to_pfn_memslot_protected() is used to detect if
the page is protected.
ioremap_cache_force() is a hack to bypass
Hi all,
Changes since 20200521:
My fixes tree contains:
cd2b06ec45d6 ("device_cgroup: Fix RCU list debugging warning")
The ext4 tree gained a conflict against the fscrypt tree.
The jc_docs tree gained a conflict against the ext4 tree.
The drm-msm tree still had its build failure so I
Wire up hypercalls for the feature and define VM_KVM_PROTECTED.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/Kconfig | 1 +
arch/x86/kvm/cpuid.c | 3 +++
arch/x86/kvm/x86.c | 9 +
include/linux/mm.h | 4
4 files changed, 17 insertions(+)
diff --git a/arch/x86/Kconfig
We are going unmap guest pages from direct mapping and cannot rely on it
for guest memory access. Use temporary kmap_atomic()-style mapping to
access guest memory.
Signed-off-by: Kirill A. Shutemov
---
virt/kvm/kvm_main.c | 57 +++--
1 file changed, 55
hvclock is shared between the guest and the hypervisor. It has to be
accessible by host.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/kernel/kvmclock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/kvmclock.c b/arch/x86/kernel/kvmclock.c
index
== Background / Problem ==
There are a number of hardware features (MKTME, SEV) which protect guest
memory from some unauthorized host access. The patchset proposes a purely
software feature that mitigates some of the same host-side read-only
attacks.
== What does this set mitigate? ==
- Host
Make force_dma_unencrypted() return true for KVM to get DMA pages mapped
as shared.
__set_memory_enc_dec() now informs the host via hypercall if the state
of the page has changed from shared to private or back.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/Kconfig | 1 +
On Fri, May 22, 2020 at 03:42:18PM +0300, Dmitry Osipenko wrote:
> 22.05.2020 15:26, Thierry Reding пишет:
> > On Wed, May 20, 2020 at 01:08:57PM -0700, Sowjanya Komatineni wrote:
> >> When auto calibration timeouts, calibration is disabled and fail-safe
> >> drive strength values are programmed
Mirror SEV, use SWIOTLB always if KVM memory protection is enabled.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/Kconfig | 1 +
arch/x86/kernel/kvm.c| 2 ++
arch/x86/kernel/pci-swiotlb.c| 3 ++-
arch/x86/mm/mem_encrypt.c| 20
force_dma_unencrypted() has to return true for KVM guest with the memory
protected enabled. Move it out of AMD SME code.
Introduce new config option X86_MEM_ENCRYPT_COMMON that has to be
selected by all x86 memory encryption features.
This is preparation for the following patches.
On Wed, May 20, 2020 at 03:01:22PM +0300, Andy Shevchenko wrote:
> Enables probing via the ACPI PRP0001 route but more is mostly about
> removing examples of this that might get copied into new drivers.
>
> Also fixes
> drivers/mux/adgs1408.c:112:34: warning: unused variable 'adgs1408_of_match
The new interface allows to detect if the page is protected.
A protected page cannot be accessed directly by the host: it has to be
mapped manually.
This is preparation for the next patch.
Signed-off-by: Kirill A. Shutemov
---
arch/powerpc/kvm/book3s_64_mmu_hv.c| 2 +-
On 21/05/2020 20:08, Andrew Morton wrote:
On Thu, 21 May 2020 16:23:06 +0100 Steven Price wrote:
Jan alert me[1] that the W+X detection debug feature was broken in x86
by my change[2] to switch x86 to use the generic ptdump infrastructure.
Fundamentally the approach of trying to move the
On Fri, May 22, 2020 at 12:31:47PM +0100, Lee Jones wrote:
> On Fri, 22 May 2020, Thierry Reding wrote:
>
> > On Thu, May 21, 2020 at 08:15:05AM +0100, Lee Jones wrote:
> > > On Wed, 20 May 2020, Guru Das Srinagesh wrote:
> > >
> > > > On Mon, Apr 27, 2020 at 07:44:34AM +0100, Lee Jones wrote:
>
SMCCC v1.2 adds a new optional function SMCCC_ARCH_SOC_ID to obtain a
SiP defined SoC identification value. Indeed of making it custom
attribute, let us add the same as generic attribute to soc_device.
There are various ways in which it can be represented in shortened form
for efficiency and ease
Hi,
While attempting to add custom sysfs attributes for SMCCC ARCH_SOC_ID
Arnd suggested to make it generic. Here is my first attempt.
The original thread/discussion can be found here[1]
Regards,
Sudeep
[1]
SMCCC v1.2 adds a new optional function SMCCC_ARCH_SOC_ID to obtain a
SiP defined SoC identification value. Add support for the same.
Also using the SoC bus infrastructure, let us expose the platform
specific SoC atrributes under sysfs.
Reviewed-by: Steven Price
Acked-by: Etienne Carriere
22.05.2020 15:26, Thierry Reding пишет:
> On Wed, May 20, 2020 at 01:08:57PM -0700, Sowjanya Komatineni wrote:
>> When auto calibration timeouts, calibration is disabled and fail-safe
>> drive strength values are programmed based on the signal voltage.
>>
>> Different fail-safe drive strength
YueHaibing wrote:
> In file included from ./include/linux/firmware.h:6:0,
> from drivers/net/wireless/mediatek/mt76/mt7915/mcu.c:4:
> In function ‘__mt7915_mcu_msg_send’,
> inlined from ‘mt7915_mcu_send_message’ at
> drivers/net/wireless/mediatek/mt76/mt7915/mcu.c:370:6:
>
The following commit has been merged into the x86/build branch of tip:
Commit-ID: d6ee6529436a15a0541aff6e1697989ee7dc2c44
Gitweb:
https://git.kernel.org/tip/d6ee6529436a15a0541aff6e1697989ee7dc2c44
Author:Fangrui Song
AuthorDate:Wed, 20 May 2020 11:20:10 -07:00
On 2020/5/22 13:49, Xin Long wrote:
> On Fri, May 22, 2020 at 9:45 AM Yuehaibing wrote:
>>
>> On 2020/5/21 14:49, Xin Long wrote:
>>> On Tue, May 19, 2020 at 4:53 PM Steffen Klassert
>>> wrote:
On Fri, May 15, 2020 at 04:39:57PM +0800, Yuehaibing wrote:
>
> Friendly ping...
On Mon, 18 May 2020 13:29:24 -0500
Tom Zanussi wrote:
> The in-kernel trace event API should have its own section, and the
> duplicate section numbers need fixing as well.
>
> Signed-off-by: Tom Zanussi
Acked-by: Steven Rostedt (VMware)
Jon,
Care to take this in your tree?
-- Steve
>
On Fri, May 22, 2020 at 01:18:20PM +0100, Mark Brown wrote:
> On Fri, May 22, 2020 at 03:12:21PM +0300, Andy Shevchenko wrote:
> > On Fri, May 22, 2020 at 02:52:35PM +0300, Serge Semin wrote:
>
> > > Please, see it's implementation. It does atomic delay when the delay value
> > > is less than
On Fri, May 22, 2020 at 03:18:40PM +0300, Dmitry Osipenko wrote:
> 22.05.2020 15:13, Thierry Reding пишет:
> > On Wed, May 20, 2020 at 09:09:33AM -0700, Sowjanya Komatineni wrote:
> >>
> >> On 5/20/20 4:26 AM, Ulf Hansson wrote:
> >>> On Wed, 20 May 2020 at 04:00, Dmitry Osipenko wrote:
>
On Fri, May 22, 2020 at 2:53 PM Dinghao Liu wrote:
>
> pm_runtime_get_sync() increments the runtime PM usage counter even
> when it returns an error code. Thus a pairing decrement is needed on
> the error handling path to keep the counter balanced.
>
> Also, call pm_runtime_disable() when
Other LSM may set own capabilities to files. But its inode_killpriv
hook may not be called because cap_inode_killpriv breaks
the chain returning -ENODATA on remove xattr other than
XATTR_NAME_CAPS.
Signed-off-by: Dmitry Mastykin
---
security/commoncap.c | 2 +-
1 file changed, 1 insertion(+), 1
On Fri, May 22, 2020 at 02:33:12PM +0300, Tali Perry wrote:
> Add support for slave mode for Nuvoton
> NPCM BMC I2C controller driver.
I guess it will require v14, so, few nits below.
...
> +const int npcm_i2caddr[I2C_NUM_OWN_ADDR] = {
> + NPCM_I2CADDR1,
On Thu, 21 May 2020, Paul Burton wrote:
> I'm reachable but lacking free time & with no access to Malta hardware
> I can't claim to be too useful here, so thanks for responding :)
Great you're still around! I hope you're doing good in this difficult
time, and overall. I have recently learnt
20.05.2020 23:08, Sowjanya Komatineni пишет:
> When auto calibration timeouts, calibration is disabled and fail-safe
> drive strength values are programmed based on the signal voltage.
>
> Different fail-safe drive strength values based on voltage are
> applicable only for SoCs supporting 3V3 and
On 22/05/2020 13:12, Sandipan Patra wrote:
...
> /*
>* Compute the prescaler value for which (1 << PWM_DUTY_WIDTH)
>* cycles at the PWM clock rate will take period_ns nanoseconds.
>*/
> - rate = pc->clk_rate >> PWM_DUTY_WIDTH;
> + if (pc->soc->num_channels
On Fri, May 22, 2020 at 02:33:11PM +0300, Tali Perry wrote:
> Add Nuvoton NPCM BMC I2C controller driver.
I thought we are waiting for Wolfram finishing his review...
In any case see couple of comments below.
...
> +#ifdef CONFIG_DEBUG_FS
Now, do we need the rest of DEBUG_FS guards?
> +
On Wed, May 20, 2020 at 01:08:57PM -0700, Sowjanya Komatineni wrote:
> When auto calibration timeouts, calibration is disabled and fail-safe
> drive strength values are programmed based on the signal voltage.
>
> Different fail-safe drive strength values based on voltage are
> applicable only for
Add RGMII internal delay configuration for Rx and Tx.
Signed-off-by: Dan Murphy
---
drivers/net/phy/dp83869.c | 101 ++
1 file changed, 101 insertions(+)
diff --git a/drivers/net/phy/dp83869.c b/drivers/net/phy/dp83869.c
index cfb22a21a2e6..a9008d32e2b6
Add the internal delay values into the header and update the binding
with the internal delay properties.
Signed-off-by: Dan Murphy
---
.../devicetree/bindings/net/ti,dp83869.yaml | 16
1 file changed, 16 insertions(+)
diff --git
Add a helper function that will return the index in the array for the
passed in internal delay value. The helper requires the array, size and
delay value.
The helper will then return the index for the exact match or return the
index for the index to the closest smaller value.
Signed-off-by: Dan
tx-internal-delays and rx-internal-delays are a common setting for RGMII
capable devices.
These properties are used when the phy-mode or phy-controller is set to
rgmii-id, rgmii-rxid or rgmii-txid. These modes indicate to the
controller that the PHY will add the internal delay for the
Hello
The RGMII internal delay is a common setting found in most RGMII capable PHY
devices. It was found that many vendor specific device tree properties exist
to do the same function. This creates a common property to be used for PHY's
that have tunable internal delays for the Rx and Tx paths.
On Fri, May 22, 2020 at 08:03:25PM +0800, Feng Tang wrote:
> On Fri, May 22, 2020 at 02:32:35PM +0300, Serge Semin wrote:
> > On Fri, May 22, 2020 at 03:58:44PM +0800, Feng Tang wrote:
> > > Hi Serge,
> > >
> > > On Thu, May 21, 2020 at 06:33:17PM +0300, Serge Semin wrote:
> > > > > > > > +
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 051143e1602d90ea71887d92363edd539d411de5
commit: 1df23c6fe5b0654ece219985a0c32e40b100bd9a compat_ioctl: move HDIO ioctl
handling into drivers/ide
date: 5 months ago
config: xtensa-randconfig-s002-20200522
On Fri, 22 May 2020 at 14:40, Sumit Garg wrote:
>
> Hi Maxim,
>
> On Thu, 21 May 2020 at 12:17, Maxim Uvarov wrote:
> >
> > Some drivers (like ftpm) can operate only after tee-supplicant
> > runs becase of tee-supplicant provides things like storage
> > services. This patch splits probe of non
On Fri, May 22, 2020 at 7:01 PM Naresh Kamboju
wrote:
>
> On Tue, 5 May 2020 at 14:12, Yafang Shao wrote:
> >
> > From: Chris Down
> >
> > mem_cgroup_protected currently is both used to set effective low and min
> > and return a mem_cgroup_protection based on the result. As a user, this
> >
Currently ref-clk control timeout is implemented by Jiffies. However
jiffies is not accurate enough thus "false timeout" may happen.
Use more accurate delay mechanism instead, for example, ktime.
Signed-off-by: Stanley Chu
Reviewed-by: Andy Teng
---
drivers/scsi/ufs/ufs-mediatek.c | 7 ---
22.05.2020 15:13, Thierry Reding пишет:
> On Wed, May 20, 2020 at 09:09:33AM -0700, Sowjanya Komatineni wrote:
>>
>> On 5/20/20 4:26 AM, Ulf Hansson wrote:
>>> On Wed, 20 May 2020 at 04:00, Dmitry Osipenko wrote:
19.05.2020 23:44, Sowjanya Komatineni пишет:
> On 5/19/20 12:07 PM,
Hi,
This patchset fixes a clk-gating issue and introduces low-power mode for vccq2
in MediaTek platforms.
Stanley Chu (3):
scsi: ufs-mediatek: Fix imprecise waiting time for ref-clk control
scsi: ufs-mediatek: Do not gate clocks if auto-hibern8 is not entered
yet
scsi: ufs-mediatek:
There are some chances that link enters hibern8 lately by auto-hibern8
scheme during the clock-gating flow. Clocks shall not be gated if link
is still active otherwise host or device may hang.
Fix this by returning error code to the caller __ufshcd_setup_clocks()
to skip gating clocks there if
Allow device power supply to enter low-power mode if device will
do nothing to save more power.
Signed-off-by: Stanley Chu
Reviewed-by: Pengshun Zhao
---
drivers/scsi/ufs/ufs-mediatek.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/drivers/scsi/ufs/ufs-mediatek.c
On Fri, May 22, 2020 at 03:12:21PM +0300, Andy Shevchenko wrote:
> On Fri, May 22, 2020 at 02:52:35PM +0300, Serge Semin wrote:
> > Please, see it's implementation. It does atomic delay when the delay value
> > is less than 10us. But selectively gets to the usleep_range() if value is
> > greater
Added brcm,brcmnand-v2.1 and brcm,brcmnand-v2.2 as possible compatible
strings to support brcmnand controllers v2.1 and v2.2.
Signed-off-by: Álvaro Fernández Rojas
---
v4: no changes.
v3: no changes.
v2: add new patch.
Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt | 2 ++
1 file
Only v3.3-v5.0 have a different CS0 layout.
Controllers before v3.3 use the same layout for every CS.
Fixes: 27c5b17cd1b1 ("mtd: nand: add NAND driver "library" for Broadcom STB
NAND controller")
Signed-off-by: Álvaro Fernández Rojas
---
v4: no changes.
v3: no changes.
v2: fix commit log.
Current pages sizes apply to controllers after v3.4
Signed-off-by: Álvaro Fernández Rojas
---
v4: no changes.
v3: no changes.
v2: add new patch.
drivers/mtd/nand/raw/brcmnand/brcmnand.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Add support for v2.1 and v2.2 NAND controllers.
v4: fix commit subject.
v3: fix v2.1 page size shift
v2: introduce changes suggested by Miquèl.
Álvaro Fernández Rojas (5):
mtd: rawnand: brcmnand: rename v4 registers
mtd: rawnand: brcmnand: fix CS0 layout
mtd: rawnand: brcmnand: rename page
These registers are also used on v3.3.
Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Miquel Raynal
---
v4: no changes.
v3: no changes.
v2: fix commit title.
drivers/mtd/nand/raw/brcmnand/brcmnand.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
v2.1: tested on Netgear DGND3700v1 (BCM6368)
v2.2: tested on Netgear DGND3700v2 (BCM6362)
Signed-off-by: Álvaro Fernández Rojas
---
v4: use proper commit subject.
v3: fix page size shift for v2.1 controllers.
v2: split page sizes rename into a different patch.
name all block and page
On Wed, May 20, 2020 at 09:09:33AM -0700, Sowjanya Komatineni wrote:
>
> On 5/20/20 4:26 AM, Ulf Hansson wrote:
> > On Wed, 20 May 2020 at 04:00, Dmitry Osipenko wrote:
> > > 19.05.2020 23:44, Sowjanya Komatineni пишет:
> > > > On 5/19/20 12:07 PM, Sowjanya Komatineni wrote:
> > > > > On 5/19/20
Hi Jon,
> -Original Message-
> From: Jonathan Hunter
> Sent: Friday, May 22, 2020 5:20 PM
> To: Sandipan Patra ; Thierry Reding
> ; robh...@kernel.org; u.kleine-koe...@pengutronix.de
> Cc: Bibek Basu ; Laxman Dewangan
> ; linux-...@vger.kernel.org;
> devicet...@vger.kernel.org;
On Fri, May 22, 2020 at 02:52:35PM +0300, Serge Semin wrote:
> On Fri, May 22, 2020 at 02:13:40PM +0300, Andy Shevchenko wrote:
> > On Fri, May 22, 2020 at 03:07:50AM +0300, Serge Semin wrote:
> > > Since DMA transfers are performed asynchronously with actual SPI
> > > transaction, then even if
On Fri, May 22, 2020 at 02:52:35PM +0300, Serge Semin wrote:
> On Fri, May 22, 2020 at 02:13:40PM +0300, Andy Shevchenko wrote:
> > > Changelog v4:
> > > - Get back ndelay() method to wait for an SPI transfer completion.
> > > spi_delay_exec() isn't suitable for the atomic context.
> > OTOH we
Hello Miquel,
No, nothing else changed.
I will change it again with the proper subject, sorry for that.
Best regards,
Álvaro.
> El 22 may 2020, a las 13:22, Miquel Raynal
> escribió:
>
>> v2.1: tested on Netgear DGND3700v1 (BCM6368)
From: Bartosz Golaszewski
This adds yaml DT bindings for the MediaTek STAR Ethernet MAC present
on the mt8* family of SoCs.
Signed-off-by: Bartosz Golaszewski
---
.../bindings/net/mediatek,eth-mac.yaml| 89 +++
1 file changed, 89 insertions(+)
create mode 100644
From: Bartosz Golaszewski
Convert the DT binding .txt file for MediaTek's peripheral configuration
controller to YAML. There's one special case where the compatible has
three positions. Otherwise, it's a pretty normal syscon.
Signed-off-by: Bartosz Golaszewski
---
From: Bartosz Golaszewski
The PERICFG controller is present on the MT8516 SoC. Add an appropriate
compatible variant.
Signed-off-by: Bartosz Golaszewski
---
.../devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Bartosz Golaszewski
Add the ethernet0 alias for ethernet so that u-boot can find this node
and fill in the MAC address.
Signed-off-by: Bartosz Golaszewski
---
arch/arm64/boot/dts/mediatek/pumpkin-common.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Bartosz Golaszewski
Setup the pin control for the Ethernet MAC.
Signed-off-by: Bartosz Golaszewski
---
arch/arm64/boot/dts/mediatek/pumpkin-common.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/pumpkin-common.dtsi
From: Bartosz Golaszewski
This adds the driver for the MediaTek STAR Ethernet MAC currently used
on the MT8* SoC family. For now we only support full-duplex.
Signed-off-by: Bartosz Golaszewski
---
drivers/net/ethernet/mediatek/Kconfig |7 +
drivers/net/ethernet/mediatek/Makefile
From: Bartosz Golaszewski
This adds support for the PERICFG register range as a syscon. This will
soon be used by the MediaTek Ethernet MAC driver for NIC configuration.
Signed-off-by: Bartosz Golaszewski
---
arch/arm64/boot/dts/mediatek/mt8516.dtsi | 5 +
1 file changed, 5 insertions(+)
From: Bartosz Golaszewski
Add remaining properties to the ethernet node and enable it.
Signed-off-by: Bartosz Golaszewski
---
.../boot/dts/mediatek/pumpkin-common.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/pumpkin-common.dtsi
From: Bartosz Golaszewski
We'll soon by adding a second MediaTek Ethernet driver so modify the
Kconfig prompt.
Signed-off-by: Bartosz Golaszewski
---
drivers/net/ethernet/mediatek/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/mediatek/Kconfig
From: Bartosz Golaszewski
Add the Ethernet MAC node to mt8516.dtsi. This defines parameters common
to all the boards based on this SoC.
Signed-off-by: Bartosz Golaszewski
---
arch/arm64/boot/dts/mediatek/mt8516.dtsi | 12
1 file changed, 12 insertions(+)
diff --git
From: Bartosz Golaszewski
The Makefile formatting in the kernel tree usually doesn't use tabs,
so remove them before we add a second driver.
Signed-off-by: Bartosz Golaszewski
---
drivers/net/ethernet/mediatek/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Bartosz Golaszewski
This series adds support for the STAR Ethernet Controller present on MediaTeK
SoCs from the MT8* family.
First we convert the existing DT bindings for the PERICFG controller to YAML
and add a new compatible string for mt8516 variant of it. Then we add the DT
bindings
On Wed, May 20, 2020 at 04:48:16PM -0600, Rob Herring wrote:
> On Wed, May 20, 2020 at 11:16:32PM +0530, Vidya Sagar wrote:
> >
> >
> > On 20-May-20 4:47 PM, Thierry Reding wrote:
> > > On Tue, May 19, 2020 at 10:08:54PM +, Gustavo Pimentel wrote:
> > > > On Tue, May 19, 2020 at 15:58:16,
On Fri, May 22, 2020 at 02:32:35PM +0300, Serge Semin wrote:
> On Fri, May 22, 2020 at 03:58:44PM +0800, Feng Tang wrote:
> > Hi Serge,
> >
> > On Thu, May 21, 2020 at 06:33:17PM +0300, Serge Semin wrote:
> > > > > > > + dw_spi_dma_wait_rx_done(dws);
> > > > > >
> > > > > > I can understand the
Hi Andy,
On 5/13/2020 3:18 PM, Andy Shevchenko wrote:
On Wed, May 13, 2020 at 12:23 PM Jishnu Prakash wrote:
The ADC architecture on PMIC7 is changed as compared to PMIC5. The
major change from PMIC5 is that all SW communication to ADC goes through
PMK8350, which communicates with other PMICs
Hi Andy,
On 5/13/2020 3:21 PM, Andy Shevchenko wrote:
On Wed, May 13, 2020 at 12:24 PM Jishnu Prakash wrote:
This commit includes the following changes:
Add a common function used for read_raw callback for
both PMIC5 and PMIC7 ADCs.
Add exit function for ADC.
Add info_property under adc_data
Hi Andy,
On 5/13/2020 3:19 PM, Andy Shevchenko wrote:
On Wed, May 13, 2020 at 12:23 PM Jishnu Prakash wrote:
Change pr_err/pr_debug statements to dev_err/dev_dbg for
increased clarity. Also clean up some return value checks.
'Also' on the commit message == 'split this to two'.
I'll do the
On Fri, May 22, 2020 at 12:00 AM Nick Desaulniers
wrote:
>
> As debug information gets larger and larger, it helps significantly save
> the size of vmlinux images to compress the information in the debug
> information sections. Note: this debug info is typically split off from
> the final
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
fs/binfmt_script.c
between commit:
ccbb18b67323 ("exec/binfmt_script: Don't modify bprm->buf and then return
-ENOEXEC")
from the userns tree and commit:
e20ecf0e2723 ("exec: simplify the copy_strings_kernel
On Thu, May 14, 2020 at 1:45 AM Souptick Joarder wrote:
>
> First, when memory allocation for sg_list_unaligned failed, there
> is no point of calling put_pages() as we haven't pinned any pages.
>
> Second, if get_user_pages_fast() failed we should unpinned num_pinned
> pages, no point of
On 22/05/2020 12:01, Sandipan Patra wrote:
> Thanks Jonathan,
> Please help reviewing further with my replies inline.
>
>
> Thanks & Regards,
> Sandipan
>
>> -Original Message-
>> From: Jonathan Hunter
>> Sent: Friday, May 22, 2020 3:54 PM
>> To: Sandipan Patra ; Thierry Reding
>> ;
On Thu 21-05-20 12:13:12, ira.we...@intel.com wrote:
> From: Ira Weiny
>
> Add a flag to preserve FS_XFLAG_DAX in the ext4 inode.
>
> Set the flag to be user visible and changeable. Set the flag to be
> inherited. Allow applications to change the flag at any time with the
> exception of if
pm_runtime_get_sync() increments the runtime PM usage counter even
when it returns an error code. Thus a pairing decrement is needed on
the error handling path to keep the counter balanced.
Signed-off-by: Dinghao Liu
---
Changelog:
v2: - Merge two patches that fix runtime PM imbalance in
Add cold interrupt support for tsens in yaml.
Signed-off-by: Manaf Meethalavalappu Pallikunhi
---
.../bindings/thermal/qcom-tsens.yaml | 42 +++
1 file changed, 42 insertions(+)
diff --git a/Documentation/devicetree/bindings/thermal/qcom-tsens.yaml
TSENS IP v2.6+ adds cold interrupt support. It triggers set
interrupt when aggregated minimum temperature of all TSENS falls
below cold preset threshold, 5 degree Celsius and triggers
reset interrupt when aggregated minimum temperature of all TSENS
crosses above reset threshold, 10 degree Celsius.
The changes have dependency on merging tsens-common.c into tsens.c [1]
to merge first.
Dependencies:
[1] https://lkml.org/lkml/2020/4/29/1028
Changes in v3:
* Add cold interrupt support to tsens driver
* Update cold interrupt support in yaml
Manaf Meethalavalappu Pallikunhi (2):
drivers:
Add cold interrupt support for tsens in yaml.
Signed-off-by: Manaf Meethalavalappu Pallikunhi
---
.../bindings/thermal/qcom-tsens.yaml | 42 +++
1 file changed, 42 insertions(+)
diff --git a/Documentation/devicetree/bindings/thermal/qcom-tsens.yaml
Naresh Kamboju writes:
This patch is causing oom-killer while running mkfs -t ext4 on i386 kernel
running on x86_64 machine version linux-next 5.7.0-rc6-next-20200521.
I think I see what's wrong here -- if we bail out early, memory.e{min,low}
might be uninitialised.
Does this patch fix it,
TSENS IP v2.6+ adds cold interrupt support. It triggers set
interrupt when aggregated minimum temperature of all TSENS falls
below cold preset threshold, 5 degree Celsius and triggers
reset interrupt when aggregated minimum temperature of all TSENS
crosses above reset threshold, 10 degree Celsius.
The changes have dependency on merging tsens-common.c into tsens.c [1]
to merge first.
Dependencies:
[1] https://lkml.org/lkml/2020/4/29/1028
Changes in v3:
* Add cold interrupt support to tsens driver
* Update cold interrupt support in yaml
*** BLURB HERE ***
Manaf Meethalavalappu Pallikunhi
On Fri, May 22, 2020 at 03:52:39PM +0800, Muchun Song wrote:
> On Fri, May 22, 2020 at 12:47 AM Matthew Wilcox wrote:
> > > @@ -160,14 +168,23 @@ static int proc_fd_link(struct dentry *dentry,
> > > struct path *path)
> > > unsigned int fd = proc_fd(d_inode(dentry));
> > >
Hi Maxim,
On Thu, 21 May 2020 at 12:17, Maxim Uvarov wrote:
>
> Some drivers (like ftpm) can operate only after tee-supplicant
> runs becase of tee-supplicant provides things like storage
> services. This patch splits probe of non tee-supplicant dependable
> drivers to early stage, and after
801 - 900 of 1224 matches
Mail list logo
