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: Tue, 9 Jul 2019 15:52:58 +0200 [thread overview]
Message-ID: <20190709135258.GC1965@lunn.ch> (raw)
In-Reply-To: <0d595637-0081-662d-2812-0a174ee1a901@eks-engel.de>
> Hi Andrew,
> good news first, it seems to be running ;-).
Great.
>
> The interrupt GPIO pin was not correctly configured in the device tree.
>
> For now we have around 68 accesses per second, I think this is okay
> because we even have indirect access, so the bus must be more busy.
That sounds reasonable.
> Why we need access to the bus is because we have some software which was
> using the DSDT driver and now we want to switch to the UMSD driver.
> But we hope that we can forget about all the UMSD driver stuff and the
> DSDT driver stuff as well and just use the DSA part from the kernel.
> To be honest, so far I don't know what functions we need from the driver
> which aren't supported by the DSA.
You should take a close look at what you actually need. Using
DSDT/UMSD at the same time as mainline DSA does not sound like a good
idea. One can stomp over the other.
If you do decide to do this, you are going to need to add a new API to
allow DSDT/UMSD to get reliable access to the registers. You need to
take the chip->reg_lock to give you exclusive access to the
indirection registers. That also won't be accepted into mainline. We
don't want user space drivers...
Andrew
prev parent reply other threads:[~2019-07-09 13:53 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
2019-07-09 13:20 ` Benjamin Beckmeyer
2019-07-09 13:52 ` Andrew Lunn [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=20190709135258.GC1965@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.