-----Original Message----- From: sjg@google.com sjg@google.com On Behalf Of Simon Glass Sent: Friday, October 19, 2018 8:56 AM To: Bin Meng bmeng.cn@gmail.com Cc: Vabhav Sharma vabhav.sharma@nxp.com; U-Boot Mailing List <u- boot@lists.denx.de>; u-boot-dm@lists.denx.de; Andreas Dannenberg dannenberg@ti.com; Masahiro Yamada yamada.masahiro@socionext.com; Stefan Roese sr@denx.de Subject: Re: [PATCH] drivers: serial: probe all serial devices
Hi Bin,
On 15 October 2018 at 06:28, Bin Meng bmeng.cn@gmail.com wrote:
On Mon, Oct 15, 2018 at 8:15 PM Vabhav Sharma
vabhav.sharma@nxp.com wrote:
Serial subsystem search and probe only one first serial device and unable to use remaining available UART devices
This patch changes the logic to probe all available serial devices using platform data or device tree in DM model in order to use all UART devices
Signed-off-by: Vabhav Sharma vabhav.sharma@nxp.com
drivers/serial/Kconfig | 12 ++++++++++++ drivers/serial/serial-uclass.c | 42 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 54 insertions(+)
Looks more and more devices have requirement to be probed during boot. Guess we should handle such in a unified way?
How about:
- in dm_init(), after binding, we move on to an auto-probe step
- a uclass flag indicates that all devices in that uclass must be probed (that
will be useful for PCI)
For devices class respective UCLASS to be provided with auto-probe, How many class to be included?
- a way to tell DM to probe all devices in a particular uclass (e.g. a call to
dm_set_uclass_autoprobe(enum uclass_id, bool) (that will be useful for this serial case)
Do you mean to verify and send patch for serial uclass with this approach after device_probe in dm_init
Regards, Simon