From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: media: tegra-cec: Document Tegra186 and Tegra194
Date: Tue, 18 Dec 2018 22:32:56 +0100 [thread overview]
Message-ID: <20181218213255.GA4227@mithrandir> (raw)
In-Reply-To: <20181218164230.GA18480@bogus>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
On Tue, Dec 18, 2018 at 10:42:30AM -0600, Rob Herring wrote:
> On Tue, Dec 11, 2018 at 10:48:39AM +0100, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > The Tegra186 and Tegra194 contain a CEC controller that is identical to
> > that found in earlier generations. Document the compatible strings for
> > these newer chips.
>
> If identical, why don't you have a fallback compatible?
That's a good point. I think it would be fine to always fall back to the
nvidia,tegra20-cec compatible.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-12-18 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 9:48 [PATCH v2 1/3] dt-bindings: media: tegra-cec: Document Tegra186 and Tegra194 Thierry Reding
2018-12-11 9:48 ` [PATCH v2 2/3] media: tegra-cec: Support " Thierry Reding
2018-12-11 9:48 ` [PATCH v2 3/3] media: tegra-cec: Export OF device ID match table Thierry Reding
2018-12-18 16:42 ` [PATCH v2 1/3] dt-bindings: media: tegra-cec: Document Tegra186 and Tegra194 Rob Herring
2018-12-18 21:32 ` Thierry Reding [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=20181218213255.GA4227@mithrandir \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=jonathanh@nvidia.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@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).