From: Moritz Fischer <mdf@kernel.org>
To: Anatolij Gustschin <agust@denx.de>
Cc: linux-fpga@vger.kernel.org, atull@kernel.org, mdf@kernel.org
Subject: Re: [PATCH] fpga: xilinx-spi: Use unique FPGA manager names
Date: Mon, 29 Oct 2018 09:48:57 -0700 [thread overview]
Message-ID: <20181029164857.GA2453@archbook> (raw)
In-Reply-To: <20181029144222.26927-1-agust@denx.de>
Hi Anatolij,
On Mon, Oct 29, 2018 at 03:42:22PM +0100, Anatolij Gustschin wrote:
> Currently we have the same FPGA manager name for all registered
> xlnx-slave-spi managers, so it is not clear which fpga manager
> index belongs to which configuration interface (SPI slave device).
> Use unique fpga manager name for each registered manager. With
> this change we have names with SPI slave device name encoded in
> the manager name string, e.g. like "xlnx-slave-spi spi1.2".
Sounds like a udev problem that can be solved by looking at the
parent device?
Cheers,
Moritz
next prev parent reply other threads:[~2018-10-29 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 14:42 [PATCH] fpga: xilinx-spi: Use unique FPGA manager names Anatolij Gustschin
2018-10-29 16:48 ` Moritz Fischer [this message]
2018-10-30 11:19 ` Anatolij Gustschin
2018-11-01 18:21 ` Alan Tull
2018-11-01 18:33 ` Anatolij Gustschin
2018-11-01 18:46 ` Alan Tull
2018-11-01 19:23 ` Anatolij Gustschin
2018-11-01 19:44 ` Moritz Fischer
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=20181029164857.GA2453@archbook \
--to=mdf@kernel.org \
--cc=agust@denx.de \
--cc=atull@kernel.org \
--cc=linux-fpga@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 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).