From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] clk: mvebu: armada-xp: Support for MSYS SoC
Date: Thu, 20 Nov 2014 16:03:53 +0100 [thread overview]
Message-ID: <20141120150353.GG31782@lunn.ch> (raw)
In-Reply-To: <20141120155630.743ee6de@free-electrons.com>
On Thu, Nov 20, 2014 at 03:56:30PM +0100, Thomas Petazzoni wrote:
> Dear Chris Packham,
>
> On Thu, 20 Nov 2014 18:01:19 +1300, Chris Packham wrote:
> > The MSYS SoCs are a range of packet processors with integrated CPUs based
> > on armada-xp. One difference is that the TCLK frequency is fixed at 200MHz
> > as opposed to the fixed 250MHz used on armada-xp. The clock-gating options
> > are a subset of what's available on the armada-xp so this code should be
> > compatible.
>
> Well, if you have only a subset of what's available, then I would also
> suggest to introduce a separate compatible string for the gatable
> clocks.
For the kirkwood based 98dx4122, we avoided a separate gatable
compatible string, by simply not listing devices which don't
exist. For that SoC, accessing clocks which don't exist is not a
problem. However, accesses devices which don't exist does lock the
SoC.
There is a specific pin-controller compatible string:
marvell,98dx4122-pinctrl, and i guess one is also needed here.
Andrew
next prev parent reply other threads:[~2014-11-20 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 5:01 [RFC PATCH] clk: mvebu: armada-xp: Support for MSYS SoC Chris Packham
2014-11-20 5:17 ` Andrew Lunn
2014-11-20 21:12 ` Chris Packham
2014-11-20 21:36 ` Andrew Lunn
2014-11-20 22:31 ` Chris Packham
2014-11-20 14:56 ` Thomas Petazzoni
2014-11-20 15:03 ` Andrew Lunn [this message]
2014-11-20 21:14 ` Chris Packham
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=20141120150353.GG31782@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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 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.