From: Mike Frysinger <vapier.adi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: James Getzendanner
<James.Getzendanner-9geRo0GdX4k6efY3Smnssodd74u8MsAO@public.gmane.org>
Cc: "uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org"
<uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org>,
"spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [Uclinux-dist-devel] [PATCH] Clear control bits in drivers/spi/spi_bfin5xx.c as necessary
Date: Fri, 18 Dec 2009 12:34:49 -0500 [thread overview]
Message-ID: <8bd0f97a0912180934s3d2c70b7uf65d09dc016c1faa@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a0912180514k42f32162jc850f4b4abbc3f7a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Dec 18, 2009 at 08:14, Mike Frysinger wrote:
> On Fri, Dec 18, 2009 at 02:29, James Getzendanner wrote:
>> From: Andy Getzendanner <james.getzendanner@students.olin.edu>
>> The patch also modifies bfin_spi_setup() to
>> set/clear the SIZE bit as appropriate.
>
> ok, but this isnt the place to do it. the size can be changed on a
> per-transfer basis. i have a patch locally to unify the transfer size
> logic and i'll include this fix in the process.
i lied, this isnt necessary. it's already handled in the transfer code.
cr = (read_CTRL(drv_data) & (~BIT_CTL_TIMOD));
cr |= (width << 8);
write_CTRL(drv_data, cr);
where width is CFG_SPI_WORDSIZE16 or CFG_SPI_WORDSIZE8 as dictated by
the transfer.
-mike
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
spi-devel-general mailing list
spi-devel-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spi-devel-general
next prev parent reply other threads:[~2009-12-18 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 7:29 [PATCH] Clear control bits in drivers/spi/spi_bfin5xx.c as necessary James Getzendanner
[not found] ` <DA80C3E6C10BE94E8FCACEB239C2FEE46645317E77-64WhM8za9n95vsLK/AIMcA@public.gmane.org>
2009-12-18 13:14 ` [Uclinux-dist-devel] " Mike Frysinger
[not found] ` <8bd0f97a0912180514k42f32162jc850f4b4abbc3f7a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-12-18 17:34 ` Mike Frysinger [this message]
[not found] ` <8bd0f97a0912180934s3d2c70b7uf65d09dc016c1faa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-19 16:12 ` Grant Likely
[not found] ` <fa686aa41001190812l28cf29fs5471c1022d25deee-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-19 17:29 ` Mike Frysinger
[not found] ` <8bd0f97a1001190929w78624e95pa3f32e5147c2617e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-19 17:46 ` 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=8bd0f97a0912180934s3d2c70b7uf65d09dc016c1faa@mail.gmail.com \
--to=vapier.adi-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=James.Getzendanner-9geRo0GdX4k6efY3Smnssodd74u8MsAO@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@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).