From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Hein Tibosch <hein_tibosch@yahoo.es>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
michal.simek@xilinx.com,
Ludovic Desroches <ludovic.desroches@atmel.com>,
s.trumtrar@pengutronix.de, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net/macb: fix ISR clear-on-write behavior only for some SoC
Date: Tue, 14 May 2013 07:52:56 +0200 [thread overview]
Message-ID: <20130514055256.GD22508@game.jcrosoft.org> (raw)
In-Reply-To: <51918C23.7040106@yahoo.es>
On 08:58 Tue 14 May , Hein Tibosch wrote:
> On 5/14/2013 12:05 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On May 14, 2013, at 12:05 AM, Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> >
> >> Commit 749a2b6 (net/macb: clear tx/rx completion flags in ISR)
> >> introduces clear-on-write on ISR register. This behavior is not always
> >> implemented when using Cadence MACB/GEM and is breaking other platforms.
> >> We are using a new Device Tree compatibility string and a capability
> >> property to actually activate this clear-on-write behavior on ISR.
> >>
> >> Reported-by: Hein Tibosch <hein_tibosch@yahoo.es>
> >> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> > can we detect it via the IP?
>
> This was my first proposal, have it based on the value of MACB's
> register 'MID' (offset 0x00fc, lower 16 bits).
> On avr32 it reads: 0x0000010D, on Zynq it reports 0x00000119
>
> So for the moment, CAPS_ISR_CLEAR_ON_WRITE could be set if the revision
> equals to 0x00000119?
so no it will not work
as the gem on sama5 is 00020119
so version 0x119 too
nico
Acked-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Best Regards,
J.
>
> >> ---
> >> Documentation/devicetree/bindings/net/macb.txt | 2 ++
> >> drivers/net/ethernet/cadence/macb.c | 15 +++++++++++++--
> >> drivers/net/ethernet/cadence/macb.h | 5 +++++
> >> 3 files changed, 20 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/Documentation/devicetree/bindings/net/macb.txt b/Documentation/devicetree/bindings/net/macb.txt
> >> index 44afa0e..13ec4f6 100644
> >>
> >> <snip>
> >>
> >> @@ -1474,6 +1476,10 @@ static const struct of_device_id macb_dt_ids[] = {
> >> { .compatible = "cdns,macb" },
> >> { .compatible = "cdns,pc302-gem" },
> >> { .compatible = "cdns,gem" },
> >> + {
> >> + .compatible = "cdns,zynq-7000-gem",
> >> + .data = (void *)MACB_CAPS_ISR_CLEAR_ON_WRITE,
> >> + },
> >> { /* sentinel */ }
> >> };
> >> MODULE_DEVICE_TABLE(of, macb_dt_ids);
> >> @@ -1484,6 +1490,7 @@ static int __init macb_probe(struct platform_device *pdev)
> >> struct macb_platform_data *pdata;
> >> struct resource *regs;
> >> struct net_device *dev;
> >> + const struct of_device_id *dev_id;
> >> struct macb *bp;
> >> struct phy_device *phydev;
> >> u32 config;
> >> @@ -1558,6 +1565,10 @@ static int __init macb_probe(struct platform_device *pdev)
> >>
> >> dev->base_addr = regs->start;
> >>
> >> + dev_id = of_match_device(macb_dt_ids, &pdev->dev);
> As avr32 doesn't yet define CONFIG_OF:
> macb.c:1601: error: 'macb_dt_ids' undeclared
>
> Hein
next prev parent reply other threads:[~2013-05-14 6:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 16:05 [PATCH] net/macb: fix ISR clear-on-write behavior only for some SoC Nicolas Ferre
2013-05-13 16:05 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-14 0:58 ` Hein Tibosch
2013-05-14 5:52 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2013-05-14 7:18 ` Hein Tibosch
2013-05-14 7:22 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-14 7:31 ` Hein Tibosch
2013-05-14 7:49 ` Michal Simek
2013-05-14 8:32 ` Hein Tibosch
2013-06-04 6:15 ` Michal Simek
2013-06-04 6:49 ` Steffen Trumtrar
2013-06-04 6:54 ` Michal Simek
2013-06-04 7:51 ` Nicolas Ferre
2013-06-04 7:57 ` Michal Simek
2013-05-14 9:16 ` Nicolas Ferre
2013-05-14 11:38 ` Michal Simek
2013-05-14 12:30 ` Nicolas Ferre
2013-05-14 7:01 ` Steffen Trumtrar
2013-05-14 13:00 ` [PATCH v2] " Nicolas Ferre
2013-05-14 13:43 ` Hein Tibosch
2013-05-14 16:24 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-14 20:04 ` David Miller
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=20130514055256.GD22508@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=hein_tibosch@yahoo.es \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=s.trumtrar@pengutronix.de \
/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