linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Bastian Hecht <hechtb@gmail.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	linux-sh@vger.kernel.org, Paul Mundt <lethal@linux-sh.org>,
	linux-serial@vger.kernel.org,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [PATCH v3 3/3] ARM: mach-shmobile: r8a7740: Setup the serial devices using DT
Date: Tue, 5 Mar 2013 12:36:02 +0900	[thread overview]
Message-ID: <20130305033601.GP16128@verge.net.au> (raw)
In-Reply-To: <CABYn4sxPpzKGc83WkRYzcAzJ1TeDgBPgpjvnyGkvgy4kT4Jt6w@mail.gmail.com>

On Mon, Mar 04, 2013 at 04:44:30PM +0100, Bastian Hecht wrote:
> Hi Simon!
> 
> 2013/3/4 Magnus Damm <magnus.damm@gmail.com>:
> > Hi Simon,
> >
> > [Added Guennadi to CC]
> >
> > On Sat, Mar 2, 2013 at 10:31 AM, Simon Horman <horms@verge.net.au> wrote:
> >> On Fri, Mar 01, 2013 at 10:21:27AM -0600, Bastian Hecht wrote:
> >>> 2013/3/1 Simon Horman <horms@verge.net.au>:
> >>> > On Tue, Feb 26, 2013 at 11:03:28AM -0600, Bastian Hecht wrote:
> >>> >> We can now use the Device Tree for bringing up our serial devices. We
> >>> >> need to add an alternative early_devices list in setup-r8a7740 without
> >>> >> the serial devices and move them into the Armadillo-reference .dts config file.
> >>> >
> >>> > Hi Bastian,
> >>> >
> >>> > could you please refresh this patch on top of the current topic/intc-of.
> >>> > In particular, it conflicts with changes made by:
> >>> >
> >>> > ARM: shmobile: r8a7740: Do not use early devices with DT reference
> >>>
> >>> Sure.
> >>>
> >>> I've prepared the patch - but I start to wonder if the DT
> >>> specification for the SCIF devices should go into r8a7740.dtsi rather
> >>> than r8a7740-armadillo-reference.dts. So far it's included in
> >>> setup-r8a7740.c and not in the board code - that's a strong indication
> >>> for it, no?
> >>
> >> I forget exactly how the discussion went, but for the kzm9g the
> >> SDHI has ended up in the dts file for the board not the sh73a0 SoC.
> >>
> >> So I assume that r8a7740-armadillo-reference.dts is the correct place
> >> for SDHI on the armadillo.
> >>
> >> Magnus, can you confirm that SDHI belongs to the board not the SoC?
> >
> > What does the data sheet say?
> >
> > The SDHI hardware block is included in the SoC. It may however need
> > some board specific configuration. I believe the correct way is to
> > define the common parts in the SoC-specific dtsi file and add
> > board-specific configuration in the board-specific dts file. Perhaps
> > you can consult Guennadi about this, he has been tasked with SDHI and
> > MMCIF.
> >
> >>> I want to post a patchset for the CMT timer soon. There it's the same.
> >>
> >> Magnus, could you also let us know if CMT should go in the board or SoC dts?
> >
> > In the SoC. As a general rule, if there is a platform device in
> > setup-nnnn.c then the device does not need any board specific
> > configuration. Such devices should be put in the SoC-specific dtsi
> > file.
> 
> Ok I posted a v4 SCIF DT patchset putting the SCIF devices into r8a7740.dtsi.
> 
> Simon, are you aware about this in topic/intc-of? It shows up booting
> the non-DT version.
> 
> Unable to handle kernel NULL pointer dereference at virtual address 00000040
> pgd = c0004000
> [00000040] *pgd=00000000
> Internal error: Oops: 5 [#1] ARM
> CPU: 0    Not tainted  (3.8.0-rc3-00205-gfb2696a #298)
> PC is at __gpio_get_value+0x18/0x5c
> LR is at eva_init+0x190/0x544

Yes, I am aware of it, it is the reason that topic/intc-of is
not included in topic/all+next at the moment.

I believe it is caused by SH pinctl DT support.

http://permalink.gmane.org/gmane.linux.ports.sh.devel/19649


> We should add standard bootargs in the r8a7740-armadillo800eva.dts as
> well. Shall I post a small patch?

I have applied a patch to do that which should be present in v3.9-rc1.

Now that v3.9-rc1 has been released I will see about rebasing my
branches on top of it.

  reply	other threads:[~2013-03-05  3:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 17:03 [PATCH v3 1/3] serial: sh-sci: Add OF support Bastian Hecht
2013-02-26 17:03 ` [PATCH v3 2/3] ARM: mach-shmobile: r8a7740: Add DT names to clock list Bastian Hecht
2013-03-01  9:42   ` Simon Horman
2013-02-26 17:03 ` [PATCH v3 3/3] ARM: mach-shmobile: r8a7740: Setup the serial devices using DT Bastian Hecht
2013-03-01  9:42   ` Simon Horman
2013-03-01 16:21     ` Bastian Hecht
2013-03-02  1:31       ` Simon Horman
2013-03-04 12:48         ` Magnus Damm
2013-03-04 13:33           ` Guennadi Liakhovetski
2013-03-05  3:27             ` Simon Horman
2013-03-05  6:52               ` Guennadi Liakhovetski
2013-03-05  7:04                 ` Simon Horman
2013-03-04 15:44           ` Bastian Hecht
2013-03-05  3:36             ` Simon Horman [this message]
2013-02-27  8:07 ` [PATCH v3 1/3] serial: sh-sci: Add OF support Paul Mundt
2013-02-27  8:11   ` Magnus Damm
2013-02-27  8:19     ` Paul Mundt
2013-02-27  8:26       ` Magnus Damm
2013-02-27  9:04         ` Simon Horman
2013-02-27  9:34           ` Paul Mundt
2013-02-28 19:20             ` Bastian Hecht
2013-03-01  0:50             ` Simon Horman

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=20130305033601.GP16128@verge.net.au \
    --to=horms@verge.net.au \
    --cc=g.liakhovetski@gmx.de \
    --cc=hechtb@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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).