From: Andy Shevchenko <andy@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Lee Jones <lee@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: intel_soc_pmic_crc: Add support for non ACPI instantiated i2c_client
Date: Mon, 28 Oct 2024 11:19:15 +0200 [thread overview]
Message-ID: <Zx9XE6_xzEYKtnel@smile.fi.intel.com> (raw)
In-Reply-To: <56c4e49a-b729-4332-b7d2-d8d51edcbd2e@redhat.com>
On Sat, Oct 26, 2024 at 01:42:36PM +0200, Hans de Goede wrote:
> On 25-Oct-24 3:27 PM, Andy Shevchenko wrote:
> > On Fri, Oct 25, 2024 at 10:37:12AM +0200, Hans de Goede wrote:
...
> >> +static const struct i2c_device_id crystal_cove_i2c_match[] = {
> >> + { "intel-crystal-cove" },
> >
> > Why this can't be "crystal_cove_i2c"?
>
> It can be any string as long as it is unique. Typically this will
> be vendor-model-name though and having i2c in there is a bit weird
> since this is used for the modalias, which gets prefixed with
> "i2c:" already.
>
> Therefor I would prefer to keep this as is. But if you have
> a strong preference I can change this for v2.
>
> Please let me know how you want to proceed with this patch.
I think that I would like to have the same name there and in the .driver below.
If you think we need align these across PMIC MFD drivers, I'm fine with that as
well.
> >> + { }
> >> +};
...
> >> .driver = {
> >> .name = "crystal_cove_i2c",
At least two options based on the existing code:
"Crystal Cove PMIC" or "intel_soc_pmic_crc". I'm also
not against other one as long as it's done for all
PMIC MFD drivers.
> >> .pm = pm_sleep_ptr(&crystal_cove_pm_ops),
> >> .acpi_match_table = crystal_cove_acpi_match,
> >> },
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-10-28 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 8:37 [PATCH] mfd: intel_soc_pmic_crc: Add support for non ACPI instantiated i2c_client Hans de Goede
2024-10-25 13:27 ` Andy Shevchenko
2024-10-26 11:42 ` Hans de Goede
2024-10-28 9:19 ` Andy Shevchenko [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=Zx9XE6_xzEYKtnel@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=hdegoede@redhat.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.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