From: Cyril Chemparathy <cyril-l0cyMroinI0@public.gmane.org>
To: Linus Walleij <linus.ml.walleij-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org"
<davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org>,
"dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
"broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org"
<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"rpurdie-Fm38FmjxZ/leoWH0uzbU5w@public.gmane.org"
<rpurdie-Fm38FmjxZ/leoWH0uzbU5w@public.gmane.org>,
Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>,
"spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"lrg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org"
<lrg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org>
Subject: Re: [PATCH v4 01/12] misc: add driver for sequencer serial port
Date: Thu, 28 Oct 2010 12:09:35 -0400 [thread overview]
Message-ID: <4CC9A03F.80401@ti.com> (raw)
In-Reply-To: <AANLkTi=rDep3jkp2QAjVsgjZ7JQ0ysnse4TARv29fyHm-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 10/28/2010 11:49 AM, Linus Walleij wrote:
> 2010/10/26 Cyril Chemparathy <cyril-l0cyMroinI0@public.gmane.org>:
>
>> TI's sequencer serial port (TI-SSP) is a jack-of-all-trades type of serial port
>> device. It has a built-in programmable execution engine that can be programmed
>> to operate as almost any serial bus (I2C, SPI, EasyScale, and others).
>>
>> This patch adds a driver for this controller device. The driver does not
>> expose a user-land interface. Protocol drivers built on top of this layer are
>> expected to remain in-kernel.
>
> Why is this thing in drivers/misc?
>
> drivers/mfd is IMHO the apropriate place for a driver like this, and
> the subdrivers should be migrated to use mfd cells and platform
> drivers for the subdevices.
>
> All functions and abstractions you create here look suspiciously
> lot like other MFD devices.
>
> But please, beat me up if I'm wrong!
Alan had raised the same concern earlier, and my response was:
> Unlike MFDs, this device doesn't have cells with differing
> functionality. Instead it has functionally identical ports that can
> operate in a variety of modes. That said, does this still fit in with
> other MFD drivers? If so, I don't see a problem with moving it there.
I don't see a problem with moving this into MFD, but this won't be able
to use any of the functionality provided by mfd-core.
Thanks
Cyril.
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
WARNING: multiple messages have this Message-ID (diff)
From: cyril@ti.com (Cyril Chemparathy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 01/12] misc: add driver for sequencer serial port
Date: Thu, 28 Oct 2010 12:09:35 -0400 [thread overview]
Message-ID: <4CC9A03F.80401@ti.com> (raw)
In-Reply-To: <AANLkTi=rDep3jkp2QAjVsgjZ7JQ0ysnse4TARv29fyHm@mail.gmail.com>
On 10/28/2010 11:49 AM, Linus Walleij wrote:
> 2010/10/26 Cyril Chemparathy <cyril@ti.com>:
>
>> TI's sequencer serial port (TI-SSP) is a jack-of-all-trades type of serial port
>> device. It has a built-in programmable execution engine that can be programmed
>> to operate as almost any serial bus (I2C, SPI, EasyScale, and others).
>>
>> This patch adds a driver for this controller device. The driver does not
>> expose a user-land interface. Protocol drivers built on top of this layer are
>> expected to remain in-kernel.
>
> Why is this thing in drivers/misc?
>
> drivers/mfd is IMHO the apropriate place for a driver like this, and
> the subdrivers should be migrated to use mfd cells and platform
> drivers for the subdevices.
>
> All functions and abstractions you create here look suspiciously
> lot like other MFD devices.
>
> But please, beat me up if I'm wrong!
Alan had raised the same concern earlier, and my response was:
> Unlike MFDs, this device doesn't have cells with differing
> functionality. Instead it has functionally identical ports that can
> operate in a variety of modes. That said, does this still fit in with
> other MFD drivers? If so, I don't see a problem with moving it there.
I don't see a problem with moving this into MFD, but this won't be able
to use any of the functionality provided by mfd-core.
Thanks
Cyril.
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Chemparathy <cyril@ti.com>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: "davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"dbrownell@users.sourceforge.net"
<dbrownell@users.sourceforge.net>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rpurdie@rpsys.net" <rpurdie@rpsys.net>,
Samuel Ortiz <sameo@linux.intel.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH v4 01/12] misc: add driver for sequencer serial port
Date: Thu, 28 Oct 2010 12:09:35 -0400 [thread overview]
Message-ID: <4CC9A03F.80401@ti.com> (raw)
In-Reply-To: <AANLkTi=rDep3jkp2QAjVsgjZ7JQ0ysnse4TARv29fyHm@mail.gmail.com>
On 10/28/2010 11:49 AM, Linus Walleij wrote:
> 2010/10/26 Cyril Chemparathy <cyril@ti.com>:
>
>> TI's sequencer serial port (TI-SSP) is a jack-of-all-trades type of serial port
>> device. It has a built-in programmable execution engine that can be programmed
>> to operate as almost any serial bus (I2C, SPI, EasyScale, and others).
>>
>> This patch adds a driver for this controller device. The driver does not
>> expose a user-land interface. Protocol drivers built on top of this layer are
>> expected to remain in-kernel.
>
> Why is this thing in drivers/misc?
>
> drivers/mfd is IMHO the apropriate place for a driver like this, and
> the subdrivers should be migrated to use mfd cells and platform
> drivers for the subdevices.
>
> All functions and abstractions you create here look suspiciously
> lot like other MFD devices.
>
> But please, beat me up if I'm wrong!
Alan had raised the same concern earlier, and my response was:
> Unlike MFDs, this device doesn't have cells with differing
> functionality. Instead it has functionally identical ports that can
> operate in a variety of modes. That said, does this still fit in with
> other MFD drivers? If so, I don't see a problem with moving it there.
I don't see a problem with moving this into MFD, but this won't be able
to use any of the functionality provided by mfd-core.
Thanks
Cyril.
next prev parent reply other threads:[~2010-10-28 16:09 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 20:18 [PATCH v4 00/12] tnetv107x ssp driver stack Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
[not found] ` <1288124308-14999-1-git-send-email-cyril-l0cyMroinI0@public.gmane.org>
2010-10-26 20:18 ` [PATCH v4 01/12] misc: add driver for sequencer serial port Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-28 15:49 ` Linus Walleij
2010-10-28 15:49 ` Linus Walleij
[not found] ` <AANLkTi=rDep3jkp2QAjVsgjZ7JQ0ysnse4TARv29fyHm-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-28 16:09 ` Cyril Chemparathy [this message]
2010-10-28 16:09 ` Cyril Chemparathy
2010-10-28 16:09 ` Cyril Chemparathy
2010-10-28 18:14 ` Linus Walleij
2010-10-28 18:14 ` Linus Walleij
2010-10-26 20:18 ` [PATCH v4 02/12] davinci: add tnetv107x ssp platform device Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 03/12] davinci: add ssp config for tnetv107x evm board Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 04/12] spi: add ti-ssp spi master driver Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 05/12] davinci: add spi devices on tnetv107x evm Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 06/12] regulator: add driver for tps6524x regulator Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 07/12] davinci: add tnetv107x evm regulators Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 08/12] gpio: add ti-ssp gpio driver Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
[not found] ` <1288124308-14999-9-git-send-email-cyril-l0cyMroinI0@public.gmane.org>
2010-11-03 2:15 ` David Brownell
2010-11-03 2:15 ` David Brownell
2010-11-03 2:15 ` David Brownell
2010-11-03 10:18 ` Linus Walleij
2010-11-03 10:18 ` Linus Walleij
[not found] ` <AANLkTin=3K0H+YdNM2Nhz63c3+Upp+rwApo-Ww4p5qH6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-11-03 12:35 ` David Brownell
2010-11-03 12:35 ` David Brownell
2010-11-03 12:35 ` David Brownell
2010-11-03 16:24 ` Linus Walleij
2010-11-03 16:24 ` Linus Walleij
2010-11-10 4:45 ` Grant Likely
2010-11-10 4:45 ` Grant Likely
[not found] ` <20101110044530.GB4110-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2010-11-10 6:16 ` David Brownell
2010-11-10 6:16 ` David Brownell
2010-11-10 6:16 ` David Brownell
2010-11-10 6:23 ` Grant Likely
2010-11-10 6:23 ` Grant Likely
[not found] ` <20101110062310.GB7431-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2010-11-10 14:34 ` Cyril Chemparathy
2010-11-10 14:34 ` Cyril Chemparathy
2010-11-10 14:34 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 09/12] davinci: add tnetv107x evm ti-ssp gpio device Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 10/12] backlight: add support for tps6116x controller Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 11/12] davinci: add tnetv107x evm backlight device Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` [PATCH v4 12/12] davinci: add tnetv107x evm i2c eeprom device Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
2010-10-26 20:18 ` Cyril Chemparathy
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=4CC9A03F.80401@ti.com \
--to=cyril-l0cymroini0@public.gmane.org \
--cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
--cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linus.ml.walleij-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lrg-kDsPt+C1G03kYMGBc/C6ZA@public.gmane.org \
--cc=rpurdie-Fm38FmjxZ/leoWH0uzbU5w@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@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.