From: Scott Wood <scottwood@freescale.com>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCHv4 0/5] cpm2: Reset the CPM at startup and fix the cpm_uart driver accordingly.
Date: Tue, 01 Apr 2008 14:19:02 -0500 [thread overview]
Message-ID: <47F28AA6.7040903@freescale.com> (raw)
In-Reply-To: <200804011433.29841.laurentp@cse-semaphore.com>
Laurent Pinchart wrote:
> Hi everybody,
>
> these 5 patches reset the CPM in cpm2_reset() and fix the cpm_uart driver to
> initialise SMC ports correctly without relying on any initialisation
> performed by the boot loader/wrapper. They update the boot wrapper code and
> the EP8248E device tree to match the new SMC registers description.
>
> Patches 2/5, 3/5 and 4/5 (boot wrapper and EP8248E device tree updates)
> haven't been tested due to lack of hardware.
Tested OK on ep8248e.
ACK 1-5
-Scott
next prev parent reply other threads:[~2008-04-01 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 12:33 [PATCHv4 0/5] cpm2: Reset the CPM at startup and fix the cpm_uart driver accordingly Laurent Pinchart
2008-04-01 12:34 ` [PATCHv4 1/5] cpm_uart: Allocate DPRAM memory for SMC ports on CPM2-based platforms Laurent Pinchart
2008-04-01 12:34 ` [PATCHv4 2/5] powerpc: Add bootwrapper function to get virtual reg from the device tree Laurent Pinchart
2008-04-01 12:34 ` [PATCHv4 3/5] cpm-serial: Relocate CPM buffer descriptors and SMC parameter ram Laurent Pinchart
2008-04-01 12:35 ` [PATCHv4 4/5] ep8248e: Reference SMC parameter RAM base in the device tree Laurent Pinchart
2008-04-01 12:35 ` [PATCHv4 5/5] cpm2: Reset the CPM when early debugging is not enabled Laurent Pinchart
2008-04-01 19:19 ` Scott Wood [this message]
2008-04-10 15:14 ` [PATCHv4 0/5] cpm2: Reset the CPM at startup and fix the cpm_uart driver accordingly Kumar Gala
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=47F28AA6.7040903@freescale.com \
--to=scottwood@freescale.com \
--cc=laurentp@cse-semaphore.com \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).