From: Hans de Goede <hdegoede@redhat.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Lee Jones <lee.jones@linaro.org>,
LKML <linux-kernel@vger.kernel.org>, Bin Gao <bin.gao@intel.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v6] mfd: Add Cherry Trail Whiskey Cove PMIC driver
Date: Sun, 21 May 2017 11:51:43 +0200 [thread overview]
Message-ID: <b1e00631-58a5-ed7b-2ed8-7030deaf66a3@redhat.com> (raw)
In-Reply-To: <CAP=VYLqwp1RfpMo6Wavsq-bRQZMyhG+_M3jR4U7a+y0fLdXynQ@mail.gmail.com>
Hi,
On 20-05-17 21:26, Paul Gortmaker wrote:
> On Sat, May 20, 2017 at 3:21 PM, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
>> On Mon, May 15, 2017 at 2:20 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>>> Hi,
>>>
>>> This is actually v7, with the following changes:
>>>
>>> Changes in v7:
>>> -Add explanation why this is a bool and why it selects i2c-designwaree
>
> Gah -- I missed the explanation mentioned above:
>
> -Change Kconfig option from tristate to boolean and add a select for the
> i2c-bus driver, this is necessary because the chtwc PMIC provides an ACPI
> OPRegion handler, which must be available before other drivers using it
> are loaded, which can only be ensured if the mfd, opregion and i2c-bus
> drivers are built in
>
> Given that, can we get rid of the modular macros in the code now as well?
Yes we can, to be clear you are talking about dropping:
MODULE_DEVICE_TABLE(i2c, cht_wc_i2c_id);
MODULE_DEVICE_TABLE(acpi, cht_wc_acpi_ids);
MODULE_LICENSE("GPL v2");
MODULE_AUTHOR("Hans de Goede <hdegoede@redhat.com>");
And replacing:
module_i2c_driver(cht_wc_driver);
with:
builtin_i2c_driver(cht_wc_driver);
Right ?
Anything I'm missing ?
If not I will post a new version with these removed / replaced.
Regards,
Hans
next prev parent reply other threads:[~2017-05-21 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 18:17 Hans de Goede
2017-05-15 18:20 ` Hans de Goede
2017-05-20 19:21 ` Paul Gortmaker
2017-05-20 19:26 ` Paul Gortmaker
2017-05-21 9:51 ` Hans de Goede [this message]
2017-05-21 19:05 ` Paul Gortmaker
-- strict thread matches above, loose matches on Subject: below --
2017-04-19 12:56 [PATCH resend v6 0/1] " Hans de Goede
2017-04-19 12:56 ` [PATCH v6] " Hans de Goede
2017-04-24 11:55 ` Lee Jones
2017-03-27 13:27 Hans de Goede
2017-03-27 18:05 ` kbuild test robot
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=b1e00631-58a5-ed7b-2ed8-7030deaf66a3@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bin.gao@intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.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
all inboxes | Powered by JetHome®