From: Johan Jonker <jbx6244@gmail.com>
To: jbx6244@gmail.com
Cc: airlied@linux.ie, daniel@ffwll.ch, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, heiko@sntech.de,
hjc@rock-chips.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh+dt@kernel.org
Subject: Re: [PATCH v1] dt-bindings: display: rockchip: convert rockchip vop bindings to yaml
Date: Mon, 9 Mar 2020 07:55:22 +0100 [thread overview]
Message-ID: <590762ab-db79-c8b1-7f0e-b653ed4b1721@gmail.com> (raw)
In-Reply-To: <20200306170353.11393-1-jbx6244@gmail.com>
Hi,
Question for robh:
In the old txt situation we add/describe only properties that are used
by the driver/hardware itself. With yaml it also filters things in a
node that are used by other drivers like:
assigned-clocks:
assigned-clock-rates:
power-domains:
Should we add or not?
Kind regards,
Johan
PS: Will drop 'rockchip,grf' in v2 for px30, not used in vop driver?
WARNING: multiple messages have this Message-ID (diff)
From: Johan Jonker <jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: airlied-cv59FeDIM0c@public.gmane.org,
daniel-/w4YWyX8dFk@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org,
hjc-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH v1] dt-bindings: display: rockchip: convert rockchip vop bindings to yaml
Date: Mon, 9 Mar 2020 07:55:22 +0100 [thread overview]
Message-ID: <590762ab-db79-c8b1-7f0e-b653ed4b1721@gmail.com> (raw)
In-Reply-To: <20200306170353.11393-1-jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi,
Question for robh:
In the old txt situation we add/describe only properties that are used
by the driver/hardware itself. With yaml it also filters things in a
node that are used by other drivers like:
assigned-clocks:
assigned-clock-rates:
power-domains:
Should we add or not?
Kind regards,
Johan
PS: Will drop 'rockchip,grf' in v2 for px30, not used in vop driver?
WARNING: multiple messages have this Message-ID (diff)
From: Johan Jonker <jbx6244@gmail.com>
To: jbx6244@gmail.com
Cc: devicetree@vger.kernel.org, heiko@sntech.de, airlied@linux.ie,
hjc@rock-chips.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh+dt@kernel.org, daniel@ffwll.ch,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] dt-bindings: display: rockchip: convert rockchip vop bindings to yaml
Date: Mon, 9 Mar 2020 07:55:22 +0100 [thread overview]
Message-ID: <590762ab-db79-c8b1-7f0e-b653ed4b1721@gmail.com> (raw)
In-Reply-To: <20200306170353.11393-1-jbx6244@gmail.com>
Hi,
Question for robh:
In the old txt situation we add/describe only properties that are used
by the driver/hardware itself. With yaml it also filters things in a
node that are used by other drivers like:
assigned-clocks:
assigned-clock-rates:
power-domains:
Should we add or not?
Kind regards,
Johan
PS: Will drop 'rockchip,grf' in v2 for px30, not used in vop driver?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Johan Jonker <jbx6244@gmail.com>
To: jbx6244@gmail.com
Cc: devicetree@vger.kernel.org, airlied@linux.ie, hjc@rock-chips.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] dt-bindings: display: rockchip: convert rockchip vop bindings to yaml
Date: Mon, 9 Mar 2020 07:55:22 +0100 [thread overview]
Message-ID: <590762ab-db79-c8b1-7f0e-b653ed4b1721@gmail.com> (raw)
In-Reply-To: <20200306170353.11393-1-jbx6244@gmail.com>
Hi,
Question for robh:
In the old txt situation we add/describe only properties that are used
by the driver/hardware itself. With yaml it also filters things in a
node that are used by other drivers like:
assigned-clocks:
assigned-clock-rates:
power-domains:
Should we add or not?
Kind regards,
Johan
PS: Will drop 'rockchip,grf' in v2 for px30, not used in vop driver?
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-03-09 6:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 17:03 [PATCH v1] dt-bindings: display: rockchip: convert rockchip vop bindings to yaml Johan Jonker
2020-03-06 17:03 ` Johan Jonker
2020-03-06 17:03 ` Johan Jonker
2020-03-06 17:03 ` Johan Jonker
2020-03-09 6:55 ` Johan Jonker [this message]
2020-03-09 6:55 ` Johan Jonker
2020-03-09 6:55 ` Johan Jonker
2020-03-09 6:55 ` Johan Jonker
2020-03-23 19:36 ` Rob Herring
2020-03-23 19:36 ` Rob Herring
2020-03-23 19:36 ` Rob Herring
2020-03-23 19:36 ` Rob Herring
2020-03-23 19:41 ` Rob Herring
2020-03-23 19:41 ` Rob Herring
2020-03-23 19:41 ` Rob Herring
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=590762ab-db79-c8b1-7f0e-b653ed4b1721@gmail.com \
--to=jbx6244@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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 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.