From: Tony Lindgren <tony@atomide.com>
To: Nicolae Rosia <nicolae.rosia.oss@gmail.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Nicolae Rosia <Nicolae_Rosia@mentor.com>,
linux-kernel@vger.kernel.org, Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] phy: twl4030-usb: make driver DT only
Date: Tue, 15 Nov 2016 07:45:07 -0800 [thread overview]
Message-ID: <20161115154506.GJ4082@atomide.com> (raw)
In-Reply-To: <CAKP5S=0kf=S01OhSeBZtmPPSGvYMgjEdANjMn3mr7RDEuG1J0g@mail.gmail.com>
* Nicolae Rosia <nicolae.rosia.oss@gmail.com> [161115 05:26]:
> Hi,
>
> On Tue, Nov 15, 2016 at 3:20 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
> > Are you sure about this? I still see a bunch of board files in mach-omap2 using
> > twl4030.
> >
> > Thanks
> > Kishon
>
> You are right, on v4.9 it is still used in arch/arm/mach-omap2/twl-common.c.
> I forgot to mention that I'm targeting v4.10 with this. On Tony's
> for-next [0], there are no users:
> git grep twl4030_usb_data
> drivers/phy/phy-twl4030-usb.c: struct twl4030_usb_data *pdata =
> dev_get_platdata(&pdev->dev);
> drivers/usb/phy/phy-twl6030-usb.c: struct twl4030_usb_data *pdata
> = dev_get_platdata(dev);
> include/linux/i2c/twl.h:struct twl4030_usb_data {
> include/linux/i2c/twl.h: struct twl4030_usb_data *usb;
Yeah might be worht waiting on the omap3 specific driver changes until
v4.11 merge window unless the changes are blocking twl core clean up work.
Regards,
Tony
> [0] https://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git/log/?h=for-next
prev parent reply other threads:[~2016-11-15 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 10:39 [PATCH] phy: twl4030-usb: make driver DT only Nicolae Rosia
2016-11-15 13:20 ` Kishon Vijay Abraham I
2016-11-15 13:26 ` Nicolae Rosia
2016-11-15 15:45 ` Tony Lindgren [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=20161115154506.GJ4082@atomide.com \
--to=tony@atomide.com \
--cc=Nicolae_Rosia@mentor.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nicolae.rosia.oss@gmail.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