From: Jens Gehrlein <sew_s-77yLcl8UjJQ@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Guennadi Liakhovetski <lg-ynQEQJNshbs@public.gmane.org>,
a.paterniani-03BXCEkGbFHYGGNLXY5/rw@public.gmane.org,
linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org
Subject: Re: [RFC PATCH V2] generic SPI driver for all i.MX-platforms
Date: Fri, 27 Feb 2009 07:40:51 +0100 [thread overview]
Message-ID: <49A78AF3.1000606@tqs.de> (raw)
In-Reply-To: <20090226163721.GD3058-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Hi Wolfram,
Wolfram Sang schrieb:
> - ATTENTION: The original FSL-driver has a bug regarding the polarity
> CPOL which got flipped. So, if you used the FSL-driver before, then
> the SPI_MODE of your spi_device has to be corrected. Just toggle
> SPI_CPOL or make SPI_MODE_0 out of SPI_MODE_2, SPI_MODE_1 out of
> SPI_MODE_3 or vice versa.
Do I understand it right: the driver has a bug, not the CPU?
Just for clarification.
Thanks.
Kind regards,
Jens Gehrlein
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
next prev parent reply other threads:[~2009-02-27 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 16:21 [RFC PATCH V2] generic SPI driver for all i.MX-platforms Wolfram Sang
[not found] ` <1235665315-2792-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-02-26 16:37 ` Wolfram Sang
[not found] ` <20090226163721.GD3058-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-02-27 6:40 ` Jens Gehrlein [this message]
[not found] ` <49A78AF3.1000606-77yLcl8UjJQ@public.gmane.org>
2009-02-27 10:39 ` Wolfram Sang
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=49A78AF3.1000606@tqs.de \
--to=sew_s-77ylcl8ujjq@public.gmane.org \
--cc=a.paterniani-03BXCEkGbFHYGGNLXY5/rw@public.gmane.org \
--cc=lg-ynQEQJNshbs@public.gmane.org \
--cc=linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.