[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNASyzmYjjBkFxRc06rqf36-en-bvJvrKcg6iiRfjoPCxhQ@mail.gmail.com>
Date: Sat, 20 Jul 2019 12:25:58 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc: Arnd Bergmann <arnd@...db.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
DTML <devicetree@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
masahiroy@...nel.org
Subject: [Question] orphan platform data header
Hi.
I see several platform-data headers
that are not used in upstream.
For instance, please look at this driver:
drivers/leds/leds-netxbig.c
If I understood it correctly, this driver
supports both device tree and legacy board-file.
I grepped 'netxbig_led_platform_data', but
I only found the driver and platform_data header.
No board-file in upstream.
masahiro@...ver:~/ref/linux$ git grep netxbig_led_platform_data
drivers/leds/leds-netxbig.c: struct
netxbig_led_platform_data *pdata,
drivers/leds/leds-netxbig.c: struct
netxbig_led_platform_data *pdata)
drivers/leds/leds-netxbig.c: struct
netxbig_led_platform_data *pdata)
drivers/leds/leds-netxbig.c: struct netxbig_led_platform_data
*pdata = dev_get_platdata(&pdev->dev);
include/linux/platform_data/leds-kirkwood-netxbig.h:struct
netxbig_led_platform_data {
So, what shall we do?
Drop the board-file support? Or, keep it
in case somebody is still using their board-files
in downstream?
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists