devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
	"David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	"Discussions about the Letux Kernel"
	<letux-kernel@openphoenux.org>,
	kernel@pyra-handheld.com
Subject: Re: [PATCH 1/7] dt-bindings: gpu: pvrsgx: add initial bindings
Date: Tue, 22 Oct 2019 08:36:50 -0700	[thread overview]
Message-ID: <20191022153650.GL5610@atomide.com> (raw)
In-Reply-To: <CC62CE92-28DF-406E-B61C-22F8F341AAFB@goldelico.com>

* H. Nikolaus Schaller <hns@goldelico.com> [191022 15:12]:
> Hm. How should that work? Some SoC have the sgx544 as single
> core and others as dual core. This imho does not fit into
> the "img,sgx544-$revision" scheme which could be matched to.

Well don't you have then just two separate child nodes,
one for each core with their own register range?

That is assuming they're really separate instances..

> But maybe we do it the same as with the timer for the moment,
> i.e. keep it in some unpublished patch set.

Yeah makes sense to me until things get sorted out.

> At the moment I have more problems understanding how the yaml
> thing works. I understand and fully support the overall goal,
> but it is quite difficult to get a start here. And there do not
> seem to be tools or scripts to help converting from old style
> text format (even if not perfect, this would be helpful) and
> I have no yaml editor that helps keeping the indentation
> correct. So this slows down a v2 a little bit.

Sounds handy to me :)

Regards,

Tony

  reply	other threads:[~2019-10-22 15:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 18:46 [PATCH 0/7] ARM: DTS: OMAP: add child nodes describing the PVRSGX present in some OMAP SoC H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 1/7] dt-bindings: gpu: pvrsgx: add initial bindings H. Nikolaus Schaller
2019-10-21 15:07   ` Rob Herring
2019-10-21 15:45     ` H. Nikolaus Schaller
2019-10-21 17:10       ` Tony Lindgren
2019-10-21 17:25       ` Tony Lindgren
2019-10-21 18:07         ` H. Nikolaus Schaller
2019-10-22 15:02           ` Tony Lindgren
2019-10-22 15:11             ` H. Nikolaus Schaller
2019-10-22 15:36               ` Tony Lindgren [this message]
2019-10-22 16:14                 ` H. Nikolaus Schaller
2019-10-30 16:16   ` Tony Lindgren
2019-10-30 16:39     ` H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 2/7] ARM: DTS: am33xx: add sgx gpu child node H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 3/7] ARM: DTS: am3517: " H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 4/7] ARM: DTS: omap3: " H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 5/7] ARM: DTS: omap36xx: " H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 6/7] ARM: DTS: omap4: " H. Nikolaus Schaller
2019-10-18 18:46 ` [PATCH 7/7] ARM: DTS: omap5: " H. Nikolaus Schaller

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=20191022153650.GL5610@atomide.com \
    --to=tony@atomide.com \
    --cc=airlied@linux.ie \
    --cc=bcousson@baylibre.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hns@goldelico.com \
    --cc=kernel@pyra-handheld.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@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).