From: kishon@ti•com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v1 1/3] phy: phy-core: allow specifying supply at port level
Date: Thu, 26 Mar 2015 03:41:32 +0530 [thread overview]
Message-ID: <55133294.4040705@ti.com> (raw)
In-Reply-To: <1426886727-537-2-git-send-email-arun.ramamurthy@broadcom.com>
Hi,
On Saturday 21 March 2015 02:55 AM, Arun Ramamurthy wrote:
> Multi-port phy's may have per-port power supplies. Let's change phy core
> to first attempt to look up the supply at the port level, and then, if
> not found, check parent device.
Why not just have every port provide the power supply if it needs?
I don't think checking for parent device should be present in the phy-core at
all.
Thanks
Kishon
next prev parent reply other threads:[~2015-03-25 22:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 21:25 [PATCH v1 0/3] USB PHY driver for Broadcom's Cygnus chipse Arun Ramamurthy
2015-03-20 21:25 ` [PATCH v1 1/3] phy: phy-core: allow specifying supply at port level Arun Ramamurthy
2015-03-20 21:31 ` Dmitry Torokhov
2015-03-25 22:11 ` Kishon Vijay Abraham I [this message]
2015-03-25 22:17 ` Dmitry Torokhov
2015-03-25 22:39 ` Kishon Vijay Abraham I
2015-03-25 22:49 ` Dmitry Torokhov
2015-03-25 23:44 ` Kishon Vijay Abraham I
2015-03-25 23:48 ` Dmitry Torokhov
2015-03-20 21:25 ` [PATCH v1 2/3] Phy: DT binding documentation for Broadcom Cygnus USB PHY driver Arun Ramamurthy
2015-03-25 22:16 ` Kishon Vijay Abraham I
2015-03-26 0:04 ` Arun Ramamurthy
2015-03-26 23:02 ` Dmitry Torokhov
2015-03-20 21:25 ` [PATCH v1 3/3] phy: cygnus-usbphy: Add Broadcom Cygnus USB phy driver Arun Ramamurthy
2015-03-25 22:28 ` Kishon Vijay Abraham I
2015-03-25 22:42 ` Dmitry Torokhov
2015-03-26 0:01 ` Kishon Vijay Abraham I
2015-03-26 0:06 ` Arun Ramamurthy
2015-03-31 6:16 ` 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=55133294.4040705@ti.com \
--to=kishon@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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