From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM: Kirkwood: Add SPI_CHPA and SPI_CPOL support to spi-orion
Date: Wed, 21 Nov 2012 13:29:56 -0700 [thread overview]
Message-ID: <20121121202956.GA15020@obsidianresearch.com> (raw)
In-Reply-To: <20121121193552.GE15800-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
On Wed, Nov 21, 2012 at 02:35:52PM -0500, Jason Cooper wrote:
> > /* we support only mode 0, and no options */
> > - master->mode_bits = 0;
> > + master->mode_bits = SPI_CPHA | SPI_CPOL;
>
> The comment no longer seems valid. ;-) Also, you are unconditionally
> enabling these modes. Do all users of this driver support this?
Right on the comment.. Not sure about your second query?
* @mode_bits: flags understood by this controller driver
The mode_bits need to be set so the mid layer will allow consumers to
pass them down through spi->mode when it calls into
orion_spi_setup_transfer. So that looks correct..
Now, it seems a fair question what mode the driver will run in by
default now.. Previously, the driver didn't change the CPOL and CPHA
bits, so whatever the boot firmware left them at will be the mode it
uses.
If SPI consumers are not properly requesting the proper CPOL/CPHA
operation and instead relying on the boot firmware to leave the proper
bit settings then things will break for those users (they will need to
update their board's DT file, or otherwise) - but I don't see any way
to address that and implement proper programmable support?
This could affect at least dove, dreamplug, ts219 and lsxl.
Jason
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
WARNING: multiple messages have this Message-ID (diff)
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood: Add SPI_CHPA and SPI_CPOL support to spi-orion
Date: Wed, 21 Nov 2012 13:29:56 -0700 [thread overview]
Message-ID: <20121121202956.GA15020@obsidianresearch.com> (raw)
In-Reply-To: <20121121193552.GE15800@titan.lakedaemon.net>
On Wed, Nov 21, 2012 at 02:35:52PM -0500, Jason Cooper wrote:
> > /* we support only mode 0, and no options */
> > - master->mode_bits = 0;
> > + master->mode_bits = SPI_CPHA | SPI_CPOL;
>
> The comment no longer seems valid. ;-) Also, you are unconditionally
> enabling these modes. Do all users of this driver support this?
Right on the comment.. Not sure about your second query?
* @mode_bits: flags understood by this controller driver
The mode_bits need to be set so the mid layer will allow consumers to
pass them down through spi->mode when it calls into
orion_spi_setup_transfer. So that looks correct..
Now, it seems a fair question what mode the driver will run in by
default now.. Previously, the driver didn't change the CPOL and CPHA
bits, so whatever the boot firmware left them at will be the mode it
uses.
If SPI consumers are not properly requesting the proper CPOL/CPHA
operation and instead relying on the boot firmware to leave the proper
bit settings then things will break for those users (they will need to
update their board's DT file, or otherwise) - but I don't see any way
to address that and implement proper programmable support?
This could affect at least dove, dreamplug, ts219 and lsxl.
Jason
next prev parent reply other threads:[~2012-11-21 20:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 19:23 [PATCH] ARM: Kirkwood: Add SPI_CHPA and SPI_CPOL support to spi-orion Jason Gunthorpe
2012-11-21 19:23 ` Jason Gunthorpe
2012-11-21 19:35 ` Jason Cooper
2012-11-21 19:35 ` Jason Cooper
[not found] ` <20121121193552.GE15800-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2012-11-21 20:29 ` Jason Gunthorpe [this message]
2012-11-21 20:29 ` Jason Gunthorpe
[not found] ` <20121121192335.GA14868-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-12-06 14:25 ` Grant Likely
2012-12-06 14:25 ` Grant Likely
2012-12-06 17:25 ` Jason Gunthorpe
2012-12-06 17:25 ` Jason Gunthorpe
[not found] ` <20121206172504.GB9676-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-12-06 23:23 ` Grant Likely
2012-12-06 23:23 ` Grant Likely
2012-12-06 23:49 ` Jason Gunthorpe
2012-12-06 23:49 ` Jason Gunthorpe
[not found] ` <20121206234917.GF25069-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-12-06 23:53 ` Jason Cooper
2012-12-06 23:53 ` Jason Cooper
[not found] ` <20121206235311.GB21694-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2012-12-07 0:14 ` Jason Gunthorpe
2012-12-07 0:14 ` Jason Gunthorpe
[not found] ` <20121207001433.GG25069-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-12-07 0:49 ` Jason Cooper
2012-12-07 0:49 ` Jason Cooper
[not found] ` <20121207004933.GC21694-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2012-12-07 14:05 ` Grant Likely
2012-12-07 14:05 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2012-12-10 13:38 Andrew Lunn
2012-12-10 13:38 ` Andrew Lunn
[not found] ` <20121210133800.GA20001-g2DYL2Zd6BY@public.gmane.org>
2012-12-10 22:06 ` Grant Likely
2012-12-10 22:06 ` 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=20121121202956.GA15020@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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 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.