From: Darren Hart <dvhart@infradead.org>
To: "Shevchenko, Andriy" <andriy.shevchenko@intel.com>
Cc: "platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"Zha, Qipeng" <qipeng.zha@intel.com>,
"Westerberg, Mika" <mika.westerberg@intel.com>
Subject: Re: [PATCH v7] platform:x86: add Intel P-Unit mailbox IPC driver
Date: Thu, 15 Oct 2015 08:29:31 -0700 [thread overview]
Message-ID: <20151015152931.GA3049@malice.jf.intel.com> (raw)
In-Reply-To: <1444905573.8361.647.camel@intel.com>
On Thu, Oct 15, 2015 at 10:39:35AM +0000, Shevchenko, Andriy wrote:
> On Thu, 2015-10-15 at 13:35 +0300, Andy Shevchenko wrote:
> > On Sat, 2015-10-10 at 03:07 +0000, Zha, Qipeng wrote:
> > > >
> > > > Everything is quite okay, except this BAR thingy.
> > >
> > > > Can you provide a DSDT excerpt for the device to see what is
> > > > there?
> > >
> > > > I can't find such device (by ACPI id) in the tables of the
> > > > accessible hardware in our lab.
> > >
> > > Please check below acpi device definition from BIOS.
> > > Punit device is created in pmc driver, since BIOS finally reject to
> > >
> > > create a separate device for Punit.
> >
> > Thank you for mention this one. It's unfortunately a show stopper for
> > using this module as a driver (you can't assign two drivers to the
> > same
> > device). You have to convert is to a library.
>
> Oh, I'm sorry, I really missed that the IDs are different.
> So, discard this part.
>
> >
> > Moreover, I briefly looked at the intel_pmc_ipc and it should be
> > refactored a in a few ways: a) split to core part, PCI driver, and
> > ACPI
> > driver, b) improved regarding to comments you got in this review
> > (many
> > comments are applied to what we have there).
> >
> > Darren, your opinion?
>
> This by the way still valid.
I'm a bit confused. Are you just bringing up that the intel_pmc_ipc driver could
also be improved? Or are you sugesting that this driver needs to be refactored
together with the intel_pmc_ipc driver?
With respect to the intel_punit_ipc driver, I've tried to parse/map the DSDT to
the BAR mapping in the driver which you raised concerns about. Can you review
that bit and help us come to a conclusion on that since you asked for the DSDT?
(See separate response to Qipeng on that).
Thanks,
>
> >
> > >
> > > Scope (\_SB) {
> > > Device(IPC1)
> > > {
> > > …
> > > Name (RBUF, ResourceTemplate ()
> > > {
> > > Memory32Fixed (ReadWrite, 0x00000000, 0x00001000, BAR0)
> > > //
> > > IPC1 Bar
> > > // Memory32Fixed (ReadWrite, 0x00000000, 0x00001000, BAR1)
> > > //
> > > SSRAM
> > > Memory32Fixed (ReadWrite, 0x00000000, 0x00001000, MDAT)
> > > //
> > > PUnit BIOS mailbox Data
> > > Memory32Fixed (ReadWrite, 0x00000000, 0x00001000, MINF)
> > > //
> > > PUnit BIOS mailbox Interface and GTD/ISPD mailbox
> > > IO (Decode16, 0x400, 0x480, 0x4, 0x80)
> > > //
> > > ACPI IO Base address
> > > Interrupt (ResourceConsumer, Level, ActiveLow, Exclusive, ,
> > > ,
> > > ) {40} // IPC1 IRQ
> > > })
> > >
> > > …
> > > }
> > > }//end scope
> >
>
> --
> Andy Shevchenko <andriy.shevchenko@intel.com>
> Intel Finland Oy
> ---------------------------------------------------------------------
> Intel Finland Oy
> Registered Address: PL 281, 00181 Helsinki
> Business Identity Code: 0357606 - 4
> Domiciled in Helsinki
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-10-15 15:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 8:49 [PATCH v7] platform:x86: add Intel P-Unit mailbox IPC driver Qipeng Zha
2015-10-09 13:33 ` Shevchenko, Andriy
2015-10-10 3:07 ` Zha, Qipeng
2015-10-15 5:16 ` Darren Hart
2015-10-21 12:51 ` Darren Hart
2015-10-22 1:01 ` Zha, Qipeng
2015-10-22 8:04 ` Darren Hart
2015-10-22 8:35 ` Shevchenko, Andriy
2015-10-22 15:18 ` Zha, Qipeng
2015-10-22 15:43 ` Darren Hart
2015-10-24 13:35 ` Rafael J. Wysocki
2015-10-26 8:51 ` Zha, Qipeng
2015-10-27 12:30 ` Shevchenko, Andriy
2015-10-28 1:27 ` Darren Hart
2015-10-30 6:11 ` Zha, Qipeng
2015-10-30 9:56 ` Shevchenko, Andriy
2015-10-15 10:35 ` Shevchenko, Andriy
2015-10-15 10:39 ` Shevchenko, Andriy
2015-10-15 15:29 ` Darren Hart [this message]
2015-10-15 15:36 ` Shevchenko, Andriy
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=20151015152931.GA3049@malice.jf.intel.com \
--to=dvhart@infradead.org \
--cc=andriy.shevchenko@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 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.