Add Support for ArteryTek SoC's HAL driver

[Maxjta]

Origin

Q: Name of project hosting the original open source code, Provide a link to the source
A: The HAL driver link (https://github.com/Maxjta/hal_at32.git)
A: The zephyr device driver PR 86694.

Purpose

Q: Brief description of what this software does
A: This software support ArteryTek Soc's HAL driver.

Mode of integration

Q: Describe whether you'd like to integrate this external component in the main tree
or as a module, and why. If the mode of integration is a module, suggest a
repository name for the module

A: Arterytek is an SoC manufacturer that supports many models. Currently, many customers want to use Zephyr OS and integrate Arterytek SoC into the Zephyr OS system. We hope to creating a repo named hal_at32 to better support Zephyr OS in the future.

Maintainership

Q: List the person(s) that will be maintaining the integration of this external code
for the foreseeable future. Please use GitHub IDs to identify them. You can
choose to identify a single maintainer only or add collaborators as well

A: maintainer: Maxjta

Pull Request

Q: Pull request (if any) with the actual implementation of the integration, be it
in the main tree or as a module (pointing to your own fork for now). Make sure
the PR is correctly labeled as "DNM"

A: The zephyr device driver PR 86694.

Description

Long description that will help reviewers discuss suitability of the
component to solve the problem at hand (there may be a better options
available.)

Q: What is its primary functionality (e.g., SQLLite is a lightweight
database)?
A: Provides Arterytek SoC hardware driver interface.

Q: What problem are you trying to solve? (e.g., a state store is
required to maintain ...)
A: Add support Arterytek SoC's driver in Zephry OS.

Q: Why is this the right component to solve it (e.g., SQLite is small,
easy to use, and has a very liberal license.)
A:This is a Standard and efficient hardware driver for Arterytek SoC’s.

Security

Q: Does this component include any cryptographic functionality?
If so, please describe the cryptographic algorithms and protocols used.
A： ArteryTek HAL driver is not have cryptographic functionality.

Dependencies

What other components does this package depend on?

Q: Will the Zephyr project have a direct dependency on the component, or
will it be included via an abstraction layer with this component as a
replaceable implementation?
A: The Zephyr project direct dependency on the component hal_at32.

Revision

Q: Version or SHA you would like to integrate initially
A: The hal_at32 Revision(5b427d057902e13f7036f0f8d9221a0d1cb919cd)

License

Q: Please use an SPDX identifier (https://spdx.org/licenses/), such as
BSD-3-Clause
A: Yes, the license is BSD 3-Clause License

[github-actions]

Hi @Maxjta! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

[nashif]

files like https://github.com/Maxjta/hal_at32/blob/main/at32f423/drivers/inc/at32f423_adc.h#L6 have a custom license header, this is not BSD-3 clause.

[nashif]

Also, there is apache licensed files

https://github.com/Maxjta/hal_at32/blob/main/common_source/at32_hal_udc.c

[Maxjta]

@nashif
(https://github.com/Maxjta/hal_at32/blob/main/at32f423/drivers/inc/at32f423_adc.h#L6)
at32f423_adc.h: the driver part is the standard library of Arterytek. This part is open source. Does this part need to be modified?

(https://github.com/Maxjta/hal_at32/blob/main/common_source/at32_hal_udc.c)
Is this part of the apache license acceptable? Or do I need to modify this part of the license to BSD-3.

[nashif]

you do not need to modify the licenses, but any licenses included in the HAL need to be documented and all applicable licenses need to be listed as part of the original request.

Please use SPDX to mark all files with the appropriate licenses and avoid using custom text for licenses.

[Maxjta]

@nashif Thank‘s.

I will modify the hal_at32/LICENCE statement and declare this license as the Apache-2.0 and arterytek custom licenses. Is this OK?