From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: Chanwoo Choi <cw00.choi@samsung.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Heiko Stuebner <heiko@sntech.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Diederik de Haas <didi.debian@cknow.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] PM / devfreq: rockchip-dfi: add support for LPDDR5
Date: Thu, 05 Jun 2025 17:14:46 +0200 [thread overview]
Message-ID: <4244538.aeNJFYEL58@workhorse> (raw)
In-Reply-To: <DADLSAEF1YPO.V0CQK084KFFO@cknow.org>
Hello Diederik,
On Wednesday, 4 June 2025 10:24:33 Central European Summer Time Diederik de Haas wrote:
> Hi Nicolas,
>
> On Fri May 30, 2025 at 3:38 PM CEST, Nicolas Frattaroli wrote:
> > [...]
> > + case ROCKCHIP_DDRTYPE_LPDDR5:
> > + ddrmon_ver = readl_relaxed(dfi->regs);
> > + if (ddrmon_ver < 0x40) {
> > + *ctrl = DDRMON_CTRL_LPDDR5 | dfi->lp5_bank_mode;
> > + *mask |= DDRMON_CTRL_LP5_BANK_MODE_MASK;
> > + break;
> > + }
> > +
> > + /*
> > + * As it is unknown whether the unpleasant special case
> > + * behaviour used by the vendor kernel is needed for any
> > + * shipping hardware, ask users to report if they have
> > + * some of that hardware.
> > + */
> > + dev_err(&dfi->edev->dev,
> > + "unsupported DDRMON version 0x%04X, please let linux-rockchip know!\n",
> > + ddrmon_ver);
> > + return -EOPNOTSUPP;
>
> I'm guessing you mean the linux-rockchip mailing list here? If so, I
> think it's better to make that explicit as 'Joe User' who may run into
> this issue may not be aware of that mailing list. The 'linux' and
> 'rockchip' name combo is used in quite a few places.
I agree it's ambiguous, the message as it is right now is the way it is
because we're not allowed to linebreak user-facing messages for grep-
ability and I also don't want to exceed 100 lines of width (though this
is the one case where we're allowed to).
I suppose I should just replace it with the e-mail address of the list.
That should be clear enough and this error message also won't end up in
random boot logs strewn across the internet if it really is just some
engineering sample hardware or similar that's affected.
Kind regards,
Nicolas Frattaroli
>
> Cheers,
> Diederik
>
> > + default:
> > + dev_err(&dfi->edev->dev, "unsupported memory type 0x%X\n",
> > + dfi->ddr_type);
> > + return -EOPNOTSUPP;
> > + }
> > +
> > + return 0;
> > +}
> > +
> > static int rockchip_dfi_enable(struct rockchip_dfi *dfi)
> > {
> > void __iomem *dfi_regs = dfi->regs;
> > int i, ret = 0;
> > + u32 ctrl;
> > + u32 ctrl_mask;
> >
> > mutex_lock(&dfi->mutex);
> >
> > @@ -136,8 +186,11 @@ static int rockchip_dfi_enable(struct rockchip_dfi *dfi)
> > <snip>
>
next prev parent reply other threads:[~2025-06-05 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 13:38 [PATCH 0/2] RK3588 rockchip-dfi enhancements Nicolas Frattaroli
2025-05-30 13:38 ` [PATCH 1/2] PM / devfreq: rockchip-dfi: double count on RK3588 Nicolas Frattaroli
2025-05-30 13:38 ` [PATCH 2/2] PM / devfreq: rockchip-dfi: add support for LPDDR5 Nicolas Frattaroli
2025-06-04 8:24 ` Diederik de Haas
2025-06-05 15:14 ` Nicolas Frattaroli [this message]
2025-06-05 19:49 ` Diederik de Haas
2025-06-11 7:32 ` Sascha Hauer
2025-09-06 16:09 ` Chanwoo Choi
2025-09-06 18:38 ` Heiko Stübner
2025-09-06 22:46 ` Chanwoo Choi
2025-09-06 18:37 ` Heiko Stübner
2025-06-20 16:08 ` [PATCH 0/2] RK3588 rockchip-dfi enhancements Nicolas Frattaroli
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=4244538.aeNJFYEL58@workhorse \
--to=nicolas.frattaroli@collabora.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=cw00.choi@samsung.com \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=myungjoo.ham@samsung.com \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.reichel@collabora.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