All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot-DM] [PATCH] drivers: serial: probe all serial devices
Date: Fri, 26 Oct 2018 13:26:48 +0200	[thread overview]
Message-ID: <20181026112648.4CC2A240044@gemini.denx.de> (raw)
In-Reply-To: <VI1PR04MB48005B3CB205F14C4670CC2BF3F70@VI1PR04MB4800.eurprd04.prod.outlook.com>

Dear Vabhav,

In message <VI1PR04MB48005B3CB205F14C4670CC2BF3F70@VI1PR04MB4800.eurprd04.prod.outlook.com> you wrote:
> 
> > U-Boot does lazy initialization intentionally.  It is wrong to initialize devices
> > which are not actually used.

> There is configuration option to enable the device using platform
> data or device tree using DM model.

"enable" means we have all required information needed to initialize
them, if we need them.  The need arises only when someone wants to
transfer data over that UART.  If nobody uses the UArt, there is no
need to ever initialize it.

Lazy initialization is a good thing - it saves resources, especially
memory and time.  Think for example of boot time optimizations...

> For e.g: 2 UART controllers are enabled in device tree but DM
> model initialized only one, This is limitation

In which way is this a limitation?  We use only one UART (for the
serial console), so it works as supposed: only the used devices are
fully initialized.


> My suggestion is to initialize all devices which are enabled, E.g.
> use case is using UART1 for uboot consoled and UART2 for linux boot

What do you mean "for Linux boot"?  If Linux needs the UART, it will
initialize it itself in the Linux dvice driver.

> On NXP SoC, We also use UART3 for ethernet firmware logging but
> using DM model all enabled devices are not probed  posing
> limitation.

Again, this is intentional, and not a limitation.

And what exactly do you mean by "UART3 for ethernet firmware
logging"?

Maybe you should rethink your software concept.  We don't want to
have a zillion of ports in used if not really necessary.  Either you
use standard channels (STDOUT, STDERR) for logging.  Also, there
used to be a syslog compatible logging driver.

> > I have a feeling that you attempt to do the Wong Thing.

> I quoted the reason above and also discussed on in email(23 may) "
> [U-Boot-DM] QUERY:U-boot DM:SERIAL:Multiple On-chip UART
> Controller Support" with suggested solution from Simon which is
> sent as patch for review.

But Simon also explained "U-Boot only probes things in a 'lazy'
manner so far", and there should be really good reasons for
deviating from this principle.  In no way should a "probe all
devices" be made the default.

And Andreas also wrote how to solve this issue in a board-specific
way if it is really, really needed on some board.

However, you still fail to explain why you ned multiple serial ports
in U-Boot running in parallel.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Well, the way I see it, logic is only a way of being ignorant by num-
bers.                                 - Terry Pratchett, _Small Gods_

  reply	other threads:[~2018-10-26 11:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15  0:09 [U-Boot] [PATCH] drivers: serial: probe all serial devices Vabhav Sharma
2018-10-15 12:28 ` Bin Meng
2018-10-16  7:23   ` Vabhav Sharma
2018-10-19  3:25   ` Simon Glass
2018-10-25 14:00     ` Vabhav Sharma
2018-10-25 14:24     ` Bin Meng
2018-10-16  6:59 ` [U-Boot] [U-Boot-DM] " Marek Vasut
2018-10-16  7:20   ` Vabhav Sharma
2018-10-16  9:09     ` Marek Vasut
2018-10-25 13:51       ` Vabhav Sharma
2018-10-25 14:04         ` Wolfgang Denk
2018-10-25 14:19           ` Vabhav Sharma
2018-10-26 11:26             ` Wolfgang Denk [this message]
2018-11-02  8:40               ` Vabhav Sharma
2018-11-02 10:07                 ` [U-Boot] " Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181026112648.4CC2A240044@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.