From: Mikko Perttunen <mperttunen@nvidia.com>
To: devicetree@vger.kernel.org
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
Svyatoslav Ryhel <clamor95@gmail.com>
Subject: Re: [PATCH v4 7/7] drm/tegra: Add support for 8-bit CPU interface
Date: Sun, 25 Oct 2026 10:42:07 +0900 [thread overview]
Message-ID: <0g7damfVTZ2r6s4H0kv6Lg@nvidia.com> (raw)
In-Reply-To: <CAPVz0n3gzV+gAu_gzp3oTG9VOu-YiNSiQA0SdCFApKsi0dGjKQ@mail.gmail.com>
On Friday, October 23, 2026 11:14 PM Svyatoslav Ryhel wrote:
> пт, 23 жовт. 2026 р. о 11:26 Svyatoslav Ryhel <clamor95@gmail.com> пише:
> >
> > пт, 23 жовт. 2026 р. о 10:53 Mikko Perttunen <mperttunen@nvidia.com> пише:
> > >
> ...
> > > > +MODULE_ALIAS("platform:tegra-dbi");
> > > > +MODULE_AUTHOR("Svyatoslav Ryhel <clamor95@gmail.com>");
> > > > +MODULE_DESCRIPTION("Nvidia Tegra20/30 MIPI-DBI Type B driver");
> > > > +MODULE_LICENSE("GPL");
> > >
> > > No separate platform driver or device. If a separate struct device is
> > > needed for some technical purpose, we need to create a minimal separate
> > > virtual device, but unless there is a strong reason to have that we
> > > should be fine with just the dc device.
> > >
> > > Thank you
> > > Mikko
> > >
> >
> > ATM, I use bridge framework to describe interface and I am attaching
> > it to RGB since it basically uses RGB to transfer video data. It works
> > pretty nice so far.
> >
> > You propose to replicate how RGB works just for DBI?
> >
>
> One of the reasons I used separate pdev was to be able get mipi_dbi
> from it using dev_get_drvdata() from patent (dbi bridge in this case).
> DBI framework seems to not have a way to pass it in any other way,
> unless you know smth I don't.
Right, I think using a bridge is fine; passing the mipi_dbi interface is
properly done in other ways. The direct parent devdata link is a bit of
a "poor man's bus", and sometimes it breaks down, such as here.
MIPI DBI is comparable to MIPI DSI -- both have a hardware channel that
sends both pixel data and commands. I think we should follow DSI's
example and have a DBI bus and devices while keeping it as simple as
possible.
The DC driver would register a DBI host and the panel would bind as a
DBI device. The DC driver can then supply the mipi_dbi object in a field
of the mipi_dbi_device.
This is a bit more complicated than a parent devdata pointer but much
cleaner, and follows the existing DSI pattern.
next prev parent reply other threads:[~2026-10-25 1:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 13:22 [PATCH v4 0/7] drm/tegra: Add support for Tegra20/Tegra30 8-bit CPU interface Svyatoslav Ryhel
2026-10-22 13:22 ` [PATCH v4 1/7] dt-bindings: display: panel: Document Hitachi TX10D07VM0BAA and LG LH400WV3 panels Svyatoslav Ryhel
2026-10-22 13:22 ` [PATCH v4 2/7] drm/panel: Add Hitachi TX10D07VM0BAA MIPI DBI Type B panel driver Svyatoslav Ryhel
2026-10-22 13:39 ` sashiko-bot
2026-10-22 13:22 ` [PATCH v4 3/7] drm/panel: Add LG LH400WV3-SD04 " Svyatoslav Ryhel
2026-10-22 13:22 ` [PATCH v4 4/7] drm/tegra: dc: Expand available registers layouts Svyatoslav Ryhel
2026-10-23 7:14 ` Mikko Perttunen
2026-10-23 8:06 ` Svyatoslav Ryhel
2026-10-22 13:22 ` [PATCH v4 5/7] drm/tegra: rgb: Parameterize configuration based on bus flags Svyatoslav Ryhel
2026-10-22 13:41 ` sashiko-bot
2026-10-22 13:22 ` [PATCH v4 6/7] dt-bindings: display: tegra: Document 8-bit CPU parallel interface Svyatoslav Ryhel
2026-10-22 13:47 ` sashiko-bot
2026-10-22 13:22 ` [PATCH v4 7/7] drm/tegra: Add support for 8-bit CPU interface Svyatoslav Ryhel
2026-10-22 13:53 ` sashiko-bot
2026-10-23 7:53 ` Mikko Perttunen
2026-10-23 8:26 ` Svyatoslav Ryhel
2026-10-23 14:14 ` Svyatoslav Ryhel
2026-10-25 1:42 ` Mikko Perttunen [this message]
2026-10-25 8:51 ` Svyatoslav Ryhel
2026-10-28 1:35 ` Mikko Perttunen
2026-10-28 12:46 ` Svyatoslav Ryhel
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=0g7damfVTZ2r6s4H0kv6Lg@nvidia.com \
--to=mperttunen@nvidia.com \
--cc=airlied@gmail.com \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=thierry.reding@kernel.org \
--cc=tzimmermann@suse.de \
/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.