From: Martin Michlmayr <tbm@cyrius.com>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Jason Cooper <jason@lakedaemon.net>,
Oliver Hartkopp <socketcan@hartkopp.net>,
Gregory Clement <gregory.clement@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH v2] ARM: kirkwood: ts219: disable the SoC's RTC
Date: Thu, 1 Aug 2019 17:30:44 +0200 [thread overview]
Message-ID: <20190801153044.GH1843@jirafa.cyrius.com> (raw)
In-Reply-To: <20190731223233.GA15900@taurus.defre.kleine-koenig.org>
* Uwe Kleine-König <uwe@kleine-koenig.org> [2019-08-01 00:32]:
> The internal RTC doesn't work, loading the driver only yields
>
> rtc-mv f1010300.rtc: internal RTC not ticking
>
> . So disable it.
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Uwe Kleine-König <uwe@kleine-koenig.org>
Acked-by: Martin Michlmayr <tbm@cyrius.com>
This solves an issue I reported back in 2009, as Oliver Hartkopp
pointed out to my privately:
https://linux-arm-kernel.infradead.narkive.com/jySn4Wsw/patch-kirkwood-don-t-initialize-marvell-rtc-for-all-boards
(I contributed to the QNAP board support file in past but that was
replaced by the DT files.)
--
Martin Michlmayr
https://www.cyrius.com/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-01 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 22:32 [PATCH v2] ARM: kirkwood: ts219: disable the SoC's RTC Uwe Kleine-König
2019-08-01 15:30 ` Martin Michlmayr [this message]
2019-08-01 20:23 ` Alexandre Belloni
2019-08-27 13:47 ` Gregory CLEMENT
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=20190801153044.GH1843@jirafa.cyrius.com \
--to=tbm@cyrius.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=socketcan@hartkopp.net \
--cc=uwe@kleine-koenig.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.