All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Tony Lindgren" <tony@atomide.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"Aaro Koskinen" <aaro.koskinen@iki.fi>,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] HSI: omap-ssi: add clk change support
Date: Wed, 24 Feb 2016 18:05:30 +0100	[thread overview]
Message-ID: <20160224170530.GA343@earth> (raw)
In-Reply-To: <4852048.rpY1LniVlK@wuerfel>

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

Hi,

On Wed, Feb 24, 2016 at 04:19:09PM +0100, Arnd Bergmann wrote:
> On Tuesday 23 February 2016 03:34:43 Sebastian Reichel wrote:
> > 
> > On Sun, Jan 31, 2016 at 01:52:38AM +0100, Sebastian Reichel wrote:
> > > This adds support for frequency changes of the SSI
> > > functional clock, which may occur due to DVFS.
> > 
> > I queued this one for 4.6.
> > 
> 
> This causes a regression when SSI is a loadable module:
> 
> ERROR: "omap_ssi_port_update_fclk" [drivers/hsi/controllers/omap_ssi.ko] undefined!

Thanks for the notice.

> I suspect that there is now some form of circular dependency between the
> various modules, but I couldn't figure it out. Can you have a look,
> and maybe revert the commit in linux-next for the time being?

I dropped the patch from my -next branch until I figured out what's
going on.

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-02-24 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31  0:52 [PATCH 0/2] omap-ssi: clk change support Sebastian Reichel
2016-01-31  0:52 ` [PATCH 1/2] ARM: dts: OMAP3-N950-N9: Add ssi idle pinctrl state Sebastian Reichel
2016-02-12 22:08   ` Tony Lindgren
2016-01-31  0:52 ` [PATCH 2/2] HSI: omap-ssi: add clk change support Sebastian Reichel
2016-02-23  2:34   ` Sebastian Reichel
2016-02-24 15:19     ` Arnd Bergmann
2016-02-24 17:05       ` Sebastian Reichel [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=20160224170530.GA343@earth \
    --to=sre@kernel.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=arnd@arndb.de \
    --cc=bcousson@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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.