Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • early-display
  • variant-emmc-nvme-boot
  • 2023-01-25
  • v3
  • variant-emmc-nvme-boot
  • 2020-06-01
7 results

device.c

Blame
  • Forked from Reform / reform-boundary-uboot
    Source project has a limited visibility.
    • Simon Glass's avatar
      84d26e29
      dm: core: Don't use pinctrl for the root device · 84d26e29
      Simon Glass authored
      
      Currently when driver model starts up it finds the root uclass and the
      pinctrl uclass. This is because even the root node handles pinctrl
      processing.
      
      But this is not useful. The root node is not a real hardware device so
      cannot require any particular pinmux settings. Also it means that the
      memory leak tests fails, since they end up freeing more memory than
      they allocate: the marker it set after the root device and pinctrl
      uclass are allocated, and later once the pinctrl uclass is freed the memory
      used by driver model is less than when the marker was set.
      
      If a platform needs 'core' pin mulitplex settings it can do this with
      a driver that is probed on start-up. It would be an abuse of the root node
      to use this for pinctrl.
      
      To avoid this problem, only process pinctrl settings for non-root nodes.
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      84d26e29
      History
      dm: core: Don't use pinctrl for the root device
      Simon Glass authored
      
      Currently when driver model starts up it finds the root uclass and the
      pinctrl uclass. This is because even the root node handles pinctrl
      processing.
      
      But this is not useful. The root node is not a real hardware device so
      cannot require any particular pinmux settings. Also it means that the
      memory leak tests fails, since they end up freeing more memory than
      they allocate: the marker it set after the root device and pinctrl
      uclass are allocated, and later once the pinctrl uclass is freed the memory
      used by driver model is less than when the marker was set.
      
      If a platform needs 'core' pin mulitplex settings it can do this with
      a driver that is probed on start-up. It would be an abuse of the root node
      to use this for pinctrl.
      
      To avoid this problem, only process pinctrl settings for non-root nodes.
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>