All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Måns Rullgård" <mans@mansr.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
	linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [RESEND][PATCH] watchdog: add support for Sigma Designs SMP86xx
Date: Fri, 13 Nov 2015 10:28:07 -0800	[thread overview]
Message-ID: <56462BB7.9000709@roeck-us.net> (raw)
In-Reply-To: <yw1xpozdkcas.fsf@unicorn.mansr.com>

On 11/13/2015 10:02 AM, Måns Rullgård wrote:
>>>>> +static const struct of_device_id tangox_wdt_dt_ids[] = {
>>>>> +	{ .compatible = "sigma,smp8642-wdt" },
>>>>
>>>> So this is really for smp8642 only, not for any other chips in the series ?
>>>
>>> It's for about a dozen SMP86xx, SMP87xx, and SMP89xx chips.  Should I
>>> list them all?  I don't even know where to find a comprehensive list of
>>> device numbers.
>>>
>> I thought so, but I am not a devicetree expert, and I see some "xx" in
>> existing devicetree bindings. Something to ask when you submit the
>> bindings to the devicetree mailing list. Either case, I think it would
>> be either something like "sigma,smp86xx-wdt" or a list of all of them,
>> but not "sigma,smp8642-wdt" to be used for all chips.
>
> The general advice is to not use wildcards in DT bindings since the next
> chip matching the pattern might not be compatible at all.  New chips
> known to be compatible with an old one can specify both the exact chip
> and the older one such that existing drivers will work automatically.
> If at some point they are found not to be compatible after all (hardware
> bugs, perhaps) a fixed driver will work with existing device trees.
>
So I think the best approach here would be to list the chips known to work.

Thanks,
Guenter

--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: "Måns Rullgård" <mans@mansr.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
	linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [RESEND][PATCH] watchdog: add support for Sigma Designs SMP86xx
Date: Fri, 13 Nov 2015 10:28:07 -0800	[thread overview]
Message-ID: <56462BB7.9000709@roeck-us.net> (raw)
In-Reply-To: <yw1xpozdkcas.fsf@unicorn.mansr.com>

On 11/13/2015 10:02 AM, Måns Rullgård wrote:
>>>>> +static const struct of_device_id tangox_wdt_dt_ids[] = {
>>>>> +	{ .compatible = "sigma,smp8642-wdt" },
>>>>
>>>> So this is really for smp8642 only, not for any other chips in the series ?
>>>
>>> It's for about a dozen SMP86xx, SMP87xx, and SMP89xx chips.  Should I
>>> list them all?  I don't even know where to find a comprehensive list of
>>> device numbers.
>>>
>> I thought so, but I am not a devicetree expert, and I see some "xx" in
>> existing devicetree bindings. Something to ask when you submit the
>> bindings to the devicetree mailing list. Either case, I think it would
>> be either something like "sigma,smp86xx-wdt" or a list of all of them,
>> but not "sigma,smp8642-wdt" to be used for all chips.
>
> The general advice is to not use wildcards in DT bindings since the next
> chip matching the pattern might not be compatible at all.  New chips
> known to be compatible with an old one can specify both the exact chip
> and the older one such that existing drivers will work automatically.
> If at some point they are found not to be compatible after all (hardware
> bugs, perhaps) a fixed driver will work with existing device trees.
>
So I think the best approach here would be to list the chips known to work.

Thanks,
Guenter


  reply	other threads:[~2015-11-13 18:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 13:14 [RESEND][PATCH] watchdog: add support for Sigma Designs SMP86xx Mans Rullgard
2015-11-13 16:35 ` Guenter Roeck
2015-11-13 16:53   ` Måns Rullgård
2015-11-13 17:55     ` Guenter Roeck
2015-11-13 18:02       ` Måns Rullgård
2015-11-13 18:28         ` Guenter Roeck [this message]
2015-11-13 18:28           ` Guenter Roeck
2015-11-13 18:41 ` Guenter Roeck

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=56462BB7.9000709@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=mans@mansr.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.