public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux@arm.linux.org.uk,
	arnd@arndb.de, linux-sh@vger.kernel.org,
	linux-kernel@vger.kernel.org, rjw@sisk.pl, lethal@linux-sh.org,
	olof@lixom.net
Subject: Re: [PATCH 00/08] mach-shmobile: Emma Mobile EV2 support V3
Date: Fri, 18 May 2012 12:30:42 +0900	[thread overview]
Message-ID: <20120518033041.GA15280@verge.net.au> (raw)
In-Reply-To: <20120518014424.GL19000@verge.net.au>

On Fri, May 18, 2012 at 10:44:26AM +0900, Simon Horman wrote:
> Hi Magnus,
> 
> I have tested these patches on top of the soc-new branch of
> rafael's renesas tree, revision 5658c94, which is based on
> v3.4-rc6.
> 
> I also have the cherry picked following patches before applying your patches.
> 
> serial8250-em: clk_get() IS_ERR() error handling fix
> serial8250-em: Emma Mobile UART driver V2
> serial8250: Introduce serial8250_register_8250_port()
> serial8250: Clean up default map and dl code
> serial8250: Use dl_read()/dl_write() on RM9K
> serial8250: Use dl_read()/dl_write() on Alchemy
> serial8250: Add dl_read()/dl_write() callbacks
> 8250.c: less than 2400 baud fix.
> serial/8250_pci: Clear FIFOs for Intel ME Serial Over Lan device on BI
> tegra, serial8250: add ->handle_break() uart_port op
> clocksource: em_sti: Add DT support
> clocksource: em_sti: Emma Mobile STI driver V2
> clockevents: Make clockevents_config() a global symbol
> 
> I have added the follwing patch of yours
> 
> gpio: Emma Mobile GPIO driver V2
> 
> And one of my own, which just fixes a build problem
> in rafael's tree.
> 
> ARM: mach-types: Manually add KZM-A9-GT
> 
> On Wed, May 16, 2012 at 03:44:49PM +0900, Magnus Damm wrote:
> > mach-shmobile: Emma Mobile EV2 support V3
> > 
> > [PATCH 01/08] mach-shmobile: Emma Mobile EV2 SoC base support V3
> 
> Tested-by: Simon Horman <horms@verge.net.au>
> 
> > [PATCH 02/08] ARM: Undelete KZM9D mach-type V3
> 
> I did not need this patch with the base I am using,
> so I did not test it.
> 
> Reviewed-by: Simon Horman <horms@verge.net.au>
> 
> > [PATCH 03/08] mach-shmobile: KZM9D board support V3
> 
> Tested-by: Simon Horman <horms@verge.net.au>
> 
> > [PATCH 04/08] mach-shmobile: Emma Mobile EV2 SMP support V3
> 
> Tested-by: Simon Horman <horms@verge.net.au>
> 
> > [PATCH 05/08] mach-shmobile: Emma Mobile EV2 GPIO support V3
> 
> I am only seeing interripts for em_gio.0, is there a
> way to exercise em_gio.1 .. 4 ?
> 
> Duplicate names for interrupts, that is
> each of em_gio.0..4 have two entries in /proc/interripts.
> Is this intentional?
> 
>  99:         32          0       GIC  em_gio.0
>  100:          0          0       GIC  em_gio.0
>  101:          0          0       GIC  em_gio.1
>  102:          0          0       GIC  em_gio.1
>  103:          0          0       GIC  em_gio.2
>  104:          0          0       GIC  em_gio.2
>  105:          0          0       GIC  em_gio.3
>  106:          0          0       GIC  em_gio.3
>  107:          0          0       GIC  em_gio.4
>  108:          0          0       GIC  em_gio.4
>  157:      35952          0       GIC  em_sti.0
> 
> > [PATCH 06/08] mach-shmobile: KZM9D board Ethernet support V3
> 
> Tested-by: Simon Horman <horms@verge.net.au>
> 
> > [PATCH 07/08] mach-shmobile: Emma Mobile EV2 DT support V3
> 
> I applied this and the resulting kernel booted.
> 
> > [PATCH 08/08] mach-shmobile: Use DT_MACHINE for KZM9D V3
> 
> I applied this and the resulting kernel did not boot.
> I saw nothing after the uboot prompt..

Thanks for walking me through how to manually adding the dtb to the zImage.

Tested-by: Simon Horman <horms@verge.net.au>

> Lastly, could you consider suppling a patch which provides a defconfig?


  reply	other threads:[~2012-05-18  3:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  6:44 [PATCH 00/08] mach-shmobile: Emma Mobile EV2 support V3 Magnus Damm
2012-05-16  6:44 ` [PATCH 01/08] mach-shmobile: Emma Mobile EV2 SoC base " Magnus Damm
2012-05-16  6:56   ` Paul Mundt
2012-05-16  9:49     ` Magnus Damm
2012-05-16  6:45 ` [PATCH 02/08] ARM: Undelete KZM9D mach-type V3 Magnus Damm
2012-05-16  6:45 ` [PATCH 03/08] mach-shmobile: KZM9D board support V3 Magnus Damm
2012-05-16  6:45 ` [PATCH 04/08] mach-shmobile: Emma Mobile EV2 SMP " Magnus Damm
2012-05-16  6:45 ` [PATCH 05/08] mach-shmobile: Emma Mobile EV2 GPIO " Magnus Damm
2012-05-16  6:45 ` [PATCH 06/08] mach-shmobile: KZM9D board Ethernet " Magnus Damm
2012-05-16  6:45 ` [PATCH 07/08] mach-shmobile: Emma Mobile EV2 DT " Magnus Damm
2012-05-16  6:46 ` [PATCH 08/08] mach-shmobile: Use DT_MACHINE for KZM9D V3 Magnus Damm
2012-05-18  1:44 ` [PATCH 00/08] mach-shmobile: Emma Mobile EV2 support V3 Simon Horman
2012-05-18  3:30   ` Simon Horman [this message]
2012-05-18  3:40   ` Magnus Damm
2012-05-18  4:46     ` Simon Horman
2012-06-11  3:55 ` Paul Mundt

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=20120518033041.GA15280@verge.net.au \
    --to=horms@verge.net.au \
    --cc=arnd@arndb.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=olof@lixom.net \
    --cc=rjw@sisk.pl \
    /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