devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: netdev@vger.kernel.org,
	"Devicetree-discuss@lists.ozlabs.org"
	<Devicetree-discuss@lists.ozlabs.org>,
	U Bhaskar-B22300 <B22300@freescale.com>,
	socketcan-core@lists.berlios.de, Robin Holt <holt@sgi.com>,
	PPC list <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 5/5] [powerpc] Fix up fsl-flexcan device tree binding.
Date: Tue, 9 Aug 2011 15:11:25 -0500	[thread overview]
Message-ID: <4E41946D.4030003@freescale.com> (raw)
In-Reply-To: <4E418B39.6040408@grandegger.com>

On 08/09/2011 02:32 PM, Wolfgang Grandegger wrote:
> On 08/09/2011 08:17 PM, Scott Wood wrote:
>> On 08/09/2011 09:43 AM, Robin Holt wrote:
>>> In working with the socketcan developers, we have come to the conclusion
>>> the fsl-flexcan device tree bindings need to be cleaned up. 
>>> The driver does not depend upon any properties other than the required properties
>>> so we are removing the file.
>>
>> That is not the criterion for whether something should be expresed in
>> the device tree.  It's a description of the hardware, not a Linux driver
>> configuration file.  If there are integration parameters that can not be
>> inferred from "this is FSL flexcan v1.0", they should be expressed in
>> the node.
>>
>> Removing the binding altogether seems extreme as well -- we should have
>> bindings for all devices, even if there are no special properties.
> 
> Yes, of course. The commit message misleading. We do not intend to
> remove the binding but just a few unused and confusing properties.

Is it a matter of the current driver not caring, or the properties just
not making sense for any reasonable driver (ambiguous, inferrable from
the flexcan version, software configuration, etc)?

-Scott


      reply	other threads:[~2011-08-09 20:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1312901031-29887-1-git-send-email-holt@sgi.com>
     [not found] ` <1312901031-29887-6-git-send-email-holt@sgi.com>
     [not found]   ` <4E4179CB.6030101@freescale.com>
     [not found]     ` <20110809184524.GB4926@sgi.com>
2011-08-09 19:13       ` [PATCH 5/5] [powerpc] Fix up fsl-flexcan device tree binding Scott Wood
     [not found]         ` <4E4186BD.5000602-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-08-09 19:49           ` Wolfgang Grandegger
2011-08-09 19:58             ` Scott Wood
2011-08-09 20:59               ` Robin Holt
     [not found]                 ` <20110809205900.GC4926-sJ/iWh9BUns@public.gmane.org>
2011-08-10 14:52                   ` Kumar Gala
     [not found]                     ` <97251371-2772-42A5-A959-D9F7A8D0A65B-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2011-08-10 16:16                       ` Robin Holt
     [not found]     ` <4E4179CB.6030101-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-08-09 19:32       ` Wolfgang Grandegger
2011-08-09 20:11         ` Scott Wood [this message]

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=4E41946D.4030003@freescale.com \
    --to=scottwood@freescale.com \
    --cc=B22300@freescale.com \
    --cc=Devicetree-discuss@lists.ozlabs.org \
    --cc=holt@sgi.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan-core@lists.berlios.de \
    --cc=wg@grandegger.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).