[linux-yocto]: [kernel v5.10/standard/intel-sdk-5.10/intel-socfpga]: arch: arm64: altera: add dts file to support gpio on FPGA side
From: Limeng Hi Bruce, Based on FPGA ghrd(golden hardware reference design) hw design that includes gpio feature, I created a patch to add corresponding dts file to enable FPGA sw3, FPGA buttion and FPGA led. Could you please help tomerge this patch into linux-ycoto kernel repo, branch v5.10/standard/intel-sdk-5.10/intel-socfpga? diffstat info as below: Makefile |2 - socfpga_stratix10_socdk_ghrd.dts | 78 +++ 2 files changed, 79 insertions(+), 1 deletion(-) thanks, Limeng -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9567): https://lists.yoctoproject.org/g/linux-yocto/message/9567 Mute This Topic: https://lists.yoctoproject.org/mt/81448980/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [PATCH] arch: arm64: altera: add dts file to support gpio on FPGA side
From: Meng Li
Based on FPGA ghrd(golden hardware reference design) hw design
that includes gpio feature, add corresponding dts file to enable
FPGA sw3, FPGA buttion and FPGA led.
Signed-off-by: Meng Li
---
arch/arm64/boot/dts/altera/Makefile | 2 +-
.../altera/socfpga_stratix10_socdk_ghrd.dts | 78 +++
2 files changed, 79 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_ghrd.dts
diff --git a/arch/arm64/boot/dts/altera/Makefile
b/arch/arm64/boot/dts/altera/Makefile
index 43f4f47d3ea0..170f1811c4b5 100644
--- a/arch/arm64/boot/dts/altera/Makefile
+++ b/arch/arm64/boot/dts/altera/Makefile
@@ -1,3 +1,3 @@
# SPDX-License-Identifier: GPL-2.0-only
dtb-$(CONFIG_ARCH_STRATIX10) += socfpga_stratix10_socdk.dtb
socfpga_stratix10_fpga_update.dtb socfpga_stratix10_socdk_pcie.dtb \
- socfpga_stratix10_socdk_sgmii.dtb
socfpga_stratix10_socdk_nand.dtb
+ socfpga_stratix10_socdk_sgmii.dtb
socfpga_stratix10_socdk_ghrd.dtb socfpga_stratix10_socdk_nand.dtb
diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_ghrd.dts
b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_ghrd.dts
new file mode 100644
index ..a05fd640b2e5
--- /dev/null
+++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_ghrd.dts
@@ -0,0 +1,78 @@
+// SPDX-License-Identifier: GPL-2.0-only
+/*
+ * Copyright Altera Corporation (C) 2021. All rights reserved.
+ */
+
+#include "socfpga_stratix10_socdk.dts"
+
+/{
+ soc {
+
+ led_pio: gpio@1080 {
+ compatible = "altr,pio-1.0";
+ reg = <0xf9001080 0x8>;
+ altr,gpio-bank-width = <4>;
+ #gpio-cells = <2>;
+ gpio-controller;
+ resetvalue = <0>;
+ };
+
+ button_pio: gpio@1060 {
+ compatible = "altr,pio-1.0";
+ reg = <0xf9001060 0x10>;
+ interrupt-parent = <>;
+ interrupts = <0 18 4>;
+ altr,gpio-bank-width = <4>;
+ altr,interrupt-type = <2>;
+altr,interrupt_type = <2>;
+ #gpio-cells = <2>;
+ gpio-controller;
+ };
+
+ dipsw_pio: gpio@1070 {
+ compatible = "altr,pio-1.0";
+ reg = <0xf9001070 0x10>;
+ interrupt-parent = <>;
+ interrupts = <0 17 4>;
+ altr,gpio-bank-width = <4>;
+ altr,interrupt-type = <3>;
+altr,interrupt_type = <3>;
+ #gpio-cells = <2>;
+ gpio-controller;
+ };
+
+ trigger_pio: gpio@1040 {
+ compatible = "altr,pio-1.0";
+ reg = <0xf9001040 0x20>;
+ altr,gpio-bank-width = <4>;
+ #gpio-cells = <2>;
+ gpio-controller;
+ resetvalue = <0>;
+ };
+
+ soc_leds: leds {
+ compatible = "gpio-leds";
+
+ led_fpga0: fpga0 {
+ label = "fpga_led0";
+ gpios = <_pio 0 0>;
+ }; //end fpga0 (led_fpga0)
+
+ led_fpga1: fpga1 {
+ label = "fpga_led1";
+ gpios = <_pio 1 0>;
+ }; //end fpga1 (led_fpga1)
+
+ led_fpga2: fpga2 {
+ label = "fpga_led2";
+ gpios = <_pio 2 0>;
+ }; //end fpga2 (led_fpga2)
+
+ led_fpga3: fpga3 {
+ label = "fpga_led3";
+ gpios = <_pio 3 0>;
+ }; //end fpga3 (led_fpga3)
+ };
+
+ };
+};
--
2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9568):
https://lists.yoctoproject.org/g/linux-yocto/message/9568
Mute This Topic: https://lists.yoctoproject.org/mt/81448981/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [PATCH] arch: arm64: altera: add dts file to support sgmii ethernet on FPGA side
From: Meng Li
Based on FPGA hw design that includes sgmii ethernet feature,
add corresponding dts file to enable 2 ethernet ports on
stratix10 board.
Signed-off-by: Meng Li
---
arch/arm64/boot/dts/altera/Makefile | 2 +-
.../altera/socfpga_stratix10_socdk_sgmii.dts | 85 +++
2 files changed, 86 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts
diff --git a/arch/arm64/boot/dts/altera/Makefile
b/arch/arm64/boot/dts/altera/Makefile
index 817cfed02365..43f4f47d3ea0 100644
--- a/arch/arm64/boot/dts/altera/Makefile
+++ b/arch/arm64/boot/dts/altera/Makefile
@@ -1,3 +1,3 @@
# SPDX-License-Identifier: GPL-2.0-only
dtb-$(CONFIG_ARCH_STRATIX10) += socfpga_stratix10_socdk.dtb
socfpga_stratix10_fpga_update.dtb socfpga_stratix10_socdk_pcie.dtb \
- socfpga_stratix10_socdk_nand.dtb
+ socfpga_stratix10_socdk_sgmii.dtb
socfpga_stratix10_socdk_nand.dtb
diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts
b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts
new file mode 100644
index ..902262ed3ac2
--- /dev/null
+++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_sgmii.dts
@@ -0,0 +1,85 @@
+// SPDX-License-Identifier: GPL-2.0-only
+/*
+ * Copyright Altera Corporation (C) 2021. All rights reserved.
+ */
+
+#include "socfpga_stratix10_socdk.dts"
+
+/{
+ soc {
+ clocks {
+ sgmii_1_clk_0: sgmii_1_clk_0 {
+compatible = "fixed-clock";
+#clock-cells = <0>;
+clock-frequency = <12500>; /* 125.00 MHz
*/
+clock-output-names = "sgmii_1_clk_0-out_clk";
+}; //end sgmii_1_clk_0 (sgmii_1_clk_0)
+
+sgmii_1_clk_125: sgmii_1_clk_125 {
+compatible = "fixed-clock";
+#clock-cells = <0>;
+clock-frequency = <12500>; /* 125.00 MHz
*/
+clock-output-names = "sgmii_1_clk_125-out_clk";
+}; //end sgmii_1_clk_125 (sgmii_1_clk_125)
+
+sgmii_2_clk_0: sgmii_2_clk_0 {
+compatible = "fixed-clock";
+#clock-cells = <0>;
+clock-frequency = <12500>; /* 125.00 MHz
*/
+clock-output-names = "sgmii_2_clk_0-out_clk";
+}; //end sgmii_2_clk_0 (sgmii_2_clk_0)
+
+sgmii_2_clk_125: sgmii_2_clk_125 {
+compatible = "fixed-clock";
+#clock-cells = <0>;
+clock-frequency = <12500>; /* 125.00 MHz
*/
+clock-output-names = "sgmii_2_clk_125-out_clk";
+}; //end sgmii_2_clk_125 (sgmii_2_clk_125)
+ };
+
+ s10_hps_bridges: bridge@8000 {
+compatible = "altr,bridge-18.1", "simple-bus";
+reg = <0x8000 0x6000>,
+<0xf900 0x0010>;
+reg-names = "axi_h2f", "axi_h2f_lw";
+#address-cells = <2>;
+#size-cells = <1>;
+ranges = <0x 0x 0x8000 0x0004>,
+<0x0001 0x 0xf901 0x0040>,
+<0x0001 0x0040 0xf9010040 0x0008>,
+<0x0001 0x080 0xf9010080 0x0040>,
+<0x0001 0x0c0 0xf90100c0 0x0008>;
+
+sgmii_1_gmii2sgmii: phy@0x10040 {
+compatible = "altr,gmii-to-sgmii-2.0";
+reg = <0x0001 0x 0x0040>,
+<0x0001 0x0040 0x0008>;
+reg-names = "eth_tse_control_port",
"gmii_to_sgmii_adapter_avalon_slave";
+clocks = <_1_clk_0 1
_1_clk_125 _1_clk_125>;
+clock-names = "clock_in", "emac_gtx_clk",
"tse_pcs_ref_clk_clock_connection", "tse_rx_cdr_refclk";
+}; //end phy@0x10040 (sgmii_1_gmii2sgmii)
+
+sgmii_2_gmii2sgmii: phy@0x10c0 {
+compatible = "altr,gmii-to-sgmii-2.0";
+reg = <0x0001 0x0080 0x0040>,
+<0x0001 0x00c0 0x0008>;
+reg-names = "eth_tse_control_port",
"gmii_to_sgmii_adapter_avalon_slave";
+
[linux-yocto]: [kernel v5.10/standard/intel-sdk-5.10/intel-socfpga]: arch: arm64: altera: add dts file to support sgmii ethernet on FPGA side
From: Limeng Hi Bruce, Based on FPGA hw design that includes sgmii ethernet feature, I created a patch to add corresponding dts file to enable 2 ethernet ports on stratix10 board. Could you please help tomerge this patch into linux-ycoto kernel repo, branch v5.10/standard/intel-sdk-5.10/intel-socfpga? diffstat info as below: Makefile |2 socfpga_stratix10_socdk_sgmii.dts | 87 ++ 2 files changed, 88 insertions(+), 1 deletion(-) thanks, Limeng -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9565): https://lists.yoctoproject.org/g/linux-yocto/message/9565 Mute This Topic: https://lists.yoctoproject.org/mt/81446683/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] spidev.c ?
But there are NO udev files for the SPI devices defined in the DTSI
file.
On 2021-03-18 17:12, jchludzinski via lists.yoctoproject.org wrote:
That's with:
root@arria10:~# lsmod
Module Size Used by
spi_altera 16384 0
spidev 20480 0
On 2021-03-18 17:07, jchludzinski via lists.yoctoproject.org wrote:
root@arria10:~# find /sys/ -name 'spi*'
/sys/kernel/debug/clk/spi_m_clk
/sys/kernel/debug/tracing/events/spi
/sys/kernel/debug/tracing/events/spi/spi_controller_idle
/sys/kernel/debug/tracing/events/spi/spi_controller_busy
/sys/kernel/debug/tracing/events/spi/spi_message_submit
/sys/kernel/debug/tracing/events/spi/spi_message_start
/sys/kernel/debug/tracing/events/spi/spi_message_done
/sys/kernel/debug/tracing/events/spi/spi_transfer_start
/sys/kernel/debug/tracing/events/spi/spi_transfer_stop
/sys/kernel/debug/regmap/spi0.0
/sys/devices/platform/soc/ffda5000.spi/spi_master
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_sync/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_async/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_sync_immediate/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_sync/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_async/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_sync_immediate
/sys/class/spidev
/sys/class/spi_master
/sys/class/spi_master/spi0
/sys/firmware/devicetree/base/__symbols__/spi2
/sys/firmware/devicetree/base/__symbols__/spi0
/sys/firmware/devicetree/base/__symbols__/spin_ctrl_1
/sys/firmware/devicetree/base/__symbols__/spi_m_clk
/sys/firmware/devicetree/base/__symbols__/spi1
/sys/firmware/devicetree/base/__symbols__/spin_ctrl_2
/sys/firmware/devicetree/base/soc/spi@ff809000
/sys/firmware/devicetree/base/soc/spi@ffda5000
/sys/firmware/devicetree/base/soc/spi@ffda5000/resource-manager@0/spi-max-frequency
/sys/firmware/devicetree/base/soc/clkmgr@ffd04000/clocks/spi_m_clk
/sys/firmware/devicetree/base/soc/spi@ffda4000
/sys/firmware/devicetree/base/spi@0xc00c0800
/sys/firmware/devicetree/base/spi@0xc00c0800/spidev@0
/sys/firmware/devicetree/base/spi@0xc00c0800/spidev@0/spi-max-frequency/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@200/spin-controller/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@200/spin-rph/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@100/spin-controller/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@100/spin-controller-names/sys/firmware/devicetree/base/testcase-data-2/substation@100/motor-1/spin
/sys/bus/platform/drivers/spi_altera
/sys/bus/spi
/sys/bus/spi/devices/spi0.0
/sys/bus/spi/drivers/spi-nor
/sys/bus/spi/drivers/altr_a10sr/spi0.0
/sys/bus/spi/drivers/spidev
/sys/module/spidev
/sys/module/spidev/drivers/spi:spidev
/sys/module/spi_altera
On 2021-03-18 03:44, Zoran wrote:
I am guessing here But what do you have while executing the
following command being in /sys
as root?
root@arm:/sys# find . -name spi*
Zee
___
On Wed, Mar 17, 2021 at 5:41 PM jchludzinski via
lists.yoctoproject.org
wrote:
In the YOCTO/Linux source tree there's drivers/spi/ which has all
the source for SPI drivers. There's only 1 file, spidev.c, which
has:
static int __init spidev_init(void)
{
int status;
/* Claim our 256 reserved device numbers. Then register a
class
* that will key udev/mdev to add/remove /dev nodes.
Last, register
* the driver which manages those device numbers.
*/
BUILD_BUG_ON(N_SPI_MINORS > 256);
status = register_chrdev(SPIDEV_MAJOR, "spi",
_fops);
if (status < 0)
return status;
spidev_class = class_create(THIS_MODULE, "spidev");
if (IS_ERR(spidev_class)) {
unregister_chrdev(SPIDEV_MAJOR,
spidev_spi_driver.driver.name);
return PTR_ERR(spidev_class);
}
status = spi_register_driver(_spi_driver);
if (status < 0) {
class_destroy(spidev_class);
unregister_chrdev(SPIDEV_MAJOR,
spidev_spi_driver.driver.name);
}
return status;
}
module_init(spidev_init);
... for creating device files in udev.
So when I use 'make nconfig' to specifiy that I want a loadable
module for the ALTERA SPI driver, why don't I see a spidev.o file
in drivers/spi/ ?
How does spi-altera.ko create device files without a call to
register_chrdev(...).
How is it a loadable module without module_init(...)?
When I separately build spidev.c as an .ko and try loading it, I
get: "Device or resourse busy"
---John
Links: You receive all messages sent to this group.
View/Reply Online (#52767):
https://lists.yoctoproject.org/g/yocto/message/52767
Mute This Topic: https://lists.yoctoproject.org/mt/81407811/5071304
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[jchludzin...@vivaldi.net]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages
Re: [yocto] spidev.c ?
That's with:
root@arria10:~# lsmod
Module Size Used by
spi_altera 16384 0
spidev 20480 0
On 2021-03-18 17:07, jchludzinski via lists.yoctoproject.org wrote:
root@arria10:~# find /sys/ -name 'spi*'
/sys/kernel/debug/clk/spi_m_clk
/sys/kernel/debug/tracing/events/spi
/sys/kernel/debug/tracing/events/spi/spi_controller_idle
/sys/kernel/debug/tracing/events/spi/spi_controller_busy
/sys/kernel/debug/tracing/events/spi/spi_message_submit
/sys/kernel/debug/tracing/events/spi/spi_message_start
/sys/kernel/debug/tracing/events/spi/spi_message_done
/sys/kernel/debug/tracing/events/spi/spi_transfer_start
/sys/kernel/debug/tracing/events/spi/spi_transfer_stop
/sys/kernel/debug/regmap/spi0.0
/sys/devices/platform/soc/ffda5000.spi/spi_master
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_sync
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_async
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_sync_immediate
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_sync
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_async
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_sync_immediate
/sys/class/spidev
/sys/class/spi_master
/sys/class/spi_master/spi0
/sys/firmware/devicetree/base/__symbols__/spi2
/sys/firmware/devicetree/base/__symbols__/spi0
/sys/firmware/devicetree/base/__symbols__/spin_ctrl_1
/sys/firmware/devicetree/base/__symbols__/spi_m_clk
/sys/firmware/devicetree/base/__symbols__/spi1
/sys/firmware/devicetree/base/__symbols__/spin_ctrl_2
/sys/firmware/devicetree/base/soc/spi@ff809000
/sys/firmware/devicetree/base/soc/spi@ffda5000
/sys/firmware/devicetree/base/soc/spi@ffda5000/resource-manager@0/spi-max-frequency
/sys/firmware/devicetree/base/soc/clkmgr@ffd04000/clocks/spi_m_clk
/sys/firmware/devicetree/base/soc/spi@ffda4000
/sys/firmware/devicetree/base/spi@0xc00c0800
/sys/firmware/devicetree/base/spi@0xc00c0800/spidev@0
/sys/firmware/devicetree/base/spi@0xc00c0800/spidev@0/spi-max-frequency
/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@200/spin-controller
/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@200/spin-rph
/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@100/spin-controller
/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@100/spin-controller-names
/sys/firmware/devicetree/base/testcase-data-2/substation@100/motor-1/spin
/sys/bus/platform/drivers/spi_altera
/sys/bus/spi
/sys/bus/spi/devices/spi0.0
/sys/bus/spi/drivers/spi-nor
/sys/bus/spi/drivers/altr_a10sr/spi0.0
/sys/bus/spi/drivers/spidev
/sys/module/spidev
/sys/module/spidev/drivers/spi:spidev
/sys/module/spi_altera
On 2021-03-18 03:44, Zoran wrote:
I am guessing here But what do you have while executing the
following command being in /sys
as root?
root@arm:/sys# find . -name spi*
Zee
___
On Wed, Mar 17, 2021 at 5:41 PM jchludzinski via
lists.yoctoproject.org
wrote:
In the YOCTO/Linux source tree there's drivers/spi/ which has all
the source for SPI drivers. There's only 1 file, spidev.c, which
has:
static int __init spidev_init(void)
{
int status;
/* Claim our 256 reserved device numbers. Then register a
class
* that will key udev/mdev to add/remove /dev nodes.
Last, register
* the driver which manages those device numbers.
*/
BUILD_BUG_ON(N_SPI_MINORS > 256);
status = register_chrdev(SPIDEV_MAJOR, "spi",
_fops);
if (status < 0)
return status;
spidev_class = class_create(THIS_MODULE, "spidev");
if (IS_ERR(spidev_class)) {
unregister_chrdev(SPIDEV_MAJOR,
spidev_spi_driver.driver.name);
return PTR_ERR(spidev_class);
}
status = spi_register_driver(_spi_driver);
if (status < 0) {
class_destroy(spidev_class);
unregister_chrdev(SPIDEV_MAJOR,
spidev_spi_driver.driver.name);
}
return status;
}
module_init(spidev_init);
... for creating device files in udev.
So when I use 'make nconfig' to specifiy that I want a loadable
module for the ALTERA SPI driver, why don't I see a spidev.o file
in drivers/spi/ ?
How does spi-altera.ko create device files without a call to
register_chrdev(...).
How is it a loadable module without module_init(...)?
When I separately build spidev.c as an .ko and try loading it, I
get: "Device or resourse busy"
---John
Links: You receive all messages sent to this group.
View/Reply Online (#52767):
https://lists.yoctoproject.org/g/yocto/message/52767
Mute This Topic: https://lists.yoctoproject.org/mt/81407811/5071304
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[jchludzin...@vivaldi.net]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52768): https://lists.yoctoproject.org/g/yocto/message/52768
Mute This Topic:
Re: [yocto] spidev.c ?
root@arria10:~# find /sys/ -name 'spi*'
/sys/kernel/debug/clk/spi_m_clk
/sys/kernel/debug/tracing/events/spi
/sys/kernel/debug/tracing/events/spi/spi_controller_idle
/sys/kernel/debug/tracing/events/spi/spi_controller_busy
/sys/kernel/debug/tracing/events/spi/spi_message_submit
/sys/kernel/debug/tracing/events/spi/spi_message_start
/sys/kernel/debug/tracing/events/spi/spi_message_done
/sys/kernel/debug/tracing/events/spi/spi_transfer_start
/sys/kernel/debug/tracing/events/spi/spi_transfer_stop
/sys/kernel/debug/regmap/spi0.0
/sys/devices/platform/soc/ffda5000.spi/spi_master
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_sync
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_async
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_sync_immediate
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_sync
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_async
/sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_sync_immediate
/sys/class/spidev
/sys/class/spi_master
/sys/class/spi_master/spi0
/sys/firmware/devicetree/base/__symbols__/spi2
/sys/firmware/devicetree/base/__symbols__/spi0
/sys/firmware/devicetree/base/__symbols__/spin_ctrl_1
/sys/firmware/devicetree/base/__symbols__/spi_m_clk
/sys/firmware/devicetree/base/__symbols__/spi1
/sys/firmware/devicetree/base/__symbols__/spin_ctrl_2
/sys/firmware/devicetree/base/soc/spi@ff809000
/sys/firmware/devicetree/base/soc/spi@ffda5000
/sys/firmware/devicetree/base/soc/spi@ffda5000/resource-manager@0/spi-max-frequency
/sys/firmware/devicetree/base/soc/clkmgr@ffd04000/clocks/spi_m_clk
/sys/firmware/devicetree/base/soc/spi@ffda4000
/sys/firmware/devicetree/base/spi@0xc00c0800
/sys/firmware/devicetree/base/spi@0xc00c0800/spidev@0
/sys/firmware/devicetree/base/spi@0xc00c0800/spidev@0/spi-max-frequency
/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@200/spin-controller
/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@200/spin-rph
/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@100/spin-controller
/sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@100/spin-controller-names
/sys/firmware/devicetree/base/testcase-data-2/substation@100/motor-1/spin
/sys/bus/platform/drivers/spi_altera
/sys/bus/spi
/sys/bus/spi/devices/spi0.0
/sys/bus/spi/drivers/spi-nor
/sys/bus/spi/drivers/altr_a10sr/spi0.0
/sys/bus/spi/drivers/spidev
/sys/module/spidev
/sys/module/spidev/drivers/spi:spidev
/sys/module/spi_altera
On 2021-03-18 03:44, Zoran wrote:
I am guessing here But what do you have while executing the
following command being in /sys
as root?
root@arm:/sys# find . -name spi*
Zee
___
On Wed, Mar 17, 2021 at 5:41 PM jchludzinski via
lists.yoctoproject.org
wrote:
In the YOCTO/Linux source tree there's drivers/spi/ which has all the source
for SPI drivers. There's only 1 file, spidev.c, which has:
static int __init spidev_init(void)
{
int status;
/* Claim our 256 reserved device numbers. Then register a class
* that will key udev/mdev to add/remove /dev nodes. Last, register
* the driver which manages those device numbers.
*/
BUILD_BUG_ON(N_SPI_MINORS > 256);
status = register_chrdev(SPIDEV_MAJOR, "spi", _fops);
if (status < 0)
return status;
spidev_class = class_create(THIS_MODULE, "spidev");
if (IS_ERR(spidev_class)) {
unregister_chrdev(SPIDEV_MAJOR, spidev_spi_driver.driver.name);
return PTR_ERR(spidev_class);
}
status = spi_register_driver(_spi_driver);
if (status < 0) {
class_destroy(spidev_class);
unregister_chrdev(SPIDEV_MAJOR, spidev_spi_driver.driver.name);
}
return status;
}
module_init(spidev_init);
... for creating device files in udev.
So when I use 'make nconfig' to specifiy that I want a loadable module for the
ALTERA SPI driver, why don't I see a spidev.o file in drivers/spi/ ?
How does spi-altera.ko create device files without a call to
register_chrdev(...).
How is it a loadable module without module_init(...)?
When I separately build spidev.c as an .ko and try loading it, I get: "Device or
resourse busy"
---John
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52762): https://lists.yoctoproject.org/g/yocto/message/52762
Mute This Topic: https://lists.yoctoproject.org/mt/81407811/5071304
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[jchludzin...@vivaldi.net]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52767): https://lists.yoctoproject.org/g/yocto/message/52767
Mute This Topic: https://lists.yoctoproject.org/mt/81407811/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [meta-security][PATCH] ima-evm-keys: add file-checksums to IMA_EVM_X509
merged,
thanks
On 3/12/21 1:53 AM, liu.min...@gmail.com wrote:
> From: Ming Liu
>
> This ensures when a end user change the IMA_EVM_X509 key file,
> ima-evm-keys recipe will be rebuilt.
>
> Signed-off-by: Ming Liu
> ---
> meta-integrity/recipes-security/ima-evm-keys/ima-evm-keys_1.0.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta-integrity/recipes-security/ima-evm-keys/ima-evm-keys_1.0.bb
> b/meta-integrity/recipes-security/ima-evm-keys/ima-evm-keys_1.0.bb
> index 62685bb..7708aef 100644
> --- a/meta-integrity/recipes-security/ima-evm-keys/ima-evm-keys_1.0.bb
> +++ b/meta-integrity/recipes-security/ima-evm-keys/ima-evm-keys_1.0.bb
> @@ -14,3 +14,4 @@ do_install () {
> lnr ${D}${sysconfdir}/keys/x509_evm.der
> ${D}${sysconfdir}/keys/x509_ima.der
> fi
> }
> +do_install[file-checksums] += "${@'${IMA_EVM_X509}:%s' %
> os.path.exists('${IMA_EVM_X509}')}"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52766): https://lists.yoctoproject.org/g/yocto/message/52766
Mute This Topic: https://lists.yoctoproject.org/mt/81275663/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [meta-security][PATCH v2] samhain: fix compile error on powerpc
merged
thanks
On 3/11/21 1:34 AM, kai wrote:
> From: Kai Kang
>
> It fails to comile samhain for powerpc(qemuppc):
>
> | x_sh_dbIO.c: In function 'swap_short':
> | x_sh_dbIO.c:229:36: error: initializer element is not constant
> | 229 | static unsigned short ooop = *iptr;
> | |^
>
> Assign after initialization of the static variable to avoid the failure.
>
> Signed-off-by: Kai Kang
> ---
> ...-initializer-element-is-not-constant.patch | 28 +++
> recipes-ids/samhain/samhain.inc | 1 +
> 2 files changed, 29 insertions(+)
> create mode 100644
> recipes-ids/samhain/files/samhain-fix-initializer-element-is-not-constant.patch
>
> diff --git
> a/recipes-ids/samhain/files/samhain-fix-initializer-element-is-not-constant.patch
>
> b/recipes-ids/samhain/files/samhain-fix-initializer-element-is-not-constant.patch
> new file mode 100644
> index 000..72cb880
> --- /dev/null
> +++
> b/recipes-ids/samhain/files/samhain-fix-initializer-element-is-not-constant.patch
> @@ -0,0 +1,28 @@
> +Fix error when compile for powerpc:
> +
> +| x_sh_dbIO.c: In function 'swap_short':
> +| x_sh_dbIO.c:229:36: error: initializer element is not constant
> +| 229 | static unsigned short ooop = *iptr;
> +| |^
> +
> +Upstream-Status: Pending
> +
> +Signed-off-by: Kai Kang
> +---
> + src/sh_dbIO.c | 3 ++-
> + 1 file changed, 2 insertions(+), 1 deletion(-)
> +
> +diff --git a/src/sh_dbIO.c b/src/sh_dbIO.c
> +index b547ac5..23a9621 100644
> +--- a/src/sh_dbIO.c
> b/src/sh_dbIO.c
> +@@ -226,7 +226,8 @@ static unsigned short * swap_short (unsigned short *
> iptr)
> + else
> + {
> + /* alignment problem */
> +- static unsigned short ooop = *iptr;
> ++ static unsigned short ooop;
> ++ ooop = *iptr;
> + unsigned short hi = (ooop & 0xff00);
> + unsigned short lo = (ooop & 0xff);
> + ooop = (lo << 8) | (hi >> 8);
> diff --git a/recipes-ids/samhain/samhain.inc b/recipes-ids/samhain/samhain.inc
> index 6a2eb08..0148e46 100644
> --- a/recipes-ids/samhain/samhain.inc
> +++ b/recipes-ids/samhain/samhain.inc
> @@ -18,6 +18,7 @@ SRC_URI =
> "https://la-samhna.de/archive/samhain_signed-${PV}.tar.gz \
> file://samhain-avoid-searching-host-for-postgresql.patch \
> file://samhain-add-LDFLAGS-variable-for-samhain_setpwd.patch \
> file://fix-build-with-new-version-attr.patch \
> + file://samhain-fix-initializer-element-is-not-constant.patch \
> "
>
> SRC_URI[sha256sum] =
> "3e57574036d5055e9557ec5095818b419ea6c4365370fc2ccce1e9f87f9fad08"
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52765): https://lists.yoctoproject.org/g/yocto/message/52765
Mute This Topic: https://lists.yoctoproject.org/mt/81249494/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [meta-security][PATCH] fscryptctl: Fix installation path
merged.
thanks
On 3/10/21 8:52 AM, Łukasz Płachno via lists.yoctoproject.org wrote:
> - Without the patch fscryptctl is installed in
>/usr/bin/usr/local/bin instead of /usr/bin.
> ---
> recipes-security/fscryptctl/fscryptctl_1.0.0.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-security/fscryptctl/fscryptctl_1.0.0.bb
> b/recipes-security/fscryptctl/fscryptctl_1.0.0.bb
> index 440b4e3..df76a3d 100644
> --- a/recipes-security/fscryptctl/fscryptctl_1.0.0.bb
> +++ b/recipes-security/fscryptctl/fscryptctl_1.0.0.bb
> @@ -15,7 +15,7 @@ SRC_URI = "git://github.com/google/fscryptctl.git"
> S = "${WORKDIR}/git"
>
> do_install() {
> -oe_runmake DESTDIR=${D}${bindir} install
> +oe_runmake DESTDIR=${D} PREFIX=/usr install
> }
>
> RRECOMMENDS_${PN} += "\
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52764): https://lists.yoctoproject.org/g/yocto/message/52764
Mute This Topic: https://lists.yoctoproject.org/mt/81232180/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [meta-rockchip][PATCH] layer.conf: Add hardknott to compatible release branches
Applied. Thank you! :-) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52763): https://lists.yoctoproject.org/g/yocto/message/52763 Mute This Topic: https://lists.yoctoproject.org/mt/81423482/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] spidev.c ?
I am guessing here But what do you have while executing the
following command being in /sys
as root?
root@arm:/sys# find . -name spi*
Zee
___
On Wed, Mar 17, 2021 at 5:41 PM jchludzinski via
lists.yoctoproject.org
wrote:
>
> In the YOCTO/Linux source tree there's drivers/spi/ which has all the source
> for SPI drivers. There's only 1 file, spidev.c, which has:
>
> static int __init spidev_init(void)
> {
> int status;
>
> /* Claim our 256 reserved device numbers. Then register a class
> * that will key udev/mdev to add/remove /dev nodes. Last, register
> * the driver which manages those device numbers.
> */
> BUILD_BUG_ON(N_SPI_MINORS > 256);
> status = register_chrdev(SPIDEV_MAJOR, "spi", _fops);
> if (status < 0)
> return status;
>
> spidev_class = class_create(THIS_MODULE, "spidev");
> if (IS_ERR(spidev_class)) {
> unregister_chrdev(SPIDEV_MAJOR,
> spidev_spi_driver.driver.name);
> return PTR_ERR(spidev_class);
> }
>
> status = spi_register_driver(_spi_driver);
> if (status < 0) {
> class_destroy(spidev_class);
> unregister_chrdev(SPIDEV_MAJOR,
> spidev_spi_driver.driver.name);
> }
> return status;
> }
> module_init(spidev_init);
>
> ... for creating device files in udev.
>
> So when I use 'make nconfig' to specifiy that I want a loadable module for
> the ALTERA SPI driver, why don't I see a spidev.o file in drivers/spi/ ?
>
> How does spi-altera.ko create device files without a call to
> register_chrdev(...).
>
> How is it a loadable module without module_init(...)?
>
> When I separately build spidev.c as an .ko and try loading it, I get: "Device
> or resourse busy"
>
> ---John
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52762): https://lists.yoctoproject.org/g/yocto/message/52762
Mute This Topic: https://lists.yoctoproject.org/mt/81407811/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Recipes and meta-data directory tree
> OE allows you to build own distributions, so what you are looking at is two > different distributions based on different different releases but using same > build system ( OpenEmbedded ) over major releases the build system gets > changed too in terms of its metadata as well new features and some old cruft > removed like usual projects. so you have different releases, and different > machines and different distro all contributing to the differences. > Thanks for input from you. Does this mean shown differences in directory tree is result, a mix of these all listed parameters? I am aware of these are two different distributions. I am aware of these are based on different releases. I am aware of these are two different machines. I am aware of release to release to get several classes of modifications. Actually asked question means how much show differences result from usage of different YP releases. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52761): https://lists.yoctoproject.org/g/yocto/message/52761 Mute This Topic: https://lists.yoctoproject.org/mt/81407654/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] subtree …/tmp/deploy/… , files named Packages
> > what you are looking at is feeds area, where the format will vary > depending upon which online package management is in use. So you will > have to make that differentiation. Packages file is used when opkg is > used and not by rpm/dnf > for SCA perhaps you want to look at content of the packages. or maybe > use the manifests that yocto generates e.g. license manifest in images > have info on all packages that go into that image, it may not be > formatted as per your expectation > but its somewhere to start > > Thanks for helpful input. This matches my own observation. Tool-chain used in project requires additionally license.manifest file on its input. For some reason it also takes a look into files named Packages. Actually it can be clear why it does this: Packages file specifies among others each package source code address/path. Despite the question files named Packages generated for .ipk YES, for .rpm NO, is it legitimate to use these files in external tool-chain for software composition analysis? I mean these files might be Yocto internal interface not intended for purpose pointed out here. May this be true? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52760): https://lists.yoctoproject.org/g/yocto/message/52760 Mute This Topic: https://lists.yoctoproject.org/mt/81379610/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] QA notification for completed autobuilder build (yocto-3.3_M3.rc1)
Hi All, This is the full report for yocto-3.3_M3.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. new issue found: BUG id:14306 - [3.3 M3 rc1] beaglebone poky-alt wic image can not bootup Bugs verified: BUG id:14203 - [QA 3.3 M2 RC1] failure in ptest : gstreamer1.0.gstreamer-1.0/pipelines_seek.test Verified Fixed. === Bugs https://bugzilla.yoctoproject.org/show_bug.cgi?id=14306 https://bugzilla.yoctoproject.org/show_bug.cgi?id=14203 Thanks, Sangeeta > -Original Message- > From: yocto@lists.yoctoproject.org On Behalf > Of Pokybuild User > Sent: Tuesday, 16 March, 2021 6:16 AM > To: yocto@lists.yoctoproject.org > Cc: qa-build-notificat...@lists.yoctoproject.org > Subject: [yocto] QA notification for completed autobuilder build (yocto- > 3.3_M3.rc1) > > > A build flagged for QA (yocto-3.3_M3.rc1) was completed on the autobuilder > and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-3.3_M3.rc1 > > > Build hash information: > > bitbake: 53c30efec4099035d19e6717059dfceff8ff88fd > meta-arm: a949ebfd06dcae26ca3c625195e1a3ed703b2c6e > meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f > meta-intel: 850940e3e5ebc75328fa75e718235342cb6c2172 > meta-kernel: 29329d7cacc71595cecfdd05a455a0cfb164564d > meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e > oecore: fa1e1fbc082e82e41ccfeae58af97fe048c9aac7 > poky: 9fbbf40317743beacd8ac9d3f602765ed9d9fa6f > > > > This is an automated message from the Yocto Project Autobuilder > Git: git://git.yoctoproject.org/yocto-autobuilder2 > Email: richard.pur...@linuxfoundation.org > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52759): https://lists.yoctoproject.org/g/yocto/message/52759 Mute This Topic: https://lists.yoctoproject.org/mt/81362963/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][yocto-kernel-cache][yocto-5.10][PATCH] ti-j72xx: add kernel-cache configuration files for BSP ti-j72xx
This adds the cfg & scc files to support the TI J721E soc. Signed-off-by: Xulin Sun --- bsp/ti-j72xx/ti-j72xx-remoteproc.cfg | 21 ++ bsp/ti-j72xx/ti-j72xx-remoteproc.scc | 1 + bsp/ti-j72xx/ti-j72xx-standard.scc | 8 + bsp/ti-j72xx/ti-j72xx.cfg| 344 +++ bsp/ti-j72xx/ti-j72xx.scc| 8 + 5 files changed, 382 insertions(+) create mode 100644 bsp/ti-j72xx/ti-j72xx-remoteproc.cfg create mode 100644 bsp/ti-j72xx/ti-j72xx-remoteproc.scc create mode 100644 bsp/ti-j72xx/ti-j72xx-standard.scc create mode 100755 bsp/ti-j72xx/ti-j72xx.cfg create mode 100644 bsp/ti-j72xx/ti-j72xx.scc diff --git a/bsp/ti-j72xx/ti-j72xx-remoteproc.cfg b/bsp/ti-j72xx/ti-j72xx-remoteproc.cfg new file mode 100644 index ..a6eb3538 --- /dev/null +++ b/bsp/ti-j72xx/ti-j72xx-remoteproc.cfg @@ -0,0 +1,21 @@ +# +# Remoteproc drivers +# +CONFIG_REMOTEPROC=y +CONFIG_PRU_REMOTEPROC=m +CONFIG_TI_K3_R5_REMOTEPROC=m +CONFIG_TI_K3_DSP_REMOTEPROC=m + +# +# Rpmsg virtual device drivers +# +CONFIG_RPMSG_KDRV=y +CONFIG_RPMSG_KDRV_ETH_SWITCH=m +CONFIG_TI_RDEV_ETH_SWITCH_VIRT_EMAC=m +CONFIG_RPMSG_VIRTIO=m +CONFIG_RPMSG_CHAR=m +CONFIG_RPMSG_PRU=m +CONFIG_SAMPLES=y +CONFIG_SAMPLE_RPMSG_CLIENT=m +CONFIG_RPMSG_KDRV_DISPLAY=y +CONFIG_RPMSG_PROTO=m diff --git a/bsp/ti-j72xx/ti-j72xx-remoteproc.scc b/bsp/ti-j72xx/ti-j72xx-remoteproc.scc new file mode 100644 index ..1848f96b --- /dev/null +++ b/bsp/ti-j72xx/ti-j72xx-remoteproc.scc @@ -0,0 +1 @@ +kconf hardware ti-j72xx-remoteproc.cfg diff --git a/bsp/ti-j72xx/ti-j72xx-standard.scc b/bsp/ti-j72xx/ti-j72xx-standard.scc new file mode 100644 index ..650c3377 --- /dev/null +++ b/bsp/ti-j72xx/ti-j72xx-standard.scc @@ -0,0 +1,8 @@ +# SPDX-License-Identifier: MIT +define KMACHINE ti-j72xx +define KTYPE standard +define KARCH arm64 + +include ktypes/standard/standard.scc + +include ti-j72xx.scc diff --git a/bsp/ti-j72xx/ti-j72xx.cfg b/bsp/ti-j72xx/ti-j72xx.cfg new file mode 100755 index ..318fb808 --- /dev/null +++ b/bsp/ti-j72xx/ti-j72xx.cfg @@ -0,0 +1,344 @@ +# +# WARNING +# +# This file is a kernel configuration fragment, and not a full kernel +# configuration file. The final kernel configuration is made up of +# an assembly of processed fragments, each of which is designed to +# capture a specific part of the final configuration (e.g. platform +# configuration, feature configuration, and board specific hardware +# configuration). For more information on kernel configuration, please +# consult the product documentation. +# +#. + +# +# +# Platform selection +# +CONFIG_ARM64=y +CONFIG_ARCH_K3=y + +CONFIG_ARCH_K3_J721E_SOC=y +CONFIG_ARM_SMMU=y +CONFIG_ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT=y +CONFIG_ARM_SMMU_V3=y +CONFIG_TI_PAT=y +CONFIG_TI_PRUSS=m +CONFIG_ARCH_K3_AM6_SOC=y +CONFIG_CMA=y +CONFIG_DMA_CMA=y + +CONFIG_EXPERT=y +CONFIG_ARM64_64K_PAGES=y +CONFIG_TRANSPARENT_HUGEPAGE=y +CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y + +# +# DesignWare PCI Core Support +# + +CONFIG_PCI=y +CONFIG_PCI_MSI=y +CONFIG_PCI_MSI_IRQ_DOMAIN=y +CONFIG_PCI_KEYSTONE=y +CONFIG_PCI_KEYSTONE_HOST=y +CONFIG_PCI_J721E_HOST=y +CONFIG_PCI_J721E_EP=y +CONFIG_PCI_ENDPOINT=y +CONFIG_PCI_J721E=y +CONFIG_SOCIONEXT_SYNQUACER_PREITS=y +CONFIG_PCIE_CADENCE=y +CONFIG_PCIE_CADENCE_HOST=y +CONFIG_PCIE_CADENCE_EP=y +CONFIG_PCI_EPF_NTB=y +CONFIG_PCIEPORTBUS=y +CONFIG_PCI_KEYSTONE_EP=y +CONFIG_PHY_CADENCE_TORRENT=y +CONFIG_PHY_CADENCE_SIERRA=y +CONFIG_BLK_DEV_NVME=y + +# +# MMC/SD/SDIO Host Controller Drivers +# +CONFIG_MMC=y +CONFIG_MMC_SPI=y +CONFIG_MMC_SDHCI=y +CONFIG_MMC_SDHCI_PLTFM=y +CONFIG_MMC_SDHCI_AM654=y + +# +# Power management options +# +CONFIG_PM_SLEEP=y +CONFIG_PM_SLEEP_SMP=y +CONFIG_PM=y +CONFIG_PM_CLK=y +CONFIG_CPU_PM=y + +# +# CPU Frequency scaling +# +CONFIG_CPU_FREQ=y +CONFIG_CPU_FREQ_GOV_ATTR_SET=y +CONFIG_CPU_FREQ_GOV_COMMON=y +CONFIG_CPU_FREQ_STAT=y +CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y +CONFIG_CPU_FREQ_GOV_PERFORMANCE=y +CONFIG_CPU_FREQ_GOV_USERSPACE=y +CONFIG_CPU_FREQ_GOV_ONDEMAND=y +CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y + +# +# CPU frequency scaling drivers +# +CONFIG_CPUFREQ_DT=y +CONFIG_CPUFREQ_DT_PLATDEV=y + +# +# Bus devices +# +CONFIG_MTD=y +CONFIG_MTD_CMDLINE_PARTS=y +CONFIG_MTD_OF_PARTS=y +CONFIG_MTD_BLKDEVS=y +CONFIG_MTD_BLOCK=y + +# +# SCSI device support +# +CONFIG_SCSI=y +CONFIG_BLK_DEV_SD=y +CONFIG_SCSI_UFS_TI_J721E=y +CONFIG_SCSI_UFSHCD=y +CONFIG_SCSI_UFSHCD_PLATFORM=y +CONFIG_SCSI_UFS_CDNS_PLATFORM=y +CONFIG_SCSI_UFS_BSG=y + +# +# USB +# +CONFIG_USB=y +CONFIG_USB_XHCI_HCD=y +CONFIG_USB_DWC3=y +CONFIG_USB_DWC3_OF_SIMPLE=y +CONFIG_HAS_DMA=y +CONFIG_OMAP_USB2=y +CONFIG_USB_DWC3_KEYSTONE=y +CONFIG_USB_GADGET=m +CONFIG_USB_CDNS3=m +CONFIG_USB_CDNS3_GADGET=y +CONFIG_USB_CDNS3_HOST=y +CONFIG_USB_CDNS3_TI=m +CONFIG_USB_MUSB_HDRC=m +CONFIG_USB_MUSB_DUAL_ROLE=y
[yocto] [meta-rockchip][PATCH] layer.conf: Add hardknott to compatible release branches
Signed-off-by: Khem Raj --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 8eecdc5..db9961c 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -14,5 +14,5 @@ BBFILE_PRIORITY_rockchip = "1" # This should only be incremented on significant changes that will # cause compatibility issues with other layers LAYERVERSION_rockchip = "1" -LAYERSERIES_COMPAT_rockchip = "gatesgarth" +LAYERSERIES_COMPAT_rockchip = "gatesgarth hardknott" LAYERDEPENDS_rockchip = "core meta-arm" -- 2.31.0 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52758): https://lists.yoctoproject.org/g/yocto/message/52758 Mute This Topic: https://lists.yoctoproject.org/mt/81423482/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
