From: Conor Dooley <conor@kernel.org>
To: Bharat Bhushan <bbhushan2@marvell.com>
Cc: "wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>
Subject: Re: [EXT] Re: [PATCH 1/2 v8] dt-bindings: watchdog: marvell GTI system watchdog driver
Date: Sat, 27 May 2023 17:10:02 +0100 [thread overview]
Message-ID: <20230527-wiring-coping-88eba4d91f3f@spud> (raw)
In-Reply-To: <DM5PR1801MB188350DD9CFDBB3E240AC838E3449@DM5PR1801MB1883.namprd18.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2734 bytes --]
On Sat, May 27, 2023 at 02:53:25PM +0000, Bharat Bhushan wrote:
> From: Conor Dooley <conor@kernel.org>
> > On Fri, May 26, 2023 at 11:56:25AM +0530, Bharat Bhushan wrote:
> > > +properties:
> > > + compatible:
> > > + enum:
> > > + - marvell,cn9670-wdt
> > > + - marvell,cn9880-wdt
> > > + - marvell,cnf9535-wdt
> > > + - marvell,cn10624-wdt
> > > + - marvell,cn10308-wdt
> > > + - marvell,cnf10518-wdt
> >
> > static const struct of_device_id gti_wdt_of_match[] = {
> > { .compatible = "marvell,cn9670-wdt", .data = &match_data_octeontx2},
> > { .compatible = "marvell,cn9880-wdt", .data = &match_data_octeontx2},
> > { .compatible = "marvell,cnf9535-wdt", .data = &match_data_octeontx2},
> > { .compatible = "marvell,cn10624-wdt", .data = &match_data_cn10k},
> > { .compatible = "marvell,cn10308-wdt", .data = &match_data_cn10k},
> > { .compatible = "marvell,cnf10518-wdt", .data = &match_data_cn10k},
> >
> > This is a fat hint that you should be using fallback compatibles here.
> > You even had a fallback setup in your last revision, but you seem to have
> > removed it alongside the removal of the wildcards. Why did you do that?
>
> Not sure I understand this comment, Compatible in last version was as below:
>
> + properties:
> + compatible:
> + oneOf:
> + - const: marvell,octeontx2-wdt
> + - items:
> + - enum:
> + - marvell,octeontx2-95xx-wdt
> + - marvell,octeontx2-96xx-wdt
> + - marvell,octeontx2-98xx-wdt
> + - const: marvell,octeontx2-wdt
> + - const: marvell,cn10k-wdt
> + - items:
> + - enum:
> + - marvell,cn10kx-wdt
> + - marvell,cnf10kx-wdt
> + - const: marvell,cn10k-wdt
>
> By fallback do you mean " const: marvell,cn10k-wdt" and
> "const: marvell,octeontx2-wdt" ? If yes I removed because "octeontx2"
> and "cn10k" are soc family name and no a specific soc.
No, I meant that you should permit
compatible = "marvell,cn9880-wdt", "marvell,cn9670-wdt";
and
compatible = "marvell,cnf9535-wdt", "marvell,cn9670-wdt";
and
compatible = "marvell,cn9670-wdt";
so the driver only needs to contain
{ .compatible = "marvell,cn9670-wdt", .data = &match_data_octeontx2},
instead of
{ .compatible = "marvell,cn9670-wdt", .data = &match_data_octeontx2},
{ .compatible = "marvell,cn9880-wdt", .data = &match_data_octeontx2},
{ .compatible = "marvell,cnf9535-wdt", .data = &match_data_octeontx2},
Note that using fallback compatibles is separate from using wildcards,
and I was not suggesting that you go back to wildcards ;)
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-27 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 6:26 [PATCH 1/2 v8] dt-bindings: watchdog: marvell GTI system watchdog driver Bharat Bhushan
2023-05-26 6:26 ` [PATCH 2/2 v8] Watchdog: Add marvell GTI " Bharat Bhushan
2023-05-27 16:12 ` kernel test robot
2023-05-29 13:38 ` Guenter Roeck
2023-05-30 4:08 ` [EXT] " Bharat Bhushan
2023-05-26 19:37 ` [PATCH 1/2 v8] dt-bindings: watchdog: marvell GTI system " Conor Dooley
2023-05-27 14:53 ` [EXT] " Bharat Bhushan
2023-05-27 16:10 ` Conor Dooley [this message]
2023-05-29 6:14 ` Bharat Bhushan
2023-05-29 12:34 ` Conor Dooley
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=20230527-wiring-coping-88eba4d91f3f@spud \
--to=conor@kernel.org \
--cc=bbhushan2@marvell.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=sgoutham@marvell.com \
--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;
as well as URLs for NNTP newsgroup(s).