devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Pawel Moll <pawel.moll@arm.com>,
	"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
	joro <joro@8bytes.org>, SH-Linux <linux-sh@vger.kernel.org>,
	iommu@lists.linux-foundation.org,
	Rob Herring <robh+dt@kernel.org>,
	Kumar Gala <galak@codeaurora.org>,
	Simon Horman <horms+renesas@verge.net.au>
Subject: Re: [PATCH] iommu/ipmmu-vmsa: Include SoC part number in DT binding docs
Date: Tue, 20 Oct 2015 13:27:47 +0300	[thread overview]
Message-ID: <1833179.ksYYvY8Qgn@avalon> (raw)
In-Reply-To: <CANqRtoQ=nBpWX_eMUM9-febZ-cCAFayEGoUjMSpAXHaw3kekqQ@mail.gmail.com>

Hi Magnus,

On Tuesday 20 October 2015 17:58:17 Magnus Damm wrote:
> On Mon, Oct 19, 2015 at 3:44 PM, Laurent Pinchart wrote:
> > On Monday 19 October 2015 12:10:03 Magnus Damm wrote:
> >> From: Magnus Damm <damm+renesas@opensource.se>
> >> 
> >> Add part numbers for APE6 and current set of R-Car Gen2 SoCs to the
> >> IPMMU DT binding documentation. The example is also updated to show
> >> how the generic compatible string may be used as fallback.
> > 
> > I'd use a wording stronger than "may" here, as the generic compatible
> > value is required. I would also explicitly state that in the bindings
> > documentation.
>
> I don't mind using a different wording, but it becomes a bit difficult
> to describe exactly when to use the generic compatible string and when
> not to. Is it always required, or does it depend on the hardware?
> 
>  "For compatible hardware please use the generic compat string."
> Compatible with what? =)
> 
> Any ideas how to describe it correctly in the binding documentation?

Given that the generic compat string is always required I'd just say so. We 
can then update the DT bindings later when we'll introduce the first SoC not 
compatible with the generic compat string.

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2015-10-20 10:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19  3:10 [PATCH] iommu/ipmmu-vmsa: Include SoC part number in DT binding docs Magnus Damm
2015-10-19  6:44 ` Laurent Pinchart
2015-10-20  8:58   ` Magnus Damm
2015-10-20 10:27     ` Laurent Pinchart [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=1833179.ksYYvY8Qgn@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.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).