Add ENE KB1200 SOC

[ene-steven]

ene_kb1200_evb Zephyr doc preview

[gmarull]

please split into meaningful commits, see https://docs.zephyrproject.org/latest/contribute/guidelines.html

[ene-steven]

please split into meaningful commits, see https://docs.zephyrproject.org/latest/contribute/guidelines.html

KB1200 is a new chip, there is no code on zephyrproject.
I've minimized the code that can be built and run on the EVB board.
I don't know how to split into meaningful commits.

[ycsin]

I don't know how to split into meaningful commits.

Thanks for this PR. You can probably consider splitting the commit into:

1. Devicetree bindings
2. SoC
3. Board
4. Drivers (gpio, i2c, spi, ...)

Please have a look at #56370.

Lastly, the current commit title doesn't conform to Zephyr contribution guidelines (this will fail in the GitHub CI test), you will also need to provide meaningful commit message about this change, please see https://docs.zephyrproject.org/latest/contribute/guidelines.html

[ycsin]

just some of the obvious ones

[ycsin]

The title should be something like:

drivers: pinctrl: pinctrl device driver for ENE KB1200

you do not need those squared brackets.

Personally I wouldn't repeat the 'pinctrl' twice:

drivers: pinctrl: initial device driver for ENE KB1200

[github-actions]

Hi @ene-steven!
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! 🪁

[carlescufi]

@ene-steven thank you for your patience and perseverance.