From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 7/7] ARM: shmobile: kzm9g-reference: require ZB clock for Ethernet controller
Date: Wed, 05 Nov 2014 15:43:59 +0000 [thread overview]
Message-ID: <16651429.BGZ7UORT2h@avalon> (raw)
In-Reply-To: <1414515736-24905-8-git-send-email-ulrich.hecht+renesas@gmail.com>
Hi Geert,
On Thursday 30 October 2014 19:03:37 Geert Uytterhoeven wrote:
> On Thu, Oct 30, 2014 at 6:41 PM, Ulrich Hecht wrote:
> > On Wed, Oct 29, 2014 at 1:21 AM, Simon Horman <horms@verge.net.au> wrote:
> >> On Tue, Oct 28, 2014 at 06:02:16PM +0100, Ulrich Hecht wrote:
> >>> Unlike the legacy stuff, CCF disables the ethernet controller's clock
> >>> unless it is used somewhere.
> >>
> >> This feels like it should come earlier in the series to avoid
> >> breaking then fixing ethernet support for kzm9g-reference.
> >
> > The CCF support, not being used yet, doesn't actually break anything.
> > The reason this patch is separated from the rest is that it works, but
> > it's not completely clear (to me) how.
> >
> > As Laurent has pointed out before, the LAN controller is not
> > (directly) hooked up to this clock, but to an external oscillator.
> > Nonetheless Ethernet won't work unless ZB is on, which I have
> > determined by trial and error. Maybe that should have been pointed out
> > in the description...
>
> I don't have the schematics for kzm9g, but I guess the LAN controller
> is hooked up to the BSC (Bus State Controller).
Yes it is. We should probably model the BSC in DT, and add the LAN controller
as a child of the BSC node. With automatic clock management in runtime PM,
could we do without a BSC driver entirely ?
> According to the sh73a0 datasheet, ZBø is the clock for the BSC.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-11-05 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 17:02 [PATCH v3 7/7] ARM: shmobile: kzm9g-reference: require ZB clock for Ethernet controller Ulrich Hecht
2014-10-29 0:21 ` Simon Horman
2014-10-30 17:41 ` Ulrich Hecht
2014-10-30 18:03 ` Geert Uytterhoeven
2014-10-31 9:56 ` Ulrich Hecht
2014-11-05 0:36 ` Simon Horman
2014-11-05 15:43 ` Laurent Pinchart [this message]
2014-11-05 21:06 ` Geert Uytterhoeven
2014-11-06 18:20 ` Laurent Pinchart
2014-11-10 9:14 ` Geert Uytterhoeven
2014-11-21 21:23 ` 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=16651429.BGZ7UORT2h@avalon \
--to=laurent.pinchart@ideasonboard.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 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).