From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
linux-watchdog@vger.kernel.org
Cc: wim@linux-watchdog.org, linux@roeck-us.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com,
tsbogend@alpha.franken.de, p.zabel@pengutronix.de,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: [PATCH v6 0/3] watchdog: mt7621-wdt: avoid globals and arch dependencies
Date: Tue, 14 Feb 2023 11:31:37 +0300 [thread overview]
Message-ID: <b302c25e-5365-c335-c790-71b3135847d0@arinc9.com> (raw)
In-Reply-To: <7bff7c46-ed03-ba7d-6a88-f94dfd0cb1a5@arinc9.com>
On 14.02.2023 11:12, Arınç ÜNAL wrote:
> On 13.02.2023 23:05, Sergio Paracuellos wrote:
>> Hi all,
>>
>> This series make an update in the MT7621 SoC's watchdog driver code. This
>> SoC already provides a system controller node to access reset status
>> register needed for the watchdog. Instead of using MIPS architecture
>> dependent operations in header 'asm/mach-ralink/ralink_regs.h' get
>> node syscon regmap using 'syscon_regmap_lookup_by_compatible()' and use.
>> regmap APIS. Driver is also using some globals that are not needed at
>> all if a driver data structure is used along the code. Hence, add all
>> new needed stuff inside a new driver data structure. With this changes
>> driver can be properly compile tested.
>>
>> Thanks in advance for reviewing this!
>>
>> v1 of this series here [0].
>> v2 of this series here [1].
>> v3 of this series here [2].
>> v4 of this series here [3].
>> v5 of this series here [4].
>>
>> Changes in v6:
>> - Get regmap syscon using 'syscon_regmap_lookup_by_compatible()'
>> - Add COMPILE_TEST and dependencies to Kconfig.
>> - Collect Philippe Mathieu-Daudé 'Reviewed-by' tag for watchdog node
>> warning fix.
>>
>> Changes in v5:
>> - Drop patches related with device tree ABI breakage and only
>> maintain the rest.
>
> This makes me regret taking mt7621-dts out of drivers/staging. Clearly
> there were improvements to be made on the MT7621 drivers that would
> affect the devicetree binding. I don't think one would bat an eye to
> make dt-binding changes on a devicetree on drivers/staging.
>
> I also want to make a similar change that would break the ABI. I want to
> split the MediaTek MIPS (currently called Ralink) pinctrl subdrivers
> further, namely mt7620.c, to split MT7628/MT7688 pinmux data from
> MT7620, so I can properly document which function can be given to which
> group(s) for the MT7628/MT7688 SoCs.
>
> This means I've got to introduce a new compatible string for the MT76X8
> SoCs which would cause the pinctrl driver to stop working with an old DT
> for the MT76X8 SoCs. By the nature of the change, I can't make a way
> around with the code like Sergio did in v6.
Now that I think about it, I think there's a way I can introduce a new
compatible string for the sake of better documentation, and keep the
driver working with old DTs. I'd not like to convolute this series with
this conversation. I'll send a mail to the related mailing list when the
time is right.
Arınç
prev parent reply other threads:[~2023-02-14 8:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 20:05 Sergio Paracuellos
2023-02-13 20:05 ` [PATCH v6 1/3] mips: dts: ralink: mt7621: rename watchdog node from 'wdt' into 'watchdog' Sergio Paracuellos
2023-02-13 20:05 ` [PATCH v6 2/3] watchdog: mt7621-wdt: avoid static global declarations Sergio Paracuellos
2023-02-13 20:05 ` [PATCH v6 3/3] watchdog: mt7621-wdt: avoid ralink architecture dependent code Sergio Paracuellos
2023-02-14 8:31 ` Krzysztof Kozlowski
2023-02-14 8:54 ` Sergio Paracuellos
2023-02-14 9:33 ` Krzysztof Kozlowski
2023-02-14 9:50 ` Sergio Paracuellos
2023-02-14 9:54 ` Krzysztof Kozlowski
2023-02-14 12:10 ` Guenter Roeck
2023-02-14 12:15 ` Krzysztof Kozlowski
2023-02-14 15:07 ` Guenter Roeck
2023-02-16 8:20 ` Krzysztof Kozlowski
2023-02-14 8:12 ` [PATCH v6 0/3] watchdog: mt7621-wdt: avoid globals and arch dependencies Arınç ÜNAL
2023-02-14 8:31 ` Arınç ÜNAL [this message]
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=b302c25e-5365-c335-c790-71b3135847d0@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
--cc=wim@linux-watchdog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®