Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-13 Thread Zumeng Chen
ynqmp/kernel-source/ zchen@pek-lpggp4:$ ls arch   certs    CREDITS  Documentation  fs   init  Kbuild kernel  LICENSES Makefile  net samples  security  tools virt block  COPYING  crypto   drivers    include  ipc   Kconfig lib MAINTAINERS  mm    README  scripts  sound usr

Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-13 Thread Zumeng Chen
Ping On 6/11/19 9:40 AM, Zumeng Chen wrote: Hi Bruce, I just finished insane check to build xilinx-zynqmp machine with core-image-sato, all passed with boot process. Could you please help me to create a branch like that standard/xilinx-zynqmp in the following git repo. in convenient

Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-10 Thread Zumeng Chen
/standard/base, thanks~ git://git.yoctoproject.org/linux-yocto-dev Cheers, Zumeng On 6/11/19 7:37 AM, Zumeng Chen wrote: On 6/10/19 9:37 PM, Bruce Ashfield wrote: On Sun, Jun 9, 2019 at 8:00 PM Zumeng Chen wrote: Sounds I like mean, no, I just talk the reality, Xilinx did like the following

Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-10 Thread Zumeng Chen
On 6/10/19 9:37 PM, Bruce Ashfield wrote: On Sun, Jun 9, 2019 at 8:00 PM Zumeng Chen wrote: Sounds I like mean, no, I just talk the reality, Xilinx did like the following: https://github.com/Xilinx/meta-xilinx/tree/master/meta-xilinx-bsp/recipes-kernel/linux/xilinx-kmeta/bsp I think

Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-09 Thread Zumeng Chen
help me to merge zynqmp part from meta-xilinx, I'll take care the rest. Cheers, Zumeng On 6/6/19 2:55 PM, Zumeng Chen wrote: Yes, I checked it, it seems only for zynq 7000 and its special interfaces. I bet the original author didn't mean to share something for both arm64 and 32

Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-06 Thread Zumeng Chen
Yes, I checked it, it seems only for zynq 7000 and its special interfaces. I bet the original author didn't mean to share something for both arm64 and 32 :) When I created the structure I had intended for it to include the zynqmp related configs. I even had some yocto-kernel-cache patches

Re: [linux-yocto] v2 RR for xilinx-zynqmp bsp for build and boot

2019-06-05 Thread Zumeng Chen
On 6/6/19 9:18 AM, Zumeng Chen wrote: Hi Bruce, Here are the v2 changes for scc/cfg: *) Create the minimum cfg set for arm/arm64, and include it *) Remove those CFG only existed in Xilinx SDK. *) Include hotplug scc *) Remove some non-validation features, like remoteproc

[linux-yocto] [PATCH 1/2] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-05 Thread Zumeng Chen
This patch is to add scc/cfg meta to build and boot zcu102 board with the bsp of xilinx-zynqmp. Signed-off-by: Zumeng.Chen --- bsp/xilinx-zynqmp/xilinx-zynqmp-standard.scc | 8 ++ bsp/xilinx-zynqmp/xilinx-zynqmp.cfg | 164 +++

[linux-yocto] v2 RR for xilinx-zynqmp bsp for build and boot

2019-06-05 Thread Zumeng Chen
it, trust me :) No kernel build warnings. And the boot process is still OK. Cheers, Zumeng commit 30cc68182cdd6254b58795fb3afedaceb6949a70 Author: Zumeng Chen Date: Thu Jun 6 08:44:57 2019 +0800 xilinx-zynqmp: add the basic support xilinx-zynqmp This patch is to add scc/cfg meta

[linux-yocto] [PATCH 2/2] power: create the minimum set of cpu idle and cpufreq scaling for arm/arm64

2019-06-05 Thread Zumeng Chen
This patch is to create the minimum set for cpu idle/freq scaling, which is ok to both arm and arm64 with DT enablement. And we leave more specific features to the end users. Signed-off-by: Zumeng.Chen --- features/power/arm.cfg | 7 +++ features/power/arm.scc | 4 2 files changed, 11

Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-05 Thread Zumeng Chen
On 6/6/19 1:19 AM, Bruce Ashfield wrote: On Wed, Jun 5, 2019 at 4:02 AM Zumeng Chen wrote: This patch is to add scc/cfg meta to build and boot zcu102 board with the bsp of xilinx-zynqmp. See some questions below. Signed-off-by: Zumeng.Chen --- bsp/xilinx-zynqmp/xilinx-zynqmp

Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-05 Thread Zumeng Chen
On 6/5/19 11:16 PM, Bruce Ashfield wrote: On Wed, Jun 5, 2019 at 4:08 AM Zumeng Chen wrote: Hi Bruce, Forget this party :) xilinx-zynqmp is arm64 BSP with cortexA53, and it seems stable in mainline to build and boot, so I add it into linux-yocto-dev and yocto-kernel-cache. This email

Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-05 Thread Zumeng Chen
PM, Zumeng Chen wrote: This patch is to add scc/cfg meta to build and boot zcu102 board with the bsp of xilinx-zynqmp. Signed-off-by: Zumeng.Chen --- bsp/xilinx-zynqmp/xilinx-zynqmp-standard.scc | 8 + bsp/xilinx-zynqmp/xilinx-zynqmp.cfg | 227 +++ bsp/xilinx

[linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

2019-06-05 Thread Zumeng Chen
This patch is to add scc/cfg meta to build and boot zcu102 board with the bsp of xilinx-zynqmp. Signed-off-by: Zumeng.Chen --- bsp/xilinx-zynqmp/xilinx-zynqmp-standard.scc | 8 + bsp/xilinx-zynqmp/xilinx-zynqmp.cfg | 227 +++

Re: [linux-yocto] [yocto] yaffs: fix a potential memory leakage and missed put_mtd_device

2017-05-01 Thread Zumeng Chen
On 05/01/2017 11:23 AM, Bruce Ashfield wrote: On 2017-04-27 11:37 PM, Zumeng Chen wrote: Hi Bruce, This patch is to fix a missed put_mtd_device and potential memory fix for yaffs based on standard/base. Looks good to me. What kernel versions is this for ? I tried it on 4.10 and it applied

[linux-yocto] [yocto] yaffs: fix a potential memory leakage and missed put_mtd_device

2017-04-27 Thread Zumeng Chen
Hi Bruce, This patch is to fix a missed put_mtd_device and potential memory fix for yaffs based on standard/base. Cheers, Zumeng commit d9b0a935f7a778a85b029f3d6c187d40fe2b9c39 Author: Zumeng Chen <zumeng.c...@windriver.com> Date: Fri Apr 28 10:44:41 2017 +0800 yaffs: fix pot

[linux-yocto] [PATCH 1/1] yaffs: fix potential memory leakage and codes redundant

2017-04-27 Thread Zumeng Chen
put_mtd_device is match to get_mtd_device to decount users, and also fix the potential memory leakage when failure happens. Signed-off-by: Zumeng Chen <zumeng.c...@windriver.com> --- fs/yaffs2/yaffs_vfs.c | 25 - 1 file changed, 12 insertions(+), 13 deletions(-)

[linux-yocto] v2 RR for potential kernel crash from commit efb5fea23

2015-01-08 Thread Zumeng Chen
Hi, This is v2 as Paul's comments, please take them if any. Cheers, Zumeng -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [v2 PATCH 1/7] workqueue: use manager lock only to protect worker_idr

2015-01-08 Thread Zumeng Chen
Heo t...@kernel.org Signed-off-by: Zumeng Chen zumeng.c...@windriver.com --- kernel/workqueue.c | 34 ++ 1 file changed, 6 insertions(+), 28 deletions(-) diff --git a/kernel/workqueue.c b/kernel/workqueue.c index b4defde..701f2d2 100644 --- a/kernel/workqueue.c

[linux-yocto] [v2 PATCH 3/7] workqueue: async worker destruction

2015-01-08 Thread Zumeng Chen
-off-by: Tejun Heo t...@kernel.org Signed-off-by: Zumeng Chen zumeng.c...@windriver.com --- kernel/workqueue.c | 62 ++-- 1 file changed, 41 insertions(+), 21 deletions(-) diff --git a/kernel/workqueue.c b/kernel/workqueue.c index 3db9b65..593287d

[linux-yocto] [v2 PATCH 6/7] workqueue: convert worker_idr to worker_ida

2015-01-08 Thread Zumeng Chen
worker_detach_from_pool() into worker_thread(). tj: Minor description updates. Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com Signed-off-by: Tejun Heo t...@kernel.org Signed-off-by: Zumeng Chen zumeng.c...@windriver.com --- kernel/workqueue.c | 20 1 file changed, 8 insertions(+), 12

[linux-yocto] [PATCH 3/7] workqueue: async worker destruction

2014-12-19 Thread Zumeng Chen
From: Lai Jiangshan la...@cn.fujitsu.com worker destruction includes these parts of code: adjust pool's stats remove the worker from idle list detach the worker from the pool kthread_stop() to wait for the worker's task exit free the worker struct We can

[linux-yocto] [PATCH 1/7] workqueue: use manager lock only to protect worker_idr

2014-12-19 Thread Zumeng Chen
From: Lai Jiangshan la...@cn.fujitsu.com worker_idr is highly bound to managers and is always/only accessed in manager lock context. So we don't need pool-lock for it. Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com Signed-off-by: Tejun Heo t...@kernel.org (cherry picked from commit

[linux-yocto] [PATCH 2/7] workqueue: destroy_worker() should destroy idle workers only

2014-12-19 Thread Zumeng Chen
From: Lai Jiangshan la...@cn.fujitsu.com We used to have the CPU online failure path where a worker is created and then destroyed without being started. A worker was created for the CPU coming online and if the online operation failed the created worker was shut down without being started. But

[linux-yocto] [PATCH 4/7] workqueue: destroy worker directly in the idle timeout handler

2014-12-19 Thread Zumeng Chen
From: Lai Jiangshan la...@cn.fujitsu.com Since destroy_worker() doesn't need to sleep nor require manager_mutex, destroy_worker() can be directly called in the idle timeout handler, it helps us remove POOL_MANAGE_WORKERS and maybe_destroy_worker() and simplify the manage_workers() After

[linux-yocto] RR for potential kernel crash from commit efb5fea23

2014-12-19 Thread Zumeng Chen
Hi Bruce, As we discussed before, these patch series intended to fix a potential kernel crash, which is due to a invalid mm context from worker_create, and it is introduced by efb5fea2, which is a continuation of efforts trying to optimize find_vma(), avoiding potentially expensive rbtree

Re: [linux-yocto] [PATCH 12/57] arch/arm/mach-axxia: Updates to the VMFS File System

2014-03-20 Thread Zumeng Chen
On 2014年03月19日 05:43, Jacques, John M (John) wrote: Build failure. You guys are going to teach me to write comments yet! Hi Charlie, I think you might mis-understand Bruce for his comments, in most situation, you had better go through your patch again because we can get any useful