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 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support
Date: Thu, 21 May 2015 16:52:25 -0700 [thread overview]
Message-ID: <555E6FB9.6010309@broadcom.com> (raw)
In-Reply-To: <1432194094.21715.113.camel@x220>
On 5/21/2015 12:41 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_IPROC_MDIO
>> + bool "Broadcom iProc MDC/MDIO driver"
>> + depends on ARCH_BCM_IPROC
>> + default ARCH_BCM_IPROC
>> + help
>> + Enable this to support the iProc generic MDC/MDIO interface found
>> + in various iProc based SoCs. The generic MDC/MDIO interface can be
>> + used to communicate with various types of Serdes/PHYs including
>> + Ethernet, PCIe, USB, and etc.
>> +
>> + If unsure, say N.
>
>> --- a/drivers/phy/Makefile
>> +++ b/drivers/phy/Makefile
>
>> +obj-$(CONFIG_PHY_IPROC_MDIO) += phy-iproc-mdio.o
>
>> --- /dev/null
>> +++ b/drivers/phy/phy-iproc-mdio.c
>
>> +#include <linux/module.h>
>
>> +static int __init iproc_mdio_init(void)
>> +{
>> + return platform_driver_register(&iproc_mdio_driver);
>> +}
>> +arch_initcall_sync(iproc_mdio_init);
>> +
>> +MODULE_AUTHOR("Ray Jui <rjui@broadcom.com>");
>> +MODULE_DESCRIPTION("Broadcom iPROC MDC/MDIO driver");
>> +MODULE_LICENSE("GPL v2");
>
> I guess phy-iproc-mdio.o is intended to be built-in only. If that's
> correct the above three MODULE_ macros (and, probably, the include of
> linux/module.h) can safely be dropped.
>
> Thanks,
>
>
> Paul Bolle
>
I think we had previous discussions on this for the pinctrl patches.
People including Linus and me think this is good to be there at least
for information purpose.
I do not want to go over the same argument again. I'll leave this to the
subsystem maintainer. If the subsystem maintainer wants this out, I can
take it out. Otherwise, I'll leave it as it is.
Thanks,
Ray
next prev parent reply other threads:[~2015-05-21 23:52 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 [this message]
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
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=555E6FB9.6010309@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