Hi Pavel, Thanks for the feedback. OK, will send v2. By adding needed defines in kernel.h and replacing driver include math.h->kernel.h Cheers, Biju

Hi! values->value? This code is quite tricky. AFAICT it is correct, but calling rzg2l_wdt_stop() instead would make it more readable. Best regards, Pavel -- DENX Software Engineering GmbH,

Hi! Two spaces, plus "capture times" does not really explain much. According to CodingStyle, /* should be on separate line. Typo, should be "calibration" I guess. Best regards, Pavel --

Hi! I'm not sure what machine "rpc" is. It is quite probable it does not really need armv3 instruction set. We could. Even better would be running 4.4-stable with same configs, and see if they fail,

Hi! This is rather intrusive for two lines which we really need, and may cause rejects in future. I'd suggest identifying the defines needed by the driver, and just adding those. kernel.h would be

Hi Jan-San, I have shared the below MR patch request that covers the documentation steps to verify IEC Layer Test on CIP security image but unable to see this request in mailing list. Kindly let me

Hi Nobuhoro-San, Sorry for the noise. It is random issue. I cannot reproduce the issue now. The build is ok now. Cheers, Biju

Hi Pavel and Nobuhiro, I get build error[2] with defconfig with this commit id[1]. Q1) have you seen this issue? [1] commit 19dd4538e81e4019bc96ac6521af3a4ec93e110c (HEAD -> test, tag:

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc kselftest-futex: 3 runs, 2 regressions (v5.10.129-cip12-59-ge5b19636ca9c4) Regressions Summary ------------------- platform | arch |

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline: 121 runs, 10 regressions (v5.10.129-cip12-59-ge5b19636ca9c4) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline-nfs: 29 runs, 4 regressions (v5.10.129-cip12-59-ge5b19636ca9c4) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline-cip-nfs: 4 runs, 1 regressions (v5.10.129-cip12-59-ge5b19636ca9c4) Regressions Summary ------------------- platform | arch | lab |

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc build: 190 builds: 3 failed, 187 passed, 4 errors, 10 warnings (v5.10.129-cip12-59-ge5b19636ca9c4) Full Build Summary:

Hi, Yes, this problem happens sometime. And I don't know why. All emails have arrived, so I am getting a patch from MUA and applying it. Best regards, Nobuhiro

Hi All, I can see patch#2 and #3 of the series landed in [1], but it is not showing up in [2] and [3]. Any thoughts on this issue? [1] https://lists.cip-project.org/g/cip-dev/topics [2]

commit 4055ee81009e606e830af1acd9e2e35a36249713 upstream. This patch adds support for set_timeout callback. Once WDT is started, the WDT cycle setting register(WDTSET) can be updated only after

commit f43e6ddbd7d7b63b9e71927a1f50860f8d55f9cc upstream. This patch uses the force reset(WDTRSTB) for triggering WDT reset for restart callback. This method(ie, Generate Reset (WDTRSTB) Signal

commit baf1aace9ad15401f08e048a7f1fdec79821bc61 upstream. If reset_control_deassert() fails, then we won't be able to access the device registers. Therefore check the return code

commit 33d04d0fdba9fae18c7d58364643d2c606a43dba upstream. Both rzg2l_wdt_probe() and rzg2l_wdt_start() calls reset_control_ deassert() which results in a reset control imbalance. This patch fixes

commit e4cf89596c1f1e33309556699f910ced4abbaf44 upstream. This patch fixes the issue 'BUG: Invalid wait context' during restart() callback by using clk_prepare_enable() instead of