From: Chris Morgan <macroalpha82@gmail.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: Doug Anderson <dianders@chromium.org>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Sam Ravnborg <sam@ravnborg.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
cros-qcom-dts-watchers@chromium.org, linux-input@vger.kernel.org,
hsinyi@google.com, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
devicetree@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
yangcong5@huaqin.corp-partner.google.com
Subject: Re: [PATCH v3 02/10] drm/panel: Check for already prepared/enabled in drm_panel
Date: Wed, 2 Aug 2023 12:25:52 -0500 [thread overview]
Message-ID: <64ca91a3.0d0a0220.8e58d.89b3@mx.google.com> (raw)
In-Reply-To: <kuctj2p353nsae24lrhcymqqpfajbc7qoqly63zpwvdp6lgu3b@kk4gpzsapxnn>
On Mon, Jul 31, 2023 at 07:03:07PM +0200, Maxime Ripard wrote:
> Hi,
>
> On Mon, Jul 31, 2023 at 11:33:22AM -0500, Chris Morgan wrote:
> > In my case a few different panel drivers disable the regulators in the
> > unprepare/disable routines.
>
> And that's totally fine.
>
> > For at least the Rockchip DSI implementations for some reason the
> > panel gets unprepared more than once, which triggers an unbalanced
> > regulator disable.
>
> "For some reason" being that DW-DSI apparently finds it ok to bypass any
> kind of abstraction and randomly calling panel functions by itself:
>
> https://elixir.bootlin.com/linux/v6.4.7/source/drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c#L868
>
> It looks like it's fixed it current drm-misc-next though.
Good, when I get a chance I will test it out with the existing panels
I have at my disposal and submit some patches to clean them up.
>
> > Obviously though the correct course of action is to fix the reason why
> > the panel is disabled more than once, but that's at least the root
> > cause of this behavior on the few panels I've worked with.
>
> Like I said we already have a commit on the way to fix that, so it
> shouldn't be an issue anymore.
>
> I stand by what I was saying earlier though, I think it's mostly
> cargo-cult or drivers being very wrong. If anything, the DW-DSI stuff
> made me even more convinced that we shouldn't even entertain that idea
> :)
>
> Maxime
Thank you, and yes if a driver is doing something it shouldn't we
shouldn't be patching around that, we should be fixing things. Thanks
for providing me with the additional info.
Chris
next prev parent reply other threads:[~2023-08-02 17:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 20:34 [PATCH v3 00/10] drm/panel and i2c-hid: Allow panels and touchscreens to power sequence together Douglas Anderson
2023-07-25 20:34 ` [PATCH v3 01/10] dt-bindings: HID: i2c-hid: Add "panel" property to i2c-hid backed touchscreens Douglas Anderson
2023-07-25 20:34 ` [PATCH v3 02/10] drm/panel: Check for already prepared/enabled in drm_panel Douglas Anderson
2023-07-26 12:41 ` Maxime Ripard
2023-07-26 15:10 ` Doug Anderson
2023-07-27 6:37 ` Maxime Ripard
2023-07-31 16:33 ` Chris Morgan
2023-07-31 17:03 ` Maxime Ripard
2023-08-02 17:25 ` Chris Morgan [this message]
2023-08-02 17:50 ` Dave Stevenson
2023-07-25 20:34 ` [PATCH v3 03/10] drm/panel: Add a way for other devices to follow panel state Douglas Anderson
2023-07-25 20:34 ` [PATCH v3 04/10] of: property: fw_devlink: Add a devlink for panel followers Douglas Anderson
2023-07-25 20:34 ` [PATCH v3 05/10] HID: i2c-hid: Switch to SYSTEM_SLEEP_PM_OPS() Douglas Anderson
2023-07-25 20:34 ` [PATCH v3 06/10] HID: i2c-hid: Rearrange probe() to power things up later Douglas Anderson
2023-07-25 20:34 ` [PATCH v3 07/10] HID: i2c-hid: Make suspend and resume into helper functions Douglas Anderson
2023-07-25 20:34 ` [PATCH v3 08/10] HID: i2c-hid: Support being a panel follower Douglas Anderson
2023-07-26 8:57 ` Benjamin Tissoires
2023-07-26 16:07 ` Doug Anderson
2023-07-26 16:45 ` Benjamin Tissoires
2023-07-25 20:34 ` [PATCH v3 09/10] HID: i2c-hid: Do panel follower work on the system_wq Douglas Anderson
2023-07-25 20:34 ` [PATCH v3 10/10] arm64: dts: qcom: sc7180: Link trogdor touchscreens to the panels Douglas Anderson
2023-07-26 12:45 ` [PATCH v3 00/10] drm/panel and i2c-hid: Allow panels and touchscreens to power sequence together 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=64ca91a3.0d0a0220.8e58d.89b3@mx.google.com \
--to=macroalpha82@gmail.com \
--cc=andersson@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frowand.list@gmail.com \
--cc=hsinyi@google.com \
--cc=jikos@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=tzimmermann@suse.de \
--cc=yangcong5@huaqin.corp-partner.google.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).