devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Rob Herring <robh@kernel.org>
Cc: Anson Huang <anson.huang@nxp.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
	"heiko@sntech.de" <heiko@sntech.de>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"jagan@amarulasolutions.com" <jagan@amarulasolutions.com>,
	Andy Gross <andy.gross@linaro.org>,
	dl-linux-imx <linux-imx@nxp.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"marc.w.gonzalez@free.fr" <marc.w.gonzalez@free.fr>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	enric
Subject: Re: [PATCH RESEND V2 1/4] dt-bindings: fsl: scu: add watchdog binding
Date: Tue, 26 Feb 2019 14:27:50 -0800	[thread overview]
Message-ID: <20190226222750.GA30985@roeck-us.net> (raw)
In-Reply-To: <CAL_JsqJV9NxpOJi3Jh2Uk-TOmOL4rWwqZp3sodxsRinAHZ3m3w@mail.gmail.com>

On Tue, Feb 26, 2019 at 03:34:12PM -0600, Rob Herring wrote:
> > >
> > > I think Rob suggested that the SCU parent driver should instantiate the
> > > watchdog without explicit watchdog node. That would be possible, but it
> > > currently uses
> > > devm_of_platform_populate() to do the instantiation, and changing that
> > > would be a mess. Besides, it does sem to me that your suggested node would
> > > describe the hardware, so I am not sure I understand the reasoning.
> 
> It would just be a call to create a platform device instead. How is that a mess?
> 
> It's describing firmware. We have DT for describing h/w we've failed
> to make discoverable. We should not repeat that and just describe
> firmware in DT. Make the firmware discoverable! Though there are cases
> like firmware provided clocks where we still need something in DT, but
> this is not one of them.
> 

It requires extra code where an added DT node would accomplish the same.
It requires a mix of DT nodes for existing devices plus extra code for
newly added devices. To me that looks like a revert to old platform code,
which was replaced with DT descriptions over the last several years.

But then if that is where things are going, who am I to argue.

Guenter

  reply	other threads:[~2019-02-26 22:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18  6:53 [PATCH RESEND V2 0/4] Add i.MX8QXP system controller watchdog support Anson Huang
2019-02-18  6:53 ` [PATCH RESEND V2 1/4] dt-bindings: fsl: scu: add watchdog binding Anson Huang
2019-02-22 19:52   ` Rob Herring
2019-02-23 17:08     ` Guenter Roeck
2019-02-24  3:04       ` Anson Huang
2019-02-24  3:20         ` Guenter Roeck
2019-02-25  2:26           ` Anson Huang
2019-02-26 21:34             ` Rob Herring
2019-02-26 22:27               ` Guenter Roeck [this message]
2019-03-06 14:45               ` Anson Huang
2019-03-13  8:11                 ` Anson Huang
2019-03-13 19:55                   ` Rob Herring
2019-03-07 12:22               ` Aisheng Dong
2019-03-11 21:26                 ` Rob Herring
2019-03-14  2:10                   ` Anson Huang
2019-02-26 11:56       ` Aisheng Dong
2019-02-18  6:53 ` [PATCH RESEND V2 2/4] watchdog: imx_sc: Add i.MX system controller watchdog support Anson Huang
2019-02-18 22:25   ` Guenter Roeck
2019-02-24  3:29   ` Guenter Roeck
2019-02-25  2:22     ` Anson Huang
2019-02-18  6:54 ` [PATCH RESEND V2 3/4] arm64: defconfig: add support for i.MX system controller watchdog Anson Huang
2019-02-18  6:54 ` [PATCH RESEND V2 4/4] arm64: dts: freescale: imx8qxp: add watchdog support Anson Huang

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=20190226222750.GA30985@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=andy.gross@linaro.org \
    --cc=anson.huang@nxp.com \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=heiko@sntech.de \
    --cc=jagan@amarulasolutions.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=marc.w.gonzalez@free.fr \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=ulf.hansson@linaro.org \
    --cc=will.deacon@arm.com \
    /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).