From: Trent Piepho <tpiepho@impinj.com>
To: "festevam@gmail.com" <festevam@gmail.com>,
"Anson.Huang@nxp.com" <Anson.Huang@nxp.com>
Cc: "aisheng.dong@nxp.com" <aisheng.dong@nxp.com>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"Linux-imx@nxp.com" <Linux-imx@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"a.zummo@towertech.it" <a.zummo@towertech.it>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"peng.fan@nxp.com" <peng.fan@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"daniel.baluta@nxp.com" <daniel.baluta@nxp.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>
Subject: Re: [PATCH 2/3] rtc: imx-sc: Make compatible string more generic
Date: Tue, 11 Jun 2019 20:45:31 +0000 [thread overview]
Message-ID: <1560285930.2354.8.camel@impinj.com> (raw)
In-Reply-To: <CAOMZO5BCuBKHs1jXkm3qFD84_xcB=0NSwE3SLJHx9kq4Stbd_A@mail.gmail.com>
On Tue, 2019-06-11 at 17:32 -0300, Fabio Estevam wrote:
> Hi Anson,
>
> On Tue, Jun 11, 2019 at 3:31 AM <Anson.Huang@nxp.com> wrote:
> >
> > From: Anson Huang <Anson.Huang@nxp.com>
> >
> > i.MX system controller RTC driver can support all i.MX SoCs
> > with system controller inside, this patch makes the compatible
> > string more generic to support other i.MX SoCs with system
> > controller inside, such as i.MX8QM etc..
> >
> > Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> > ---
> > drivers/rtc/rtc-imx-sc.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/rtc/rtc-imx-sc.c b/drivers/rtc/rtc-imx-sc.c
> > index c933045..38ef3ca 100644
> > --- a/drivers/rtc/rtc-imx-sc.c
> > +++ b/drivers/rtc/rtc-imx-sc.c
> > @@ -178,7 +178,7 @@ static int imx_sc_rtc_probe(struct
> > platform_device *pdev)
> > }
> >
> > static const struct of_device_id imx_sc_dt_ids[] = {
> > - { .compatible = "fsl,imx8qxp-sc-rtc", },
> > + { .compatible = "fsl,imx-sc-rtc", },
>
> What is wrong with the current compatible string?
>
> If you want to support i.MX8QM just add in its dtsi:
>
> compatible = "fsl,imx8qm-sc-rtc", "fsl,imx8qxp-sc-rtc"
>
> and add a dt-bindings entry for "fsl,imx8qm-sc-rtc"
Yes, I thought this is (was?) the recommended practice for IP blocks in
SoCs that don't have their own version (vs something like a Synopsis
block used many places):
* Use the first SoC to have the block as the base compatible for the
block.
* Always add the current SoC, in additional to the base, in the SoC's
dts's list of compatibles. Even if unneeded at the present.
* The driver will list the base compatible in the match table, and will
add new ones for specific socs if/when there is a need for it.
next prev parent reply other threads:[~2019-06-11 20:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 6:33 [PATCH 1/3] dt-bindings: fsl: scu: Update RTC compatible string Anson.Huang
2019-06-11 6:33 ` [PATCH 2/3] rtc: imx-sc: Make compatible string more generic Anson.Huang
2019-06-11 10:57 ` Aisheng Dong
2019-06-11 19:11 ` Alexandre Belloni
2019-06-11 20:32 ` Fabio Estevam
2019-06-11 20:45 ` Trent Piepho [this message]
2019-06-12 0:48 ` Anson Huang
2019-06-11 6:33 ` [PATCH 3/3] arm64: dts: imx8qxp: Add fallback compatible string for RTC node Anson.Huang
2019-06-11 10:57 ` Aisheng Dong
2019-06-11 10:55 ` [PATCH 1/3] dt-bindings: fsl: scu: Update RTC compatible string Aisheng Dong
2019-07-09 2:28 ` Rob Herring
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=1560285930.2354.8.camel@impinj.com \
--to=tpiepho@impinj.com \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=a.zummo@towertech.it \
--cc=aisheng.dong@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.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).