martinayotte

  • Content Count

    3873
  • Joined

  • Last visited

About martinayotte

  • Rank
    Embedded member

Recent Profile Visitors

7235 profile views
  1. It won't appear as subfolder, but as direct node /dev/spidev0.0 ... Also, check with "dmesg | grep spi" ...
  2. Look at this doc file : /boot/dtb/overlay/README.sun8i-h3-overlays
  3. You've forgot to define "param_spidev_spi_bus" which is mandatory ...
  4. I'm not understanding exactly. Maybe because I've always producing patches manually ... Here is a summary of how I would do it : (edit the file to add "gpio-line-names" manually) nano cache/sources/linux-odroidxu4/odroid-5.4.y/arch/arm/boot/dts/exynos5420-pinctrl.dtsi (save) pushd cache/sources/linux-odroidxu4/odroid-5.4.y/ git diff arch/arm/boot/dts/exynos5420-pinctrl.dtsi > ~/my-gpio-line-names.patch popd mv ~/my-gpio-line-names.patch patches/kernel/odroidxu4-dev/odroidxu4-add-gpio-line-names.patch
  5. Be carefull : phandle can vary between builds, so better use <&pio> and <&r_pio> symbols. As I said earlier, append you overlay code in some new board specific patch such as ./patch/kernel/sunxi-dev/nanopi-duo/board-h2plus-nanopi-duo-add-overlay.patch which will also provide change to arch/arm/boot/dts/overlay/Makefile.
  6. I would choose to simply add another fragment in the same overlay ...
  7. Do you mean PL ? Simply add another "gpio-line-names" entry into "pinctrl@1f02c00" node.
  8. I've manually copied my gpio-line-names.dtbo under /boot/dts/overlay/sun8i-h3-gpio-line-names.dtbo Then, I added "overlays=gpio-line-names" in /boot/armbianEnv.txt, and rebooted ... Yes, my test was for OrangePiPC+, and tested using libgpiod "gpioinfo" ...
  9. Although I've never tried, patches could be board specific using a subdirectory such as ./patch/kernel/sunxi-dev/nanopi-duo/board-h2plus-nanopi-duo-add-device.patch BTW, I've tried dynamic loading of gpio-line-names.dtbo overlay, but it doesn't work, but doing it in /boot/armbianEnv.txt works. I think it is due that gpio-lines-names property is only checked while initializing pinctrl at boot time.
  10. For Allwinners SoC, you simply add new overlay to existing patch located there : https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/general-sunxi-overlays.patch You need to add DTS, but also add entry into the Makefile.
  11. In this specific case, since it is for exynos5420 which doesn't have any overlay mecanism yet, I will leave your PR as is ...
  12. Here is a quick/not-tested/incomplete overlay sources named gpio-line-names.dts : /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@1 { target = <&pio>; __overlay__ { gpio-line-names = "", "", "", "", "TX", "RX", "", "", "", "", "", "", "", "", "", "STATUS-LED", "MUTE", "SPDIF-OUT", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", ""; }; }; }; Then, compile it as DTB with this command : dtc -O dtb -I dts -o gpio-line-names.dtbo gpio
  13. Do you mean how to write an overlay ? Or do you mean how "gpio-line-names" is used ? Here is a general example from https://elixir.bootlin.com/linux/v4.7/source/Documentation/devicetree/bindings/gpio/gpio.txt gpio-controller@00000000 { compatible = "foo"; reg = <0x00000000 0x1000>; gpio-controller; #gpio-cells = <2>; ngpios = <18>; gpio-line-names = "MMC-CD", "MMC-WP", "VDD eth", "RST eth", "LED R", "LED G", "LED B", "Col A", "Col B", "Col C", "Col D", "Row A", "Row B", "Row C", "Row D", "NMI button", "poweroff", "reset"; }