All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Benjamin Beckmeyer <beb@eks-engel.de>
Cc: netdev@vger.kernel.org
Subject: Re: i.mx6ul with DSA in multi chip addressing mode - no MDIO access
Date: Mon, 8 Jul 2019 16:57:33 +0200	[thread overview]
Message-ID: <20190708145733.GA9027@lunn.ch> (raw)
In-Reply-To: <5e35a41c-be0e-efd4-cb69-cf5c860b872e@eks-engel.de>

> Hi Andrew,
> I got it working a little bit better. When I'm fast enough I can read
> the registers I want but it isn't a solution.

Why do you need to read registers?

What you actually might be interested in is the debugfs patches in
Viviens github tree.

> Here is an output of the tracing even with my custom accesses.
> mii -i 2 0 0x9b60; mii -i 2 1
> phyid:2, reg:0x01 -> 0xc801
> 
> Do you know how to delete EEInt bit? It is always one. And now all 
> accesses coming from the kworker thread. Maybe this is your polling 
> function?

EEInt should clear on read for older chips. For 6390, it might be
necessary to read global 2, register 0x13, index 03.
 
> I view the INT pin on an oscilloscope but it never changed. So maybe
> this is the problem. We just soldered a pull-up to that pin but it 
> still never changend. Maybe you have an idea?

The EEInt bit is probably masked. So it will not generate in
interrupt.

> So what I think is, because of the EEInt bit is never set back to one 
> i will poll it as fast as possible.

Is it forever looping in mv88e6xxx_g1_irq_thread_work? Or is it the
polling code, mv88e6xxx_irq_poll() firing every 100ms?

	Andrew

  reply	other threads:[~2019-07-08 14:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03 13:10 i.mx6ul with DSA in multi chip addressing mode - no MDIO access Benjamin Beckmeyer
2019-07-03 15:55 ` Andrew Lunn
2019-07-04  4:33   ` Benjamin Beckmeyer
2019-07-04  8:54   ` Benjamin Beckmeyer
2019-07-04 13:27     ` Andrew Lunn
2019-07-04 14:39       ` Benjamin Beckmeyer
2019-07-04 15:53         ` Andrew Lunn
2019-07-05 12:41           ` Benjamin Beckmeyer
2019-07-05 14:36             ` Andrew Lunn
2019-07-08 13:55               ` Benjamin Beckmeyer
2019-07-08 14:57                 ` Andrew Lunn [this message]
2019-07-09 13:20                   ` Benjamin Beckmeyer
2019-07-09 13:52                     ` Andrew Lunn

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=20190708145733.GA9027@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=beb@eks-engel.de \
    --cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.