All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shevchenko, Andriy" <andriy.shevchenko@intel.com>
To: "platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	"Zha, Qipeng" <qipeng.zha@intel.com>
Cc: "dvhart@infradead.org" <dvhart@infradead.org>,
	"Westerberg, Mika" <mika.westerberg@intel.com>
Subject: Re: [PATCH v4] platform:x86: add Intel P-Unit mailbox IPC driver
Date: Thu, 8 Oct 2015 12:18:42 +0000	[thread overview]
Message-ID: <1444306721.8361.470.camel@intel.com> (raw)
In-Reply-To: <C6287702A945AC47BE5DB5DFD4B5C6DD0196B567@SHSMSX104.ccr.corp.intel.com>

On Thu, 2015-10-08 at 03:16 +0000, Zha, Qipeng wrote:
> > 
> > > > +	ipcdev.base[BIOS_MAILBOX] = addr;
> > > > +	addr += MAILBOX_REGISTER_SPACE;
> > > > +	ipcdev.base[GTDRIVER_MAILBOX] = addr;
> > > > +	addr += MAILBOX_REGISTER_SPACE;
> > > > +	ipcdev.base[ISPDRIVER_MAILBOX] = addr;
> 
> > > Looks akward, does the platform have the several resources for 
> > > different purpose? Why do you unify them (who does guarantee the 
> > > non-breakable segment for all resources?) first and then split 
> > > up?
> > > Please, refactor.
> 
> > From spec, these three parts are consecutive, so only define one 
> > acpi resource entry is reasonable way,
> > But BIOS maintainer finally make the resource like this due to 
> > request from Window os driver,
> > So can't treat these three as three separate parts.
> 
>  Andriy, Darren:  this is my before feedback, and
> a) Punit function is configured as ACPI device in BIOS, not PCI 
> device(seems can't configure as PCI).
> b) To make it compatible(same acpi entry) for WOS, BIOS define Punit 
> mem resource as res0,  so this driver is coding as this.
>      So this driver is depend on acpi entry in BIOS to get device 
> resource like all acpi device drivers.
>      In future, I don't think BIOS will change current defined 
> resource for Punit function.

Can you show the excerpt from DSDT then?

>  
> 
> 

-- 
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.

  reply	other threads:[~2015-10-08 12:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 10:29 [PATCH v4] platform:x86: add Intel P-Unit mailbox IPC driver Qipeng Zha
2015-09-08 10:42 ` Shevchenko, Andriy
2015-09-14  2:42   ` Zha, Qipeng
2015-09-17 17:45     ` Darren Hart
2015-09-18  1:29       ` Zha, Qipeng
2015-09-18  2:43         ` Darren Hart
2015-10-08  3:16     ` Zha, Qipeng
2015-10-08 12:18       ` Shevchenko, Andriy [this message]
2015-10-08 16:09       ` Darren Hart

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=1444306721.8361.470.camel@intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=dvhart@infradead.org \
    --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.