From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/8] arm: K3: Add initial support for TI's K3 generation of SoCs
Date: Fri, 24 Aug 2018 20:21:19 +0530 [thread overview]
Message-ID: <ff8cdfbd-e599-a375-050c-75cd8caf2266@ti.com> (raw)
In-Reply-To: <20180824141054.GK26633@bill-the-cat>
On Friday 24 August 2018 07:40 PM, Tom Rini wrote:
> On Tue, Aug 21, 2018 at 08:00:48PM +0530, Lokesh Vutla wrote:
>
>> Add support for Texas Instruments' K3 Generation Processor
>> families.
> [snip]
>> diff --git a/drivers/serial/ns16550.c b/drivers/serial/ns16550.c
>> index 9c80090aa7..f48d82f051 100644
>> --- a/drivers/serial/ns16550.c
>> +++ b/drivers/serial/ns16550.c
>> @@ -175,7 +175,7 @@ void NS16550_init(NS16550_t com_port, int baud_divisor)
>> ;
>>
>> serial_out(CONFIG_SYS_NS16550_IER, &com_port->ier);
>> -#if defined(CONFIG_ARCH_OMAP2PLUS)
>> +#if defined(CONFIG_ARCH_OMAP2PLUS) || defined(CONFIG_ARCH_K3)
>> serial_out(0x7, &com_port->mdr1); /* mode select reset TL16C750*/
>> #endif
>>
>> @@ -183,7 +183,8 @@ void NS16550_init(NS16550_t com_port, int baud_divisor)
>> serial_out(ns16550_getfcr(com_port), &com_port->fcr);
>> if (baud_divisor != -1)
>> NS16550_setbrg(com_port, baud_divisor);
>> -#if defined(CONFIG_ARCH_OMAP2PLUS) || defined(CONFIG_SOC_DA8XX)
>> +#if defined(CONFIG_ARCH_OMAP2PLUS) || defined(CONFIG_SOC_DA8XX) || \
>> + defined(CONFIG_ARCH_K3)
>> /* /16 is proper to hit 115200 with 48MHz */
>> serial_out(0, &com_port->mdr1);
>> #endif
>
> K3 would also be using CONFIG_OMAP_SERIAL once
> https://patchwork.ozlabs.org/patch/956252/ is applied (which I'll do in
> the next release) yes? I think 956252 needs a follow-up that changes
> the above hunks to be testing off CONFIG_OMAP_SERIAL instead so this
I did not make this change because ns16550 is also used by non-DM
platforms. Since OMAP_SERIAL is DM specific, converting this #ifdef to
OMAP_SERIAL would break non DM platforms. I guess I should still add ||
OMAP_SERIAL. Ill post a v2 for 956252.
Thanks and regards,
Lokesh
next prev parent reply other threads:[~2018-08-24 14:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 14:30 [U-Boot] [PATCH 0/8] [1/3] Initial support Texas Instrument's AM654 Platform Lokesh Vutla
2018-08-21 14:30 ` [U-Boot] [PATCH 1/8] arm: K3: Add initial support for TI's K3 generation of SoCs Lokesh Vutla
2018-08-24 14:10 ` Tom Rini
2018-08-24 14:51 ` Lokesh Vutla [this message]
2018-08-24 14:55 ` Tom Rini
2018-08-24 15:14 ` Lokesh Vutla
2018-08-24 15:21 ` Tom Rini
2018-08-21 14:30 ` [U-Boot] [PATCH 2/8] arm: K3: Add support for AM654 SoC definition Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-24 14:58 ` Lokesh Vutla
2018-08-24 15:01 ` Tom Rini
2018-08-21 14:30 ` [U-Boot] [PATCH 3/8] arm: K3: Update _start instruction Lokesh Vutla
2018-08-21 14:30 ` [U-Boot] [PATCH 4/8] arm: K3: am654: Add support for boot device detection Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-24 14:58 ` Lokesh Vutla
2018-08-21 14:30 ` [U-Boot] [PATCH 5/8] arm: K3: am654: Unlock control module registers during init Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-21 14:30 ` [U-Boot] [PATCH 6/8] armv8: K3: am654: Add custom MMU support Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-21 14:30 ` [U-Boot] [PATCH 7/8] armv8: K3: am654: Introduce FIT generator script Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-24 14:59 ` Lokesh Vutla
2018-08-21 14:30 ` [U-Boot] [PATCH 8/8] armv8: K3: am654: Add support for generating build targets Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-26 6:11 ` [U-Boot] [PATCH 0/8] [1/3] Initial support Texas Instrument's AM654 Platform Alexander Graf
2018-08-27 9:31 ` Lokesh Vutla
2018-08-27 9:52 ` Alexander Graf
2018-08-27 10:07 ` Lokesh Vutla
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=ff8cdfbd-e599-a375-050c-75cd8caf2266@ti.com \
--to=lokeshvutla@ti.com \
--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