From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753340AbcEMO1N (ORCPT ); Fri, 13 May 2016 10:27:13 -0400 Received: from mx2.suse.de ([195.135.220.15]:37953 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751631AbcEMO1L (ORCPT ); Fri, 13 May 2016 10:27:11 -0400 Date: Fri, 13 May 2016 16:27:09 +0200 Message-ID: From: Takashi Iwai To: Guenter Roeck Cc: Lucas Stach , Wim Van Sebroeck , linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] sp5100_tco: properly check for new register layouts In-Reply-To: <572961D5.6060507@roeck-us.net> References: <1462295758-3299-1-git-send-email-dev@lynxeye.de> <572961D5.6060507@roeck-us.net> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.5 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 04 May 2016 04:43:33 +0200, Guenter Roeck wrote: > > On 05/03/2016 10:15 AM, Lucas Stach wrote: > > Commits 190aa4304de6 (Add AMD Mullins platform support) and > > cca118fa2a0a94 (Add AMD Carrizo platform support) enabled the > > driver on a lot more devices, but the following commit missed > > a single location in the code when checking if the SB800 register > > offsets should be used. This leads to the wrong register being > > written which in turn causes ACPI to go haywire. > > > > Fix this by introducing a helper function to check for the new > > register layout and use this consistently. > > > > https://bugzilla.kernel.org/show_bug.cgi?id=114201 > > https://bugzilla.redhat.com/show_bug.cgi?id=1329910 > > Fixes: bdecfcdb5461 (sp5100_tco: fix the device check for SB800 > > and later chipsets) > > Cc: stable@vger.kernel.org (4.5+) > > Signed-off-by: Lucas Stach > > Reviewed-by: Guenter Roeck What is the status of this patch? I still can't find it in linux-next. We've got more and more bug reports about this, so would love to get this resolved soonish. thanks, Takashi