From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Chanwoo Choi <chanwoo@kernel.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: RE: [PATCH v1 1/2] extcon: add Realtek DHC RTD SoC Type-C driver
Date: Wed, 30 Aug 2023 03:59:31 +0000 [thread overview]
Message-ID: <249af57804f3405f80f28879e31637b3@realtek.com> (raw)
In-Reply-To: <c70c08b4-be67-14da-be25-5473ffd0ca7d@kernel.org>
Hi Chanwoo,
> >>> +#define TYPE_C_EN_SWITCH BIT(29)
> >>> +#define TYPE_C_TXRX_SEL (BIT(28) | BIT(27)) #define
> >>> +TYPE_C_SWITCH_MASK (TYPE_C_EN_SWITCH | TYPE_C_TXRX_SEL)
> #define
> >>> +TYPE_C_ENABLE_CC1 TYPE_C_EN_SWITCH #define
> TYPE_C_ENABLE_CC2
> >>> +(TYPE_C_EN_SWITCH | TYPE_C_TXRX_SEL) #define TYPE_C_DISABLE_CC
> >>> +~TYPE_C_SWITCH_MASK
> >>> +
> >>> + val_cc = readl(reg);
> >>
> >> I'd like you to use regmap interface to access the register by using
> >> regmap_read, regmap_write. You can create the regmap instance via
> >> devm_regmap_init_mmio() on probe instead of using 'type_c->reg_base'
> >> at the multipe point.
> >>
> >> For example,
> >> struct regmap_config rtk_regmap_config = {
> >> .reg_bits = 32,
> >> .val_bits = 32,
> >> };
> >>
> >> void __iomem *base;
> >>
> >> base = devm_platform_get_and_ioremap_resource(pdev, 0,
> &res);
> >> if (IS_ERR(base))
> >> return PTR_ERR(base);
> >>
> >> regmap = devm_regmap_init_mmio(dev, base,
> >> &rtk_regmap_config);
> >>
> >> ---
> >>
> >> And then just call regmap_read without any calculation between
> >> base address and specific register.
> >>
> >> regmap_read(regmap, USB_TYPEC_CTRL_CC1_0)
> >>
> >
> > I studied mmio's regmap.
> >
> > It only changed one encoding method. And simplifies the calculation
> between the base address and the specific register.
>
> The regmap provides the consistent interface to access register regardless of
> mmio/i2c/spi and so on. It is the advantage of regmap.
>
> And regmap provides the like register dump via debugfs, is able to specify the
> kind of register like writable, readable, volatile type.
> It is possible to specify the more detailed register information in device driver
> in order to improve the readability. It allows you to express more detail of this
> device than just working.
These are all advantages of regmap, I agree.
I haven't delved into regmap yet.
>
> > If the register is 32-bit aligned, other operations look the same as
> readl/writel.
> > I think regmap is more simplified if the read registers are not 32-bit aligned,
> e.g. nvmem read/write.
>
> I'm sorry. I don't understand of what is accurate meaning.
> Could you please explain your opinion more detailed with example of this
> patch?
Sorry, I misunderstood regmap, I thought he could read register like read otp tables by nvmem regardless of his bitness and size.
So my answer should be incorrect.
Thank,
Stanley
prev parent reply other threads:[~2023-08-30 4:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 10:28 [PATCH v1 1/2] extcon: add Realtek DHC RTD SoC Type-C driver Stanley Chang
2023-08-22 10:28 ` [PATCH v1 2/2] dt-bindings: extcon: Add Realtek DHC RTD SoC Type-C Stanley Chang
2023-08-22 15:38 ` Krzysztof Kozlowski
2023-08-24 6:03 ` Stanley Chang[昌育德]
2023-08-24 6:26 ` Krzysztof Kozlowski
2023-08-24 7:23 ` Stanley Chang[昌育德]
2023-08-24 8:43 ` Krzysztof Kozlowski
2023-08-24 9:23 ` Stanley Chang[昌育德]
2023-08-24 9:56 ` Krzysztof Kozlowski
2023-08-24 10:05 ` Stanley Chang[昌育德]
2023-08-22 15:35 ` [PATCH v1 1/2] extcon: add Realtek DHC RTD SoC Type-C driver Krzysztof Kozlowski
2023-08-24 6:09 ` Stanley Chang[昌育德]
2023-08-23 0:26 ` kernel test robot
2023-08-23 14:15 ` kernel test robot
2023-08-24 19:43 ` Chanwoo Choi
2023-08-25 9:39 ` Stanley Chang[昌育德]
2023-08-29 11:15 ` Stanley Chang[昌育德]
2023-08-29 19:18 ` Chanwoo Choi
2023-08-30 3:59 ` Stanley Chang[昌育德] [this message]
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=249af57804f3405f80f28879e31637b3@realtek.com \
--to=stanley_chang@realtek.com \
--cc=chanwoo@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--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