spidev_test: new package
PATCH v3 1/1 spidev_test: new package
Signed-off-by Gustavo Zacarias <[email protected]>
--- package/Config.in | 1 + package/spidev_test/Config.in | 17 +++++++++++++++++ package/spidev_test/spidev_test.mk | 32 ++++++++++++++++++++++++++++++++ 3 files changed, 50 insertions(+) create mode 100644 package/spidev_test/Config.in create mode 100644 package/spidev_test/spidev_test.mk
package/Config.in +1 -0
@@ -85,6 +85,7 @@ endif source "package/ramsmp/Config.in" source "package/ramspeed/Config.in" source "package/rt-tests/Config.in" + source "package/spidev_test/Config.in" source "package/strace/Config.in" source "package/stress/Config.in" source "package/sysprof/Config.in"
package/spidev_test/Config.in new file +17 -0
@@ -0,0 +1,17 @@ +config BR2_PACKAGE_SPIDEV_TEST + bool "spidev_test" + help + SPI testing utility (using spidev driver). + + This package builds and installs the userspace 'spidev_test' + command. It is up to the user to ensure that the kernel + configuration has all suitable options enabled to allow a + proper operation of 'spidev_test'. + + The version used is based on your toolchain headers version, + if it's older than 3.15 then 3.0 is used, otherwise 3.15 + is used. + This means you won't have quad-pumped SPI support if your + toolchain is too old. + + https://www.kernel.org/doc/Documentation/spi/spidev_test.c
package/spidev_test/spidev_test.mk new file +32 -0
@@ -0,0 +1,32 @@ +################################################################################ +# +# spidev_test +# +################################################################################ + +# v3.15+ requires SPI_TX_QUAD/SPI_RX_QUAD to build +# Normally kernel headers can't be newer than kernel so switch based on that. +# If you need quad-pumped spi support you need to upgrade your toolchain. +ifeq ($(BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_15),y) +SPIDEV_TEST_VERSION = v3.15 +else +SPIDEV_TEST_VERSION = v3.0 +endif +SPIDEV_TEST_SITE = http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/spi +SPIDEV_TEST_SOURCE = spidev_test.c?id=$(SPIDEV_TEST_VERSION) +SPIDEV_TEST_LICENSE = GPLv2 + +# Downloaded file is C source +SPIDEV_TEST_EXTRACT_CMDS = + +define SPIDEV_TEST_BUILD_CMDS + $(TARGET_MAKE_ENV) $(TARGET_CC) $(TARGET_CFLAGS) -x c \ + -o $(@D)/spidev_test $(BR2_DL_DIR)/$(SPIDEV_TEST_SOURCE) +endef + +define SPIDEV_TEST_INSTALL_TARGET_CMDS + $(INSTALL) -D -m 755 $(@D)/spidev_test \ + $(TARGET_DIR)/usr/sbin/spidev_test +endef + +$(eval $(generic-package))
Signature · 1 line
2.0.4
Thomas Petazzoni
AppliedPATCH v3 1/1 spidev_test: new package
Dear Gustavo Zacarias,
Quoted 8 lines · Gustavo Zacarias
Signed-off-by Gustavo Zacarias <[email protected]>--- package/Config.in | 1 + package/spidev_test/Config.in | 17 +++++++++++++++++ package/spidev_test/spidev_test.mk | 32 ++++++++++++++++++++++++++++++++ 3 files changed, 50 insertions(+) create mode 100644 package/spidev_test/Config.in create mode 100644 package/spidev_test/spidev_test.mk
Applied, after doing a small change, see below.
package/spidev_test/spidev_test.mk line 25
Quoted 7 lines
package/spidev_test/spidev_test.mk new file +7
-0+# Downloaded file is C source +SPIDEV_TEST_EXTRACT_CMDS = + +define SPIDEV_TEST_BUILD_CMDS + $(TARGET_MAKE_ENV) $(TARGET_CC) $(TARGET_CFLAGS) -x c \ + -o $(@D)/spidev_test $(BR2_DL_DIR)/$(SPIDEV_TEST_SOURCE) +endef
I've chosen to actually implement SPIDEV_TEST_EXTRACT_CMDS by copying the source file from $(BR2_DL_DIR) to $(@D). This allows to have patches applied on spidev_test, or to do some manual tweaks (for testing) in the build directory and rebuild the package. Consequently, I've dropped the "-x c" option since the file is now copied with a .c extension.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com