From: Wolfgang Grandegger <wg@grandegger.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] [RFC] ptp: IEEE 1588 clock support
Date: Thu, 29 Apr 2010 13:31:42 +0200 [thread overview]
Message-ID: <4BD96E1E.8070200@grandegger.com> (raw)
In-Reply-To: <20100429094208.GA6889@riccoc20.at.omicron.at>
Richard Cochran wrote:
> On Thu, Apr 29, 2010 at 11:24:24AM +0200, Wolfgang Grandegger wrote:
>> I used these interrupt number fixes as well but it was not necessary for
>> the actual net-next-2.6 tree. Need to check why? I remember some version
>> dependent re-mapping code.
>
> I argued on the ppc list with Scott Wood about adding dts files, one
> for each of mpc8313 rev A, B, and C, but he advocated fixing this
> problem in uboot instead. Is the fix in uboot, or in the kernel?
It seems to be fixed in u-boot:
commit 7120c888101952b7e61b9e54bb42370904aa0e68
Author: Kim Phillips <kim.phillips@freescale.com>
Date: Mon Oct 12 11:06:19 2009 -0500
mpc83xx: mpc8313 - handle erratum IPIC1 (TSEC IRQ number swappage)
mpc8313e erratum IPIC1 swapped TSEC interrupt ID numbers on rev. 1
h/w (see AN3545). The base device tree in use has rev. 1 ID numbers,
so if on Rev. 2 (and higher) h/w, we fix them up here.
Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
Reviewed-by: Roland Lezuo <roland.lezuo@chello.at>
>> That's missing to get the PPS signal output. But it should probably go
>> to gianfar_ptp.c.
>
> Well, this fix is specific to the mpc8313, but the gianfar_ptp driver
> is for all eTECs. For example, I have the ptp code running on the
> p2020rdb and p2020ds, too.
>
> I don't think board fixups really belong in the PTP clock driver.
>
> Just my 2 cents,
I see, fine for me if setting those bits does not harm.
Wolfgang.
next prev parent reply other threads:[~2010-04-30 17:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 9:13 [PATCH 0/3] [RFC] ptp: IEEE 1588 clock support Richard Cochran
2010-04-27 10:20 ` Richard Cochran
2010-04-27 13:35 ` Wolfgang Grandegger
2010-04-27 16:20 ` Wolfgang Grandegger
2010-04-28 5:47 ` Richard Cochran
2010-04-28 13:50 ` Wolfgang Grandegger
2010-04-28 14:31 ` Wolfgang Grandegger
2010-04-29 6:54 ` Richard Cochran
[not found] ` <20100429065422.GA5803-7KxsofuKt4IfAd9E5cN8NEzG7cXyKsk/@public.gmane.org>
2010-04-29 8:08 ` Wolfgang Grandegger
2010-04-29 8:38 ` Richard Cochran
2010-04-29 9:24 ` Wolfgang Grandegger
2010-04-29 9:42 ` Richard Cochran
2010-04-29 11:31 ` Wolfgang Grandegger [this message]
2010-04-29 12:02 ` Wolfgang Grandegger
2010-04-29 15:34 ` Richard Cochran
2010-04-29 20:30 ` Wolfgang Grandegger
2010-05-02 11:51 ` Wolfgang Grandegger
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=4BD96E1E.8070200@grandegger.com \
--to=wg@grandegger.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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).