public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] ARM: mvebu: soc changes for v3.13 (round 2)
Date: Thu, 17 Oct 2013 15:20:57 -0700	[thread overview]
Message-ID: <87ob6nzghi.fsf@linaro.org> (raw)
In-Reply-To: <20131017135409.GG22434@titan.lakedaemon.net> (Jason Cooper's message of "Thu, 17 Oct 2013 09:54:09 -0400")

Jason Cooper <jason@lakedaemon•net> writes:

> Guys,
>
> The only thing exciting here is the workaround for the mv643xx_eth bug.
> Whenever you shut off it's clock (and folks have good reason to do
> this), it loses it's mac address.  In the happy, ideal boot-from-DT
> world, this isn't a problem, since the bootloader will set
> local-mac-address in the DT.  However, we aren't in that world (yet).
>
> We've been tossing around different solutions to the problem over the
> past year or so, and this one seems a) the least painful, and b) most in
> line with what the future will hold.  eg, the driver (on reload or
> resume) will need to read the mac address from the DT, regardless of how
> the mac address got there.
>
> thx,
>
> Jason.
>
> The following changes since commit e1cb367de27ca5c186b0f120c3c10a4a0e8edd2e:
>
>   ARM: kirkwood: Add standby support (2013-10-08 15:41:52 +0000)
>
> are available in the git repository at:
>
>   git://git.infradead.org/linux-mvebu.git tags/soc-3.13-2
>
> for you to fetch changes up to d7f5baeedbdb48d4f5bb2b4f6f56f32b7f2f7aff:
>
>   Documentation: arm/Marvell: clarify Armada SoCs that match 78xx0 pattern (2013-10-08 17:27:59 +0000)
>
> ----------------------------------------------------------------
> mvebu soc changes for v3.13 (round 2)
>
>  - kirkwood
>     - remove mbus init, pcie clk init
>     - retain MAC addr for DT ethernet (work around broken IP)
>     - docs: clarify Armada SoCs

Pulled into next/soc.

This had a minor conflict in board-dt.c with Sebastian's clk-of-init
branch that's part of next/cleanup.  Please double check my conflict
resolution (currently in our to-build branch, not yet pushed to for-next)

Thanks,

Kevin

  reply	other threads:[~2013-10-17 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 13:54 [GIT PULL] ARM: mvebu: soc changes for v3.13 (round 2) Jason Cooper
2013-10-17 22:20 ` Kevin Hilman [this message]
2013-10-18 11:27   ` Sebastian Hesselbarth
2013-10-18 13:25   ` 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=87ob6nzghi.fsf@linaro.org \
    --to=khilman@linaro$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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