From: "Måns Rullgård" <mans-2StjZFpD7GcAvxtiuMwx3w@public.gmane.org>
To: Geert Uytterhoeven <geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
Cc: linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel\@vger.kernel.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [TROLL PATCH] spi: add option to create spidev nodes for unclaimed chip selects
Date: Thu, 21 Jan 2016 17:23:01 +0000 [thread overview]
Message-ID: <yw1x4me6onii.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <CAMuHMdXgL-mXPhTw6d=eRwBme3nU=FNp4G+JSNcJrY0UVe8kUg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Geert Uytterhoeven's message of "Thu, 21 Jan 2016 18:11:07 +0100")
Geert Uytterhoeven <geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org> writes:
> On Thu, Jan 21, 2016 at 5:36 PM, Mans Rullgard <mans-2StjZFpD7GcAvxtiuMwx3w@public.gmane.org> wrote:
>> This adds an option to create spidev nodes for any chip selects not
>> bound to a driver via DT/ACPI. It probably doesn't play nicely with
>> modules.
>
> And with pinmux, FWIW ;-)
In my particular case, I can put whatever pinmux I want in the DT and
bring out the SPI signals, but I simply don't know what device will be
connected.
--
Måns Rullgård
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-01-21 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 16:36 [TROLL PATCH] spi: add option to create spidev nodes for unclaimed chip selects Mans Rullgard
[not found] ` <1453394169-11458-1-git-send-email-mans-2StjZFpD7GcAvxtiuMwx3w@public.gmane.org>
2016-01-21 17:11 ` Geert Uytterhoeven
[not found] ` <CAMuHMdXgL-mXPhTw6d=eRwBme3nU=FNp4G+JSNcJrY0UVe8kUg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-21 17:23 ` Måns Rullgård [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=yw1x4me6onii.fsf@unicorn.mansr.com \
--to=mans-2stjzfpd7gcavxtiumwx3w@public.gmane.org \
--cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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