You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment the Kconfig logic for disks is using CONFIG_DISK_ACCESS as a "driver" to select CONFIG_DISK_DRIVERS and to get the correct disk driver in the code. Also the DT_HAS_..._ENABLED mechanism is used to enable the correct driver from devicetree.
Would it not be better to use the DT_HAS_..._ENABLED mechanism to select the driver and to use imply DISK_ACCESS in each of the driver Kconfigs (as each of the drivers is using disk_access_register)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
At the moment the Kconfig logic for disks is using
CONFIG_DISK_ACCESS
as a "driver" to selectCONFIG_DISK_DRIVERS
and to get the correct disk driver in the code. Also the DT_HAS_..._ENABLED mechanism is used to enable the correct driver from devicetree.Would it not be better to use the DT_HAS_..._ENABLED mechanism to select the driver and to use
imply DISK_ACCESS
in each of the driver Kconfigs (as each of the drivers is usingdisk_access_register
)?@danieldegrasse, @jfischer-no
Beta Was this translation helpful? Give feedback.
All reactions