From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Michal Simek <michal.simek@amd.com>
Cc: u-boot@lists.denx.de, etienne.carriere@st.com, sjg@chromium.org,
linus.walleij@linaro.org, Oleksii_Moisieiev@epam.com
Subject: Re: [RFC 4/6] gpio: add scmi driver based on pinctrl
Date: Thu, 7 Sep 2023 08:37:58 +0900 [thread overview]
Message-ID: <ZPkNVr2nn0zW38dF@octopus> (raw)
In-Reply-To: <523ca6eb-3737-d090-8006-f127eda2330b@amd.com>
On Wed, Sep 06, 2023 at 04:56:56PM +0200, Michal Simek wrote:
>
>
> On 9/6/23 04:40, AKASHI Takahiro wrote:
> > This DM-compliant driver deals with SCMI pinctrl protocol and presents
> > gpio devices exposed by SCMI firmware (server).
> >
> > Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> > ---
> > drivers/pinctrl/pinctrl-scmi.c | 544 ++++++++++++++++++++++++++++++++-
> > 1 file changed, 539 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/pinctrl/pinctrl-scmi.c b/drivers/pinctrl/pinctrl-scmi.c
> > index 3ebdad57b86c..73d385bdbfcc 100644
> > --- a/drivers/pinctrl/pinctrl-scmi.c
> > +++ b/drivers/pinctrl/pinctrl-scmi.c
> > @@ -11,21 +11,20 @@
> > #include <malloc.h>
> > #include <scmi_agent.h>
> > #include <scmi_protocols.h>
> > +#include <asm-generic/gpio.h>
> > #include <dm/device_compat.h>
> > +#include <dm/device-internal.h>
> > +#include <dm/lists.h>
> > #include <dm/pinctrl.h>
> > /**
> > * struct scmi_pin - attributes for a pin
> > * @name: Name of pin
> > - * @value: Value of pin
> > - * @flags: A set of flags
> > * @function: Function selected
> > * @status: An array of status of configuration types
> > */
> > struct scmi_pin {
> > char *name;
> > - u32 value;
> > - u32 flags;
>
>
> You have added this in 3/6 then there is no reason to remove it in this version.
Right.
It was my mistake in a last-minute cleanup.
The hunk should be merged in 3/6.
BTW, this part of code, holding status of every pin's pinconf properties
locally, is a bit clumsy. I'd remove the whole code if possible.
-Takahiro Akashi
> M
next prev parent reply other threads:[~2023-09-07 0:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 2:40 [RFC 0/6] firmware: scmi: add SCMI pinctrl protocol support AKASHI Takahiro
2023-09-06 2:40 ` [RFC 1/6] firmware: scmi: fix protocol enumeration logic AKASHI Takahiro
2023-09-10 19:13 ` Simon Glass
2023-09-11 4:58 ` AKASHI Takahiro
2023-09-06 2:40 ` [RFC 2/6] firmware: scmi: add pinctrl protocol support AKASHI Takahiro
2023-09-06 2:40 ` [RFC 3/6] pinctrl: add scmi driver AKASHI Takahiro
2023-09-10 19:13 ` Simon Glass
2023-09-11 5:14 ` AKASHI Takahiro
2023-09-06 2:40 ` [RFC 4/6] gpio: add scmi driver based on pinctrl AKASHI Takahiro
2023-09-06 14:56 ` Michal Simek
2023-09-06 23:37 ` AKASHI Takahiro [this message]
2023-09-07 12:23 ` Simon Glass
2023-09-08 4:32 ` AKASHI Takahiro
2023-09-10 19:13 ` Simon Glass
2023-09-11 5:38 ` AKASHI Takahiro
2023-09-06 2:40 ` [RFC 5/6] firmware: scmi: add pseudo pinctrl protocol support on sandbox AKASHI Takahiro
2023-09-10 19:13 ` Simon Glass
2023-09-11 5:23 ` AKASHI Takahiro
2023-09-06 2:40 ` [RFC 6/6] test: dm: add SCMI pinctrl test AKASHI Takahiro
2023-09-10 19:13 ` Simon Glass
2023-09-11 5:47 ` AKASHI Takahiro
2023-09-22 18:27 ` Simon Glass
2023-09-06 3:09 ` [RFC 0/6] firmware: scmi: add SCMI pinctrl protocol support Fabio Estevam
2023-09-07 9:58 ` AKASHI Takahiro
2023-09-08 12:14 ` Peng Fan
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=ZPkNVr2nn0zW38dF@octopus \
--to=takahiro.akashi@linaro.org \
--cc=Oleksii_Moisieiev@epam.com \
--cc=etienne.carriere@st.com \
--cc=linus.walleij@linaro.org \
--cc=michal.simek@amd.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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