From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>, Len Brown <lenb@kernel.org>,
jani.nikula@linux.intel.com
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>,
"russianneuromancer @ ya . ru" <russianneuromancer@ya.ru>,
Vincent Gerris <vgerris@gmail.com>,
linux-i2c@vger.kernel.org, tagore.chandan@gmail.com,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 4/5] i2c: designware-baytrail: Force the CPU to C1 state while holding the punit semaphore
Date: Mon, 02 Jan 2017 10:26:34 +0200 [thread overview]
Message-ID: <1483345594.9552.179.camel@linux.intel.com> (raw)
In-Reply-To: <c6933f49-6f1b-d24a-1878-8893bfe88090@redhat.com>
On Sat, 2016-12-31 at 22:29 +0100, Hans de Goede wrote:
> This makes sense, the iosf_mbi code which is used by the
> i2c bus semaphore code has this:
>
> arch/x86/platform/intel/iosf_mbi.c:
>
> int iosf_mbi_read(u8 port, u8 opcode, u32 offset, u32 *mdr)
> {
> u32 mcr, mcrx;
> unsigned long flags;
> int ret;
>
> /* Access to the GFX unit is handled by GPU code */
> if (port == BT_MBI_UNIT_GFX) {
> WARN_ON(1);
> return -EPERM;
> }
>
> ...
> }
>
> So the i915 driver definitely is interacting with the punit
> through the mailbox interface too...
Yes, they have private mailbox support. Once I talked to Ville to make
at least definitions common between two: iosf_mbi.h and whatever i915 is
using, but have no time to implement that.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-01-02 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161210141908.16470-1-hdegoede@redhat.com>
[not found] ` <20161210141908.16470-4-hdegoede@redhat.com>
[not found] ` <1481381595.7188.6.camel@linux.intel.com>
[not found] ` <a1e46965-9cef-1ec0-ddb4-3a527cd71045@redhat.com>
[not found] ` <5425712f-550e-cc30-3b52-5bd25eabc5d9@redhat.com>
[not found] ` <CAJvTdKnqdhYo1hTp33z-dUCO3H5sROZQtDdSaGiL_EwW3DbbqQ@mail.gmail.com>
[not found] ` <e415e26c-8781-6ce1-c0f9-a68249e542d3@redhat.com>
2016-12-31 21:29 ` [PATCH v2 4/5] i2c: designware-baytrail: Force the CPU to C1 state while holding the punit semaphore Hans de Goede
2017-01-02 8:26 ` Andy Shevchenko [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=1483345594.9552.179.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=russianneuromancer@ya.ru \
--cc=tagore.chandan@gmail.com \
--cc=tiwai@suse.de \
--cc=vgerris@gmail.com \
--cc=wsa@the-dreams.de \
/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