From: Sam Ravnborg <sam@ravnborg.org>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: dave.stevenson@raspberrypi.com, david@lechnology.com,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
maxime@cerno.tech, robh+dt@kernel.org, thierry.reding@gmail.com
Subject: Re: [PATCH v4 3/3] drm/tiny: Add MIPI DBI compatible SPI driver
Date: Sun, 20 Feb 2022 22:30:54 +0100 [thread overview]
Message-ID: <YhKzDi9CBrjLGm/X@ravnborg.org> (raw)
In-Reply-To: <5357536f-c2ff-d778-dbd6-87c8079ab855@tronnes.org>
Hi Noralf,
> >> mode->flags) {
> >> dev_err(dev, "%pOF: panel-timing out of bounds\n", dev->of_node);
> >> return -EINVAL;
> >> }
> > With the display_timing => drm_display_mode I think the above is no
> > longer required.
> >
>
> I still need to verify the values to ensure that front_porch and
> sync_len are zero. Maybe I need a comment now to tell what I'm checking
> since I'm further away from the DT values:
>
> /*
> * Make sure width and height are set and that only back porch and
> * pixelclock are set in the other timing values. Also check that
> * width and height don't exceed the 16-bit value specified by MIPI DCS.
> */
Yes, that would be nice.
>
> >>
> >> /* The driver doesn't use the pixel clock but it is mandatory so fake
> >> one if not set */
> >> if (!mode->pixelclock)
> >> mode->pixelclock = mode->htotal * mode->vtotal * 60 / 1000;
> >>
> >> dbidev->top_offset = vback_porch;
> >> dbidev->left_offset = hback_porch;
> >>
> >> return 0;
> >> }
> >>
> >>
> >> int of_get_drm_panel_display_mode(struct device_node *np,
> >> struct drm_display_mode *dmode, u32 *bus_flags)
> >> {
> > Not sure about the bus_flags argument here - seems misplaced.
> >
>
> I did the same as of_get_drm_display_mode(), don't panel drivers need
> the bus flags?
In my haste I missed the display_timing combines flags for the bus and
the mode - so yes it is needed.
>
> >> u32 width_mm = 0, height_mm = 0;
> >> struct display_timing timing;
> >> struct videomode vm;
> >> int ret;
> >>
> >> ret = of_get_display_timing(np, "panel-timing", &timing);
> >> if (ret)
> >> return ret;
> >>
> >> videomode_from_timing(&timing, vm);
> >>
> >> memset(dmode, 0, sizeof(*dmode));
> >> drm_display_mode_from_videomode(&vm, dmode);
> >> if (bus_flags)
> >> drm_bus_flags_from_videomode(&vm, bus_flags);
> >
> > This does a:
> > display_timing => video_mode => drm_display_display_mode
> >
> > We could do a:
> > display_timing => drm_display_mode.
> >
>
> I'll leave this to others to sort out. I want the function to look the
> same as of_get_drm_display_mode() and it uses videomode. If videomode
> goes away both can be fixed at the same time.
When I have dig myself out of the bridge hole I am in I may take a
look at this.
Sam
next prev parent reply other threads:[~2022-02-20 21:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 15:11 [PATCH v4 0/3] drm/tiny: Add MIPI DBI compatible SPI driver Noralf Trønnes
2022-02-18 15:11 ` [PATCH v4 1/3] dt-bindings: display: add bindings for MIPI DBI compatible SPI panels Noralf Trønnes
2022-02-19 15:25 ` Sam Ravnborg
2022-02-21 2:36 ` Rob Herring
2022-02-21 11:31 ` Noralf Trønnes
2022-02-22 17:26 ` Rob Herring
2022-02-18 15:11 ` [PATCH v4 2/3] drm/mipi-dbi: Add driver_private member to struct mipi_dbi_dev Noralf Trønnes
2022-02-19 15:25 ` Sam Ravnborg
2022-02-18 15:11 ` [PATCH v4 3/3] drm/tiny: Add MIPI DBI compatible SPI driver Noralf Trønnes
2022-02-19 22:10 ` Sam Ravnborg
2022-02-20 10:04 ` Sam Ravnborg
2022-02-20 14:19 ` Noralf Trønnes
2022-02-20 18:11 ` Noralf Trønnes
2022-02-20 19:57 ` Sam Ravnborg
2022-02-20 20:34 ` Noralf Trønnes
2022-02-20 21:30 ` Sam Ravnborg [this message]
2022-02-20 15:59 ` Noralf Trønnes
2022-02-20 21:32 ` Sam Ravnborg
2022-02-21 9:05 ` Maxime Ripard
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=YhKzDi9CBrjLGm/X@ravnborg.org \
--to=sam@ravnborg.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=maxime@cerno.tech \
--cc=noralf@tronnes.org \
--cc=robh+dt@kernel.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).