From: ian.molton@codethink.co.uk (Ian Molton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RFC] ARM: shmobile: Add early debugging support using SCIF(A)
Date: Tue, 7 Oct 2014 11:37:17 +0100 [thread overview]
Message-ID: <20141007113717.d8dcc5607caf23971ec06c9d@codethink.co.uk> (raw)
In-Reply-To: <2257006.dpJJ6zLgnP@avalon>
To be fair, my patches were in last month, and awaiting a chance to test on Rcar-H1...
Can we share credit (Signed-off-by:) on the core, lager, 7779, and Kconfig patches please?
Cheers guys :)
(Its been a crap year for me, I've had almost zero chance to mainline anything :( )
-Ian
On Mon, 06 Oct 2014 01:18 +0300
Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> Hi Geert,
>
> Thank you for the patch.
>
> It looks like you've beaten Ian Molton (CC'ed) on this, he was planning to
> send exactly the same thing.
>
> On Thursday 02 October 2014 21:02:43 Geert Uytterhoeven wrote:
> > Add serial port debug macros for the SCIF(A) serial ports.
> > This includes all shmobile SoCs, except for EMEV2.
> >
> > On SoCs using the legacy machine_desc.map_io(), an identity mapping of
> > the SCIF(A) registers must be set up in .map_io(). On all but r8a7779
> > this was already done.
> >
--
Ian Molton <ian.molton@codethink.co.uk>
next prev parent reply other threads:[~2014-10-07 10:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 19:02 [PATCH] [RFC] ARM: shmobile: Add early debugging support using SCIF(A) Geert Uytterhoeven
2014-10-03 0:04 ` Khiem Nguyen
2014-10-03 7:21 ` Geert Uytterhoeven
2014-10-03 10:19 ` Khiem Nguyen
2014-10-03 11:28 ` Geert Uytterhoeven
2014-10-05 22:18 ` Laurent Pinchart
2014-10-06 6:03 ` Wolfram Sang
2014-10-06 6:14 ` Magnus Damm
2014-10-06 8:56 ` Geert Uytterhoeven
2014-10-06 9:01 ` Wolfram Sang
2014-10-06 9:08 ` Geert Uytterhoeven
2014-10-07 10:37 ` Ian Molton [this message]
2014-10-07 11:07 ` Geert Uytterhoeven
2014-10-07 12:39 ` Geert Uytterhoeven
2014-10-05 23:36 ` Magnus Damm
2014-10-06 9:18 ` Geert Uytterhoeven
2014-10-07 10:49 ` Arnd Bergmann
2014-10-07 11:46 ` Geert Uytterhoeven
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=20141007113717.d8dcc5607caf23971ec06c9d@codethink.co.uk \
--to=ian.molton@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.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).