Add ARCH_BST for bst SoC series support.

Signed-off-by: Ge Gordon <gordon.ge@bst.ai>
Signed-off-by: Albert Yang <yangzh0906@thundersoft.com>
---
Changes for v2:
- Placed the configuration entry in correct alphabetical order
- Used generic family name (ARCH_BST) instead of SoC-specific naming
- Followed upstream kernel naming and description conventions
---
 arch/arm64/Kconfig.platforms | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index a541bb029aa4..4412d54b224d 100644
--- a/arch/arm64/Kconfig.platforms
+++ b/arch/arm64/Kconfig.platforms
@@ -106,6 +106,14 @@ config ARCH_BLAIZE
 	help
 	  This enables support for the Blaize SoC family
 
+config ARCH_BST
+	bool "Black Sesame Technologies SoC Family"
+	help
+	  This enables support for Black Sesame Technologies (BST) SoC family.
+	  BST produces automotive-grade system-on-chips for intelligent driving,
+	  focusing on computer vision and AI capabilities. The BST C1200 family
+	  includes SoCs for ADAS and autonomous driving applications.
+
 config ARCH_EXYNOS
 	bool "Samsung Exynos SoC family"
 	select COMMON_CLK_SAMSUNG
@@ -402,4 +410,6 @@ config ARCH_ZYNQMP
 	help
 	  This enables support for Xilinx ZynqMP Family
 
+
+
 endmenu # "Platform selection"
-- 
2.25.1

On 02/07/2025 11:44, Albert Yang wrote:
> Add ARCH_BST for bst SoC series support.
> 
> Signed-off-by: Ge Gordon <gordon.ge@bst.ai>
> Signed-off-by: Albert Yang <yangzh0906@thundersoft.com>


All your patches come in some big delays (this one came 2.5h later).
Maybe there is something with mail server on your side?


> ---
> Changes for v2:
> - Placed the configuration entry in correct alphabetical order
> - Used generic family name (ARCH_BST) instead of SoC-specific naming
> - Followed upstream kernel naming and description conventions
> ---
>  arch/arm64/Kconfig.platforms | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index a541bb029aa4..4412d54b224d 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -106,6 +106,14 @@ config ARCH_BLAIZE
>  	help
>  	  This enables support for the Blaize SoC family
>  
> +config ARCH_BST
> +	bool "Black Sesame Technologies SoC Family"
> +	help
> +	  This enables support for Black Sesame Technologies (BST) SoC family.
> +	  BST produces automotive-grade system-on-chips for intelligent driving,
> +	  focusing on computer vision and AI capabilities. The BST C1200 family
> +	  includes SoCs for ADAS and autonomous driving applications.
> +
>  config ARCH_EXYNOS
>  	bool "Samsung Exynos SoC family"
>  	select COMMON_CLK_SAMSUNG
> @@ -402,4 +410,6 @@ config ARCH_ZYNQMP
>  	help
>  	  This enables support for Xilinx ZynqMP Family
>  
> +
> +

Why this change?

Best regards,
Krzysztof

Hi Krzysztof,

Thank you for the feedback.

> All your patches come in some big delays (this one came 2.5h later).
> Maybe there is something with mail server on your side?

You are right, there seems to be an issue with mail delivery timing. I will investigate this and consider using b4 send for future submissions to ensure reliable delivery.

> Why this change?

You are absolutely correct to point this out. The extra blank lines at the end of the file were added accidentally and serve no purpose. I have removed them.

Changes made:
1. Removed the unnecessary blank lines at the end of Kconfig.platforms
2. Corrected changelog placement:
   - Initially I incorrectly placed changelog in the commit message
   - Per Linux kernel documentation, changelog should be placed after the "---" separator
   - Removed changelog from commit message to follow proper kernel conventions
   - The changelog will be included after "---" when sending patches via git format-patch

The updated commit properly describes the purpose and scope of the configuration option without any extraneous whitespace changes, and follows correct Linux kernel commit message format.

Best regards,
Albert Yang