From: Maris <maris.rob-rHNaxI9ti4Y@public.gmane.org>
To: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Proposal spi.h
Date: Wed, 10 Feb 2010 13:22:02 +0100 [thread overview]
Message-ID: <op.u7wva0n77fwl0e@rob-desktop.lan> (raw)
In-Reply-To: <mailman.2334.1265803025.4911.spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
> ------------------------------
>
> Message: 2
> Date: Wed, 10 Feb 2010 08:36:27 +0100
> From: Maris <maris.rob-rHNaxI9ti4Y@public.gmane.org>
> Subject: [spi-devel-general] Proposal spi.h
> To: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> Message-ID: <op.u7wh21l67fwl0e-iGVHgWvKxCYNKJm4j5fLFA@public.gmane.org>
> Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
>
> * extend spi_device struct element 'mode' to u16 (currently u8, fully
> utilized as of 2.6.3x)
> * chip_select to s16 (until now also u8)
I forgot to mention whzy signed: negative values for gpio-indices,
positive as usual for SSEL lines.
-Rob
>
> Background:
> Chip select size change: allow specification of SPI-device
> hardware-related spi control per device-specific (native) or gpio-based
> control.
> mode size change: obligatory... A mode bit could also be assigned a
> selection bit: chip_select interpreted as native SSEL-index or as
> gpio-index (instead of negative value for chip_select).
>
> Chip select differentiation bottom line: Naming of the device. I'm not
> sure how to establish this. spidev0.x are normally assigned for chip
> selects driven by the SPI peripheral hardware. GPIO-based:
> spidev0.gpioxx?
>
> -Rob
>
>
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
next parent reply other threads:[~2010-02-10 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2334.1265803025.4911.spi-devel-general@lists.sourceforge.net>
[not found] ` <mailman.2334.1265803025.4911.spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
2010-02-10 12:22 ` Maris [this message]
2010-02-10 7:36 Proposal spi.h Maris
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=op.u7wva0n77fwl0e@rob-desktop.lan \
--to=maris.rob-rhnaxi9ti4y@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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).