From: Tony Lindgren <tony@atomide.com>
To: Keerthy <j-keerthy@ti.com>
Cc: Lee Jones <lee.jones@linaro.org>,
milo.kim@ti.com, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] mfd: Remove redundant i2c_device_id
Date: Tue, 6 Jun 2017 03:44:38 -0700 [thread overview]
Message-ID: <20170606104437.GY3730@atomide.com> (raw)
In-Reply-To: <918f5112-b200-b5ae-c4d2-c75e5e227e9a@ti.com>
* Keerthy <j-keerthy@ti.com> [170606 00:52]:
> On Tuesday 06 June 2017 01:00 PM, Keerthy wrote:
> > On Tuesday 06 June 2017 12:47 PM, Lee Jones wrote:
> >>>> Are all of these drivers DT only?
> >>>
> >>> At least i did not find any platform code calling on to these drivers.
> >>> No dependency on OF as such. Hence sent these 9.
> >>
> >> I can't accept these changes on any drivers which does not depend on
> >> OF as a hard requirement.
> >
> > Okay. So that is a per-requisite. At least palmas, tps65218, lp873x,
> > tps65217 imho can have the OF dependency. I will post patches for that
> > and then will resurrect this series.
> >
> > Thanks for your feedback.
>
> Tony,
>
> I do not see any platform specific code for tps65218, tps65217 and
> palmas. I believe they are all completely Device Tree based. Can i make
> them depend on OF? It helps me clear up some unused data from their mfd
> drivers.
Yes all of arch/arm/mach-omap2 is device tree only nowadays.
There may be other SoCs or architectures using these too,
but grepping for platform_data should reveal that.
Regards,
Tony
next prev parent reply other threads:[~2017-06-06 10:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 9:18 [PATCH 0/9] mfd: Remove redundant i2c_device_id Keerthy
2017-06-04 9:18 ` [PATCH 1/9] mfd: tps65217: " Keerthy
2017-06-04 9:18 ` [PATCH 2/9] mfd: tps65218: " Keerthy
2017-06-04 9:18 ` [PATCH 3/9] mfd: palmas: " Keerthy
2017-06-04 9:18 ` [PATCH 4/9] mfd: lp873x: " Keerthy
2017-06-04 9:18 ` [PATCH 5/9] mfd: lp8788: " Keerthy
2017-06-04 9:18 ` [PATCH 6/9] mfd: lp3943: " Keerthy
2017-06-04 9:18 ` [PATCH 7/9] mfd: tps65086: " Keerthy
2017-06-04 9:18 ` [PATCH 8/9] mfd: tps65090: " Keerthy
2017-06-04 9:18 ` [PATCH 9/9] mfd: tps6586x: " Keerthy
2017-06-05 10:37 ` [PATCH 0/9] mfd: " Lee Jones
2017-06-05 14:37 ` Keerthy
2017-06-06 7:17 ` Lee Jones
2017-06-06 7:30 ` Keerthy
2017-06-06 7:48 ` Keerthy
2017-06-06 10:44 ` Tony Lindgren [this message]
2017-06-06 11:01 ` Keerthy
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=20170606104437.GY3730@atomide.com \
--to=tony@atomide.com \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=milo.kim@ti.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