From: Kishon Vijay Abraham I <kishon@ti.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Vivek Gautam <gautamvivek1987@gmail.com>,
Vivek Gautam <gautam.vivek@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
<andrew.kim@intel.com>
Subject: Re: [PATCHv4 2/6] phy: improved lookup method
Date: Wed, 19 Nov 2014 11:42:24 +0530 [thread overview]
Message-ID: <546C34C8.5070907@ti.com> (raw)
In-Reply-To: <20141118153642.GA8881@kuha.fi.intel.com>
Hi,
On Tuesday 18 November 2014 09:06 PM, Heikki Krogerus wrote:
> On Tue, Nov 18, 2014 at 10:49:18AM +0530, Kishon Vijay Abraham I wrote:
>> On Monday 17 November 2014 09:10 PM, Heikki Krogerus wrote:
>>> On Thu, Nov 13, 2014 at 07:03:01PM +0530, Vivek Gautam wrote:
>>>> How about adding the change in attached patch [1] on top of this patch.
>>>> Just introduced the phy pointer in "phy_lookup" structure, and
>>>> modified phy_find() accordingly.
>>>
>>> I would be fine if we used the phy pointer to match, but if we have
>>> the pointer to the phy in the lookup, then I would say we need to
>>> remove the phy_name member.
>>>
>>> Otherwise we would have to support two ways of finding the lookups
>>> (one for the "static" lookups where we match to the phy_name and other
>>> where we match to the pointer). That means we will also not be able to
>>> create "static" lookups, but those would be only needed if we wanted to
>>> create them in board files. I don't think there will ever be need to
>>> create the lookups in board files, so I'm more then happy to remove
>>> the static way of creating the lookups.
>>
>> Just using the phy pointer sounds good. But interested to know where the phy
>> pointer will be added to the lookup table.
>
> I'm making assumption that there will not be any (new) platforms where
> the bindings are not provided in HW descriptions like dt or ACPI
> tables. That leaves the lookups to be useful only in cases where a
> driver has to, for whatever reason, pass it's phy's forward, like
> dwc3 host. ULPI will be an other case where we will need to use them.
right.
>
> Now the only user for the lookups is twl4030-usb, but since it's
> actually just ULPI type PHY in cases where we have platform data to
> deal with (please correct me if I'm wrong), I think we could later
You mean passing the consumer info using platform data?
> remove it's need for platform data completely with the help of the
> ULPI bus I'm working with.
Sure.
I'll be closing my phy tree by friday, so would be great if you can send your
patches before that with "Tested-by" from Vivek.
Thanks
Kishon
next prev parent reply other threads:[~2014-11-19 6:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 14:39 [PATCHv4 0/6] phy: simplified phy lookup Heikki Krogerus
2014-10-17 14:39 ` [PATCHv4 1/6] phy: safer to_phy() macro Heikki Krogerus
2014-10-17 15:31 ` Felipe Balbi
2014-10-17 14:39 ` [PATCHv4 2/6] phy: improved lookup method Heikki Krogerus
2014-10-31 12:33 ` Vivek Gautam
2014-11-11 6:42 ` Kishon Vijay Abraham I
2014-11-11 8:37 ` Vivek Gautam
2014-11-11 8:50 ` Kishon Vijay Abraham I
2014-11-11 8:53 ` Vivek Gautam
2014-11-13 13:33 ` Vivek Gautam
2014-11-14 14:15 ` Heikki Krogerus
2014-11-17 12:08 ` Vivek Gautam
2014-11-17 15:40 ` Heikki Krogerus
2014-11-18 5:19 ` Kishon Vijay Abraham I
2014-11-18 15:36 ` Heikki Krogerus
2014-11-19 5:33 ` Kishon Vijay Abraham I
2014-11-19 6:12 ` Kishon Vijay Abraham I [this message]
2014-10-17 14:39 ` [PATCHv4 3/6] arm: omap3: twl: use the new lookup method with usb phy Heikki Krogerus
2014-11-03 21:26 ` Tony Lindgren
2014-10-17 14:39 ` [PATCHv4 4/6] phy: remove the old lookup method Heikki Krogerus
2014-10-17 14:39 ` [PATCHv4 5/6] base: platform: name the device already during allocation Heikki Krogerus
2014-10-17 14:39 ` [PATCHv4 6/6] usb: dwc3: host: convey the PHYs to xhci Heikki Krogerus
2014-11-06 7:25 ` Kishon Vijay Abraham I
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=546C34C8.5070907@ti.com \
--to=kishon@ti.com \
--cc=andrew.kim@intel.com \
--cc=gautam.vivek@samsung.com \
--cc=gautamvivek1987@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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
Powered by JetHome