mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Baatz <gmbnomis@gmail.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Jason Cooper <jason@lakedaemon.net>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Russell King <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ARM: kirkwood: fix to retain gbe MAC addresses for DT kernels
Date: Sun, 3 Feb 2013 00:49:20 +0100	[thread overview]
Message-ID: <20130202234919.GB17361@schnuecks.de> (raw)
In-Reply-To: <1359577799-23351-1-git-send-email-sebastian.hesselbarth@gmail.com>

Hi Sebastian, Jason,

On Wed, Jan 30, 2013 at 09:29:58PM +0100, Sebastian Hesselbarth wrote:
> The ethernet controller used on kirkwood looses its MAC address
> register contents when the corresponding clock is gated. As soon as
> mv643xx_eth is built as module, the clock gets gated and when loading
> the module, the MAC address is gone.
> 
> Proper DT support for the mv643xx_eth driver is expected soon, so we add
> a workaround to always enable ge0/ge1 clocks on kirkwood. This workaround
> is also already used on non-DT kirkwood kernels.
> 
> Reported-by: Simon Baatz <gmbnomis@gmail.com>
> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>

Tested this on IB-NAS6210 (kirkwood, single GBE interface). Using
mv643xx_eth as a module works again now and yields

# cat /sys/kernel/debug/clk/tclk/ge[01]/clk_enable_count 
2
1

as expected.

- Simon

  reply	other threads:[~2013-02-02 23:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30  1:26 [PATCH 1/2] ARM: kirkwood: provide ge clock aliases for shared smi Sebastian Hesselbarth
2013-01-30  1:26 ` [PATCH 2/2] ARM: kirkwood: fix to retain gbe MAC addresses for DT kernels Sebastian Hesselbarth
2013-01-30 18:30   ` Jason Cooper
2013-01-30 20:29     ` [PATCH v2 " Sebastian Hesselbarth
2013-02-02 23:49       ` Simon Baatz [this message]
2013-02-04  1:34       ` Jason Cooper

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=20130202234919.GB17361@schnuecks.de \
    --to=gmbnomis@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=sebastian.hesselbarth@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

all inboxes | Powered by JetHome®