[65183] sam0: initialize GCLK2 in wdt_sam0_init

[vlm-laba7]

Initialize GCLK2 to output 1.024kHz required by watchdog timer.

Fixes: #65183

[github-actions]

Hello @vlm-laba7, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

[henrikbrixandersen]

Thanks! Please reformat the Git commit log to follow the project standard (please see https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-message-guidelines) and add a DCO sign-off (see https://docs.zephyrproject.org/latest/contribute/guidelines.html#developer-certification-of-origin-dco).

[attie-argentum]

Thanks for the patch!

This would probably fit better in soc/arm/atmel_sam0/common/soc_samd2x.c, where GCLK Gen 2 is indeed marked up for the WDT.

[nandojve]

Hi @vlm-laba7 ,

Please, rebase on top of main and make sure CI is green.

@attie-argentum , could you revisit this?

[nandojve]

Hi @vlm-laba7 ,

Make sure you fix compliance check otherwise it is not possible to merge your PR:

Error: See https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines for more details

 d5b2a263d918263113ce3203a5291c5b04f0bfbd: author email (vlm <[email protected]>) needs to match one of the signed-off-by entries.
d5b2a[26](https://github.com/zephyrproject-rtos/zephyr/actions/runs/6877251017/job/18754400492?pr=65211#step:9:27)3d918263113ce3203a5291c5b04f0bfbd: author email (vlm <[email protected]>) does not follow the syntax: First Last <email>.

[vlm-laba7]

@nandojve done

[stephanosio]

Signed-off-by: Vlad Laba7 [email protected]

@vlm-laba7 Unless your last name actually contains 7, please use your full name as required by the DCO policy.

[vlm-laba7]

@stephanosio sorry, I prefer not to use any names on this account - feel free to author this commit

[nandojve]

Hi @kartben,

@stephanosio sorry, I prefer not to use any names on this account - feel free to author this commit

Do you know who can help to clarify this?

[kartben]

feel free to author this commit

Unfortunately I don't think we can accept contributions not covered by the DCO, as that's how the contributor acknowledges they have the rights to contribute the code to Zephyr under the Apache 2.0 License.

[nandojve]

feel free to author this commit

Unfortunately I don't think we can accept contributions not covered by the DCO, as that's how the contributor acknowledges they have the rights to contribute the code to Zephyr under the Apache 2.0 License.

This means that someone should open another PR with a solution and we need to close this, right?

[martinjaeger]

feel free to author this commit

Unfortunately I don't think we can accept contributions not covered by the DCO, as that's how the contributor acknowledges they have the rights to contribute the code to Zephyr under the Apache 2.0 License.

This means that someone should open another PR with a solution and we need to close this, right?

You can also edit this PR in place as a maintainer. Just add @vlm-laba7's repo as a new remote in git and force-push to the branch as usual.

[attie-argentum]

Untested (I don't have the hardware), but looks sensible to me - thanks!

[github-actions]

Hi @vlm-laba7!
Congratulations on getting your very first Zephyr pull request merged 🎉🥳. This is a fantastic achievement, and we're thrilled to have you as part of our community!

To celebrate this milestone and showcase your contribution, we'd love to award you the Zephyr Technical Contributor badge. If you're interested, please claim your badge by filling out this form: Claim Your Zephyr Badge.

Thank you for your valuable input, and we look forward to seeing more of your contributions in the future! 🪁