From: Maxime Coquelin <maxime.coquelin-qxv4g6HH51o@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [STLinux Kernel] [PATCH v3 0/4] spi: st: New driver for ST's SPI Controller
Date: Mon, 8 Dec 2014 14:53:39 +0100 [thread overview]
Message-ID: <5485AD63.6090308@st.com> (raw)
In-Reply-To: <11694915.sCOqLZA7N1@wuerfel>
On 12/08/2014 02:22 PM, Arnd Bergmann wrote:
> On Monday 08 December 2014 12:53:30 Lee Jones wrote:
>> This is a new driver which controls the SPI component of ST's
>> Synchronous Serial Controller (SSC).
>>
> How does this related to the i2c driver for drivers/i2c/busses/i2c-st.c?
> Could you have the same piece of hardware do one or the other mode
> depending on pin configuration, or is each instance hardwired to
> a particular mode?
This is the same IP, that can be configured either in SPI or I2C.
>
> Is there any code worth sharing between the two drivers?
No, except a couple of registers, they are managed in a ways.
The way it is used, a single SSC instance can only be used either in SPI
or I2C mode on a board,
so I think it wouldn't make sense to create a MFD driver to manage it.
Kr,
Maxime
>
> Arnd
>
> _______________________________________________
> Kernel mailing list
> Kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org
> http://www.stlinux.com/mailman/listinfo/kernel
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-12-08 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 12:53 [PATCH v3 0/4] spi: st: New driver for ST's SPI Controller Lee Jones
2014-12-08 12:53 ` [PATCH v3 1/4] spi: Add new driver for STMicroelectronics' " Lee Jones
2014-12-08 13:12 ` [STLinux Kernel] " Patrice Chotard
2014-12-08 12:53 ` [PATCH v3 2/4] spi: st: Provide Device Tree binding documentation Lee Jones
2014-12-08 12:53 ` [PATCH v3 3/4] ARM: sti: Provide DT nodes for SSC[0..4] Lee Jones
2014-12-08 12:53 ` [PATCH v3 4/4] ARM: sti: Provide DT nodes for SBC SSC[0..2] Lee Jones
2014-12-08 13:15 ` [STLinux Kernel] " Peter Griffin
[not found] ` <1418043214-14324-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-12-08 13:22 ` [PATCH v3 0/4] spi: st: New driver for ST's SPI Controller Arnd Bergmann
2014-12-08 13:53 ` Maxime Coquelin [this message]
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=5485AD63.6090308@st.com \
--to=maxime.coquelin-qxv4g6hh51o@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@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).