From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: George Cherian <george.cherian@ti.com>
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:53:41 +0200 [thread overview]
Message-ID: <51F77F15.7090306@linutronix.de> (raw)
In-Reply-To: <51F74CEC.8040407@ti.com>
On 07/30/2013 07:19 AM, George Cherian wrote:
>> 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.
that omap-control driver looks a little strange. It has a compatible
field saying ti,omap-control-usb and then it requires additionally a
ti,type property which should have been avoided.
But back to the initial problem. I don't really like the idea of
touching in the control-module registers but others do it as well.
So the idea of a control driver doesn't sound that bad.
- an am335x-reset device
- a phy driver with a reference to that reset device.
- non-standard phy calls for power & wak eup on/off.
Let me think about it.
>
> Thoughts???
I think I buy it but give me a bit…
>
Sebastian
next prev parent reply other threads:[~2013-07-30 8:53 UTC|newest]
Thread overview: 45+ 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 ` 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 12:34 ` George Cherian
2013-07-19 13:20 ` Kishon Vijay Abraham I
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 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 12:34 ` George Cherian
2013-07-19 13:32 ` Kishon Vijay Abraham I
2013-07-19 13:32 ` Kishon Vijay Abraham I
2013-07-29 15:17 ` Sebastian Andrzej Siewior
2013-07-30 5:19 ` George Cherian
2013-07-30 5:19 ` George Cherian
2013-07-30 8:53 ` Sebastian Andrzej Siewior [this message]
2013-07-30 14:24 ` George Cherian
2013-07-30 14:24 ` George Cherian
2013-07-30 14:33 ` Felipe Balbi
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 12:34 ` George Cherian
2013-07-19 13:34 ` Kishon Vijay Abraham I
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-20 3:41 ` George Cherian
2013-07-22 5:45 ` George Cherian
2013-07-22 5:45 ` George Cherian
2013-07-20 3:36 ` 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 12:34 ` George Cherian
2013-07-19 13:44 ` Kishon Vijay Abraham I
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-07-19 13:17 ` 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=51F77F15.7090306@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=balbi@ti.com \
--cc=george.cherian@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.