[PATCH v3 1/6] at91: kernel: bump to 5.10

[Hauke Mehrtens]

On 9/10/21 11:56 AM, Claudiu.Beznea at microchip.com wrote:
> On 09.09.2021 22:52, Hauke Mehrtens wrote:
>>> Bump at91 targets to kernel v5.10. With this patches and files for
>>> wb45n and wb50n were removed as they are now included in upstream
>>> kernel. Along with this:
>>> - the kernel config for sam9x targets has been refreshed (with
>>>     make kernel_menuconfig + save);
>>> - CONFIG_ARCH_AT91 and specific sam9x SoCs (AT91RM9200, AT91SAM9,
>>>     SAM9X60) has been enabled such that sam9x SoCs to be able to boot.
>>>
>>> Signed-off-by: Claudiu Beznea <claudiu.beznea at microchip.com>
>>> ---
>>>    target/linux/at91/Makefile                    |   2 +-
>>>    .../at91/files/arch/arm/boot/dts/wb45n.dts    | 220 ------------------
>>>    .../at91/files/arch/arm/boot/dts/wb50n.dts    | 113 ---------
>>>    .../at91/files/arch/arm/boot/dts/wb50n.dtsi   | 205 ----------------
>>>    target/linux/at91/image/sam9x.mk              |   1 +
>>>    target/linux/at91/image/sama5.mk              |   1 +
>>>    .../101-ARM-at91-build-dtb-for-q5xr5.patch    |  10 +
>>>    .../101-ARM-at91-build-dtb-for-q5xr5.patch    |  10 -
>>>    .../102-ARM-at91-build-dtb-for-wb45n.patch    |  12 -
>>>    ...2-ARM-at91-wb45n-fix-duplicate-label.patch |  20 --
>>>    .../103-ARM-at91-build-dtb-for-wb50n.patch    |  12 -
>>>    ...3-ARM-at91-wb50n-fix-duplicate-label.patch |  39 ----
>>>    target/linux/at91/sam9x/config-default        | 105 ++++-----
>>>    13 files changed, 57 insertions(+), 693 deletions(-)
>>>    delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb45n.dts
>>>    delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb50n.dts
>>>    delete mode 100644 target/linux/at91/files/arch/arm/boot/dts/wb50n.dtsi
>>>    create mode 040000 target/linux/at91/patches-5.10
>>>    create mode 100644
>>> target/linux/at91/patches-5.10/101-ARM-at91-build-dtb-for-q5xr5.patch
>>>    delete mode 040000 target/linux/at91/patches-5.4
>>>    delete mode 100644
>>> target/linux/at91/patches-5.4/101-ARM-at91-build-dtb-for-q5xr5.patch
>>>    delete mode 100644
>>> target/linux/at91/patches-5.4/102-ARM-at91-build-dtb-for-wb45n.patch
>>>    delete mode 100644
>>> target/linux/at91/patches-5.4/102-ARM-at91-wb45n-fix-duplicate-label.patch
>>>    delete mode 100644
>>> target/linux/at91/patches-5.4/103-ARM-at91-build-dtb-for-wb50n.patch
>>>    delete mode 100644
>>> target/linux/at91/patches-5.4/103-ARM-at91-wb50n-fix-duplicate-label.patch
>>>
>> ......
>>> -CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
>>> -CONFIG_HAVE_RSEQ=y
>>> -CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
>>> -CONFIG_HAVE_UID16=y
>>> -CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
>>> -CONFIG_HZ_FIXED=0
>>> +CONFIG_HZ=128
>>> +CONFIG_HZ_FIXED=128
>>
>> CONFIG_HZ=100 is set in the generic configuration, do you really need 128?
> 
> It is the result of doing make kernel_menuconfig + save as arch/arm/Kconfig
> from Linux kernel tree has these lines:
> 
> config HZ_FIXED
> 
>          int
> 
>          default 128 if SOC_AT91RM9200
> 
>          default 0
> 
> 
> Since SOC_AT91RM9200 has been introduced in this commit (along with
> SOC_AT91SAM9, SOC_SAM9X60) as the targets were not able to boot without
> these config flags, the CONFIG_HZ_FIXED has been selected accordingly to 128.
> 
> The Linux commit that introduces this is:
> 
> commit 1164f672d71ac103d85207b0453f3127c0efefb3
> Author: Alexandre Belloni <alexandre.belloni at bootlin.com>
> Date:   Fri Mar 13 22:57:24 2015 +0100
> 
>      ARM: at91: drop AT91_TIMER_HZ
> 
>      Drop AT91_TIMER_HZ as this can be handled using HZ_FIXED. Initial help
> message
>      was:
> 
>      On AT91rm9200 chips where you're using a system clock derived
>      from the 32768 Hz hardware clock, this tick rate should divide
>      it exactly: use a power-of-two value, such as 128 or 256, to
>      reduce timing errors caused by rounding.
> 
>      Signed-off-by: Alexandre Belloni <alexandre.belloni at free-electrons.com>
>      Signed-off-by: Nicolas Ferre <nicolas.ferre at atmel.com>
> 
>  From commit description seems better to keep it at 128.
> 
> Thank you,
> Claudiu Beznea
> 

Hi Claudiu,

Thank you for the explanation, I was not aware that there is a special 
handling for this SoC. Using CONFIG_HZ_FIXED=128 and CONFIG_HZ=128 is 
fine with me.

Hauke
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x93DD20630910B515.asc
Type: application/pgp-keys
Size: 13571 bytes
Desc: OpenPGP public key
URL: <http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20210911/d2bca2b9/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20210911/d2bca2b9/attachment.sig>