From: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com> To: <linux-arm-kernel@lists.infradead.org>, <soc@kernel.org> Cc: <will@kernel.org>, <catalin.marinas@arm.com>, <arnd@arndb.de>, <olof@lixom.net>, <misono.tomohiro@jp.fujitsu.com> Subject: [RFC PATCH 00/10] Add Fujitsu A64FX soc entry/hardware barrier driver Date: Fri, 8 Jan 2021 19:52:31 +0900 [thread overview] Message-ID: <20210108105241.1757799-1-misono.tomohiro@jp.fujitsu.com> (raw) (Resend as cover letter title was missing in the first time. Sorry for noise) Hello, This series adds Fujitsu A64FX SoC entry in drivers/soc and hardware barrier driver for it. [Driver Description] A64FX CPU has several functions for HPC workload and hardware barrier is one of them. It is a mechanism to realize fast synchronization by PEs belonging to the same L3 cache domain by using implementation defined hardware registers. For more details, see A64FX HPC extension specification in https://github.com/fujitsu/A64FX The driver mainly offers a set of ioctls to manipulate related registers. Patch 1-9 implements driver code and patch 10 finally adds kconfig, Makefile and MAINTAINER entry for the driver. Also, C library and test program for this driver is available on: https://github.com/fujitsu/hardware_barrier The driver is based on v5.11-rc2 and tested on FX700 environment. [RFC] This is the first time we upstream drivers for our chip and I want to confirm driver location and patch submission process. Based on my observation it seems drivers/soc folder is right place to put this driver, so I added Kconfig entry for arm64 platform config, created soc/fujitsu folder and updated MAINTAINER entry accordingly (last patch). Is it right? Also for final submission I think I need to 1) create some public git tree to push driver code (github or something), 2) make pull request to SOC team (soc@kernel.org). Is it a correct procedure? I will appreciate any help/comments. sidenote: We plan to post other drivers for A64FX HPC extension (prefetch control and cache control) too anytime soon. Misono Tomohiro (10): soc: fujitsu: hwb: Add hardware barrier driver init/exit code soc: fujtisu: hwb: Add open operation soc: fujitsu: hwb: Add IOC_BB_ALLOC ioctl soc: fujitsu: hwb: Add IOC_BW_ASSIGN ioctl soc: fujitsu: hwb: Add IOC_BW_UNASSIGN ioctl soc: fujitsu: hwb: Add IOC_BB_FREE ioctl soc: fujitsu: hwb: Add IOC_GET_PE_INFO ioctl soc: fujitsu: hwb: Add release operation soc: fujitsu: hwb: Add sysfs entry soc: fujitsu: hwb: Add Kconfig/Makefile to build fujitsu_hwb driver MAINTAINERS | 7 + arch/arm64/Kconfig.platforms | 5 + drivers/soc/Kconfig | 1 + drivers/soc/Makefile | 1 + drivers/soc/fujitsu/Kconfig | 24 + drivers/soc/fujitsu/Makefile | 2 + drivers/soc/fujitsu/fujitsu_hwb.c | 1253 ++++++++++++++++++++++++ include/uapi/linux/fujitsu_hpc_ioctl.h | 41 + 8 files changed, 1334 insertions(+) create mode 100644 drivers/soc/fujitsu/Kconfig create mode 100644 drivers/soc/fujitsu/Makefile create mode 100644 drivers/soc/fujitsu/fujitsu_hwb.c create mode 100644 include/uapi/linux/fujitsu_hpc_ioctl.h -- 2.26.2
WARNING: multiple messages have this Message-ID (diff)
From: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com> To: <linux-arm-kernel@lists.infradead.org>, <soc@kernel.org> Cc: olof@lixom.net, catalin.marinas@arm.com, will@kernel.org, misono.tomohiro@jp.fujitsu.com, arnd@arndb.de Subject: [RFC PATCH 00/10] Add Fujitsu A64FX soc entry/hardware barrier driver Date: Fri, 8 Jan 2021 19:52:31 +0900 [thread overview] Message-ID: <20210108105241.1757799-1-misono.tomohiro@jp.fujitsu.com> (raw) Message-ID: <20210108105231.EK15VDkLvvXbZFl1jOdbnRjgKpMj3cG7sEGhg9GRdkc@z> (raw) (Resend as cover letter title was missing in the first time. Sorry for noise) Hello, This series adds Fujitsu A64FX SoC entry in drivers/soc and hardware barrier driver for it. [Driver Description] A64FX CPU has several functions for HPC workload and hardware barrier is one of them. It is a mechanism to realize fast synchronization by PEs belonging to the same L3 cache domain by using implementation defined hardware registers. For more details, see A64FX HPC extension specification in https://github.com/fujitsu/A64FX The driver mainly offers a set of ioctls to manipulate related registers. Patch 1-9 implements driver code and patch 10 finally adds kconfig, Makefile and MAINTAINER entry for the driver. Also, C library and test program for this driver is available on: https://github.com/fujitsu/hardware_barrier The driver is based on v5.11-rc2 and tested on FX700 environment. [RFC] This is the first time we upstream drivers for our chip and I want to confirm driver location and patch submission process. Based on my observation it seems drivers/soc folder is right place to put this driver, so I added Kconfig entry for arm64 platform config, created soc/fujitsu folder and updated MAINTAINER entry accordingly (last patch). Is it right? Also for final submission I think I need to 1) create some public git tree to push driver code (github or something), 2) make pull request to SOC team (soc@kernel.org). Is it a correct procedure? I will appreciate any help/comments. sidenote: We plan to post other drivers for A64FX HPC extension (prefetch control and cache control) too anytime soon. Misono Tomohiro (10): soc: fujitsu: hwb: Add hardware barrier driver init/exit code soc: fujtisu: hwb: Add open operation soc: fujitsu: hwb: Add IOC_BB_ALLOC ioctl soc: fujitsu: hwb: Add IOC_BW_ASSIGN ioctl soc: fujitsu: hwb: Add IOC_BW_UNASSIGN ioctl soc: fujitsu: hwb: Add IOC_BB_FREE ioctl soc: fujitsu: hwb: Add IOC_GET_PE_INFO ioctl soc: fujitsu: hwb: Add release operation soc: fujitsu: hwb: Add sysfs entry soc: fujitsu: hwb: Add Kconfig/Makefile to build fujitsu_hwb driver MAINTAINERS | 7 + arch/arm64/Kconfig.platforms | 5 + drivers/soc/Kconfig | 1 + drivers/soc/Makefile | 1 + drivers/soc/fujitsu/Kconfig | 24 + drivers/soc/fujitsu/Makefile | 2 + drivers/soc/fujitsu/fujitsu_hwb.c | 1253 ++++++++++++++++++++++++ include/uapi/linux/fujitsu_hpc_ioctl.h | 41 + 8 files changed, 1334 insertions(+) create mode 100644 drivers/soc/fujitsu/Kconfig create mode 100644 drivers/soc/fujitsu/Makefile create mode 100644 drivers/soc/fujitsu/fujitsu_hwb.c create mode 100644 include/uapi/linux/fujitsu_hpc_ioctl.h -- 2.26.2 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-01-08 10:40 UTC|newest] Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-08 10:52 Misono Tomohiro [this message] 2021-01-08 10:52 ` [RFC PATCH 00/10] Add Fujitsu A64FX soc entry/hardware barrier driver Misono Tomohiro 2021-01-08 10:52 ` [PATCH 01/10] soc: fujitsu: hwb: Add hardware barrier driver init/exit code Misono Tomohiro 2021-01-08 10:52 ` Misono Tomohiro 2021-01-08 10:52 ` [PATCH 02/10] soc: fujtisu: hwb: Add open operation Misono Tomohiro 2021-01-08 10:52 ` Misono Tomohiro 2021-01-08 10:52 ` [PATCH 03/10] soc: fujitsu: hwb: Add IOC_BB_ALLOC ioctl Misono Tomohiro 2021-01-08 10:52 ` Misono Tomohiro 2021-01-08 13:22 ` Arnd Bergmann 2021-01-08 13:22 ` Arnd Bergmann 2021-01-12 11:02 ` misono.tomohiro 2021-01-12 11:02 ` misono.tomohiro 2021-01-12 12:34 ` Arnd Bergmann 2021-01-12 12:34 ` Arnd Bergmann 2021-01-08 10:52 ` [PATCH 04/10] soc: fujitsu: hwb: Add IOC_BW_ASSIGN ioctl Misono Tomohiro 2021-01-08 10:52 ` Misono Tomohiro 2021-01-08 10:52 ` [PATCH 05/10] soc: fujitsu: hwb: Add IOC_BW_UNASSIGN ioctl Misono Tomohiro 2021-01-08 10:52 ` Misono Tomohiro 2021-01-08 10:52 ` [PATCH 06/10] soc: fujitsu: hwb: Add IOC_BB_FREE ioctl Misono Tomohiro 2021-01-08 10:52 ` Misono Tomohiro 2021-01-08 10:52 ` [PATCH 07/10] soc: fujitsu: hwb: Add IOC_GET_PE_INFO ioctl Misono Tomohiro 2021-01-08 10:52 ` Misono Tomohiro 2021-01-08 10:52 ` [PATCH 08/10] soc: fujitsu: hwb: Add release operation Misono Tomohiro 2021-01-08 10:52 ` Misono Tomohiro 2021-01-08 13:25 ` Arnd Bergmann 2021-01-08 13:25 ` Arnd Bergmann 2021-01-12 10:38 ` misono.tomohiro 2021-01-12 10:38 ` misono.tomohiro 2021-01-08 10:52 ` [PATCH 09/10] soc: fujitsu: hwb: Add sysfs entry Misono Tomohiro 2021-01-08 10:52 ` Misono Tomohiro 2021-01-08 13:27 ` Arnd Bergmann 2021-01-08 13:27 ` Arnd Bergmann 2021-01-12 10:40 ` misono.tomohiro 2021-01-12 10:40 ` misono.tomohiro 2021-01-08 10:52 ` [PATCH 10/10] soc: fujitsu: hwb: Add Kconfig/Makefile to build fujitsu_hwb driver Misono Tomohiro 2021-01-08 10:52 ` Misono Tomohiro 2021-01-08 12:54 ` [RFC PATCH 00/10] Add Fujitsu A64FX soc entry/hardware barrier driver Mark Rutland 2021-01-08 12:54 ` Mark Rutland 2021-01-08 14:23 ` Arnd Bergmann 2021-01-08 14:23 ` Arnd Bergmann 2021-01-08 15:51 ` Mark Rutland 2021-01-08 15:51 ` Mark Rutland 2021-01-12 10:24 ` misono.tomohiro 2021-01-12 10:24 ` misono.tomohiro 2021-01-12 14:22 ` Arnd Bergmann 2021-01-12 14:22 ` Arnd Bergmann 2021-01-15 11:10 ` misono.tomohiro 2021-01-15 11:10 ` misono.tomohiro 2021-01-15 12:24 ` Arnd Bergmann 2021-01-15 12:24 ` Arnd Bergmann 2021-01-19 5:30 ` misono.tomohiro 2021-01-19 5:30 ` misono.tomohiro 2021-02-18 9:49 ` misono.tomohiro 2021-02-18 9:49 ` misono.tomohiro 2021-03-01 7:53 ` misono.tomohiro 2021-03-01 7:53 ` misono.tomohiro 2021-03-02 11:06 ` Arnd Bergmann 2021-03-02 11:06 ` Arnd Bergmann 2021-03-03 11:20 ` misono.tomohiro 2021-03-03 11:20 ` misono.tomohiro 2021-03-03 13:33 ` Arnd Bergmann 2021-03-03 13:33 ` Arnd Bergmann 2021-03-04 7:03 ` misono.tomohiro 2021-03-04 7:03 ` misono.tomohiro 2021-01-12 10:32 ` misono.tomohiro 2021-01-12 10:32 ` misono.tomohiro
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210108105241.1757799-1-misono.tomohiro@jp.fujitsu.com \ --to=misono.tomohiro@jp.fujitsu.com \ --cc=arnd@arndb.de \ --cc=catalin.marinas@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=olof@lixom.net \ --cc=soc@kernel.org \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.