Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp441347imm; Tue, 7 Aug 2018 22:56:25 -0700 (PDT) X-Google-Smtp-Source: AA+uWPwGm8EMJ5Twdr5l42NgVj5BKLjvtQkipFRWSIVpDnAILtZUBn4B6Ieq4bG5uxCjxVXTIpGM X-Received: by 2002:a65:6104:: with SMTP id z4-v6mr1161346pgu.361.1533707785394; Tue, 07 Aug 2018 22:56:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533707785; cv=none; d=google.com; s=arc-20160816; b=V5ZE+57rRSpoqlMAKQOfvJOCU5abK7DxASDImneNUmN7hRPOc/cCyuf5yQSqEqOXMJ nZbMgyiKTNniWQ+sJbFmczIFce5HyAPx0/1cPSzDfCwzRYu6afZSa1s6Bz/+CoZnWApl 863R3UTuYFZ/rXEgKrD1VbuBL2NWROR9mFspgwaD4nN5pYQcctZ5VGM6glNQD9/ibxCR tJn3/XEA4TQAWW9Z4v0Du9aYfMxvQpWJDZdRaWIEj9cwe1YI46Cj9Eiihiq7g5gFT9qb nszRZvfJebQdnqsx1iw3XUxgD8VZhDuZM4pQavzmUQsWPR8S13W6SjsHv+zdQcOoS4lX lRfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:subject:content-transfer-encoding :mime-version:organization:references:in-reply-to:date:cc:to:from :message-id:arc-authentication-results; bh=DQzUjfumeM8kCzgve29oiN5ZGVvR7G9AClS2Li+1/T8=; b=EZCKW2JurbYUnkxxWqp/UCWyBOkp9B57GGvs+N8wGzL1eL82eqDbLlwswLH1icl6ix A5MVPSxRyYFq40nGKs+fih4ZT74CwdIle5ymMVtTK1el19HJfn6wKdtxGR84JWfwmBNW wG+w6w8foCp2lcHmcTMmRfstPzXtzpw7yLe+gD1UuQaAHcUW0LmzTBcZhY8z7VYVBwsh K82EEYSiWELt6fUIqhCzUmBEcn7sAudEhC5WlbEqFaQAjcrfVnRGHE+ke8hZn5YudZPT 3c9RFKPVy8xl0P5y0AXgEhG/XUDTQvN0lWJNM4jOrVwQoUTw6bxu4F84Pe+9mmtJPyAb jwQQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f9-v6si3545079pgi.12.2018.08.07.22.56.11; Tue, 07 Aug 2018 22:56:25 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727052AbeHHINQ (ORCPT + 99 others); Wed, 8 Aug 2018 04:13:16 -0400 Received: from baldur.buserror.net ([165.227.176.147]:54876 "EHLO baldur.buserror.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726542AbeHHINP (ORCPT ); Wed, 8 Aug 2018 04:13:15 -0400 Received: from [2601:449:8400:7293:12bf:48ff:fe84:c9a0] by baldur.buserror.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1fnHMl-0007ub-Od; Wed, 08 Aug 2018 00:50:41 -0500 Message-ID: <7526e100693e4db9bb3adf576254b2161086dfe8.camel@buserror.net> From: Scott Wood To: Bharat Bhushan , Rob Herring Cc: "benh@kernel.crashing.org" , "paulus@samba.org" , "mpe@ellerman.id.au" , "galak@kernel.crashing.org" , "mark.rutland@arm.com" , "kstewart@linuxfoundation.org" , "gregkh@linuxfoundation.org" , "devicetree@vger.kernel.org" , "linuxppc-dev@lists.ozlabs.org" , "linux-kernel@vger.kernel.org" , "keescook@chromium.org" , "tyreld@linux.vnet.ibm.com" , "joe@perches.com" Date: Wed, 08 Aug 2018 00:50:38 -0500 In-Reply-To: References: <1532684881-19310-1-git-send-email-Bharat.Bhushan@nxp.com> <1532684881-19310-4-git-send-email-Bharat.Bhushan@nxp.com> <20180807180938.GA13623@rob-hp-laptop> Organization: Red Hat Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.1-2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2601:449:8400:7293:12bf:48ff:fe84:c9a0 X-SA-Exim-Rcpt-To: bharat.bhushan@nxp.com, robh@kernel.org, benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au, galak@kernel.crashing.org, mark.rutland@arm.com, kstewart@linuxfoundation.org, gregkh@linuxfoundation.org, devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, keescook@chromium.org, tyreld@linux.vnet.ibm.com, joe@perches.com X-SA-Exim-Mail-From: oss@buserror.net X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on baldur.localdomain X-Spam-Level: X-Spam-Status: No, score=-17.5 required=5.0 tests=ALL_TRUSTED,BAYES_00, GREYLIST_ISWHITE autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * -15 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -1.5 GREYLIST_ISWHITE The incoming server has been whitelisted for this * recipient and sender Subject: Re: [RFC 3/5] powerpc/mpic: Add support for non-contiguous irq ranges X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +0000) X-SA-Exim-Scanned: Yes (on baldur.buserror.net) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2018-08-08 at 03:37 +0000, Bharat Bhushan wrote: > > -----Original Message----- > > From: Scott Wood [mailto:oss@buserror.net] > > Sent: Wednesday, August 8, 2018 2:34 AM > > To: Rob Herring ; Bharat Bhushan > > > > Cc: benh@kernel.crashing.org; paulus@samba.org; mpe@ellerman.id.au; > > galak@kernel.crashing.org; mark.rutland@arm.com; > > kstewart@linuxfoundation.org; gregkh@linuxfoundation.org; > > devicetree@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; linux- > > kernel@vger.kernel.org; keescook@chromium.org; > > tyreld@linux.vnet.ibm.com; joe@perches.com > > Subject: Re: [RFC 3/5] powerpc/mpic: Add support for non-contiguous irq > > ranges > > > > On Tue, 2018-08-07 at 12:09 -0600, Rob Herring wrote: > > > On Fri, Jul 27, 2018 at 03:17:59PM +0530, Bharat Bhushan wrote: > > > > Freescale MPIC h/w may not support all interrupt sources reported by > > > > hardware, "last-interrupt-source" or platform. On these platforms a > > > > misconfigured device tree that assigns one of the reserved > > > > interrupts leaves a non-functioning system without warning. > > > > > > There are lots of ways to misconfigure DTs. I don't think this is > > > special and needs a property. > > > > Yeah, the system will be just as non-functioning if you specify a valid- > > but- > > wrong-for-the-device interrupt number. > > Some is one additional benefits of this changes, MPIC have reserved regions > for un-supported interrupts and read/writes to these reserved regions seams > have no effect. > MPIC driver reads/writes to the reserved regions during init/uninit and > save/restore state. > > Let me know if it make sense to have these changes for mentioned reasons. The driver has been doing this forever with no ill effect. What is the motivation for this change? -Scott