From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Yang A Fang <yang.a.fang@intel.com>,
Yu Chen <yu.c.chen@intel.com>
Subject: Re: [PATCH 2/2] ACPI / LPSS: Deassert resets for SPI host controllers on Braswell
Date: Wed, 18 Feb 2015 18:13:03 +0200 [thread overview]
Message-ID: <20150218161303.GT1508@lahna.fi.intel.com> (raw)
In-Reply-To: <3423831.zXJf7A6g9H@vostro.rjw.lan>
On Wed, Feb 18, 2015 at 05:25:09PM +0100, Rafael J. Wysocki wrote:
> On Wednesday, February 18, 2015 01:50:17 PM Mika Westerberg wrote:
> > On some Braswell systems BIOS leaves resets for SPI host controllers
> > active. This prevents the SPI driver from transferring messages on wire.
> >
> > Fix this in similar way that we do for I2C already by deasserting resets
> > for the SPI host controllers.
> >
> > Reported-by: Yang A Fang <yang.a.fang@intel.com>
> > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> OK, so these two would need to go into "stable" I suppose?
Yes, if possible.
> What "stable" series we need them to go into?
Braswell support was added in v3.17 so I think from v3.17 onwards.
next prev parent reply other threads:[~2015-02-18 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 11:50 [PATCH 1/2] ACPI / LPSS: Always disable I2C host controllers Mika Westerberg
2015-02-18 11:50 ` [PATCH 2/2] ACPI / LPSS: Deassert resets for SPI host controllers on Braswell Mika Westerberg
2015-02-18 16:25 ` Rafael J. Wysocki
2015-02-18 16:13 ` Mika Westerberg [this message]
2015-02-18 12:54 ` [PATCH 1/2] ACPI / LPSS: Always disable I2C host controllers Mika Westerberg
2015-02-18 16:24 ` Rafael J. Wysocki
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=20150218161303.GT1508@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=yang.a.fang@intel.com \
--cc=yu.c.chen@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