From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: spi-devel-general@lists.sourceforge.net,
akpm@linux-foundation.org, dbrownell@users.sourceforge.net,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v3 1/4] of: adapt of_find_i2c_driver() to be usable by SPI also
Date: Fri, 25 Jul 2008 14:52:38 -0400 [thread overview]
Message-ID: <fa686aa40807251152t22848f69l924b0f83f1871165@mail.gmail.com> (raw)
In-Reply-To: <9e4733910807251002w7da115e5r53600f1cf4e3891@mail.gmail.com>
On Fri, Jul 25, 2008 at 1:02 PM, Jon Smirl <jonsmirl@gmail.com> wrote:
> On 7/25/08, Grant Likely <grant.likely@secretlab.ca> wrote:
>> On Fri, Jul 25, 2008 at 11:40 AM, Jon Smirl <jonsmirl@gmail.com> wrote:
>> > On 7/25/08, Grant Likely <grant.likely@secretlab.ca> wrote:
>> >> + * First method is to lookup the compatible value in of_modalias_table.
>> >> + * Second is to look for a "linux,<modalias>" entry in the compatible list
>> >> + * and used that for modalias. Third is to strip off the manufacturer
>> >> + * prefix from the first compatible entry and use the remainder as modalias
>> >
>> > I also think this is a problem. Embedding the name of Linux device
>> > drivers into device firmware makes it almost impossible to rename the
>> > device driver. Again, what is a case where generic part numbers can't
>> > be listed in the alias section of the linux device driver?
>> >
>> > Even eeprom was just fixed to take generic part numbers (at24).
>>
>> Again, I agree, but this change is very much a stop gap measure to get
>> things working in a sane way without having to create bad device tree
>> bindings (device tree bindings are hard to change, code is not). I've
>> been considering posting a patch to remove this clause from the
>> functions, but that needs to be reviewed separately from this change.
>
> Isn't putting "compatible="linux,modalias"" into your device tree a
> really bad idea?
Yes, it is, but I still need to preserve existing behavior in this
patch. That change needs to be reviewed separately. I'll submit
another patch to deal with this.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-07-25 18:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 7:33 [PATCH v3 0/4 REPOST] OF infrastructure for SPI devices Grant Likely
2008-07-25 7:33 ` [PATCH v3 1/4] of: adapt of_find_i2c_driver() to be usable by SPI also Grant Likely
2008-07-25 15:40 ` Jon Smirl
2008-07-25 16:21 ` Grant Likely
2008-07-25 17:02 ` Jon Smirl
2008-07-25 18:52 ` Grant Likely [this message]
2008-07-25 7:33 ` [PATCH v3 2/4] spi: split up spi_new_device() to allow two stage registration Grant Likely
2008-07-25 19:00 ` David Brownell
2008-07-25 19:34 ` Grant Likely
2008-07-25 7:33 ` [PATCH v3 3/4] spi: Add OF binding support for SPI busses Grant Likely
2008-07-25 7:33 ` [PATCH v3 4/4] powerpc/mpc5200: Add mpc5200-spi (non-PSC) device driver Grant Likely
2008-07-25 18:19 ` Daniel Walker
2008-07-26 2:45 ` Grant Likely
2008-07-26 4:47 ` Daniel Walker
2008-07-26 5:20 ` Grant Likely
2008-07-27 21:41 ` David Brownell
2008-07-25 14:46 ` [PATCH v3 0/4 REPOST] OF infrastructure for SPI devices Jon Smirl
2008-08-02 22:46 ` Jon Smirl
2008-07-27 21:49 ` David Brownell
2008-07-28 16:39 ` 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=fa686aa40807251152t22848f69l924b0f83f1871165@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).