• Lukas Bulwahn's avatar
    ata: clean up how architectures enable PATA_PLATFORM and PATA_OF_PLATFORM · 3ebe59a5
    Lukas Bulwahn authored
    There are two options for platform device PATA support:
    
      PATA_PLATFORM: Generic platform device PATA support
      PATA_OF_PLATFORM: OpenFirmware platform device PATA support
    
    If an architecture allows the generic platform device PATA support, it
    shall select HAVE_PATA_PLATFORM. Then, Generic platform device PATA support
    is available and can be selected.
    
    If an architecture has OpenFirmware support, which it indicates by
    selecting OF, OpenFirmware platform device PATA support is available
    and can be selected.
    If OpenFirmware platform device PATA support is selected, then the
    functionality (code files) from Generic platform device PATA support needs
    to be integrated in the kernel build for the OpenFirmware platform device
    PATA support to work. Select PATA_PLATFORM in PATA_OF_PLATFORM to make sure
    the needed files are added in the build.
    
    So, architectures with OpenFirmware support, do not need to additionally
    select HAVE_PATA_PLATFORM. It is only needed by architecture that want the
    non-OF pata-platform module.
    
    Reflect this way of intended use of config symbols in the ata Kconfig and
    adjust all architecture definitions.
    
    This follows the suggestion from Arnd Bergmann (see Link).
    Suggested-by: default avatarArnd Bergmann <arnd@arndb.de>
    Link: https://lore.kernel.org/all/4b33bffc-2b6d-46b4-9f1d-d18e55975a5a@www.fastmail.com/Signed-off-by: default avatarLukas Bulwahn <lukas.bulwahn@gmail.com>
    Reviewed-by: default avatarArnd Bergmann <arnd@arndb.de>
    Signed-off-by: default avatarDamien Le Moal <damien.lemoal@opensource.wdc.com>
    3ebe59a5
Kconfig 29.3 KB