From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] serial: 16550: Add JZ47xx support
Date: Thu, 26 May 2016 00:35:28 +0200 [thread overview]
Message-ID: <574628B0.6050708@denx.de> (raw)
In-Reply-To: <574627C3.8060906@gmail.com>
On 05/26/2016 12:31 AM, Daniel Schwierzeck wrote:
>
>
> Am 26.05.2016 um 00:21 schrieb Marek Vasut:
>> On 05/26/2016 12:17 AM, Daniel Schwierzeck wrote:
>>>
>>>
>>> Am 25.05.2016 um 02:19 schrieb Marek Vasut:
>>>> The Ingenic JZ47xx requires special bit (UART_EN) set in FCR register
>>>> in order to work at all. Add this special case handling into the driver.
>>>>
>>>> Signed-off-by: Marek Vasut <marex@denx.de>
>>>> Cc: Tom Rini <trini@konsulko.com>
>>>> Cc: Simon Glass <sjg@chromium.org>
>>>> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
>>>> Cc: Paul Burton <paul.burton@imgtec.com>
>>>> ---
>>>> drivers/serial/ns16550.c | 8 ++++++++
>>>> 1 file changed, 8 insertions(+)
>>>>
>>>> diff --git a/drivers/serial/ns16550.c b/drivers/serial/ns16550.c
>>>> index 30ba0aa..1323881 100644
>>>> --- a/drivers/serial/ns16550.c
>>>> +++ b/drivers/serial/ns16550.c
>>>> @@ -50,6 +50,14 @@ DECLARE_GLOBAL_DATA_PTR;
>>>> #endif
>>>> #endif
>>>>
>>>> +#ifdef CONFIG_ARCH_JZ47XX
>>>> +#undef UART_FCRVAL
>>>> +/* Ingenic JZ47xx SoCs require that a 'UART Module Enable' bit be set */
>>>> +#define UART_FCR_UME 0x10
>>>> +#define UART_FCRVAL (UART_FCR_FIFO_EN | UART_FCR_RXSR | \
>>>> + UART_FCR_TXSR | UART_FCR_UME)
>>>> +#endif
>>>
>>> I think this could be added as DT property
>>
>> Not for SPL, which has 14 kiB size limit and it is itching to overflow.
>> I am literally counting bytes in the SPL and removing slop from
>> structures to make it fit, just barely. With the USB loader, I can
>> brutalize the SPL into having extremely rudimentary UART support now
>> (like printch() being the most advanced output mechanism, but you can
>> only use it three times, otherwise the code won't fit and the board is
>> eaten by demons) and this is where this patch comes into play.
>>
>> So yes, for full u-boot, this _should_ be part of DT. For SPL, please apply.
>>
>
> ok, but wouldn't it be better to introduce an option like
> CONFIG_SYS_NS16550_UME instead of using the SoC-specific
> CONFIG_ARCH_JZ47XX. This driver is messed up enough ;)
I was undecided between this (like the IER) and adding new ifdef (like
SOC_KEYSTONE). Whichever way is fine with me. Yeah, the driver is
repugnant for sure.
>>>> +
>>>> #ifndef CONFIG_SYS_NS16550_IER
>>>> #define CONFIG_SYS_NS16550_IER 0x00
>>>> #endif /* CONFIG_SYS_NS16550_IER */
>>>>
>>>
>>
>>
>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-05-25 22:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 0:19 [U-Boot] [PATCH] serial: 16550: Add JZ47xx support Marek Vasut
2016-05-25 22:17 ` Daniel Schwierzeck
2016-05-25 22:21 ` Marek Vasut
2016-05-25 22:31 ` Daniel Schwierzeck
2016-05-25 22:35 ` Marek Vasut [this message]
2016-05-26 13:29 ` Simon Glass
2016-05-26 16:34 ` Marek Vasut
2016-05-26 16:44 ` Simon Glass
2016-05-26 16:47 ` Marek Vasut
2016-05-26 16:48 ` Simon Glass
2016-05-26 16:53 ` Marek Vasut
2016-05-26 17:07 ` Simon Glass
2016-05-26 17:35 ` Marek Vasut
2016-05-26 17:47 ` Simon Glass
2016-05-26 17:01 ` Marek Vasut
2016-05-26 11:46 ` Paul Burton
2016-05-26 12:05 ` Marek Vasut
2016-05-26 13:55 ` Paul Burton
2016-05-26 18:22 ` Marek Vasut
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=574628B0.6050708@denx.de \
--to=marex@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.