On Wed, Oct 14, 2020 at 01:19:36AM -0500, Samuel Holland wrote:
> The codec's clock input is shared among all AIFs, and shared with other
> audio-related hardware in the SoC, including I2S and SPDIF controllers.
> To ensure sample rates selected by userspace or by codec2codec DAI links
> are mainta
We don't need to check whether the node is memoryless numa node before
calling allocator interface. SLUB(and SLAB,SLOB) relies on the page
allocator to pick a node. Page allocator should deal with memoryless
nodes just fine. It has zonelists constructed for each possible nodes.
And it will automati
Documentation support for Rockchip RK3xxx NAND flash controllers
Signed-off-by: Yifeng Zhao
---
(no changes since v8)
Changes in v8:
- Fix make dt_binding_check error
Changes in v7:
- Fix some wrong define
Changes in v6:
- Fix some wrong define
- Modified the definition of compatible
Changes
Rockchp's NFC(Nand Flash Controller) has four versions: V600, V622, V800 and
V900.This series patch can support all four versions.
Changes in v11:
- Fix compile error.
Changes in v10:
- Fix compile error on master v5.9-rc7
Changes in v9:
- The nfc->buffer will realloc while the page size of t
Add NAND FLASH Controller(NFC) node for RK3036 SoC.
Signed-off-by: Yifeng Zhao
---
(no changes since v1)
arch/arm/boot/dts/rk3036.dtsi | 52 +++
1 file changed, 52 insertions(+)
diff --git a/arch/arm/boot/dts/rk3036.dtsi b/arch/arm/boot/dts/rk3036.dtsi
index 09
This driver supports Rockchip NFC (NAND Flash Controller) found on RK3308,
RK2928, RKPX30, RV1108 and other SOCs. The driver has been tested using
8-bit NAND interface on the ARM based RK3308 platform.
Support Rockchip SoCs and NFC versions:
- PX30 and RK3326(NFCv900).
ECC: 16/40/60/70 bit
Add NAND FLASH Controller(NFC) node for PX30 SoC.
Signed-off-by: Yifeng Zhao
---
(no changes since v1)
arch/arm64/boot/dts/rockchip/px30.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/px30.dtsi
b/arch/arm64/boot/dts/rockchip/px30.dtsi
in
Add maintainers to ROCKCHIP NFC.
Signed-off-by: Yifeng Zhao
---
(no changes since v1)
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5919b758c708..b2db04cfec61 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2362,12 +2362,12 @
Add NAND FLASH Controller(NFC) node for RV1108 SoC.
Signed-off-by: Yifeng Zhao
---
(no changes since v1)
arch/arm/boot/dts/rv1108.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/rv1108.dtsi b/arch/arm/boot/dts/rv1108.dtsi
index a1a08cb9364e..1696ea19488b
People,
At https://www.kernel.org/doc/html/latest/leds/leds-class.html we can
read that the LEDS code supposedly optimizes away when certain
conditions are met.
Especially the Realtek HDA driver *unconditionally* (as found in 5.9.1)
*wants* to enable LED functionality.
I.e.: if this blockade is li
On Sat, 17 Oct 2020 07:06:17 +
guo...@kernel.org wrote:
> From: Guo Ren
>
> It will cause warning messages:
> echo function_graph > /sys/kernel/debug/tracing/current_tracer
> [ 47.691397] [ cut here ]
> [ 47.692899] WARNING: CPU: 0 PID: 11 at arch/riscv/kernel/pat
From: Yanfei Xu
There are two 'start_pfn' declared in compact_zone() which have
different meaning. Rename the second one to 'iteration_start_pfn'
to prevent trace_mm_compaction_end() from tracing an undesirable
value.
BTW, remove an useless semicolon.
Acked-by: David Hildenbrand
Acked-by: Vlas
On Mon, Oct 19, 2020 at 07:50:41AM +0200, Christophe Leroy wrote:
> Le 19/10/2020 à 06:55, Joel Stanley a écrit :
> >>In the old days, marking a function 'static inline' was forcing
> >>GCC to inline, but since commit ac7c3e4ff401 ("compiler: enable
> >>CONFIG_OPTIMIZE_INLINING forcibly") GCC may d
I´ve been working with the philosophy for a Fair Pay Bitstreaming
project for a while now. It is taking shape, and we consider including
apps such as BT Kul 3-D Engine ("Game Maker"), BT Tracker, BT Paint and
BT Cam being suitable for the project, BT X.
Which says alot about our kernel policie
Hi Marc,
> -Original Message-
> From: Marc Kleine-Budde
> Sent: 2020年10月19日 16:16
> To: Joakim Zhang ; robh...@kernel.org;
> shawn...@kernel.org; s.ha...@pengutronix.de
> Cc: ker...@pengutronix.de; dl-linux-imx ; Ying Liu
> ; linux-...@vger.kernel.org; Pankaj Bansal
> ; net...@vger.kerne
This introduces the pureLiFi LiFi driver for LiFi-X, LiFi-XC
and LiFi-XL USB devices.
This driver implementation has been based on the zd1211rw driver.
Driver is based on 802.11 softMAC Architecture and uses
native 802.11 for configuration and management.
The driver is compiled and tested in ARM
Add NAND FLASH Controller(NFC) node for RK2928, RK3066, RK3168
and RK3188 SoCs.
Signed-off-by: Yifeng Zhao
---
(no changes since v1)
arch/arm/boot/dts/rk3xxx.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/rk3xxx.dtsi b/arch/arm/boot/dts/rk3xxx.dtsi
index 85
From: Yifeng Zhao
Add NAND FLASH Controller(NFC) node for RK3308 SoC.
Signed-off-by: Yifeng Zhao
Signed-off-by: Yifeng Zhao
---
(no changes since v1)
arch/arm64/boot/dts/rockchip/rk3308.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk
On 10/19/20 10:39 AM, Joakim Zhang wrote:
>>> +#define FLEXCAN_IMX_SC_R_CAN(x)(IMX_SC_R_CAN_0 + (x))
>>
>> Why not move it into the appropriate svc header file?
>
> Sorry, not quite understand. Which file do you mean the appropriate svc
> header file? Is it include/dt-bindings/firmware
Hello RT-list!
I'm pleased to announce the 4.4.240-rt209 stable release.
This is an update to latest stable release. There are no RT changes.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v4.4-rt
Head SHA1: 8c45
Hello,
Michal Koutný writes:
> On Fri, Oct 16, 2020 at 10:53:08AM -0400, Johannes Weiner
> wrote:
>> The central try_charge() function charges recursively all the way up
>> to and including the root.
> Except for use_hiearchy=0 (which is the case here as Richard
> wrote). The reparenting is he
On Sat, Oct 03, 2020 at 07:50:43AM +0300, Jarkko Sakkinen wrote:
> +config INTEL_SGX
Since the directory for this was renamed some iterations ago from
arch/x86/kernel/cpu/sgx to intel_sgx given the feedback from Boris,
I'm wondering should this also be renamed as X86_SGX?
/Jarkko
Hi Viresh,
thank you for your suggestion on using 'opp-shared'.
I think it could work for most of the cases we explained earlier.
Summarising, there are two parts of this entire proposal:
1) where/how to get the information: now we are focusing on taking advantage of
'opp-shared' within an empty
On 19.10.20 09:54, Wei Yang wrote:
> On Mon, Oct 12, 2020 at 02:53:23PM +0200, David Hildenbrand wrote:
>> Let's add a safe mechanism to unplug memory, avoiding long/endless loops
>> when trying to offline memory - similar to in SBM.
>>
>> Fake-offline all memory (via alloc_contig_range()) before t
> From: Yanfei Xu
>
> There are two 'start_pfn' declared in compact_zone() which have
> different meaning. Rename the second one to 'iteration_start_pfn'
> to prevent trace_mm_compaction_end() from tracing an undesirable
> value.
>
> BTW, remove an useless semicolon.
>
> Acked-by: David Hildenbran
Thank you for the review. Comments below.
The 10/15/2020 10:34, Jakub Kicinski wrote:
>
> On Thu, 15 Oct 2020 11:54:15 + Henrik Bjoernlund wrote:
> > + [IFLA_BRIDGE_CFM_MEP_CONFIG_MDLEVEL] = {
> > + .type = NLA_U32, .validation_type = NLA_VALIDATE_MAX, .max = 7 },
>
> NLA
On Mon, Oct 19, 2020 at 03:50:32PM +0800, Xu Yilun wrote:
> On Mon, Oct 19, 2020 at 03:46:23PM +0800, Wu, Hao wrote:
> > > On Fri, Oct 16, 2020 at 09:21:50AM -0700, Tom Rix wrote:
> > > >
> > > > On 10/15/20 11:02 PM, Xu Yilun wrote:
> > > > > Add support for overriding the default matching of a df
Le 19/10/2020 à 10:32, Segher Boessenkool a écrit :
On Mon, Oct 19, 2020 at 07:50:41AM +0200, Christophe Leroy wrote:
Le 19/10/2020 à 06:55, Joel Stanley a écrit :
In the old days, marking a function 'static inline' was forcing
GCC to inline, but since commit ac7c3e4ff401 ("compiler: enable
Both read-side users of func_table/func_buf need locking. Without that,
one can easily confuse the code by repeatedly setting altering strings
like:
while (1)
for (a = 0; a < 2; a++) {
struct kbsentry kbs = {};
strcpy((char *)kbs.kb_string, a ? ".\n" : "8
Use 'strlen' of the string, add one for NUL terminator and simply do
'copy_to_user' instead of the explicit 'for' loop. This makes the
KDGKBSENT case more compact.
The only thing we need to take care about is NULL 'func_table[i]'. Use
an empty string in that case.
The original check for overflow
On Wed, Oct 14, 2020 at 01:19:39AM -0500, Samuel Holland wrote:
> The AIF clock control register has the same layout for all three AIFs.
> The only difference between them is that AIF3 is missing some fields. We
> can reuse the same register field definitions for all three registers,
> and use the
These rules must be followed when accessing the TX descriptor:
1. A TX descriptor is "cleanable" only when its value is non-zero
and the owner bit is set to "software"
2. A TX descriptor is "writable" only when its value is zero regardless
the edotr mask.
Fixes: 52c0cae87465 ("ftgmac100: Remove
On 17/10/2020 08:08, Sam Ravnborg wrote:
> Hi Neil.
>
> On Tue, Sep 29, 2020 at 11:25:17AM +0200, Neil Armstrong wrote:
>> Hi Sam,
>>
>> Is there anything more to change ?
> Sorry for taking so long to get back to you on this.
>
> All patches looks good and are:
> Reviewed-by: Sam Ravnborg
>
>
On Mon, 19 Oct 2020 at 07:39, Dylan Hung wrote:
>
> The cpu accesses the register and the memory via different bus/path on
> aspeed soc. So we can not guarantee that the tx-poll command
Just the 2600, or other versions too?
> (register access) is always behind the tx descriptor (memory). In ot
This patch series fixes the ftgmac100 mac hw issues on aspeed soc.
Fixes: 52c0cae ("ftgmac100: Remove tx descriptor accessors")
Fixes: 39bfab8 ("net: ftgmac100: Add support for DT phy-handle property")
Fixes: 10cbd64 ("ftgmac100: Rework NAPI & interrupts handling")
Dylan Hung (4):
ftgmac100: F
the tx-poll command may advance the tx descriptor due the HW design.
By adding a pseudo read and proper memory barrier, we can ensure all the
data are ready before TX poll command.
Fixes: 52c0cae87465 ("ftgmac100: Remove tx descriptor accessors")
Signed-off-by: Dylan Hung
Signed-off-by: Joel Stan
On Mon, Oct 19, 2020 at 12:06:13PM +0800, Xu Yilun wrote:
> On Fri, Oct 16, 2020 at 09:21:50AM -0700, Tom Rix wrote:
> >
> > On 10/15/20 11:02 PM, Xu Yilun wrote:
> > > Add support for overriding the default matching of a dfl device to a dfl
> > > driver. It follows the same way that can be used f
On the AST2600 care must be taken to ensure writes appear correctly when
modifying the interrupt reglated registers.
Add a function to perform a read after all writes to the IER and ISR registers.
Fixes: 39bfab8844a0 ("net: ftgmac100: Add support for DT phy-handle property")
Signed-off-by: Dylan
The interrupt handler may set the flag to reset the mac in the future,
but that flag is not cleared once the reset has occured.
Fixes: 10cbd6407609 ("ftgmac100: Rework NAPI & interrupts handling")
Signed-off-by: Dylan Hung
Signed-off-by: Joel Stanley
---
drivers/net/ethernet/faraday/ftgmac100.c
Hi,
Any further comments?
Thanks,
Meenakshi
> -Original Message-
> From: Meenakshi Aggarwal
> Sent: Tuesday, September 29, 2020 3:33 PM
> To: shawn...@kernel.org; robh...@kernel.org; Varun Sethi
> ; Leo Li ; linux-arm-
> ker...@lists.infradead.org; devicet...@vger.kernel.org; linux-
> k
On 29/09/2020 14:39, Leo Yan wrote:
Hi Leo,
> This patch is to refactor address packet handling, it defines macros for
> address packet's header and payload, these macros are used by decoder
> and the dump flow.
So I was thinking about these next few patches a bit. I understand that
it's common
On Mon, Oct 19, 2020 at 04:52:33PM +0800, Xu Yilun wrote:
> On Mon, Oct 19, 2020 at 12:06:13PM +0800, Xu Yilun wrote:
> > On Fri, Oct 16, 2020 at 09:21:50AM -0700, Tom Rix wrote:
> > >
> > > On 10/15/20 11:02 PM, Xu Yilun wrote:
> > > > Add support for overriding the default matching of a dfl devi
Hi Marc,
> -Original Message-
> From: Marc Kleine-Budde
> Sent: 2020年10月19日 16:42
> To: Joakim Zhang ; robh...@kernel.org;
> shawn...@kernel.org; s.ha...@pengutronix.de
> Cc: ker...@pengutronix.de; dl-linux-imx ; Ying Liu
> ; linux-...@vger.kernel.org; Pankaj Bansal
> ; net...@vger.kerne
On 18.10.20 05:57, Wei Yang wrote:
> On Fri, Oct 16, 2020 at 11:18:39AM +0200, David Hildenbrand wrote:
>> On 16.10.20 06:03, Wei Yang wrote:
>>> On Mon, Oct 12, 2020 at 02:53:03PM +0200, David Hildenbrand wrote:
Let's trigger from offlining code when we're not allowed to touch online
>
> Her
On 10/19/20 11:03 AM, Joakim Zhang wrote:
>>> include/dt-bindings/firmware/imx/rsrc.h:111:#define IMX_SC_R_CAN_0
>> 105
>
> As I can see in rsrc.h file, it just list each resource sequentially, and
> there is a note in the comments:
> "Note items from list should never be changed or removed (onl
From: V Sujith Kumar Reddy
Disable MI2S bit clock from PAUSE/STOP/SUSPEND usecase instead of
shutdown time. Acheive this by invoking clk_disable API from
cpu daiops trigger instead of cpu daiops shutdown.
Change non-atomic API "clk_prepare_enable" to atomic API
"clk_enable" in trigger, as trigger
In case failure to setup Post interrupt for an IRQ, it make no sense
to assign irqfd->producer to the producer.
This change makes code more robust.
Signed-off-by: Zhenzhong Duan
---
arch/x86/kvm/x86.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kvm/x86.c b/arc
If Post interrupt is disabled due to hardware limit or forcely disabled
by "intremap=nopost" parameter, return -EINVAL so that the legacy mode IRQ
isn't registered as IRQ bypass producer.
With this change, below message is printed:
"vfio-pci :db:00.0: irq bypass producer (token 60c8cda
kmemleak report:
unreferenced object 0x9071c65644e0 (size 96):
comm "systemd-udevd", pid 347, jiffies 4294898424 (age 810.828s)
hex dump (first 32 bytes):
02 01 00 00 00 00 00 00 00 00 10 00 02 04 00 00
00 00 00 00 00 00 a0 86 00 00 00 00 00 00 00 00 ...
On 19.10.20 05:48, Wei Yang wrote:
> On Mon, Oct 12, 2020 at 02:53:22PM +0200, David Hildenbrand wrote:
>> Let's try to unplug completely offline big blocks first. Then, (if
>> enabled via unplug_offline) try to offline and remove whole big blocks.
>>
>> No locking necessary - we can deal with conc
On 19.10.20 04:26, Wei Yang wrote:
> On Mon, Oct 12, 2020 at 02:53:19PM +0200, David Hildenbrand wrote:
>> Currently, we do not support device block sizes that exceed the Linux
>> memory block size. For example, having a device block size of 1 GiB (e.g.,
>> gigantic pages in the hypervisor) won't w
On Mon, Oct 19, 2020 at 10:28:27AM +0530, Viresh Kumar wrote:
> On 16-10-20, 12:12, Sudeep Holla wrote:
> > On Fri, Oct 16, 2020 at 07:00:21AM +0100, Sudeep Holla wrote:
> > > On Fri, Oct 16, 2020 at 09:54:34AM +0530, Viresh Kumar wrote:
> > > > On 15-10-20, 19:05, Sudeep Holla wrote:
> > > > > OK,
On 2020-10-17 05:18, jaeg...@kernel.org wrote:
The below call stack prevents clk_gating at every IO completion.
We can remove the condition, ufshcd_any_tag_in_use(), since
clkgating_work
will check it again.
Thanks for fixing it, actually we have noticed this for a while.
It used to work well
Hi Joel,
> -Original Message-
> From: Joel Stanley [mailto:j...@jms.id.au]
> Sent: Monday, October 19, 2020 4:57 PM
> To: Dylan Hung ; Benjamin Herrenschmidt
>
> Cc: David S . Miller ; Jakub Kicinski
> ; net...@vger.kernel.org; Linux Kernel Mailing List
> ; Po-Yu Chuang ;
> linux-aspeed ;
On 19-10-20, 10:17, Sudeep Holla wrote:
> On Mon, Oct 19, 2020 at 10:28:27AM +0530, Viresh Kumar wrote:
> > On 16-10-20, 12:12, Sudeep Holla wrote:
> > > On Fri, Oct 16, 2020 at 07:00:21AM +0100, Sudeep Holla wrote:
> > > > On Fri, Oct 16, 2020 at 09:54:34AM +0530, Viresh Kumar wrote:
> > > > > On
[Why] the func bios_parser_get_src_obj () is similar to
bios_parser_get_dst_obj () which is fixed by the
commit("drm/amd/display: Banch of smatch error and warning fixes
in DC").
the symbol 'id' is uninitialized and it is not checked before dereference
it,may lead to null pointer dereference.
On Sun 18-10-20 05:56:54, Roman Anufriev wrote:
> Current quota state flags scheme doesn't include project quota and thus
> shows all flags after DQUOT_USAGE_ENABLED wrong. Fix this and also add
> DQUOT_NOLIST_DIRTY to the scheme.
>
> Signed-off-by: Roman Anufriev
Thanks. I've added the patch to
The code has been in a irq-disabled context since it is hard IRQ. There
is no necessity to do it again.
Signed-off-by: Tian Tao
---
drivers/gpu/ipu-v3/ipu-image-convert.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/ipu-v3/ipu-image-convert.c
b/drivers/gp
> From: Krzysztof Struczynski
> Sent: Monday, September 14, 2020 2:08 PM
> > When Roberto Sassu and Krzysztof Struczynski contacted me about the
> > status of Stefan Berger's patch set, based on Yuqiong Sun's work, I was
> > under the impression that they would be rebasing it on the latest
> > kern
Hi!
On Sat, Oct 10, 2020 at 06:46:03PM +0800, wuyan wrote:
> Signed-off-by: wuyan
A commit log would be welcome here. Also, the last time you contributed
you used the name Martin Wu in your Signed-off-by, it would be nice to
be consistent there.
> Change-Id: I7edbc00fd0968d0301757f5a75dbd6f53d6
On Sun, Oct 18 2020 at 22:37, Ira Weiny wrote:
> On Fri, Oct 16, 2020 at 02:55:21PM +0200, Thomas Gleixner wrote:
>> Subject: x86/entry: Move nmi entry/exit into common code
>> From: Thomas Gleixner
>> Date: Fri, 11 Sep 2020 10:09:56 +0200
>>
>> Add blurb here.
>
> How about:
>
> To prepare for s
On 16/10/2020 05:07, Viresh Kumar wrote:
> On 15-10-20, 15:03, Jon Hunter wrote:
>> If not too late, would you mind dropping this patch for v5.10?
>
> It is already part of Linus's master now.
OK, thanks. I will send a revert for this once rc1 is out.
Cheers
Jon
--
nvpublic
On Fri, Oct 16, 2020 at 08:32:03PM -0700, Ira Weiny wrote:
> On Fri, Oct 16, 2020 at 12:57:43PM +0200, Peter Zijlstra wrote:
> > On Fri, Oct 09, 2020 at 12:42:51PM -0700, ira.we...@intel.com wrote:
> > > From: Fenghua Yu
> > >
> > > Define a helper, update_pkey_val(), which will be used to suppor
On Fri, Oct 16, 2020 at 10:14:10PM -0700, Ira Weiny wrote:
> > so it either needs to
> > explicitly do so, or have an assertion that preemption is indeed
> > disabled.
>
> However, I don't think I understand clearly. Doesn't [get|put]_cpu_ptr()
> handle the preempt_disable() for us?
It does.
>
--
Hi friend
I am a banker in ADB BANK. I want to transfer an abandoned sum of
USD15.6Million to your Bank account. 40/percent will be your share.
No risk involved but keeps it as secret. Contact me for more details.
Please reply me through my alternative email id only (salif.musa...@gmail.com
On 10/19/20 10:36 AM, yanfei...@windriver.com wrote:
From: Yanfei Xu
There are two 'start_pfn' declared in compact_zone() which have
different meaning. Rename the second one to 'iteration_start_pfn'
to prevent trace_mm_compaction_end() from tracing an undesirable
value.
"to prevent confusion.
On Monday 19 October 2020 10:09:19 CEST David Laight wrote:
> From: Joe Perches
> > Sent: 17 October 2020 01:12
> >
> > On Fri, 2020-10-16 at 23:33 +0100, Colin King wrote:
> > > From: Colin Ian King
> > >
> > > Don't populate const array filter_ies on the stack but instead
> > > make it static. M
On 19-10-20, 09:50, Nicola Mazzucato wrote:
> Hi Viresh,
>
> thank you for your suggestion on using 'opp-shared'.
> I think it could work for most of the cases we explained earlier.
>
> Summarising, there are two parts of this entire proposal:
> 1) where/how to get the information: now we are foc
Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM:
dts: exynos: Remove Exynos5440"). Drop the obsolete bindings for
exynos5440-pcie.
Signed-off-by: Marek Szyprowski
---
.../bindings/pci/samsung,exynos5440-pcie.txt | 58 ---
1 file changed, 58 deletions(-)
From: Jaehoon Chung
Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM:
dts: exynos: Remove Exynos5440"). Rework this driver to support DWC PCIe
variant found in the Exynos5433 SoCs.
The main difference in Exynos5433 variant is lack of the MSI support
(the MSI interrupt is n
From: Jaehoon Chung
Add dt-bindings for the Samsung Exynos PCIe controller (Exynos5433
variant).
Signed-off-by: Jaehoon Chung
[mszyprow: updated the binding to latest driver changes, rewrote it in yaml,
rewrote commit message]
Signed-off-by: Marek Szyprowski
---
.../bindings/pci/sa
From: Jaehoon Chung
Add the nodes relevant to PCIe PHY and PCIe support. PCIe is used for the
WiFi interface (Broadcom Limited BCM4358 802.11ac Wireless LAN SoC).
Signed-off-by: Jaehoon Chung
[mszyprow: rewrote commit message, reworked board/generic dts/dtsi split]
Signed-off-by: Marek Szyprows
Dear All,
This patchset is a resurrection of the DW PCIe support for the Exynos5433
SoCs posted long time ago here: https://lkml.org/lkml/2016/12/26/6 and
later here: https://lkml.org/lkml/2017/12/21/296 .
In meantime the support for the Exynos5440 SoCs has been completely
dropped from mainline k
From: Jaehoon Chung
Add dt-bindings for the Samsung Exynos PCIe PHY controller (Exynos5433
variant).
Signed-off-by: Jaehoon Chung
[mszyprow: updated the binding to latest driver changes, rewrote it in yaml,
rewrote commit message]
Signed-off-by: Marek Szyprowski
---
.../bindings/ph
From: Jaehoon Chung
Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM:
dts: exynos: Remove Exynos5440"). Rework this driver to support PCIe PHY
variant found in the Exynos5433 SoCs.
Signed-off-by: Jaehoon Chung
[mszyprow: reworked the driver to support only Exynos5433 vari
On 19/10/2020 00:30, Ian Rogers wrote:
On Sun, Oct 18, 2020 at 1:51 AM kernel test robot wrote:
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: fcc9c5243c478f104014daf4d23db86098d2aef0 ("perf metricgroup: Hack a fix for
aliases when covering multiple PMUs")
url:
On Sun, Oct 18, 2020 at 11:51:19PM +0200, Daniel Vetter wrote:
> On Sun, Oct 18, 2020 at 10:45 PM Peilin Ye wrote:
> > I'm confused, I see it on LKML in the link above. Sure I'll resend soon.
>
> My brain didn't work, sorry about the confusion.
>
> I'll pick up the patches tomorrow, probably not
Hi Nathan,
On 10/13/20 4:39 AM, Nathan Chancellor wrote:
> As it stands now, the vdso32 Makefile hardcodes the linker to ld.bfd
> using -fuse-ld=bfd with $(CC). This was taken from the arm vDSO
> Makefile, as the comment notes, done in commit d2b30cd4b722 ("ARM:
> 8384/1: VDSO: force use of BFD
SLAB objects which outlive their descendant memcg are moved to their
parent memcg where they may be uncharged. However if they are moved to
the root memcg and use_hierarchy=0, uncharging will result in negative
page counter values. This is because when use_hierarchy=0, the root
memcg's page counter
+Morten
On Fri, Oct 16, 2020 at 11:27:02PM +0800, Jonathan Cameron wrote:
> Both ACPI and DT provide the ability to describe additional layers of
> topology between that of individual cores and higher level constructs
> such as the level at which the last level cache is shared.
> In ACPI this can
This patch set is to move tsc testing from x86 specific to common
testing case. Since Arnaldo found the building failure for patch set
v4 [1], the first four patches have been merged but the last two patches
were left out; this patch set is to resend the last two patches with
fixed the building fa
So far tsc is enabled on x86_64, i386 and Arm64 architectures, add
checking helper to skip this testing for other architectures.
Signed-off-by: Leo Yan
---
tools/perf/tests/builtin-test.c | 1 +
tools/perf/tests/perf-time-to-tsc.c | 13 +
tools/perf/tests/tests.h| 1
x86 arch provides the testing for conversion between tsc and perf time,
the testing is located in x86 arch folder. Move this testing out from
x86 arch folder and place it into the common testing folder, so allows
to execute tsc testing on other architectures (e.g. Arm64).
This patch removes the i
Le 16/10/2020 à 17:27, Jonathan Cameron a écrit :
> Both ACPI and DT provide the ability to describe additional layers of
> topology between that of individual cores and higher level constructs
> such as the level at which the last level cache is shared.
> In ACPI this can be represented in PPTT as
On Mon, Oct 12, 2020 at 07:03:25PM +0200, Michal Suchánek wrote:
> > > >
> > > > > Also the boards that do not have the flsh are either broken or
> > > > > obsolete.
> > > >
> > > > Making general statements without arguments doesn't really make it true
> > > > though. Plenty of boards to have fl
On Mon, Oct 19, 2020 at 11:47:10AM +0200, Marek Szyprowski wrote:
> Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM:
> dts: exynos: Remove Exynos5440"). Drop the obsolete bindings for
> exynos5440-pcie.
>
> Signed-off-by: Marek Szyprowski
> ---
> .../bindings/pci/samsung,
On 10/15/20 11:07 PM, Michael Auchter wrote:
> This patch adds an extcon driver for the TI TUSB320 USB Type-C device.
> This can be used to detect whether the port is configured as a
> downstream or upstream facing port.
>
> Signed-off-by: Michael Auchter
> ---
> Changes since v1:
> - Drop licens
On Mon, Oct 19, 2020 at 11:47:11AM +0200, Marek Szyprowski wrote:
> From: Jaehoon Chung
>
> Add dt-bindings for the Samsung Exynos PCIe controller (Exynos5433
> variant).
The title has typo and actually entire "Doc" should be dropped. Just
"dt-bindings: pci:". This applies to all DT patches.
>
On Mon, Oct 19, 2020 at 02:54:11PM +0530, Viresh Kumar wrote:
> On 19-10-20, 10:17, Sudeep Holla wrote:
> > On Mon, Oct 19, 2020 at 10:28:27AM +0530, Viresh Kumar wrote:
> > > On 16-10-20, 12:12, Sudeep Holla wrote:
> > > > On Fri, Oct 16, 2020 at 07:00:21AM +0100, Sudeep Holla wrote:
> > > > > On
Mikhail reported a lockdep spat detailing how __zram_bvec_read() and
__zram_bvec_write() use zstrm->lock and zspage->lock in opposite order.
Reported-by: Mikhail Gavrilov
Signed-off-by: Peter Zijlstra (Intel)
Tested-by: Mikhail Gavrilov
---
drivers/block/zram/zram_drv.c | 8 +---
1 file
On Mon, Oct 19, 2020 at 11:47:12AM +0200, Marek Szyprowski wrote:
> From: Jaehoon Chung
>
> Add dt-bindings for the Samsung Exynos PCIe PHY controller (Exynos5433
> variant).
>
> Signed-off-by: Jaehoon Chung
> [mszyprow: updated the binding to latest driver changes, rewrote it in yaml,
>
On Mon, Oct 19, 2020 at 11:47:13AM +0200, Marek Szyprowski wrote:
> From: Jaehoon Chung
>
> Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM:
> dts: exynos: Remove Exynos5440"). Rework this driver to support PCIe PHY
> variant found in the Exynos5433 SoCs.
>
> Signed-off-b
For the exclusive reference page, the non-atomic operations is enough,
so replace them to non-atomic operations.
Signed-off-by: Muchun Song
---
include/linux/page-flags.h | 2 ++
mm/memory.c| 4 ++--
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/linux/pag
From: Ahmed S. Darwish
The usage of in_interrupt() in drivers is phased out for various reasons.
Various comments use !in_interrupt() to describe calling context for probe()
and remove() functions. That's wrong because the calling context has to be
preemptible task context, which is not what !in
in_interrupt() is a pretty vague context description as it means: hard
interrupt, soft interrupt or bottom half disabled regions.
Replace the vague comment with a proper reasoning why spin_lock_irqsave()
needs to be used.
Signed-off-by: Ahmed S. Darwish
Signed-off-by: Sebastian Andrzej Siewior
isp1362_show_regs() is a debugging-only function, with no call sites. It
prints the cached value of the HCuPINTENB register if in_interupt() is
true, otherwise it reads the actual register content.
The usage of in_interrupt() in drivers is phased out and Linus clearly
requested that code which cha
Folks,
in the discussion about preempt count consistency accross kernel configurations:
https://lore.kernel.org/r/20200914204209.256266...@linutronix.de/
Linus clearly requested that code in drivers and libraries which changes
behaviour based on execution context should either be split up so t
On 18/10/2020 21:30, Fabien Parent wrote:
As the binding documentation says, #mbox-cells must have a value of 2,
but the example use a value 3. The MT8173 device tree correctly use
mbox-cells = <2>. This commit fixes the example.
Signed-off-by: Fabien Parent
---
Fixes: 19d8e335d58a ("dt-bi
usb_hcd_msp_remove() has a pdev argument which isn't used and the function
is used only within this file.
Remove pdev and make usb_hcd_msp_remove() static.
Signed-off-by: Thomas Gleixner
---
V2: Split out from comments patch
---
drivers/usb/host/ehci-pmcmsp.c |4 ++--
1 file changed, 2 inse
From: Ahmed S. Darwish
The usage of in_interrupt() in drivers is phased out for various reasons.
Documenting calling contexts of functions with 'in_interrupt()' or
'!in_interrupt()' is imprecise: For a function which might sleep the
condition is preemptible task context, which is not what '!in_i
701 - 800 of 1116 matches
Mail list logo
