From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Merge all ns16550 dm serial drivers into one
Date: Fri, 14 Aug 2015 10:58:27 -0600 [thread overview]
Message-ID: <55CE1E33.8040005@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ2QP50koDqpXpNJ8L33+b_ZOM3DUWr2RBoS=L97dGLirw@mail.gmail.com>
On 08/14/2015 10:50 AM, Simon Glass wrote:
> Hi Bin,
>
> On 14 August 2015 at 03:18, Bin Meng <bmeng.cn@gmail.com> wrote:
>> Hi,
>>
>> Currently there are 5 dm serial drivers, all of which are ns16550
>> compatible drivers. They are:
>>
>> serial_omap.c
>> serial_dw.c
>> serial_tegra.c
>> serial_x86.c
>> serial_ppc.c
>>
>> All these drivers are pretty much similar. I think we can justmerge
>> these into one ns16550 driver.
>>
>> If you think this is necessary, I will send a patch series to do this.
>
> The tegra one is there because it needs an input clock and Stephen
> didn't want to add this to the device tree binding (the kernel has a
> clock framework which gets around this problem).
>
> After that I followed the same pattern. I would support updating the
> binding to support an input clock. Even with the new clock framework
> in U-Boot it might be painful to fit it into SPL in some cases.
The clock is already in the DT, in both Linux and U-Boot's copy, at
least for Tegra DTs:
uarta: serial at 0,70006000 {
compatible = "nvidia,tegra124-uart", ...
...
clocks = <&tegra_car TEGRA124_CLK_UARTA>;
next prev parent reply other threads:[~2015-08-14 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 9:18 [U-Boot] [RFC] Merge all ns16550 dm serial drivers into one Bin Meng
2015-08-14 16:50 ` Simon Glass
2015-08-14 16:58 ` Stephen Warren [this message]
2015-08-14 16:59 ` Simon Glass
2015-08-14 22:40 ` Bin Meng
2015-08-14 22:51 ` Stephen Warren
2015-08-14 23:18 ` Simon Glass
2015-08-14 23:57 ` Bin Meng
2015-08-15 2:56 ` Stephen Warren
2015-08-15 3:09 ` Bin Meng
2015-08-15 2:57 ` Stephen Warren
2015-08-15 3:12 ` Bin Meng
2015-08-15 4:05 ` Stephen Warren
2015-08-16 21:10 ` Simon Glass
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=55CE1E33.8040005@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox