public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: "Cathy Xu (许华婷)" <ot_cathy.xu@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"sean.wang@kernel.org" <sean.wang@kernel.org>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	"krzk@kernel.org" <krzk@kernel.org>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Guodong Liu (刘国栋)" <Guodong.Liu@mediatek.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: mediatek: Add support for MT8196
Date: Tue, 14 Jan 2025 07:47:06 +0000	[thread overview]
Message-ID: <8ed4a30710a3dc56595898417d00c2eca0659f75.camel@mediatek.com> (raw)
In-Reply-To: <2a773ddb-2836-40cf-a08b-ac47430aeb78@kernel.org>

On Wed, 2024-12-11 at 08:56 +0100, Krzysztof Kozlowski wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> On 11/12/2024 06:54, ot907280 wrote:
> > From: Guodong Liu <guodong.liu@mediatek.corp-partner.google.com>
> > 
> > Add pinctrl driver for mt8196
> > 
> > Signed-off-by: Guodong Liu <guodong.liu@mediatek.com>
> > Signed-off-by: ot907280 <ot_cathy.xu@mediatek.com>
> 
> 
> Please use real names, not logins.
> 
> <form letter>
> Please use scripts/get_maintainers.pl to get a list of necessary
> people
> and lists to CC. It might happen, that command when run on an older
> kernel, gives you outdated entries. Therefore please be sure you base
> your patches on recent Linux kernel.
> 
> Tools like b4 or scripts/get_maintainer.pl provide you proper list of
> people, so fix your workflow. Tools might also fail if you work on
> some
> ancient tree (don't, instead use mainline) or work on fork of kernel
> (don't, instead use mainline). Just use b4 and everything should be
> fine, although remember about `b4 prep --auto-to-cc` if you added new
> patches to the patchset.
> 
> You missed at least devicetree list (maybe more), so this won't be
> tested by automated tooling. Performing review on untested code might
> be
> a waste of time.
> 
> Please kindly resend and include all necessary To/Cc entries.
> </form letter>
  Thank you for your review. I will use real names and run
scripts/get_maintainers.pl on recent Linux kernel in next version.

> 
> 
> > ---
> >  drivers/pinctrl/mediatek/Kconfig              |   12 +
> >  drivers/pinctrl/mediatek/Makefile             |    1 +
> >  drivers/pinctrl/mediatek/pinctrl-mt8196.c     | 1757 +++++++++++
> >  drivers/pinctrl/mediatek/pinctrl-mtk-mt8196.h | 2791
> > +++++++++++++++++
> >  include/dt-bindings/pinctrl/mt8196-pinfunc.h  | 1572 ++++++++++
> >  5 files changed, 6133 insertions(+)
> >  create mode 100644 drivers/pinctrl/mediatek/pinctrl-mt8196.c
> >  create mode 100644 drivers/pinctrl/mediatek/pinctrl-mtk-mt8196.h
> >  create mode 100644 include/dt-bindings/pinctrl/mt8196-pinfunc.h
> 
> Please run scripts/checkpatch.pl and fix reported warnings. Then
> please
> run `scripts/checkpatch.pl --strict` and (probably) fix more
> warnings.
> Some warnings can be ignored, especially from --strict run, but the
> code
> here looks like it needs a fix. Feel free to get in touch if the
> warning
> is not clear.
  Sorry, the other warnings reported by run `scripts/checkpatch.pl --
strict` will be fixed in next version, but it didn't report the warning
here. Could you please tell me what warning you are referring to here?
Thanks~

> 
> 
> 
> > +static const char * const mt8196_pinctrl_register_base_names[] = {
> > +     "iocfg0", "iocfg_rt", "iocfg_rm1", "iocfg_rm2",
> > +     "iocfg_rb", "iocfg_bm1", "iocfg_bm2", "iocfg_bm3",
> > +     "iocfg_lt", "iocfg_lm1", "iocfg_lm2", "iocfg_lb1",
> > +     "iocfg_lb2", "iocfg_tm1", "iocfg_tm2", "iocfg_tm3",
> > +};
> > +
> > +static const struct mtk_pin_soc mt8196_data = {
> > +     .reg_cal        = mt8196_reg_cals,
> > +     .pins   = mtk_pins_mt8196,
> > +     .npins  = ARRAY_SIZE(mtk_pins_mt8196),
> > +     .ngrps  = ARRAY_SIZE(mtk_pins_mt8196),
> > +     .nfuncs = 8,
> > +     .gpio_m = 0,
> > +     .base_names     = mt8196_pinctrl_register_base_names,
> > +     .nbase_names    =
> > ARRAY_SIZE(mt8196_pinctrl_register_base_names),
> > +     .pull_type = mt8196_pull_type,
> > +     .bias_set_combo = mtk_pinconf_bias_set_combo,
> > +     .bias_get_combo = mtk_pinconf_bias_get_combo,
> > +     .drive_set      = mtk_pinconf_drive_set_rev1,
> > +     .drive_get      = mtk_pinconf_drive_get_rev1,
> > +     .adv_drive_get  = mtk_pinconf_adv_drive_get_raw,
> > +     .adv_drive_set  = mtk_pinconf_adv_drive_set_raw,
> > +};
> > +
> > +static const struct of_device_id mt8196_pinctrl_of_match[] = {
> > +     { .compatible = "mediatek,mt8196-pinctrl", .data =
> > &mt8196_data },
> 
> 
> Please run scripts/checkpatch.pl and fix reported warnings. Then
> please
> run `scripts/checkpatch.pl --strict` and (probably) fix more
> warnings.
> Some warnings can be ignored, especially from --strict run, but the
> code
> here looks like it needs a fix. Feel free to get in touch if the
> warning
> is not clear.
  Sorry, it's the same here, no warnings were reported here. Could you
please point it out? Thank you~  

> 
> > +     { }
> > +};
> > +
> > +static struct platform_driver mt8196_pinctrl_driver = {
> > +     .driver = {
> > +             .name = "mt8196-pinctrl",
> > +             .of_match_table = mt8196_pinctrl_of_match,
> > +             .pm = &mtk_paris_pinctrl_pm_ops,
> > +     },
> > +     .probe = mtk_paris_pinctrl_probe,
> > +};
> > +
> > +static int __init mt8196_pinctrl_init(void)
> > +{
> > +     return platform_driver_register(&mt8196_pinctrl_driver);
> > +}
> > +arch_initcall(mt8196_pinctrl_init);
> > +
> > +MODULE_LICENSE("GPL");
> 
> 
> ...
> 
> > +#endif /* __PINCTRL_MTK_MT8196_H */
> > diff --git a/include/dt-bindings/pinctrl/mt8196-pinfunc.h
> > b/include/dt-bindings/pinctrl/mt8196-pinfunc.h
> > new file mode 100644
> > index 000000000000..717351b12255
> > --- /dev/null
> > +++ b/include/dt-bindings/pinctrl/mt8196-pinfunc.h
> > @@ -0,0 +1,1572 @@
> > +/* SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause */
> > +/*
> > + * Copyright (C) 2024 Mediatek Inc.
> > + * Author: Guodong Liu <Guodong.Liu@mediatek.com>
> > + */
> > +
> > +#ifndef __MT8196_PINFUNC_H
> > +#define __MT8196_PINFUNC_H
> > +
> > +#include <dt-bindings/pinctrl/mt65xx.h>
> > +
> > +#define PINMUX_GPIO0__FUNC_GPIO0 (MTK_PIN_NO(0) | 0)
> > +#define PINMUX_GPIO0__FUNC_DMIC1_CLK (MTK_PIN_NO(0) | 1)
> > +#define PINMUX_GPIO0__FUNC_SPI3_A_MO (MTK_PIN_NO(0) | 3)
> > +#define PINMUX_GPIO0__FUNC_FMI2S_B_LRCK (MTK_PIN_NO(0) | 4)
> > +#define PINMUX_GPIO0__FUNC_SCP_DMIC1_CLK (MTK_PIN_NO(0) | 5)
> > +#define PINMUX_GPIO0__FUNC_TP_GPIO14_AO (MTK_PIN_NO(0) | 6)
> 
> 
> These aren't really bindings. If you disagree, point me to the usage
> in
> the driver.
  Sorry, I misunderstood the meaning of the bindings earlier. The
really bindings will be uploaded in next version.

> 
> 
> 
> Best regards,
> Krzysztof

  reply	other threads:[~2025-01-14  7:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  5:54 [PATCH] pinctrl: mediatek: Add support for MT8196 ot907280
2024-12-11  7:56 ` Krzysztof Kozlowski
2025-01-14  7:47   ` Cathy Xu (许华婷) [this message]
2025-01-14 11:25     ` Krzysztof Kozlowski
2025-01-15  1:25       ` Cathy Xu (许华婷)
2024-12-12  4:53 ` kernel test robot
2024-12-20 16:26 ` kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2024-11-11  8:53 ot907280
2024-11-11  9:12 ` Christophe JAILLET
2025-01-13 10:03   ` Cathy Xu (许华婷)
2024-11-13 13:28 ` Linus Walleij
2025-01-13  9:35   ` Cathy Xu (许华婷)

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=8ed4a30710a3dc56595898417d00c2eca0659f75.camel@mediatek.com \
    --to=ot_cathy.xu@mediatek.com \
    --cc=Guodong.Liu@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=sean.wang@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