Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp1772108pxx; Fri, 30 Oct 2020 20:12:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyVKxk7tIWf6cxmsrvplOQwKXOClX/TETIz72lW+m8wLggAcF6yAmtm6lBPl/bCoFoJGY2l X-Received: by 2002:a50:9ec6:: with SMTP id a64mr5636905edf.382.1604113948486; Fri, 30 Oct 2020 20:12:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1604113948; cv=none; d=google.com; s=arc-20160816; b=WJzitAg07YU0gT8Ol5UGnnCJ+wMvRxp8wD+7diQ6UDCp2kx296pUa7uL1fPNqOx+Jp qCt40JJKefG7ZC3bvm94CAHhq0Wet96EwMLY/1YD6heHbtUNdYb13ronsrFjcYhkHK6O UBRPHLgNBin0ocUNrOgTDiZlsvGaMzIC1Kdshle7atqZHVsTsA0wKEo+KLMJXhzUPH0I qVgM7W0qcsm64C6phgRwssOdF8MZUy/yESfpmLug02XMeqBt/i/Mw38NXDdyxY3Yea0N HWipq+p8WD0xsYwwcN9ypzKRoIwuQ57hQMi7XcwD7j9UrcoD/FUY7/gdzOcqXnZr+XE/ wC9w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=80Rbj4Zv4zgFU/y9w5qHyIUsSC7ZojKWfXg4J90qtUw=; b=E/jEBmYLcTzui5VUiZiZx9yLOBuAleygzrLncD1mgZhDZ473TDgMyNO6B1s3NLgkwj Vg/Jf1tkKiqk/B/CgHKYQl9KeV/UcfrQX5L2ML66+JuNb6+JNEpRlTMFm76VKf78vN2e fogaaw7l/zaKU6P09dWUddRgLVOwHLVpmMb2d75tLAeLjafQLiozWsCBQw29e9Ecs4ev 3pPo4hA9s5azjuW5H8FfsDhvS+f2FCv2eJmLVnWJdjpZiKhmXg8B9yu8tinF5nFdHcCg zBlyt5dJoGDEETk/4+N+2M1Fv9B4D4pfE6E6Lwgo8HvfIQBs7b6HqwbMpTZlSoz/BekC WfWw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g8si7066936ejm.497.2020.10.30.20.12.05; Fri, 30 Oct 2020 20:12:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725856AbgJaDK2 (ORCPT + 99 others); Fri, 30 Oct 2020 23:10:28 -0400 Received: from szxga03-in.huawei.com ([45.249.212.189]:2359 "EHLO szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725536AbgJaDK2 (ORCPT ); Fri, 30 Oct 2020 23:10:28 -0400 Received: from dggeme755-chm.china.huawei.com (unknown [172.30.72.53]) by szxga03-in.huawei.com (SkyGuard) with ESMTP id 4CNPLp5ws2z503m; Sat, 31 Oct 2020 11:10:26 +0800 (CST) Received: from [10.140.157.68] (10.140.157.68) by dggeme755-chm.china.huawei.com (10.3.19.101) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Sat, 31 Oct 2020 11:10:26 +0800 Subject: Re: Using fixed LPI number for some Device ID To: Thomas Gleixner , Marc Zyngier CC: Jason Cooper , References: <0baed5b0-6cbe-6492-b4af-fe758f461602@huawei.com> <04e31996-6eb8-3bb9-e333-bc46eebe3d7a@huawei.com> <87eelfksm1.fsf@nanos.tec.linutronix.de> From: Dongjiu Geng Message-ID: <7205d3e0-a03a-a06c-f3f4-9a28e58931e0@huawei.com> Date: Sat, 31 Oct 2020 11:10:24 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <87eelfksm1.fsf@nanos.tec.linutronix.de> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.140.157.68] X-ClientProxiedBy: dggeme713-chm.china.huawei.com (10.1.199.109) To dggeme755-chm.china.huawei.com (10.3.19.101) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020/10/31 10:59, Thomas Gleixner wrote: > On Sat, Oct 31 2020 at 10:19, Dongjiu Geng wrote: >> Hi Marc, >> Sorry to disturb you, Currently the LPI number is not fixed for >> the device. The LPI number is dynamically allocated start from 8092. >> For two OS which shares the ITS, One OS needs to configure the device >> interrupt required by another OS, and the other OS uses a fixed >> interrupt ID to respond the interrupt. Therefore, the LPI IRQ number >> of the device needed be fixed. I want to upstream this feature that >> allocate fixed LPI number for the device that is specified through >> the DTS. What is your meaning? Thanks > > What's the purpose of resending the same thing within less than 24 > hours? Do you really expect maintainers to be available 24/7 and being Sorry for the noise, Because Marc rarely uses the ARM email address, so I replace to use Marc's kernel.org address instead of ARM email address. > able to respond within less than a day? > > > . >