From: Keerthy <j-keerthy@ti.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: "Lee Jones" <lee.jones@linaro.org>,
"Enric Balletbò i Serra" <eballetbo@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"Mark Brown" <broonie@kernel.org>,
"Tony Lindgren" <tony@atomide.com>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>
Subject: Re: [PATCH v3] mfd: tps65217: Introduce dependency on CONFIG_OF
Date: Wed, 30 Aug 2017 14:29:42 +0530 [thread overview]
Message-ID: <2bf0adc1-c44d-d98c-3e89-8a1e6488d588@ti.com> (raw)
In-Reply-To: <CABxcv=kMOJsPEC-x_eRtt-K76sF5-tFnC7ye6FuBh4WC_f2KRQ@mail.gmail.com>
On Wednesday 30 August 2017 01:35 PM, Javier Martinez Canillas wrote:
> Hello Keerthy,
>
> On Wed, Aug 30, 2017 at 7:50 AM, Keerthy <j-keerthy@ti.com> wrote:
>> Currently the driver boots only via device tree hence add a
>> dependency on CONFIG_OF. This leaves with a bunch of unused code
>> so clean that up. This patch also makes use of probe_new function
>> in place of the probe function so as to avoid passing i2c_device_id.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> ---
>>
>> Changes in v3:
>>
>> * Added more details to commit log.
>> * No changes in code. Rebased to latest next branch.
>>
>> Changes in v2:
>>
>> * Cleaned up chip_id and data attached to the match.
>> * Cleaned up i2c_dev_id
>> * dropped the rest of the patches in series for now
>>
>> Boot tested and checked for regulator registrations on am335x-boneblack
>>
>
> Did you check building as a module? Autoload won't work if you remove
> the I2C device ID table.
You are right! I tracked many of your patches that are already in master
branch so assumed it to be working. Seems like not. Thanks for your
feedback.
>
> [snip]
>
>>
>> -static const struct i2c_device_id tps65217_id_table[] = {
>> - {"tps65217", TPS65217},
>> - { /* sentinel */ }
>> -};
>> -MODULE_DEVICE_TABLE(i2c, tps65217_id_table);
>> -
>
> Unfortunately this can't be removed yet. We are getting there but
> still some patches need to land.
>
> Rest of the patch looks good, so if you keep the I2C device ID table
> feel free to add:
>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Thanks!
>
> Best regards,
> Javier
>
prev parent reply other threads:[~2017-08-30 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 5:50 Keerthy
2017-08-30 8:05 ` Javier Martinez Canillas
2017-08-30 8:59 ` Keerthy [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=2bf0adc1-c44d-d98c-3e89-8a1e6488d588@ti.com \
--to=j-keerthy@ti.com \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=eballetbo@gmail.com \
--cc=javier@dowhile0.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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®