From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Raag Jadav <raag.jadav@intel.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1 2/3] pinctrl: intel: Add a generic Intel pin control platform driver
Date: Mon, 13 Nov 2023 14:53:34 +0200 [thread overview]
Message-ID: <20231113125334.GQ17433@black.fi.intel.com> (raw)
In-Reply-To: <ZVISwHwoLpy3nGDT@smile.fi.intel.com>
On Mon, Nov 13, 2023 at 02:12:48PM +0200, Andy Shevchenko wrote:
> On Fri, Nov 03, 2023 at 07:57:38AM +0200, Mika Westerberg wrote:
> > On Mon, Oct 30, 2023 at 04:10:33PM +0200, Andy Shevchenko wrote:
>
> ...
>
> > > +config PINCTRL_INTEL_PLATFORM
> > > + tristate "Intel pinctrl and GPIO platform driver"
> > > + depends on ACPI
> > > + select PINCTRL_INTEL
> > > + help
> > > + This pinctrl driver provides an interface that allows configuring
> > > + of Intel PCH pins and using them as GPIOs.
> >
> > Add here some description that explains why this needs to be enabled,
> > for example for Lunar Lake. Now it is all too generic for distro folks
> > to understand if this is needed or not.
>
> OK!
>
> ...
>
> > > + * Copyright (C) 2021-2023, Intel Corporation
> >
> > That's 2023
>
> As-is it is still valid and reflects the history.
>
> ...
>
> > > + ngpps = device_get_child_node_count(dev);
> > > + if (ngpps == 0)
> >
> > if (!nggps)
>
> 0 is a plain number here (as count) and explicit comparison makes sense.
> But I'm okay with another form.
>
>
> > > + return -ENODEV;
>
> ...
>
> > > + ncommunities = 1,
> >
> > Why this is 1? Can't we have more communities?
>
> As for now (version 1.0 of the specification) it's assumed that it's one
> community per device node in the ACPI, so I would leave this as is (we have
> also drivers with single community per device node, hence this is kinda
> pattern. Should I add a comment?
>
Yes, I think it warrants a comment.
> ...
>
> > > + struct device *dev = &pdev->dev;
> > > + struct intel_pinctrl_soc_data *data;
> >
> >
> > Change the ordering of the above:
> >
> > struct intel_pinctrl_soc_data *data;
> > struct device *dev = &pdev->dev;
>
> Sure.
>
> ...
>
> > > +static const struct acpi_device_id intel_platform_pinctrl_acpi_match[] = {
> > > + { }
> >
> > And add the _CID here in this patch as I commented in the last patch.
>
> OK! I'll squash the next patch into this one.
>
> > > +};
>
> --
> With Best Regards,
> Andy Shevchenko
>
next prev parent reply other threads:[~2023-11-13 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 14:10 [PATCH v1 0/3] pinctrl: intel: Add generic platform driver Andy Shevchenko
2023-10-30 14:10 ` [PATCH v1 1/3] pinctrl: intel: Revert "Unexport intel_pinctrl_probe()" Andy Shevchenko
2023-10-30 14:10 ` [PATCH v1 2/3] pinctrl: intel: Add a generic Intel pin control platform driver Andy Shevchenko
2023-11-03 5:57 ` Mika Westerberg
2023-11-13 12:12 ` Andy Shevchenko
2023-11-13 12:53 ` Mika Westerberg [this message]
2023-10-30 14:10 ` [PATCH v1 3/3] pinctrl: intel: Add ACPI ID to the generic " Andy Shevchenko
2023-11-01 6:32 ` Mika Westerberg
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=20231113125334.GQ17433@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raag.jadav@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.