From: Kishon Vijay Abraham I <kishon@ti.com>
To: kishon@ti.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, lee.jones@linaro.org,
sergei.shtylyov@cogentembedded.com,
antoine.tenart@free-electrons.com
Cc: kgene.kim@samsung.com, maxime.ripard@free-electrons.com
Subject: [RFC PATCH 0/2] phy: core: better support for multi-phy in phy-core
Date: Fri, 4 Jul 2014 20:37:52 +0530 [thread overview]
Message-ID: <1404486474-28312-1-git-send-email-kishon@ti.com> (raw)
In multi-phy PHY providers, each PHY should be modeled as sub-node of PHY
provider. So it makes sense for the controller node to have the phandle for
the sub-node instead of the PHY-provider node in the 'phy' property.
This patch series added support so that the controller node can have the
phandle to the sub-node. So if the phy specifier does not have any other
fields other than the phandle (and the PHY driver uses the default xlate),
phy_get will return the correct PHY.
However if the phy_sepcifier has other fields and the PHY driver provides
its own xlate, the PHY driver can use the *phy->dev.of_node*. (note that
now phy->dev.of_node will have the node pointer of the sub-node).
Kishon Vijay Abraham I (2):
phy: core: Fix of_phy_provider_lookup to return PHY provider for sub
node
phy: core: the node pointer of PHY need not be the same as that of
PHY provider
Documentation/phy.txt | 10 ++++++----
drivers/phy/phy-bcm-kona-usb2.c | 2 +-
drivers/phy/phy-core.c | 35 +++++++++++++++++++++++++++--------
drivers/phy/phy-exynos-dp-video.c | 2 +-
drivers/phy/phy-exynos-mipi-video.c | 2 +-
drivers/phy/phy-exynos5-usbdrd.c | 3 ++-
drivers/phy/phy-exynos5250-sata.c | 2 +-
drivers/phy/phy-mvebu-sata.c | 2 +-
drivers/phy/phy-omap-usb2.c | 2 +-
drivers/phy/phy-samsung-usb2.c | 3 ++-
drivers/phy/phy-sun4i-usb.c | 2 +-
drivers/phy/phy-ti-pipe3.c | 2 +-
drivers/phy/phy-twl4030-usb.c | 2 +-
drivers/phy/phy-xgene.c | 2 +-
include/linux/phy/phy.h | 15 ++++++++++-----
15 files changed, 57 insertions(+), 29 deletions(-)
--
1.7.9.5
WARNING: multiple messages have this Message-ID (diff)
From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/2] phy: core: better support for multi-phy in phy-core
Date: Fri, 4 Jul 2014 20:37:52 +0530 [thread overview]
Message-ID: <1404486474-28312-1-git-send-email-kishon@ti.com> (raw)
In multi-phy PHY providers, each PHY should be modeled as sub-node of PHY
provider. So it makes sense for the controller node to have the phandle for
the sub-node instead of the PHY-provider node in the 'phy' property.
This patch series added support so that the controller node can have the
phandle to the sub-node. So if the phy specifier does not have any other
fields other than the phandle (and the PHY driver uses the default xlate),
phy_get will return the correct PHY.
However if the phy_sepcifier has other fields and the PHY driver provides
its own xlate, the PHY driver can use the *phy->dev.of_node*. (note that
now phy->dev.of_node will have the node pointer of the sub-node).
Kishon Vijay Abraham I (2):
phy: core: Fix of_phy_provider_lookup to return PHY provider for sub
node
phy: core: the node pointer of PHY need not be the same as that of
PHY provider
Documentation/phy.txt | 10 ++++++----
drivers/phy/phy-bcm-kona-usb2.c | 2 +-
drivers/phy/phy-core.c | 35 +++++++++++++++++++++++++++--------
drivers/phy/phy-exynos-dp-video.c | 2 +-
drivers/phy/phy-exynos-mipi-video.c | 2 +-
drivers/phy/phy-exynos5-usbdrd.c | 3 ++-
drivers/phy/phy-exynos5250-sata.c | 2 +-
drivers/phy/phy-mvebu-sata.c | 2 +-
drivers/phy/phy-omap-usb2.c | 2 +-
drivers/phy/phy-samsung-usb2.c | 3 ++-
drivers/phy/phy-sun4i-usb.c | 2 +-
drivers/phy/phy-ti-pipe3.c | 2 +-
drivers/phy/phy-twl4030-usb.c | 2 +-
drivers/phy/phy-xgene.c | 2 +-
include/linux/phy/phy.h | 15 ++++++++++-----
15 files changed, 57 insertions(+), 29 deletions(-)
--
1.7.9.5
WARNING: multiple messages have this Message-ID (diff)
From: Kishon Vijay Abraham I <kishon@ti.com>
To: <kishon@ti.com>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>, <lee.jones@linaro.org>,
<sergei.shtylyov@cogentembedded.com>,
<antoine.tenart@free-electrons.com>
Cc: <kgene.kim@samsung.com>, <maxime.ripard@free-electrons.com>
Subject: [RFC PATCH 0/2] phy: core: better support for multi-phy in phy-core
Date: Fri, 4 Jul 2014 20:37:52 +0530 [thread overview]
Message-ID: <1404486474-28312-1-git-send-email-kishon@ti.com> (raw)
In multi-phy PHY providers, each PHY should be modeled as sub-node of PHY
provider. So it makes sense for the controller node to have the phandle for
the sub-node instead of the PHY-provider node in the 'phy' property.
This patch series added support so that the controller node can have the
phandle to the sub-node. So if the phy specifier does not have any other
fields other than the phandle (and the PHY driver uses the default xlate),
phy_get will return the correct PHY.
However if the phy_sepcifier has other fields and the PHY driver provides
its own xlate, the PHY driver can use the *phy->dev.of_node*. (note that
now phy->dev.of_node will have the node pointer of the sub-node).
Kishon Vijay Abraham I (2):
phy: core: Fix of_phy_provider_lookup to return PHY provider for sub
node
phy: core: the node pointer of PHY need not be the same as that of
PHY provider
Documentation/phy.txt | 10 ++++++----
drivers/phy/phy-bcm-kona-usb2.c | 2 +-
drivers/phy/phy-core.c | 35 +++++++++++++++++++++++++++--------
drivers/phy/phy-exynos-dp-video.c | 2 +-
drivers/phy/phy-exynos-mipi-video.c | 2 +-
drivers/phy/phy-exynos5-usbdrd.c | 3 ++-
drivers/phy/phy-exynos5250-sata.c | 2 +-
drivers/phy/phy-mvebu-sata.c | 2 +-
drivers/phy/phy-omap-usb2.c | 2 +-
drivers/phy/phy-samsung-usb2.c | 3 ++-
drivers/phy/phy-sun4i-usb.c | 2 +-
drivers/phy/phy-ti-pipe3.c | 2 +-
drivers/phy/phy-twl4030-usb.c | 2 +-
drivers/phy/phy-xgene.c | 2 +-
include/linux/phy/phy.h | 15 ++++++++++-----
15 files changed, 57 insertions(+), 29 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-07-04 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 15:07 Kishon Vijay Abraham I [this message]
2014-07-04 15:07 ` [RFC PATCH 0/2] phy: core: better support for multi-phy in phy-core Kishon Vijay Abraham I
2014-07-04 15:07 ` Kishon Vijay Abraham I
2014-07-04 15:07 ` [RFC PATCH 1/2] phy: core: Fix of_phy_provider_lookup to return PHY provider for sub node Kishon Vijay Abraham I
2014-07-04 15:07 ` Kishon Vijay Abraham I
2014-07-04 15:07 ` Kishon Vijay Abraham I
2014-07-07 13:43 ` Lee Jones
2014-07-07 13:43 ` Lee Jones
2014-07-04 15:07 ` [RFC PATCH 2/2] phy: core: the node pointer of PHY need not be the same as that of PHY provider Kishon Vijay Abraham I
2014-07-04 15:07 ` Kishon Vijay Abraham I
2014-07-04 15:07 ` Kishon Vijay Abraham I
2014-07-07 13:12 ` Lee Jones
2014-07-07 13:12 ` Lee Jones
2014-07-07 14:09 ` Kishon Vijay Abraham I
2014-07-07 14:09 ` Kishon Vijay Abraham I
2014-07-07 14:09 ` Kishon Vijay Abraham I
2014-07-07 14:59 ` Lee Jones
2014-07-07 14:59 ` Lee Jones
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=1404486474-28312-1-git-send-email-kishon@ti.com \
--to=kishon@ti.com \
--cc=antoine.tenart@free-electrons.com \
--cc=kgene.kim@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=sergei.shtylyov@cogentembedded.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 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.