All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Lawrence <stephen.lawrence@renesas.com>
To: linux-sh@vger.kernel.org
Subject: RE: [PATCH 2/2] ARM: shmobile: r8a7794: alt: Enable ethernet controller
Date: Mon, 09 Feb 2015 14:36:17 +0000	[thread overview]
Message-ID: <SINPR06MB2987EA04DA1ACD9FAF76FD792270@SINPR06MB298.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <1422348356-18675-2-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Hi Guys,

> -----Original Message-----
> From: linux-sh-owner@vger.kernel.org [mailto:linux-sh-
> owner@vger.kernel.org] On Behalf Of Laurent Pinchart
> Sent: 05 February 2015 12:18
> To: Sergei Shtylyov; linux-sh@vger.kernel.org
> Subject: Re: [PATCH 2/2] ARM: shmobile: r8a7794: alt: Enable ethernet
> controller
> 

[snip]

> > >>> The hardware manual tells me the PHY uses IRQ8#, not IRQ0#.
> > >>
> > >> I don't have the complete Alt schematics.
> > >>
> > > I don't have *any* Alt schematics, only SILK.
> >
> > And SILK also has the PHY IRQ connected to IRQ8#.
> >
> > >> I've double-checked the block
> > >> diagram and it mentions "GP1_24(IRQ)"
> > >>
> > > GP1_24 is connected to the PHY's RST# pin, according to the hardware
> > > manual. Which seems bad to me -- we hardly needed such kind of reset with
> > > the device tree. :-/ Hopefully, U-Boot leaves it high...
> > >
> > >> next to the PHY. This patch is thus
> > >> incorrect, but where did you find a mention of IRQ8 ?
> > >>
> > > In the Alt hardware manual, rev. 0.04. :-)
> >
> > Mentioned in several places there.
> >
> > Probably it makes sense to compare the dates of our documents. The
> > aforementioned manual is dated June 4, 2014.
> 
> The block diagram I have mentions "Rev0.04 Nov 22, 2013", as well as
> "PRELIMINARY". Let's use IRQ8 then. IRQ0 is clearly wrong anyway, and we can
> always fix this later if the hardware manual is wrong.
> 

The Alt schematics I have (rev 0.18 April 24 2014) match what you are saying.
RST# on the PHY connected to GP1_24 and INTRP to IRQ8# with pull and pull down resistors as shown in the h/w manual 0.04 Debug Ether block diagram.

Cheers

Steve

  parent reply	other threads:[~2015-02-09 14:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  8:45 [PATCH 2/2] ARM: shmobile: r8a7794: alt: Enable ethernet controller Laurent Pinchart
2015-01-27  8:53 ` Geert Uytterhoeven
2015-01-27  8:55 ` Laurent Pinchart
2015-01-28  6:48 ` Simon Horman
2015-02-03 21:43 ` Sergei Shtylyov
2015-02-04 17:29 ` Laurent Pinchart
2015-02-04 17:38 ` Sergei Shtylyov
2015-02-04 18:12 ` Geert Uytterhoeven
2015-02-04 18:18 ` Sergei Shtylyov
2015-02-04 19:37 ` Sergei Shtylyov
2015-02-05 12:17 ` Laurent Pinchart
2015-02-05 12:35 ` Sergei Shtylyov
2015-02-05 14:47 ` Laurent Pinchart
2015-02-09 14:36 ` Stephen Lawrence [this message]
2015-02-09 17:05 ` Laurent Pinchart
2015-02-09 17:15 ` Sergei Shtylyov

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=SINPR06MB2987EA04DA1ACD9FAF76FD792270@SINPR06MB298.apcprd06.prod.outlook.com \
    --to=stephen.lawrence@renesas.com \
    --cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.