From: Kevin Hilman <khilman@linaro.org>
To: Tushar Behera <tushar.behera@linaro.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, arnd@arndb.de,
patches@linaro.org, kgene.kim@samsung.com, olof@lixom.net
Subject: Re: [PATCH] ARM: EXYNOS: Consolidate multiple low-level UART port definitions
Date: Fri, 31 May 2013 11:20:45 -0700 [thread overview]
Message-ID: <871u8n105e.fsf@linaro.org> (raw)
In-Reply-To: <1369888827-9427-1-git-send-email-tushar.behera@linaro.org> (Tushar Behera's message of "Thu, 30 May 2013 10:10:27 +0530")
Tushar Behera <tushar.behera@linaro.org> writes:
> There are two definitions for low-level UART ports for Exynos platform.
> CONFIG_S3C_LOWLEVEL_UART_PORT is used for printing "Uncompressing
> Linux... done, booting the kernel." and CONFIG_S3C_UART for other
> low-level messages.
>
> The assumption for both the uart ports is that they are pre-configured
> in the bootloader. Since they are essentially the same always, it
> would be good to consolidate them to use only one macro, in this case
> 'DEBUG_S3C_UART' would be a better option.
>
> 'DEBUG_S3C_UART' is defined only if DEBUG_LL is enabled. We can safely
> disable this option when DEBUG_LL is not defined and we can boot various
> boards with different UART port settings. Only drawback of this
> approach is that when DEBUG_LL is not defined, we would be missing the
> print "Uncompressing Linux... done, booting the kernel."
Perfectly acceptable to me (and already the case on OMAP.)
> Since CONFIG_S3C_LOWLEVEL_UART_PORT is still used by other Samsung
> boards, the consolidation applies only for ARCH_EXYNOS.
>
> Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
Acked-by: Kevin Hilman <khilman@linaro.org>
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: EXYNOS: Consolidate multiple low-level UART port definitions
Date: Fri, 31 May 2013 11:20:45 -0700 [thread overview]
Message-ID: <871u8n105e.fsf@linaro.org> (raw)
In-Reply-To: <1369888827-9427-1-git-send-email-tushar.behera@linaro.org> (Tushar Behera's message of "Thu, 30 May 2013 10:10:27 +0530")
Tushar Behera <tushar.behera@linaro.org> writes:
> There are two definitions for low-level UART ports for Exynos platform.
> CONFIG_S3C_LOWLEVEL_UART_PORT is used for printing "Uncompressing
> Linux... done, booting the kernel." and CONFIG_S3C_UART for other
> low-level messages.
>
> The assumption for both the uart ports is that they are pre-configured
> in the bootloader. Since they are essentially the same always, it
> would be good to consolidate them to use only one macro, in this case
> 'DEBUG_S3C_UART' would be a better option.
>
> 'DEBUG_S3C_UART' is defined only if DEBUG_LL is enabled. We can safely
> disable this option when DEBUG_LL is not defined and we can boot various
> boards with different UART port settings. Only drawback of this
> approach is that when DEBUG_LL is not defined, we would be missing the
> print "Uncompressing Linux... done, booting the kernel."
Perfectly acceptable to me (and already the case on OMAP.)
> Since CONFIG_S3C_LOWLEVEL_UART_PORT is still used by other Samsung
> boards, the consolidation applies only for ARCH_EXYNOS.
>
> Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
Acked-by: Kevin Hilman <khilman@linaro.org>
next prev parent reply other threads:[~2013-05-31 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 4:40 [PATCH] ARM: EXYNOS: Consolidate multiple low-level UART port definitions Tushar Behera
2013-05-30 4:40 ` Tushar Behera
2013-05-30 21:11 ` Olof Johansson
2013-05-30 21:11 ` Olof Johansson
2013-05-31 2:58 ` Tushar Behera
2013-05-31 2:58 ` Tushar Behera
2013-05-31 18:20 ` Kevin Hilman [this message]
2013-05-31 18:20 ` Kevin Hilman
2013-06-04 9:43 ` Tushar Behera
2013-06-04 9:43 ` Tushar Behera
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=871u8n105e.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=patches@linaro.org \
--cc=tushar.behera@linaro.org \
/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.