Yes, Maxim is working for a project of us, and I asked him to propose these backports for CIP. They will likely become relevant for other boards as well because the bootloader-started watchdog is a

[...] Are you working for Siemens on this? Can you provide the config you are using? The reason I ask is that CIP kernel branches will have hardware support limited to the needs of members.

Hello Ben, Thank you! Thanks for checking, it's good to know that you've got the h/w up and running. Yep. shmobile_defconfig omits EXT4_FS. I keep meaning to ask why... Kind regards, Chris

Hi Daniel, once you want to release Project-X, besides moving the gitlab project away from cip-playground, remember that you need to move the content to the CIP wiki. We are not using the gitlab wiki

Hi Agustin Benito Bethencourt <agustin.benito@...> writes: We should also report that #139 https://gitlab.com/cip-project/cip-testing/testing/issues/139 is preventing the provisioning of

Hi, we will held our tech meeting in the usual time: 10 UTC Link to the video chat room:

Morning! Agustin Benito Bethencourt <agustin.benito@...> writes: Yes, the initramfs and lava to 2017-7 updates are in master, lava is working fine, remaining issues are with a recent

This all looks good. I've applied these patches locally and will push out soon. I booted it on my board and confirm that Ethernet and eMMC are now working. However, I had to enable EXT4_FS because

From: Sebastian Reichel <sebastian.reichel@...> Backport from kernel.org, upstream commit 2501b015313f On some systems its desirable to have watchdog reboot the system when it does not

From: Guenter Roeck <linux@...> Backport from kernel.org, upstream commit 3c10bbde10fe WDOG_HW_RUNNING indicates that the hardware watchdog is running while the watchdog device is closed.

From: Wei Yongjun <yongjun_wei@...> Backport from kernel.org, upstream commit 138913cb632b Fix the error handling paths of watchdog_dev_init(). Signed-off-by: Wei Yongjun

From: Rasmus Villemoes <rasmus.villemoes@...> Backport from kernel.org, upstream commit 3fbfe9264756 If the driver indicates that the watchdog is running, the framework should feed it until

From: Pratyush Anand <panand@...> Backport from kernel.org, upstream commit 1894cad9bf2c When max_hw_heartbeat_ms has a none zero value, max_timeout is not used. So it's value can be 0. In

From: Guenter Roeck <linux@...> Backport from kernel.org, upstream commit e1f30282a1d3 lockdep reports the following circular locking

From: Guenter Roeck <linux@...> Backport from kernel.org, upstream commit 11d7aba9ceb7 The watchdog infrastructure now supports handling watchdog keepalive if the watchdog is running while

From: Guenter Roeck <linux@...> Backport from kernel.org, upstream commit d0684c8a9354 Not all hardware watchdogs can be stopped. The driver for such watchdogs would typically only set the

From: Guenter Roeck <linux@...> Backport from kernel.org, upstream commit ee142889e32f The WDOG_HW_RUNNING flag is expected to be set by watchdog drivers if the hardware watchdog is

From: Guenter Roeck <linux@...> Backport from kernel.org, upstream commit 664a39236e71 Introduce an optional hardware maximum heartbeat in the watchdog core. The hardware maximum heartbeat

Hello Ben, This series contains * backport of patches of watchdog core infrastructure supporting handling watchdog keepalive. * imx21_wdt converted to use infrastructure triggered keepalives. *

Hi, Ah, there are further agenda issue. I understand. No problem. As soon as Robert is back and landed, he (or myself) will contact you directly with the info. I see. -- Agustin Benito