From: Darren Hart <dvhart@infradead.org>
To: "Zha, Qipeng" <qipeng.zha@intel.com>
Cc: "Fleming, Matt" <matt.fleming@intel.com>,
"Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"Westerberg, Mika" <mika.westerberg@intel.com>
Subject: Re: [PATCH] platform:x86: add Intel Punit mailbox IPC driver
Date: Fri, 28 Aug 2015 11:57:22 -0700 [thread overview]
Message-ID: <20150828185722.GA88873@vmdeb7> (raw)
In-Reply-To: <C6287702A945AC47BE5DB5DFD4B5C6DD01949DAE@SHSMSX104.ccr.corp.intel.com>
On Wed, Aug 26, 2015 at 08:22:33AM +0000, Zha, Qipeng wrote:
> On Tue, Aug 18, 2015 at 04:50:56PM +0100, Matt Fleming wrote:
> > On Mon, 2015-08-10 at 16:04 +0100, Shevchenko, Andriy wrote:
> > >
> > > Matt, by the way intel_pmc_ipc.c module creates iTCO device (LPC bus).
> > > Does it look correct?
> >
> > Yeah, it looks OK to me. Note there are changes queued up in Lee Jones'
> > tree for changing the lpc_ich_info into itco_wdt_platform_data.
> >
> > Btw, is there a reason that intel_pmc_ipc doesn't use the mfd_* API
> > since it's concerned with multiple functions?
>
> > Qipeng?
>
> > I saw the v2 come in, but didn't see this question addressed in the changelog.
>
> When design P-unit driver, we got feedback from BIOS that there will allocate a dedicate
> ACPI id for P-unit controller, and finally BIOS decide not do that, just put some necessary
> Resource in PMC acpi table.
> After that, we got request to do same thing for iTco.
>
> I agree it's better to update pmc driver to use mfd_add_devices to create punit and iTco device.
Does this mean there sill be a v4 I should be waiting for?
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2015-08-28 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 15:58 [PATCH] platform:x86: add Intel Punit mailbox IPC driver Qipeng Zha
2015-08-05 21:25 ` Darren Hart
2015-08-07 12:29 ` Mika Westerberg
2015-08-10 15:04 ` Shevchenko, Andriy
2015-08-18 15:50 ` Matt Fleming
2015-08-25 20:33 ` Darren Hart
2015-08-26 8:22 ` Zha, Qipeng
2015-08-28 18:57 ` Darren Hart [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=20150828185722.GA88873@vmdeb7 \
--to=dvhart@infradead.org \
--cc=andriy.shevchenko@intel.com \
--cc=matt.fleming@intel.com \
--cc=mika.westerberg@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=qipeng.zha@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