linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lubomir Rintel <lkundrak@v3.sk>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Eric Miao <eric.y.miao@gmail.com>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Russell King <linux@armlinux.org.uk>
Subject: [PATCH v2 0/4] Enable the timer clock on DT MMP2
Date: Tue, 18 Sep 2018 22:54:51 +0200	[thread overview]
Message-ID: <20180918205455.25464-1-lkundrak@v3.sk> (raw)

This makes the timer work for me on an OLPC XO 1.75, which is a
device-tree based MMP2 platform.

Compared to v1 patch set, this makes the clock optional to keep compatibility
with older device trees or platforms with a compatible timer that don't seem
to require the clock.

Lubomir Rintel (4):
      dt-bindings: mrvl,mmp-timer: add clock
      DT: marvell,mmp2: add clock to the timer
      ARM: mmp2: initialize clocks before the timer
      ARM: mmp/mmp2: dt: enable the clock

Thanks,
Lubo



             reply	other threads:[~2018-09-18 20:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18 20:54 Lubomir Rintel [this message]
2018-09-18 20:54 ` [PATCH v2 1/4] dt-bindings: mrvl,mmp-timer: add clock Lubomir Rintel
2018-09-26 22:51   ` Rob Herring
2018-11-03 19:14   ` Pavel Machek
2018-09-18 20:54 ` [PATCH v2 2/4] DT: marvell,mmp2: add clock to the timer Lubomir Rintel
2018-11-03 19:15   ` Pavel Machek
2018-09-18 20:54 ` [PATCH v2 3/4] ARM: mmp2: initialize clocks before " Lubomir Rintel
2018-11-03 19:15   ` Pavel Machek
2018-09-18 20:54 ` [PATCH 4/4] ARM: mmp/mmp2: dt: enable the clock Lubomir Rintel
2018-11-03 19:17   ` Pavel Machek

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=20180918205455.25464-1-lkundrak@v3.sk \
    --to=lkundrak@v3.sk \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eric.y.miao@gmail.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).