All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Paul Walmsley <paul@pwsan.com>
Cc: mporter@linaro.org, Benoit Cousson <bcousson@baylibre.com>,
	joelagnel@ti.com, NeilBrown <neilb@suse.de>,
	linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
	Wolfram Sang <wsa@sang-engineering.com>
Subject: Re: [PATCH] ARM: OMAP2+: don't try to register the main clock twice.
Date: Thu, 8 May 2014 09:02:58 +0200	[thread overview]
Message-ID: <20140508070258.GA2656@katana> (raw)
In-Reply-To: <alpine.DEB.2.02.1405072233470.23579@utopia.booyaka.com>

[-- Attachment #1: Type: text/plain, Size: 984 bytes --]


> > I also get this message printed for the d_can driver with am335x; they 
> > have two entries in drivers/clk/ti/clk-33xx.c. Probably as a workaround 
> > to match the desired clock name for the d_can driver? Didn't really 
> > investigate yet.
> 
> That's pretty weird.  I wonder where the second fck alias is coming from?  
> The DT & hwmod data for those devices looks relatively straightforward.  
> Is the hwmod code adding fck aliases for both of the entries from the 
> clock file?

$ grep 'can' drivers/clk/ti/clk-33xx.c 
 * This program is free software; you can redistribute it and/or
	DT_CLK(NULL, "dcan0_fck", "dcan0_fck"),
	DT_CLK("481cc000.d_can", NULL, "dcan0_fck"),
	DT_CLK(NULL, "dcan1_fck", "dcan1_fck"),
	DT_CLK("481d0000.d_can", NULL, "dcan1_fck"),

I quickly tried to remove the entries not specifying platform devices
but that prevented my system from booting (Huh?). Still, no time to
really check it, though.

Thanks,

   Wolfram


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2014-05-08  7:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 11:50 [PATCH] ARM: OMAP2+: don't try to register the main clock twice Wolfram Sang
2014-04-11 18:33 ` Paul Walmsley
2014-04-17  8:55   ` Wolfram Sang
2014-05-07 23:20     ` Paul Walmsley
2014-05-08  7:02       ` Wolfram Sang [this message]

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=20140508070258.GA2656@katana \
    --to=wsa@the-dreams.de \
    --cc=bcousson@baylibre.com \
    --cc=joelagnel@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mporter@linaro.org \
    --cc=neilb@suse.de \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.com \
    --cc=wsa@sang-engineering.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 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.