From: Mark Rutland <mark.rutland@arm.com>
To: Michal Simek <monstr@monstr.eu>
Cc: Harini Katakam <harinik@xilinx.com>,
"wim@iguana.be" <wim@iguana.be>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Pawel Moll <Pawel.Moll@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"rob@landley.net" <rob@landley.net>,
"michals@xilinx.com" <michals@xilinx.com>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] watchdog: Add Cadence WDT driver
Date: Thu, 29 May 2014 14:19:40 +0100 [thread overview]
Message-ID: <20140529131940.GG24233@leverpostej> (raw)
In-Reply-To: <53870129.5010505@monstr.eu>
On Thu, May 29, 2014 at 10:43:05AM +0100, Michal Simek wrote:
> Hi Mark,
>
> >> +static struct of_device_id cdns_wdt_of_match[] = {
> >> + { .compatible = "xlnx,zynq-wdt-r1p2", },
> >> + { .compatible = "cdns,wdt-r1p2", },
> >
> > If these can currently be handled identically, why not just have
> > "cdns,wdt-r1p2" in the driver and in your dts have:
> >
> > compatible = "xlnx,zynq-wdt-r1p2", "cdns,wdt-r1p2";
> >
> > If we need to distinguish the two for some reason later we can always
> > add the "xlnx,zynq-wdt-r1p2" string to the driver.
>
> I would prefer to have 2 compatible strings just because
> of that we don't know what is different compare to origin cadence
> version. We have done the same for spi-cadence.c that's why
> it shouldn't be any problem to keep it as is.
> Having zynq compatible property here and using it give us option
> that if another SoC vendor come with new configuration or clean
> cadence one we can simple handle it without changing compatible
> property for us.
Sure, we can have two documented strings. But as I mention for the
moment the driver only needs to support the one string so long as a
given dts has both. Then we can later distinguish the zynq variant (or
any other) as necessary.
Cheers,
Mark.
next prev parent reply other threads:[~2014-05-29 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 10:18 [PATCH v2 1/2] watchdog: Add Cadence WDT driver Harini Katakam
[not found] ` <1401185895-3677-1-git-send-email-harinik-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2014-05-27 10:18 ` [PATCH v2 2/2] devicetree: Add Cadence WDT devicetree bindings documentation Harini Katakam
2014-05-29 9:12 ` Mark Rutland
2014-05-29 9:27 ` Harini Katakam
2014-05-29 9:37 ` Michal Simek
2014-05-29 9:21 ` [PATCH v2 1/2] watchdog: Add Cadence WDT driver Mark Rutland
2014-05-29 9:38 ` Harini Katakam
2014-05-29 9:43 ` Michal Simek
2014-05-29 13:19 ` Mark Rutland [this message]
2014-06-02 6:25 ` Michal Simek
2014-06-02 13:17 ` Mark Rutland
2014-06-02 13:28 ` Michal Simek
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=20140529131940.GG24233@leverpostej \
--to=mark.rutland@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=harinik@xilinx.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=monstr@monstr.eu \
--cc=rob@landley.net \
--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;
as well as URLs for NNTP newsgroup(s).