All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: "Zha, Qipeng" <qipeng.zha@intel.com>
Cc: "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 v4] platform:x86: add Intel P-Unit mailbox IPC driver
Date: Thu, 8 Oct 2015 17:09:42 +0100	[thread overview]
Message-ID: <20151008160942.GD101005@vmdeb7> (raw)
In-Reply-To: <C6287702A945AC47BE5DB5DFD4B5C6DD0196B567@SHSMSX104.ccr.corp.intel.com>

On Thu, Oct 08, 2015 at 03:16:02AM +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

My apologies Qipeng, I missed this response from you.

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

An acpidump would be good to see, along with the couple minor changes requested.
I want this to get into next sooner rather than later, so I'm queueing to
testing today. If we could get the next rev and the acpidump out soon, we can
get to linux-next this weekend which would be ideal for 4.4.

-- 
Darren Hart
Intel Open Source Technology Center

      parent reply	other threads:[~2015-10-08 16:10 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
2015-10-08 16:09       ` 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=20151008160942.GD101005@vmdeb7 \
    --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.