From: "Stefan Sørensen" <stefan.sorensen@spectralink.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: grant.likely@linaro.org, robh+dt@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dp83640: Get gpio and master/slave configuration from DT
Date: Tue, 11 Feb 2014 09:01:25 +0100 [thread overview]
Message-ID: <1392105685.2133.2.camel@e37108.spectralink.com> (raw)
In-Reply-To: <20140210184604.GA4296@netboy>
On Mon, 2014-02-10 at 19:46 +0100, Richard Cochran wrote:
> On Mon, Feb 10, 2014 at 02:00:40PM +0100, Stefan Sørensen wrote:
> > This patch removes the module parameters gpio_tab and chosen_phy in favour of
> > retrieving the configuration from DT through the properties
>
> Can we please keep the module parameters? I have two platforms with
> phyters neither of which will ever support DT, namely ixp and m68k,
> and I want to run recent kernels on them.
I will keep the module parameters as fallback. Will it be OK to split
the gpio_tab parameter into separate calibrate-pin, perout-pins and
extts-pins parameters?
> > The configuration is now stored for each master clock device, allowing different
> > gpio setups for each master.
>
> What do you mean by "each master"? Do you mean each individual PHY device
> or each group of PHYs on the same MDIO bus?
I mean each group of PHYs. I will reword that.
Stefan
prev parent reply other threads:[~2014-02-11 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 13:00 [PATCH] dp83640: Get gpio and master/slave configuration from DT Stefan Sørensen
[not found] ` <1392037240-30913-1-git-send-email-stefan.sorensen-usnHOLptxrsHrNJx0XZkJA@public.gmane.org>
2014-02-10 13:42 ` Mark Rutland
2014-02-10 15:25 ` Stefan Sørensen
2014-02-10 15:39 ` Mark Rutland
2014-02-10 18:46 ` Richard Cochran
2014-02-11 8:01 ` Stefan Sørensen [this message]
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=1392105685.2133.2.camel@e37108.spectralink.com \
--to=stefan.sorensen@spectralink.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).