From: Mark Brown <broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
To: Tobias Klauser <tklauser-93Khv+1bN0NyDzI6CaY1VQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
Frederic Lambert
<frdrc66-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] spi/spi-altera: Allow to explicitely override bus number via dts
Date: Wed, 1 Feb 2012 13:55:24 +0000 [thread overview]
Message-ID: <20120201135524.GD13723@sirena.org.uk> (raw)
In-Reply-To: <1328025246-23450-1-git-send-email-tklauser-93Khv+1bN0NyDzI6CaY1VQ@public.gmane.org>
On Tue, Jan 31, 2012 at 04:54:06PM +0100, Tobias Klauser wrote:
> From: Frederic Lambert <frdrc66-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>
> Until now we let the code in spi.c assign us the bus number if the platform
> device didn't specify its id. This patch adds the possibility to explicitely
> specify the bus number via device tree.
Why would this be required? Bus numbers are a Linux specific thing...
next prev parent reply other threads:[~2012-02-01 13:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 15:54 [PATCH] spi/spi-altera: Allow to explicitely override bus number via dts Tobias Klauser
[not found] ` <1328025246-23450-1-git-send-email-tklauser-93Khv+1bN0NyDzI6CaY1VQ@public.gmane.org>
2012-02-01 13:55 ` Mark Brown [this message]
[not found] ` <20120201135524.GD13723-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-02-01 14:01 ` Frederic LAMBERT
[not found] ` <CAMVnO+kWX=NYi+YU9H5nRc9UksCJLQUi-_Kj9UASwoiqZj9tGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-01 14:08 ` Mark Brown
[not found] ` <20120201140838.GE13723-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-02-01 14:25 ` Frederic LAMBERT
[not found] ` <CAMVnO+m5DTYeK9mHcciqU-y7HGP-d9FXWkvTV4ZJJLTRqjK7LQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-01 14:35 ` Mark Brown
[not found] ` <20120201143558.GF13723-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-02-01 14:53 ` Frederic LAMBERT
[not found] ` <CAMVnO+n2SW=e7EP-MjLbFeF7ZW6e=FwL=UdOd=cd-XN=C132Qg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-01 15:05 ` Mark Brown
[not found] ` <20120201150517.GG13723-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-02-01 15:29 ` Frederic LAMBERT
[not found] ` <CAMVnO+kvjbxW7EdMe_YF=oSp0bR-RqaP_rPM57tyHzGKhsoNxg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-01 15:42 ` Mark Brown
[not found] ` <20120201154204.GH13723-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-02-01 15:52 ` Frederic LAMBERT
[not found] ` <CAMVnO+nB77XOQHfL1zZLve_=z6vFk_HMF+hj=iMTAuOAYSRExA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-01 17:57 ` Grant Likely
2012-02-01 18:10 ` Mark Brown
2012-02-01 17:59 ` Grant Likely
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=20120201135524.GD13723@sirena.org.uk \
--to=broonie-gfdadszt00ze9xe1eozjha@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=frdrc66-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=tklauser-93Khv+1bN0NyDzI6CaY1VQ@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;
as well as URLs for NNTP newsgroup(s).