From: Bert Vermeulen <bert@biot.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: ralf@linux-mips.org, sameo@linux.intel.com,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: Add support for CPLD chip on Mikrotik RB4xx boards
Date: Tue, 07 Apr 2015 17:48:02 +0200 [thread overview]
Message-ID: <5523FC32.3080904@biot.com> (raw)
In-Reply-To: <20150407065217.GC3461@x1>
On 07/04/15 08:52, Lee Jones wrote:
> On Mon, 06 Apr 2015, Bert Vermeulen wrote:
>
>> The SPI-connected CPLD chip controls access to the main NAND flash
>> chip and five LEDs.
>>
>> Signed-off-by: Bert Vermeulen <bert@biot.com>
>> ---
>> arch/mips/include/asm/mach-ath79/rb4xx_cpld.h | 49 +++++
>> drivers/mfd/Kconfig | 7 +
>> drivers/mfd/Makefile | 1 +
>> drivers/mfd/rb4xx-cpld.c | 279 ++++++++++++++++++++++++++
>> 4 files changed, 336 insertions(+)
>> create mode 100644 arch/mips/include/asm/mach-ath79/rb4xx_cpld.h
>> create mode 100644 drivers/mfd/rb4xx-cpld.c
>
> This device doesn't look like an MFD, it rather looks like a CPLD
> driver. We had a recent submission like this [1], perhaps this will
> provide another argument for drivers/programmables or something.
>
> [1] https://lkml.org/lkml/2015/2/17/42
Yup, got bounced into drivers/mfd after initially submitting it as an SPI
protocol driver (where it lives in openwrt). Indeed it's not a great fit
anywhere -- not even programmables: this thing has its firmware on board,
nothing ever feeds it on startup.
Drivers for CPLDs don't necessarily have anything in common -- these are
customized chips basically. In this case it's a NAND controller and GPIO/LED
expander rolled into one.
--
Bert Vermeulen
bert@biot.com
next prev parent reply other threads:[~2015-04-07 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 1:51 [PATCH] mfd: Add support for CPLD chip on Mikrotik RB4xx boards Bert Vermeulen
2015-04-06 7:27 ` Paul Bolle
2015-04-06 10:13 ` Andy Shevchenko
2015-04-06 22:49 ` Bert Vermeulen
2015-04-07 6:52 ` Lee Jones
2015-04-07 15:48 ` Bert Vermeulen [this message]
2015-04-07 16:31 ` Andy Shevchenko
2015-07-28 12:51 ` Ralf Baechle
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=5523FC32.3080904@biot.com \
--to=bert@biot.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=sameo@linux.intel.com \
/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.