public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] ppc4xx: Fix UART baudrate setup by FDT
Date: Mon, 5 Jan 2009 14:08:25 +0100	[thread overview]
Message-ID: <200901051408.25346.sr@denx.de> (raw)
In-Reply-To: <200901021215.13810.matthias.fuchs@esd-electronics.com>

Hi Matthias,

On Friday 02 January 2009, Matthias Fuchs wrote:
> On ppc4xx platforms __ft_board_setup updates clock-frequency
> properties of all ns16550 compatible UARTs. This is not a good
> idea when those UARTs are external discrete UARTs that are
> not clocked by some internal clocks. So any external clock value
> in the DTB is overwritten and those UARTs will not be setup correctly
> by the Linux kernel.
>
> This patch uses the approach from fdt_fixup_ethernet(). Only UART nodes
> that have a serial* alias are updated.

Wouldn't it be "better" to check if an external UART clock is configured via 
CONFIG_SYS_EXT_SERIAL_CLOCK and just use it instead of the calculated 
internal clock value in this case?

BTW: This patch version is not ppc4xx specific as it touches the common 
fdt_support.c. So you would need to split this patch if we decide to go your 
way.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2009-01-05 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-28 17:35 [U-Boot] [PATCH] ppc4xx: Fix UART baudrate setup by FDT Matthias Fuchs
2009-01-02 11:15 ` [U-Boot] [PATCH V2] " Matthias Fuchs
2009-01-05 13:08   ` Stefan Roese [this message]
2009-01-05 20:10     ` Matthias Fuchs
2009-01-06  8:07       ` Stefan Roese
2009-01-06 19:15         ` Matthias Fuchs
2009-01-07 15:37           ` Stefan Roese

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=200901051408.25346.sr@denx.de \
    --to=sr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox