From: "Vishnu Reddy" <vishnu.reddy@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>,
<krzysztof.kozlowski@linaro.org>, <s.nawrocki@samsung.com>,
<alim.akhtar@samsung.com>, <linus.walleij@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <pankaj.dubey@samsung.com>,
<ravi.patel@samsung.com>, <gost.dev@samsung.com>
Subject: RE: [PATCH v2] pinctrl: samsung: Add support for pull-up and pull-down
Date: Wed, 26 Jun 2024 17:19:28 +0530 [thread overview]
Message-ID: <07f201dac7be$e81317d0$b8394770$@samsung.com> (raw)
In-Reply-To: <38fae674-f672-46e0-a44e-1278deaaf36a@kernel.org>
> -----Original Message-----
> From: Krzysztof Kozlowski [mailto:krzk@kernel.org]
> Sent: 24 June 2024 19:27
> To: Vishnu Reddy <vishnu.reddy@samsung.com>;
> krzysztof.kozlowski@linaro.org; s.nawrocki@samsung.com;
> alim.akhtar@samsung.com; linus.walleij@linaro.org
> Cc: linux-arm-kernel@lists.infradead.org; linux-samsung-
> soc@vger.kernel.org; linux-gpio@vger.kernel.org; linux-
> kernel@vger.kernel.org; pankaj.dubey@samsung.com;
> ravi.patel@samsung.com; gost.dev@samsung.com
> Subject: Re: [PATCH v2] pinctrl: samsung: Add support for pull-up and pull-
> down
>
> On 20/06/2024 12:34, Vishnu Reddy wrote:
> > gpiolib framework has the implementation of setting up the
> > PUD configuration for GPIO pins but there is no driver support.
> >
> > Add support to handle the PUD configuration request from the
> > userspace in samsung pinctrl driver.
> >
> > Signed-off-by: Vishnu Reddy <vishnu.reddy@samsung.com>
> > ---
> > Verified the offset from the user manual of following Exynos SoC series
> > and found the current code is taking care of correct offset for pull-up
> > and pull-down
> >
> > Exynos-3250
> > Exynos-3470
> > Exynos-4412
> > Exynos-4415
> > Exynos-5250
> > Exynos-5260
> > Exynos-5410
> > Exynos-5420
> > Exynos-5422
> > Exynos-7420
> > Exynos-7580
> > Exynos-7880
> > Exynos-9820
> > Exynos-9830
> > Exynos-4210
> > Exynos-S5PC210
> > Exynos-S5PV310
> >
> > This patch is tested on FSD platform
>
> You verified but...
>
> > diff --git a/drivers/pinctrl/samsung/pinctrl-samsung.h
> b/drivers/pinctrl/samsung/pinctrl-samsung.h
> > index d50ba6f07d5d..758b623a4bea 100644
> > --- a/drivers/pinctrl/samsung/pinctrl-samsung.h
> > +++ b/drivers/pinctrl/samsung/pinctrl-samsung.h
> > @@ -61,6 +61,13 @@ enum pincfg_type {
> > #define PIN_CON_FUNC_INPUT 0x0
> > #define PIN_CON_FUNC_OUTPUT 0x1
> >
> > +/*
> > + * Values for the pin PUD register.
> > + */
> > +#define PIN_PUD_PULL_UP_DOWN_DISABLE 0x0
> > +#define PIN_PUD_PULL_DOWN_ENABLE 0x1
> > +#define PIN_PUD_PULL_UP_ENABLE 0x3
>
> ... I said it is not correct, so you send the same? If you think I was
> wrong, then please respond and keep discussion going. Sending the same
> suggests you just ignored my comment.
>
> Look at two headers s5pv210-pinctrl.h and s3c64xx-pinctrl.h. How did you
> resolve these?
Thank you for sharing the s5pv210-pinctrl.h and s3c64xx-pinctrl.h file names for the pin value information.
I have not ignored your comment. Unfortunately, I don't have the user manuals for the s3c64xx and s5pv210 series.
I have an idea to handle the PIN_PULL_UP value of the s3c64xx and s5pv210 series by checking the compatibility with the of_device_is_compatible API.
Will it be okay or do you have any other suggestions?
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2024-06-26 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240620103950epcas5p10514d4a19bdfd505d7d92ceb1fe10cc7@epcas5p1.samsung.com>
2024-06-20 10:34 ` [PATCH v2] pinctrl: samsung: Add support for pull-up and pull-down Vishnu Reddy
2024-06-24 3:54 ` Alim Akhtar
2024-06-24 13:56 ` Krzysztof Kozlowski
2024-06-26 11:49 ` Vishnu Reddy [this message]
2024-06-26 13:01 ` Krzysztof Kozlowski
2024-06-27 13:35 ` Vishnu Reddy
2024-06-27 15:22 ` Krzysztof Kozlowski
2024-06-27 15:27 ` Krzysztof Kozlowski
2024-07-03 3:19 ` Vishnu Reddy
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='07f201dac7be$e81317d0$b8394770$@samsung.com' \
--to=vishnu.reddy@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=gost.dev@samsung.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.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-samsung-soc@vger.kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=s.nawrocki@samsung.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).