From: Richard Cochran <richardcochran@gmail.com>
To: Harini Katakam <harinikatakamlinux@gmail.com>
Cc: Andrei Pistirica <andrei.pistirica@microchip.com>,
netdev@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
davem@davemloft.net, Nicolas Ferre <nicolas.ferre@atmel.com>,
Harini Katakam <harini.katakam@xilinx.com>,
Punnaiah Choudary Kalluri <punnaia@xilinx.com>,
"michals@xilinx.com" <michals@xilinx.com>,
Anirudha Sarangi <anirudh@xilinx.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
alexandre.belloni@free-electrons.com, tbultel@pixelsurmer.com
Subject: Re: [RFC PATCH 1/2] macb: Add 1588 support in Cadence GEM.
Date: Thu, 8 Sep 2016 09:44:44 +0200 [thread overview]
Message-ID: <20160908074444.GA3341@netboy> (raw)
In-Reply-To: <CAFcVECJxJgJUeO4=yudwTj5NkxDob5tCZaom9YTqWWmtt7ajFw@mail.gmail.com>
On Thu, Sep 08, 2016 at 10:22:43AM +0530, Harini Katakam wrote:
> I cant be sure of the version of Cadence GEM used in SAMA5D2
> but these registers (sub ns increments alteast) only exist in
> the IP version used in Zynq Ultrascale+ MPSoC.
Then you need to find a way to make sure the driver only binds to the
correct silicon.
Thanks,
Richard
next prev parent reply other threads:[~2016-09-08 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 12:53 [RFC PATCH 1/2] macb: Add 1588 support in Cadence GEM Andrei Pistirica
2016-09-02 12:53 ` [RFC PATCH 2/2] macb: Enable 1588 support in SAMA5D2 platform Andrei Pistirica
2016-09-06 7:43 ` Harini Katakam
2016-09-06 16:37 ` Richard Cochran
2016-09-09 14:08 ` Andrei Pistirica
2016-09-06 7:36 ` [RFC PATCH 1/2] macb: Add 1588 support in Cadence GEM Harini Katakam
2016-09-06 15:48 ` Richard Cochran
2016-09-08 4:52 ` Harini Katakam
2016-09-08 7:44 ` Richard Cochran [this message]
2016-09-08 19:06 ` Richard Cochran
2016-09-09 13:51 ` Andrei Pistirica
-- strict thread matches above, loose matches on Subject: below --
2016-11-18 12:05 Rafal Ozieblo
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=20160908074444.GA3341@netboy \
--to=richardcochran@gmail.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=andrei.pistirica@microchip.com \
--cc=anirudh@xilinx.com \
--cc=boris.brezillon@free-electrons.com \
--cc=davem@davemloft.net \
--cc=harini.katakam@xilinx.com \
--cc=harinikatakamlinux@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=punnaia@xilinx.com \
--cc=tbultel@pixelsurmer.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 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).