linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Cherian <george.cherian@ti.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-usb@vger.kernel.org, balbi@ti.com,
	linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
	linux-omap@vger.kernel.org, kishon@ti.com
Subject: Re: [PATCH v2 2/4] phy: phy-amxxxx-usb: Add PHY driver for amxxxx platform
Date: Tue, 30 Jul 2013 10:49:40 +0530	[thread overview]
Message-ID: <51F74CEC.8040407@ti.com> (raw)
In-Reply-To: <20130729151754.GB827@linutronix.de>

On 7/29/2013 8:47 PM, Sebastian Andrzej Siewior wrote:
> * George Cherian | 2013-07-19 18:04:35 [+0530]:
>
>> Adds phy driver support for am33xx platform, the host/device
>> peripheral controller shall get this phy object to control the phy
>> operations.
> If you rebase this on-top of the two instances patches I've sent earlier
> then you can bury patch 3 and 4, right?

Yes True. I posted it for completeness.


>
> I don't like very much the way you obtain the phy id:
>> +		of_property_read_u32(np, "id", &phy->id);
> with the .dts changes I made you should able to use
>      of_alias_get_id()
> instead.
>
> Let me look what you have additionaly:
> - usbotg_fck
>    Is this really required? I have the phy as a child of the "main"
>    device which has a hwmod property which is associated with this clock.
>    So pm enable/ disable should also enable this clock if possible,
>    right?
>
> - device wakeup via omap_control_am335x_phy_wkup()
>    Now. that is one thing that the simple phy driver is missing. If you
>    call a magic function for this to happen than I don't have to worry
>    about the missing memory space for this function.
>
> So from what I see now, it is most likely the easiest thing to just add
> that wakeup to the phy driver I posted. Do you agree?

The whole idea of writing a seperate phy driver was to use the generic phy framework
and most of the amxxxx devices have the same phy (eg am335x, am437x).
Now since the register is shared in am335x for phy_wkup (Not in the case of am437x)
how are you planning to  map it. I feel if omap_control_usb can delegate the writes
to phy_wkup, phy_on and phy_off, it makes the life simpler.

Thoughts???

> If so we need to figure out where the memory for the wakeup register is
> comming from. We need also to ensure that both phys can not write at the
> same time. A look would be nice.
>
>> Signed-off-by: George Cherian <george.cherian@ti.com>
> Sebastian


-- 
-George


  reply	other threads:[~2013-07-30  5:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 12:34 [PATCH v2 0/4] Add phy support for AM335X platform using Generic PHy framework George Cherian
2013-07-19 12:34 ` [PATCH v2 1/4] usb: phy: phy-omap-control: Add API to power and wakeup George Cherian
2013-07-19 13:20   ` Kishon Vijay Abraham I
2013-07-29 14:25   ` Sebastian Andrzej Siewior
2013-07-30  4:53     ` George Cherian
2013-07-30  7:35       ` Sebastian Andrzej Siewior
2013-07-19 12:34 ` [PATCH v2 2/4] phy: phy-amxxxx-usb: Add PHY driver for amxxxx platform George Cherian
2013-07-19 13:32   ` Kishon Vijay Abraham I
2013-07-29 15:17   ` Sebastian Andrzej Siewior
2013-07-30  5:19     ` George Cherian [this message]
2013-07-30  8:53       ` Sebastian Andrzej Siewior
2013-07-30 14:24         ` George Cherian
2013-07-30 14:33           ` Felipe Balbi
2013-07-30 14:39             ` Sebastian Andrzej Siewior
2013-07-19 12:34 ` [PATCH v2 3/4] arm: dts: Add USB phy nodes for AM33XX George Cherian
2013-07-19 13:34   ` Kishon Vijay Abraham I
2013-07-19 13:56   ` Sergei Shtylyov
2013-07-19 14:20     ` Sebastian Andrzej Siewior
2013-07-19 18:33       ` Sergei Shtylyov
2013-07-19 18:42         ` Sebastian Andrzej Siewior
2013-07-20  3:41           ` George Cherian
2013-07-22  5:45             ` George Cherian
2013-07-20  3:36         ` George Cherian
2013-07-19 12:34 ` [PATCH v2 4/4] usb: musb: dsps: Remove the phy control from glue and add phy driver APIs George Cherian
2013-07-19 13:44   ` Kishon Vijay Abraham I
2013-07-19 13:17 ` [PATCH v2 0/4] Add phy support for AM335X platform using Generic PHy framework Kishon Vijay Abraham I
2013-08-10 11:59 ` Ezequiel Garcia
2013-08-14 10:36   ` Sebastian Andrzej Siewior

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=51F74CEC.8040407@ti.com \
    --to=george.cherian@ti.com \
    --cc=balbi@ti.com \
    --cc=bigeasy@linutronix.de \
    --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 \
    /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;
as well as URLs for NNTP newsgroup(s).