From: Paul Cercueil <paul@crapouillou.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Wim Van Sebroeck <wim@iguana.be>,
devicetree@vger.kernel.org, linux-mips@linux-mips.org,
open list <linux-kernel@vger.kernel.org>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2 5/8] MIPS: jz4740: dts: Add bindings for the jz4740-wdt driver
Date: Wed, 03 Jan 2018 13:01:06 +0100 [thread overview]
Message-ID: <1514980866.1642.0@smtp.crapouillou.net> (raw)
In-Reply-To: <698e7ae5-9f19-1282-7b82-0e2fd2080906@roeck-us.net>
Le mer. 3 janv. 2018 à 5:46, Guenter Roeck <linux@roeck-us.net> a
écrit :
> On 01/02/2018 08:48 AM, Paul Cercueil wrote:
>> Hi PrasannaKumar,
>>
>> Le mar. 2 janv. 2018 à 17:37, PrasannaKumar Muralidharan
>> <prasannatsmkumar@gmail.com> a écrit :
>>> Hi Paul,
>>>
>>> On 30 December 2017 at 19:21, Paul Cercueil <paul@crapouillou.net>
>>> wrote:
>>>> Also remove the watchdog platform_device from platform.c, since it
>>>> wasn't used anywhere anyway.
>>>>
>>>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>>>> ---
>>>> arch/mips/boot/dts/ingenic/jz4740.dtsi | 8 ++++++++
>>>> arch/mips/jz4740/platform.c | 16 ----------------
>>>> 2 files changed, 8 insertions(+), 16 deletions(-)
>>>>
>>>> v2: No change
>>>>
>>>> diff --git a/arch/mips/boot/dts/ingenic/jz4740.dtsi
>>>> b/arch/mips/boot/dts/ingenic/jz4740.dtsi
>>>> index cd5185bb90ae..26c6b561d6f7 100644
>>>> --- a/arch/mips/boot/dts/ingenic/jz4740.dtsi
>>>> +++ b/arch/mips/boot/dts/ingenic/jz4740.dtsi
>>>> @@ -45,6 +45,14 @@
>>>> #clock-cells = <1>;
>>>> };
>>>>
>>>> + watchdog: watchdog@10002000 {
>>>> + compatible = "ingenic,jz4740-watchdog";
>>>> + reg = <0x10002000 0x10>;
>>>> +
>>>> + clocks = <&cgu JZ4740_CLK_RTC>;
>>>> + clock-names = "rtc";
>>>> + };
>>>> +
>>>
>>> The watchdog driver calls jz4740_timer_enable_watchdog and
>>> jz4740_timer_disable_watchdog which defined in
>>> arch/mips/jz4740/timer.c. It accesses registers iomapped by timer
>>> code. Declaring register size as 0x10 does not show the real
>>> picture.
>>> Better use register size as 0x100 and let timer, wdt, pwm drivers to
>>> share them.
>>
>> As you said, it accesses registers iomapped by timer code. So the
>> watchdog
>> driver doesn't need to iomap them.
>>
>>> Code from one of your branches
>>> (https://github.com/OpenDingux/linux/blob/for-upstream-clocksource/arch/mips/boot/dts/ingenic/jz4740.dtsi)
>>> does it. Can you prepare a patch series and send it?
>>> I have a patch set that moves timer code out of arch/mips/jz4740/
>>> and
>>> does a similar thing for watchdog and pwm. As your new timer driver
>>> is
>>> better than the existing one I have not sent my patches yet. I would
>>> like to see it getting mainlined as it paves way for removing most
>>> of
>>> code in arch/mips/jz4740.
>>
>> The whole 'for-upstream-clocksource' branch is supposed to go
>> upstream,
>> but I can't do it in one big patchset without having lots of
>> breakages with
>> my other patchsets (jz4770 SoC support, and jz4740 watchdog updates)
>> currently under review. That also makes it simpler to upstream than
>> having
>> one single patchset that touches 6 different frameworks (MIPS, irq,
>> clocks,
>> clocksource, watchdog, PWM).
>>
>> So I will submit it in two steps, first the irq/clocks/clocksource
>> drivers
>> (this patchset) hopefully for 4.16, and then the
>> platform/watchdog/PWM fixes
>> for 4.17.
>>
>
> I kind of lost it in this exchange, sorry. At this point I don't know
> if something
> is wrong with the watchdog patches, and I have no clue what the
> upstream path
> is supposed to be. My working assumption is that 1) something may be
> wrong with
> the current version of the patches, and, 2), even if not, none of the
> patches
> is expected to find its way upstream through the watchdog subsystem.
> Plus, 3),
> even if some of the patches are supposed to go upstream through the
> watchdog
> subsystem, that won't happen in 4.16, and the patches will be
> resubmitted later
> when they are ready [and will hopefully marked clearly for submission
> through
> the watchdog subsystem].
>
> With that in mind, I'll mark the series for my reference as "not
> applicable".
> If this is wrong please let me know.
>
> Guenter
Sorry, my fault, PrasannaKumar mentionned my 'for-upstream-clocksource'
branch requesting
me to submit it upstream, which I am doing in parallel of this one. I
thought I was
answering him in the other patchset's thread, hence the confusion.
There is nothing wrong with these watchdog patches. Upstream path is
through the MIPS tree.
Paul
next prev parent reply other threads:[~2018-01-03 12:01 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 16:29 [PATCH 0/7] jz4740 watchdog driver & platform cleanups Paul Cercueil
2017-12-28 16:29 ` [PATCH 1/7] watchdog: JZ4740: Disable clock after stopping counter Paul Cercueil
2017-12-28 18:38 ` Guenter Roeck
2017-12-30 13:51 ` [PATCH v2 1/8] " Paul Cercueil
2017-12-30 13:51 ` [PATCH v2 2/8] watchdog: jz4740: Use devm_* functions Paul Cercueil
2017-12-30 16:08 ` Guenter Roeck
2017-12-30 13:51 ` [PATCH v2 3/8] watchdog: JZ4740: Register a restart handler Paul Cercueil
2018-01-20 7:31 ` PrasannaKumar Muralidharan
2018-01-20 15:45 ` Guenter Roeck
2018-01-20 16:04 ` PrasannaKumar Muralidharan
2018-01-20 17:56 ` Guenter Roeck
2017-12-30 13:51 ` [PATCH v2 4/8] watchdog: JZ4740: Drop module remove function Paul Cercueil
2017-12-30 16:08 ` Guenter Roeck
2018-01-20 7:41 ` PrasannaKumar Muralidharan
2018-01-20 15:50 ` Guenter Roeck
2018-01-20 15:59 ` PrasannaKumar Muralidharan
2017-12-30 13:51 ` [PATCH v2 5/8] MIPS: jz4740: dts: Add bindings for the jz4740-wdt driver Paul Cercueil
2018-01-02 16:37 ` PrasannaKumar Muralidharan
2018-01-02 16:48 ` Paul Cercueil
2018-01-03 4:46 ` Guenter Roeck
2018-01-03 12:01 ` Paul Cercueil [this message]
2018-01-03 14:28 ` PrasannaKumar Muralidharan
2017-12-30 13:51 ` [PATCH v2 6/8] MIPS: jz4780: dts: Fix watchdog node Paul Cercueil
2018-03-05 18:25 ` James Hogan
2017-12-30 13:51 ` [PATCH v2 7/8] MIPS: qi_lb60: Enable the jz4740-wdt driver Paul Cercueil
2018-03-05 18:28 ` James Hogan
2017-12-30 13:51 ` [PATCH v2 8/8] MIPS: jz4740: Drop old platform reset code Paul Cercueil
2018-03-05 18:31 ` James Hogan
2017-12-28 16:29 ` [PATCH 2/7] watchdog: jz4740: Use devm_* functions Paul Cercueil
2017-12-28 17:48 ` Guenter Roeck
2017-12-28 19:59 ` Paul Cercueil
2017-12-28 20:19 ` Guenter Roeck
2017-12-28 20:22 ` Paul Cercueil
2017-12-28 21:03 ` Guenter Roeck
2017-12-28 18:40 ` Guenter Roeck
2017-12-28 16:29 ` [PATCH 3/7] watchdog: JZ4740: Register a restart handler Paul Cercueil
2017-12-28 18:40 ` Guenter Roeck
2017-12-28 16:29 ` [PATCH 4/7] MIPS: jz4740: dts: Add bindings for the jz4740-wdt driver Paul Cercueil
2017-12-28 16:29 ` [PATCH 5/7] MIPS: jz4780: dts: Fix watchdog node Paul Cercueil
2017-12-28 17:33 ` Mathieu Malaterre
2017-12-28 16:29 ` [PATCH 6/7] MIPS: qi_lb60: Enable the jz4740-wdt driver Paul Cercueil
2017-12-28 16:29 ` [PATCH 7/7] MIPS: jz4740: Drop old platform reset code Paul Cercueil
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=1514980866.1642.0@smtp.crapouillou.net \
--to=paul@crapouillou.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=prasannatsmkumar@gmail.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=wim@iguana.be \
/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