From: Lee Jones <lee.jones@linaro.org>
To: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
Cc: openbmc@lists.ozlabs.org, Andrew Jeffery <andrew@aj.id.au>,
James Feist <james.feist@linux.intel.com>,
Jason M Biils <jason.m.bills@linux.intel.com>,
Joel Stanley <joel@jms.id.au>,
Vernon Mauery <vernon.mauery@linux.intel.com>
Subject: Re: [PATCH linux-next v5 08/13] drivers/mfd: Add PECI client mfd driver
Date: Wed, 4 Jul 2018 07:42:30 +0100 [thread overview]
Message-ID: <20180704064230.GC20176@dell> (raw)
In-Reply-To: <e387da06-1b73-a497-be59-9c25df9bb7f9@linux.intel.com>
On Mon, 18 Jun 2018, Jae Hyun Yoo wrote:
> On 6/17/2018 10:59 PM, Lee Jones wrote:
> > On Thu, 14 Jun 2018, Jae Hyun Yoo wrote:
> >
> > > Thanks for the review. Please see my inline answers.
> > >
> > > On 6/12/2018 11:30 PM, Lee Jones wrote:
> > > > On Fri, 01 Jun 2018, Jae Hyun Yoo wrote:
> > > >
> > > > > This commit adds PECI client mfd driver.
> > > > >
> > > > > Signed-off-by: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
> > > > > Cc: Andrew Jeffery <andrew@aj.id.au>
> > > > > Cc: James Feist <james.feist@linux.intel.com>
> > > > > Cc: Jason M Biils <jason.m.bills@linux.intel.com>
> > > > > Cc: Joel Stanley <joel@jms.id.au>
> > > > > Cc: Vernon Mauery <vernon.mauery@linux.intel.com>
> > > > > ---
> > > > > drivers/mfd/Kconfig | 11 ++
> > > > > drivers/mfd/Makefile | 1 +
> > > > > drivers/mfd/peci-client.c | 205 ++++++++++++++++++++++++++++++++
> > > > > include/linux/mfd/peci-client.h | 60 ++++++++++
> > > > > 4 files changed, 277 insertions(+)
> > > > > create mode 100644 drivers/mfd/peci-client.c
> > > > > create mode 100644 include/linux/mfd/peci-client.h
>
> > [...]
> >
> > > > > +static struct peci_driver peci_client_driver = {
> > > >
> > > > I'm pretty sure this will be NAKED by the platform Maintainer.
> > >
> > > Does it have problems? Can you please give me a hint?
> >
> > New bus types are usually only added for well defined, heavily used
> > buses which AFAIK all have their own subsystems. Why can't you use
> > one of the existing bus types? Platform is the most frequently used.
> >
>
> I implemented this PECI drivers as a simple platform drivers in V1 but
> I had to change it to follow other maintainers' suggestions. I believe
> driver core maintainers are reviewing the PECI subsystem implementation
> code in this patch set as well.
I don't see this discussion. How is it progressing?
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2018-07-04 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 18:22 [PATCH linux-next v5 08/13] drivers/mfd: Add PECI client mfd driver Jae Hyun Yoo
2018-06-13 6:30 ` Lee Jones
2018-06-14 17:48 ` Jae Hyun Yoo
2018-06-18 5:59 ` Lee Jones
2018-06-18 17:09 ` Jae Hyun Yoo
2018-07-04 6:41 ` Lee Jones
2018-07-05 16:33 ` Jae Hyun Yoo
2018-07-04 6:42 ` Lee Jones [this message]
2018-07-05 16:39 ` Jae Hyun Yoo
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=20180704064230.GC20176@dell \
--to=lee.jones@linaro.org \
--cc=andrew@aj.id.au \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=james.feist@linux.intel.com \
--cc=jason.m.bills@linux.intel.com \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=vernon.mauery@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 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).