linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Kundrát" <jan.kundrat@cesnet.cz>
To: Lukasz Majewski <lukma@denx.de>
Cc: Mark Brown <broonie@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>, <linux-spi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spidev: Enable the Liebherr's BK4 board to work with spidev driver
Date: Mon, 01 Oct 2018 16:20:32 +0200	[thread overview]
Message-ID: <47e37a54-6df6-47c0-b38b-ad35e9bd4ce4@cesnet.cz> (raw)
In-Reply-To: <20180927223152.24990-1-lukma@denx.de>

On pátek 28. září 2018 0:31:52 CEST, Lukasz Majewski wrote:
> With this commit the DSPI driver on the BK4 board can be used for SPI
> transmission managed from user space (via /dev/spidev0.0).

Hi Lukasz,
I tried submitting a similar patch for another devicem but got no reaction 
[1]. In the meanwhile, there has been another proposal [2] which moves 
handling of this into userspace via udev. You might want to take a look at 
that mechanism instead (and perhaps send your Tested-by tag). It has worked 
well for me.

[1] https://patchwork.kernel.org/patch/10558889/
[2] 
https://patchwork.kernel.org/project/spi-devel-general/list/?series=21295

Cheers,
Jan

  reply	other threads:[~2018-10-01 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 22:31 [PATCH] spidev: Enable the Liebherr's BK4 board to work with spidev driver Lukasz Majewski
2018-10-01 14:20 ` Jan Kundrát [this message]
2018-10-01 14:22   ` Mark Brown
2018-10-02  8:11     ` Lukasz Majewski
2018-10-02 13:09       ` Mark Brown
2018-10-08 13:57 ` Applied "spidev: Enable the Liebherr's BK4 board to work with spidev driver" to the spi tree Mark Brown

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=47e37a54-6df6-47c0-b38b-ad35e9bd4ce4@cesnet.cz \
    --to=jan.kundrat@cesnet.cz \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=lukma@denx.de \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@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).