From: Ray Jui <rjui@broadcom.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
<linux-kernel@vger.kernel.org>,
"JD (Jiandong) Zheng" <jdzheng@broadcom.com>,
Arun Parameswaran <arunp@broadcom.com>,
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH 4/5] phy: cygnus: pcie: Add Cygnus PCIe PHY support
Date: Thu, 21 May 2015 16:53:32 -0700 [thread overview]
Message-ID: <555E6FFC.2080309@broadcom.com> (raw)
In-Reply-To: <1432194775.21715.118.camel@x220>
On 5/21/2015 12:52 AM, Paul Bolle wrote:
> On Tue, 2015-05-19 at 18:23 -0700, Ray Jui wrote:
>> --- a/drivers/phy/Kconfig
>> +++ b/drivers/phy/Kconfig
>
>> +config PHY_CYGNUS_PCIE
>> + bool "Broadcom Cygnus PCIe PHY driver"
>> + depends on ARCH_BCM_CYGNUS
>> + select GENERIC_PHY
>> + select PHY_IPROC_MDIO
>> + default ARCH_BCM_CYGNUS
>> + help
>> + Enable this to support the Broadcom Cygnus PCIe PHY.
>> +
>> + The host communicates with the PHY through the iProc MDC/MDIO
>> + interface.
>> +
>> + If unsure, say N.
>> +
>> +
>
>> --- a/drivers/phy/Makefile
>> +++ b/drivers/phy/Makefile
>
>> +obj-$(CONFIG_PHY_CYGNUS_PCIE) += phy-cygnus-pcie.o
>
>> --- /dev/null
>> +++ b/drivers/phy/phy-cygnus-pcie.c
>
>> +#include <linux/module.h>
>
>> +static const struct of_device_id cygnus_pcie_phy_match_table[] = {
>> + { .compatible = "brcm,cygnus-pcie-phy" },
>> + { }
>> +};
>> +MODULE_DEVICE_TABLE(of, cygnus_pcie_phy_match_table);
>> +
>> +static struct platform_driver cygnus_pcie_phy_driver = {
>> + .driver = {
>> + .name = "cygnus-pcie-phy",
>> + .of_match_table = cygnus_pcie_phy_match_table,
>> + },
>> + .probe = cygnus_pcie_phy_probe,
>> +};
>> +module_platform_driver(cygnus_pcie_phy_driver);
>> +
>> +MODULE_AUTHOR("Ray Jui <rjui@broadcom.com>");
>> +MODULE_DESCRIPTION("Broadcom Cygnus PCIe PHY driver");
>> +MODULE_LICENSE("GPL v2");
>
> And here I guess you intend this to be buildable as a module. If that's
> the intention I think PHY_CYGNUS_PCIE needs to be tristate.
Yes, I'll change the PCIe PHY driver to tristate in the Kconfig. Thanks!
>
> Thanks,
>
>
> Paul Bolle
>
next prev parent reply other threads:[~2015-05-21 23:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 1:23 [PATCH 0/5] Add Cygnus PCIe PHY support Ray Jui
2015-05-20 1:23 ` [PATCH 1/5] phy: iproc-mdio: Define DT binding Ray Jui
2015-05-21 13:07 ` Kishon Vijay Abraham I
2015-05-21 21:29 ` Ray Jui
2015-05-20 1:23 ` [PATCH 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support Ray Jui
2015-05-21 7:41 ` Paul Bolle
2015-05-21 23:52 ` Ray Jui
2015-05-22 8:39 ` Paul Bolle
2015-05-21 13:12 ` Kishon Vijay Abraham I
2015-05-21 21:35 ` Ray Jui
2015-05-21 21:51 ` Florian Fainelli
2015-05-21 22:02 ` Ray Jui
2015-05-20 1:23 ` [PATCH 3/5] phy: cygnus: pcie: Define DT binding Ray Jui
2015-05-21 13:14 ` Kishon Vijay Abraham I
2015-05-21 21:59 ` Ray Jui
2015-05-21 23:36 ` Ray Jui
2015-05-20 1:23 ` [PATCH 4/5] phy: cygnus: pcie: Add Cygnus PCIe PHY support Ray Jui
2015-05-21 7:52 ` Paul Bolle
2015-05-21 23:53 ` Ray Jui [this message]
2015-05-22 8:47 ` Paul Bolle
2015-05-21 13:19 ` Kishon Vijay Abraham I
2015-05-20 1:23 ` [PATCH 5/5] ARM: dts: enable PCIe PHY support for Cygnus Ray Jui
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=555E6FFC.2080309@broadcom.com \
--to=rjui@broadcom.com \
--cc=arunp@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=jdzheng@broadcom.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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