devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: 杨孙运 <yangsunyun1993@gmail.com>,
	"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: syyang <syyang@lontium.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	andrzej.hajda@intel.com, neil.armstrong@linaro.org,
	rfoss@kernel.org, Laurent.pinchart@ideasonboard.com,
	jonas@kwiboo.se, jernej.skrabec@gmail.com,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] This patch adds a new DRM bridge driver for the Lontium LT9611C chip.
Date: Thu, 4 Sep 2025 13:04:28 +0200	[thread overview]
Message-ID: <e2c40d56-e0aa-45fa-958d-97dcf4f92a6c@kernel.org> (raw)
In-Reply-To: <CAFQXuNZUfAJe4QEDfi+-1N99xO0_z5_Omnsn_-SXr2QPtvdL_g@mail.gmail.com>

On 04/09/2025 12:48, 杨孙运 wrote:
>>> +
>>> +static void lt9611c_cleanup_resources(struct lt9611c *lt9611c)
>>> +{
>>> +     struct device *dev = lt9611c->dev;
>>> +
>>> +     if (lt9611c->work_inited) {
>>> +             cancel_work_sync(&lt9611c->work);
>>> +             lt9611c->work_inited = false;
>>> +             dev_err(dev, "work cancelled\n");
>>
>> Why???
>>
> ?? I don't understand.

You need to explain why that line - printing error - should be here. And
focus on "WHY" part.

> 
>>> +     }
>>> +
>>> +     if (lt9611c->bridge_added) {
>>> +             drm_bridge_remove(&lt9611c->bridge);
>>> +             lt9611c->bridge_added = false;
>>> +             dev_err(dev, "DRM bridge removed\n");
>>> +     }
>>> +
>>> +     if (lt9611c->regulators_enabled) {
>>> +             regulator_bulk_disable(ARRAY_SIZE(lt9611c->supplies), lt9611c->supplies);
>>> +             lt9611c->regulators_enabled = false;
>>> +             dev_err(dev, "regulators disabled\n");
>>> +     }
>>> +
>>> +     if (lt9611c->audio_pdev)
>>> +             lt9611c_audio_exit(lt9611c);
>>> +
>>> +     if (lt9611c->fw) {
>>
>> You definitely don't need firmware when the bridge is up and running.
>>
> The previous text has already described the working logic of the firmware.
> 
>>> +             release_firmware(lt9611c->fw);
>>> +             lt9611c->fw = NULL;
>>> +             dev_err(dev, "firmware released\n");
>>> +     }
>>> +
>>> +     if (lt9611c->dsi0_node) {
>>> +             of_node_put(lt9611c->dsi0_node);
>>> +             lt9611c->dsi0_node = NULL;
>>> +             dev_err(dev, "dsi0 node released\n");

Your driver is way, way to noisy.

Please read coding style - what does it say about driver being silent?


Best regards,
Krzysztof

  reply	other threads:[~2025-09-04 11:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 12:38 [PATCH v1 0/2] Add LT9611C DRM bridge driver and device tree binding syyang
2025-09-03 12:38 ` [PATCH v1 1/2] This patch adds a new device tree binding documentation syyang
2025-09-03 16:33   ` Rob Herring (Arm)
2025-09-04  2:25     ` [PATCH v2 " syyang
2025-09-04  2:53       ` Dmitry Baryshkov
2025-09-04  5:49       ` Krzysztof Kozlowski
2025-09-04  8:08         ` 杨孙运
2025-09-04  8:26           ` Krzysztof Kozlowski
2025-09-04 11:27             ` 杨孙运
2025-09-04  2:21   ` [PATCH v1 " Dmitry Baryshkov
     [not found]     ` <CAFQXuNYKcGHyWLD5hjj24CrbaXzkaKsLU4R2vmhYaryQArA_yQ@mail.gmail.com>
2025-09-04  2:56       ` Dmitry Baryshkov
2025-09-03 12:38 ` [PATCH v1 2/2] This patch adds a new DRM bridge driver for the Lontium LT9611C chip syyang
2025-09-04  2:52   ` Dmitry Baryshkov
2025-09-04 10:48     ` 杨孙运
2025-09-04 11:04       ` Krzysztof Kozlowski [this message]
2025-09-04 11:17         ` 杨孙运
2025-09-04 14:39       ` Dmitry Baryshkov
2025-09-05  2:55         ` 杨孙运
2025-09-05  8:10           ` neil.armstrong
2025-09-05  8:58             ` 杨孙运
2025-09-05 14:24               ` Dmitry Baryshkov
2025-09-08  1:14                 ` 杨孙运
2025-09-08 10:17                   ` Dmitry Baryshkov
2025-09-05 14:10           ` Dmitry Baryshkov
2025-09-08 11:03   ` Jani Nikula
2025-09-08 11:07   ` Jani Nikula

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=e2c40d56-e0aa-45fa-958d-97dcf4f92a6c@kernel.org \
    --to=krzk@kernel.org \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=andrzej.hajda@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=robh@kernel.org \
    --cc=syyang@lontium.com \
    --cc=yangsunyun1993@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).