All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Steve Twiss <stwiss.opensource@diasemi.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Wim Van Sebroeck <wim@iguana.be>,
	Lee Jones <lee.jones@linaro.org>,
	Eduardo Valentin <edubezval@gmail.com>,
	Zhang Rui <rui.zhang@intel.com>,
	DEVICETREE <devicetree@vger.kernel.org>,
	LINUX-INPUT <linux-input@vger.kernel.org>,
	LINUX-PM <linux-pm@vger.kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	Support Opensource <Support.Opensource@diasemi.com>,
	LINUX-KERNEL <linux-kernel@vger.kernel.org>,
	LINUX-WATCHDOG <linux-watchdog@vger.kernel.org>
Subject: Re: [PATCH V1 04/10] watchdog: da9061: watchdog driver (RFC)
Date: Fri, 7 Oct 2016 16:35:54 -0700	[thread overview]
Message-ID: <20161007233554.GA21386@dtor-ws> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB7018CCE282C@SW-EX-MBX02.diasemi.com>

On Fri, Oct 07, 2016 at 06:01:23PM +0000, Steve Twiss wrote:
> On 07 October 2016 18:02, Guenter Roeck wrote:
> 
> > > On 06 October 2016 19:49, Guenter Roeck wrote:
> > > > On Thu, Oct 06, 2016 at 04:28:14PM +0000, Steve Twiss wrote:
> > > > > I am using the compatible string to pick a different configuration .data block:
> > > > > { .compatible = "dlg,da9062-watchdog", .data = &da9062_watchdog_info },
> > > > > { .compatible = "dlg,da9061-watchdog", .data = &da9061_watchdog_info },
> > > > >
> > > > > But, it is just my opinion to keep the "name" different.
> > > > > This will not be my decision if accepted into the Linux kernel, but I would like to
> > > > > at least be consistent for DA9061 and DA9062 so ... is this an issue?
> > > >
> > > > FWIW the driver doesn't really need to be updated in the first place.
> > > > A compatible statement listing both da9061 and da9062 would do it.
> > >
> > > I will make the changes you requested: deprecate the existing compatibility
> > > for da9062-watchdog and make a new compatibility string which combines both
> > > da9061 and da9062.
> > >
> > That is not what I asked for.
> 
> Ok. Did you mean separate compatible statements with data sections pointing at 
> the same structure?
> 
> Like this:
> { .compatible = "dlg,da9062-watchdog", .data = &da9062_watchdog_info },
> { .compatible = "dlg,da9061-watchdog", .data = &da9062_watchdog_info },
> 
> So this would be the only change needed in the device driver.

If there is no change in IP block then I do not see why we need to
introduce new names at all. The dts can specify fallback compatible
stting. Note, it is called *compatible* not "model" or "device id" or
whatever. So you can just say in DTS:

	compatible = "dlg,da9061-watchdog", "dlg,da9062-watchdog";

and leave the driver alone. That goes for input part as well. You only
need to add new compatible to the driver when it in fact is
*incompatible* with the existing blocks.

Thanks.

-- 
Dmitry

  reply	other threads:[~2016-10-07 23:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 16:28 [PATCH V1 04/10] watchdog: da9061: watchdog driver (RFC) Steve Twiss
2016-10-06 16:28 ` Steve Twiss
2016-10-06 18:49 ` Guenter Roeck
2016-10-07 14:56   ` Steve Twiss
2016-10-07 17:02     ` Guenter Roeck
     [not found]       ` <20161007170214.GA21349-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-10-07 18:01         ` Steve Twiss
2016-10-07 18:01           ` Steve Twiss
2016-10-07 23:35           ` Dmitry Torokhov [this message]
2016-10-08  0:22             ` Guenter Roeck
     [not found]               ` <84f51754-cbd4-7a85-6ab6-83e1f47fd936-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-10-08  6:33                 ` Steve Twiss
2016-10-08  6:33                   ` Steve Twiss

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=20161007233554.GA21386@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=Support.Opensource@diasemi.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=stwiss.opensource@diasemi.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.