From: Thierry Reding <thierry.reding@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: airlied@linux.ie, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
tomi.valkeinen@ti.com, sam@ravnborg.org
Subject: Re: [PATCH v3 0/4] drm/panel: Support for OSD101T2045-53TS and OSD101T2587-53TS
Date: Tue, 23 Apr 2019 15:18:53 +0200 [thread overview]
Message-ID: <20190423131853.GP23448@ulmo> (raw)
In-Reply-To: <c25a9364-f69f-17b4-34d6-ec29e68118d3@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2754 bytes --]
On Tue, Apr 23, 2019 at 04:00:26PM +0300, Peter Ujfalusi wrote:
> Hi Thierry,
>
> On 23/04/2019 14.55, Thierry Reding wrote:
> > On Tue, Feb 26, 2019 at 09:55:19AM +0200, Peter Ujfalusi wrote:
> >> Hi,
> >>
> >> Changes since v2:
> >> - Added Reviewed-by from Rob to the binding patches
> >> - Added help text to Kconfig (osd101t2587-53ts)
> >> - Print the error values in dev_err/warn
> >> - Added Reviewed-by from Sam to the osd101t2587-53ts patch
> >>
> >> Changes since v1 (only panel-osd-osd101t2587-53ts changed):
> >> - Removed unused members from struct osd101t2587_panel
> >> - Use backlight_enable/backlight_disable
> >> - Use devm_of_find_backlight()
> >> - osd101t2587_of_match table standardized
> >> - osd101t2587_panel_unprepare() added to shutdown and remove callbacks to turn
> >> power off
> >> - Fix probe in case mipi_dsi_attach() would fail
> >>
> >> Add support for OSD101T2045-53TS and OSD101T2587-53TS from One Stop Displays.
> >>
> >> The two panel is similar with one big difference: OSD101T2587-53TS requires the
> >> MIPI_DSI_TURN_ON_PERIPHERAL message, thus can not be handled by panel-simple.
> >>
> >> Regards,
> >> Peter
> >> ---
> >> Peter Ujfalusi (4):
> >> dt-bindings: display: Add bindings for OSD101T2045-53TS
> >> drm/panel: simple: Add support for OSD101T2045-53TS
> >> dt-bindings: display: Add bindings for OSD101T2587-53TS panel
> >> drm/panel: Add OSD101T2587-53TS driver
> >>
> >> .../display/panel/osd,osd101t2045-53ts.txt | 11 +
> >> .../display/panel/osd,osd101t2587-53ts.txt | 14 +
> >> drivers/gpu/drm/panel/Kconfig | 9 +
> >> drivers/gpu/drm/panel/Makefile | 1 +
> >> .../drm/panel/panel-osd-osd101t2587-53ts.c | 254 ++++++++++++++++++
> >> drivers/gpu/drm/panel/panel-simple.c | 34 +++
> >> 6 files changed, 323 insertions(+)
> >> create mode 100644 Documentation/devicetree/bindings/display/panel/osd,osd101t2045-53ts.txt
> >> create mode 100644 Documentation/devicetree/bindings/display/panel/osd,osd101t2587-53ts.txt
> >> create mode 100644 drivers/gpu/drm/panel/panel-osd-osd101t2587-53ts.c
> >
> > Applied all four patches. Note that I had to change the osd vendor
> > string to osddisplays, which is the one that is documented in
> > vendor-prefixes.txt.
>
> I recall checking the vendor-prefixes.txt and not finding OSD in there.
> Odd, as it is indeed there.
>
> > I'm assuming that this is the same vendor, based on the model names. If
> > this is a different vendor, do let me know.
>
> Yes it is the same one.
>
> Thank you and sorry for missing it,
No worries, it was merged (March 18) after you sent out your series
(February 26).
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-04-23 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 7:55 [PATCH v3 0/4] drm/panel: Support for OSD101T2045-53TS and OSD101T2587-53TS Peter Ujfalusi
2019-02-26 7:55 ` [PATCH v3 1/4] dt-bindings: display: Add bindings for OSD101T2045-53TS Peter Ujfalusi
2019-02-26 7:55 ` [PATCH v3 2/4] drm/panel: simple: Add support " Peter Ujfalusi
2019-02-26 7:55 ` [PATCH v3 3/4] dt-bindings: display: Add bindings for OSD101T2587-53TS panel Peter Ujfalusi
2019-02-26 7:55 ` [PATCH v3 4/4] drm/panel: Add OSD101T2587-53TS driver Peter Ujfalusi
2019-04-23 11:55 ` [PATCH v3 0/4] drm/panel: Support for OSD101T2045-53TS and OSD101T2587-53TS Thierry Reding
2019-04-23 13:00 ` Peter Ujfalusi
2019-04-23 13:18 ` 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=20190423131853.GP23448@ulmo \
--to=thierry.reding@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=tomi.valkeinen@ti.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).