devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "TY_Chang[張子逸]" <tychang@realtek.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 1/7] pinctrl: realtek: Add common pinctrl driver for Realtek DHC RTD SoCs
Date: Mon, 18 Sep 2023 03:02:31 +0000	[thread overview]
Message-ID: <ae5a5665e11242e49b9b84d54b1d4ac3@realtek.com> (raw)
In-Reply-To: <CACRpkda8_nV1UiDO0_qvcc_z8ODQqckwaCGg6A5-Qm0NADi_Ng@mail.gmail.com>


Hi Linus,
>
>Hi Tzuyi,
>
>thanks for the new version! This is starting to look really good.
>
>On Thu, Aug 24, 2023 at 12:57 PM Tzuyi Chang <tychang@realtek.com> wrote:
>
>> The RTD SoCs share a similar design for pinmux and pinconfig.
>> This common pinctrl driver supports different variants within the RTD
>> SoCs.
>>
>> Signed-off-by: Tzuyi Chang <tychang@realtek.com>
>(...)
>> +static void rtd_pinctrl_update_bits(struct rtd_pinctrl *data, unsigned int offset,
>> +                                   unsigned int mask, unsigned int
>> +val) {
>> +       unsigned int reg = readl_relaxed(data->base + offset);
>> +
>> +       reg &= ~mask;
>> +       reg |= (mask & val);
>> +       writel_relaxed(reg, data->base + offset); }
>
>This function is essentially a reimplementation of regmap_update_bits() using
>regmap_mmio with .user_relaxed_mmio property set in the config.
>
>Have you considered just using regmap-mmio for this?
>

Thank you for the suggestion. I'll use regmap_mmio to replace it in the next version.

>Yours,
>Linus Walleij


Thanks,
Tzuyi Chang

  reply	other threads:[~2023-09-18  3:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 10:56 [PATCH v2 0/7] Add pinctrl driver support for Realtek DHC SoCs Tzuyi Chang
2023-08-24 10:56 ` [PATCH v2 1/7] pinctrl: realtek: Add common pinctrl driver for Realtek DHC RTD SoCs Tzuyi Chang
2023-09-11  8:58   ` Linus Walleij
2023-09-18  3:02     ` TY_Chang[張子逸] [this message]
2023-08-24 10:56 ` [PATCH v2 2/7] pinctrl: realtek: Add pinctrl driver for RTD1315E Tzuyi Chang
2023-08-24 10:56 ` [PATCH v2 3/7] pinctrl: realtek: Add pinctrl driver for RTD1319D Tzuyi Chang
2023-08-24 10:57 ` [PATCH v2 4/7] pinctrl: realtek: Add pinctrl driver for RTD1619B Tzuyi Chang
2023-08-24 10:57 ` [PATCH v2 5/7] dt-bindings: pinctrl: realtek: add RTD1315E pinctrl binding Tzuyi Chang
2023-08-24 21:11   ` Rob Herring
2023-08-29  7:22     ` TY_Chang[張子逸]
2023-08-29  7:40       ` Krzysztof Kozlowski
2023-09-01  9:55         ` TY_Chang[張子逸]
2023-08-24 10:57 ` [PATCH v2 6/7] dt-bindings: pinctrl: realtek: add RTD1319D " Tzuyi Chang
2023-08-24 21:13   ` Rob Herring
2023-08-29  7:23     ` TY_Chang[張子逸]
2023-09-11  8:52   ` Linus Walleij
2023-08-24 10:57 ` [PATCH v2 7/7] dt-bindings: pinctrl: realtek: add RTD1619B " Tzuyi Chang
2023-09-11  8:53   ` Linus Walleij

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=ae5a5665e11242e49b9b84d54b1d4ac3@realtek.com \
    --to=tychang@realtek.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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).