linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zahari Doychev <zahari.doychev@linux.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Zahari Doychev <zahari.doychev@linux.com>,
	linux-kernel@vger.kernel.org, lee.jones@linaro.org,
	wsa@the-dreams.de, linus.walleij@linaro.org, wim@iguana.be,
	linux@roeck-us.net, linux-i2c@vger.kernel.org,
	linux-gpio@vger.kernel.org, gnurou@gmail.com,
	linux-watchdog@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] add support for DMO embedded controller
Date: Thu, 27 Oct 2016 17:54:29 +0200	[thread overview]
Message-ID: <20161027155429.GD3701@mail> (raw)
In-Reply-To: <20161027150151.GA19519@kroah.com>

On Thu, Oct 27, 2016 at 05:01:51PM +0200, Greg KH wrote:
> On Thu, Oct 27, 2016 at 12:47:11PM +0200, Zahari Doychev wrote:
> > This patch series adds support for the Data Modul Embedded Controller(dmec)
> > which is implemented within an on board FPGA found on Data Modul embedded
> > CPU modules.
> > 
> > The dmec is connected to the host through the LPC bus and its registers are
> > mapped into the host I/O space. The controller supports two addressing modes:
> > linear and indexed.
> > 
> > The driver adds support for the following functionality:
> > 
> > - i2c
> > - gpio
> > - watchdog
> > - running time meter (rtm)
> 
> Why do you want these in staging?  I need a TODO file listing what needs
> to be done to the code to get it out of staging, and for someone to
> agree to work toward that goal.

Actually there is no reason to have them in staging. I was not sure what was
the right way to go. I just wanted to get some feedback. The drivers have been
through a lot of testing so next time I will resend the patches putting
each driver in its subsystem.

Regards Zahari

> 
> Please resend the series with that information.
> 
> thanks,
> 
> greg k-h

      reply	other threads:[~2016-10-27 15:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27 10:47 [RFC PATCH 0/5] add support for DMO embedded controller Zahari Doychev
2016-10-27 10:47 ` [RFC PATCH 1/5] dmec: add DMO mfd driver Zahari Doychev
2016-10-27 10:47 ` [RFC PATCH 2/5] i2c-dmec: add i2c bus support for dmec Zahari Doychev
2016-10-27 10:47 ` [RFC PATCH 3/5] gpio-dmec: gpio " Zahari Doychev
     [not found]   ` <fe8ac70204de48edd8a3da8a783b10810f3d4ca1.1477564996.git-series.zahari.doychev-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
2016-10-29  9:05     ` Linus Walleij
2016-10-31  8:50       ` Zahari Doychev
     [not found]         ` <20161031085044.GC9050-S5msFFqROX52XvNHrDenQA@public.gmane.org>
2016-10-31 12:26           ` Linus Walleij
2016-10-27 10:47 ` [RFC PATCH 4/5] wdt-dmec: watchdog " Zahari Doychev
2016-10-27 10:47 ` [RFC PATCH 5/5] rtm-dmec: running time meter support Zahari Doychev
2016-10-27 15:01 ` [RFC PATCH 0/5] add support for DMO embedded controller Greg KH
2016-10-27 15:54   ` Zahari Doychev [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=20161027155429.GD3701@mail \
    --to=zahari.doychev@linux.com \
    --cc=gnurou@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=wim@iguana.be \
    --cc=wsa@the-dreams.de \
    /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).