[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180809214414.20905-1-paul@crapouillou.net>
Date: Thu, 9 Aug 2018 23:43:50 +0200
From: Paul Cercueil <paul@...pouillou.net>
To: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Thierry Reding <thierry.reding@...il.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
Guenter Roeck <linux@...ck-us.net>,
Ralf Baechle <ralf@...ux-mips.org>,
Paul Burton <paul.burton@...s.com>,
James Hogan <jhogan@...nel.org>,
Jonathan Corbet <corbet@....net>,
Lee Jones <lee.jones@...aro.org>,
Mathieu Malaterre <malat@...ian.org>,
Ezequiel Garcia <ezequiel@...labora.co.uk>
Cc: linux-pwm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-watchdog@...r.kernel.org,
linux-mips@...ux-mips.org, linux-doc@...r.kernel.org,
linux-clk@...r.kernel.org
Subject: [PATCH v6 00/24] Ingenic TCU patchset v6
Hi,
This is the V6 of my Ingenic Timer/Counter Unit (TCU) patchset.
Major changes since V5:
- ingenic,timer-channel / ingenic,clocksource-channel devicetree
properties for the ingenic-timer driver are gone. The system timer
will default to use TCU channel #0, the clocksource will default to
use TCU channel #1. When a client driver requests one of these TCU
channels (e.g. the PWM driver), the ingenic-timer driver will
dynamically switch the system timer or clocksource to a new TCU
channel.
- The big watchdog commit in v5 was split into multiple smaller commits.
- The watchdog driver now just sets its clock to the lowest rate
possible, and calculate the maximum timeout from that.
- The PWM driver now requests the TCU channels it wants to use using the
API functions provided by ingenic-timer. Channels 0 and 1 can now be
used.
- The register lengths in the pwm/watchdog nodes were fixed. They no
longer overlap.
- Small fixes here and there, see each patch's changelog for more info.
Regards,
-Paul Cercueil
Powered by blists - more mailing lists