From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751558AbbCKHvl (ORCPT ); Wed, 11 Mar 2015 03:51:41 -0400 Received: from mga02.intel.com ([134.134.136.20]:38472 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751257AbbCKHvj (ORCPT ); Wed, 11 Mar 2015 03:51:39 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,380,1422950400"; d="scan'208";a="690279703" Message-ID: <54FFF408.1000703@linux.intel.com> Date: Wed, 11 Mar 2015 15:51:36 +0800 From: "Li, Aubrey" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Ingo Molnar CC: Ingo Molnar , "alan@linux.intel.com" , Arjan van de Ven , "Rafael J. Wysocki" , "Brown, Len" , "H. Peter Anvin" , x86@kernel.org, LKML Subject: Re: [PATCH v2] x86: Bypass legacy PIC and PIT in ACPI hardware reduced mode References: <54FFC593.6070002@linux.intel.com> <20150311062324.GA29788@gmail.com> In-Reply-To: <20150311062324.GA29788@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2015/3/11 14:23, Ingo Molnar wrote: > > * Li, Aubrey wrote: > >> On a platform in ACPI Hardware-reduced mode, the legacy PIC and PIT >> may not be initialized even though they may be present in silicon. >> Touching these legacy components causes unexpected result on system. > > s/causes unexpected result on system/ > causes unexpected results on the system > >> >> On Bay Trail-T(ASUS-T100) platform, touching these legacy components > > s/On Bay Trail-T(ASUS-T100) platform/ > On the Bay Trail-T(ASUS-T100) platform > > Ok, my final bike shed painting job would be to move the > 'acpi_gbl_reduced_hardware' flag check inside acpi_reduced_hw_init(): > that makes it nicely self-sustained and all in a single place. > > With that fixed it looks good to me. Thanks, I'll cook v3 soon, :-) > > Should I merge it for v4.0 upstream merge, in tip:x86/urgent? > > The 'touches hardware in unexpected ways' aspect qualifies it for > urgent treatment IMO. Currently the unexpected result is that it blocks a low power idle during suspend. I'm not sure if it can be for x86/urgent. But it would be nice if it can be a bug-fix in v4.0. Thanks, -Aubrey > > Thanks, > > Ingo > >