From: "Max Fierke" <max@maxfierke.com>
To: "Samuel Holland" <samuel@sholland.org>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
thierry.reding@gmail.com, "Sam Ravnborg" <sam@ravnborg.org>,
airlied@linux.ie, daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH v3 1/4] dt-bindings: vendor-prefixes: Add prefix for ClockworkPi
Date: Mon, 31 Oct 2022 19:59:07 -0500 [thread overview]
Message-ID: <5efcce2b-4534-4777-8daa-d1ff2b6bb1c7@app.fastmail.com> (raw)
In-Reply-To: <f09812a7-5d7e-f8f8-aba4-7645810a8c52@sholland.org>
On Sat, Oct 29, 2022, at 1:17 PM, Samuel Holland wrote:
> Hi Max,
>
> The vendor uses "clockwork" as the prefix in their downstream
> devicetrees[1][2][3], so I would suggest using the same here. I think
> there is a distinction between "Clockwork" the company and "ClockworkPi"
> the product. This is what I did for the board devicetree I sent[4].
>
> Regards,
> Samuel
>
Hi Samuel,
Ah yes, I struggled a bit with the distinction because the company itself
seems to be a bit inconsistent here.
I will follow your lead and post a v4 follow-up with that vendor prefix
changed.
Glad to see someone else working on support for this hardware!
Thanks,
Max
next prev parent reply other threads:[~2022-11-01 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 3:44 [PATCH v3 0/4] Introduce ClockworkPi CWD686 DRM panel driver Max Fierke
2022-09-18 3:44 ` [PATCH v3 1/4] dt-bindings: vendor-prefixes: Add prefix for ClockworkPi Max Fierke
2022-10-29 18:17 ` Samuel Holland
2022-11-01 0:59 ` Max Fierke [this message]
2022-09-18 3:44 ` [PATCH v3 2/4] dt-bindings: display: Add ClockworkPi CWD686 panel Max Fierke
2022-09-18 3:44 ` [PATCH v3 3/4] drm: panel: Add driver for ClockworkPi cwd686 panel Max Fierke
2022-09-18 3:44 ` [PATCH v3 4/4] drm/panel: clockworkpi-cwd686: Implement .get_orientation callback Max Fierke
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=5efcce2b-4534-4777-8daa-d1ff2b6bb1c7@app.fastmail.com \
--to=max@maxfierke.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=samuel@sholland.org \
--cc=thierry.reding@gmail.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).