Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp1767801pxx; Fri, 30 Oct 2020 20:02:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwAz8m6Ri5EN+k53Xwu1zBwrjVOPl7IHPIlestuOpVLoMo10r0Jilu+7AodfZfMvK2o3XiD X-Received: by 2002:aa7:d4d8:: with SMTP id t24mr5877903edr.247.1604113343812; Fri, 30 Oct 2020 20:02:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1604113343; cv=none; d=google.com; s=arc-20160816; b=TyOo5rx565VSN3IK7duoIe4OG0tL8mhm3pYM8Agb6vI9VLaqUxiqiNGpRIZhCPqJUs OMruSVI8T1eUMJ6alXp02S2Y434OttUjHf6pTX3yJEqItyrMNgQXKOOdOAxUIkw18Npg Ed+TCdQvsfhyyOL0UTex5LWMGT2FvzJuFYAZNjRwSqkllQSEEsIe6vZ+84fKVftEnAcT L7KBCDMRv62gGjokVsxDvWtUgUtyrcHLFHcndNZ04zZZkcvdz0kXgCSPpf2SbjjtYsUE RX84IJOeYhyDWpQ1H1Y2bnQ5q8CnohgEsr61bxVnLrdr7gJpBbjK/7HUpuTh5axtzxFc GHXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:dkim-signature:dkim-signature:from; bh=6uiNh5DlF5wTnHdgy+YpD+SqJcx0IkmhXz5iicz0GMY=; b=sg7Vfjz71CZXwT6N2A4WZk93shpG8d5pb45wilFFVRCBjU/UouWqXh1VVDxCX8512k DQnB3CLgVjMGU+8oN0nGjIPPv2MEXnEVCtdPYEcZ5TNBfSQljoX+Sv9m11oDjH9YL2kR /IuklehMTwoAIV+1nCieuSuBTpQKkXHjJtNrIAXT8/2UfepL8xgcD6mNM/NitQW/0fhk kFEL4WbMMePEQIVcqOd0wzEzyESZEipw2eI9AYtVxtwum37lGYpHBPPRNBQI6mrYEB8Z YeE2fWFD6eCUGneyf4tX0tNpGKL8DxXjA0FjJF1Ca0P4GvGuTzBSLoh7t46HeO64KodG BiWA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b="u0jS/W4Z"; dkim=neutral (no key) header.i=@linutronix.de header.b=sXLfoSJJ; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f17si5936491edr.158.2020.10.30.20.02.00; Fri, 30 Oct 2020 20:02:23 -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; dkim=pass header.i=@linutronix.de header.s=2020 header.b="u0jS/W4Z"; dkim=neutral (no key) header.i=@linutronix.de header.b=sXLfoSJJ; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725856AbgJaC7w (ORCPT + 99 others); Fri, 30 Oct 2020 22:59:52 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:46482 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725536AbgJaC7w (ORCPT ); Fri, 30 Oct 2020 22:59:52 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1604113190; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=6uiNh5DlF5wTnHdgy+YpD+SqJcx0IkmhXz5iicz0GMY=; b=u0jS/W4ZA0MqKNeekd3D42zHuUiEpyDVvJspZyugAuvhh63dfnvs/vfX9pPy1beb4YCzMy /WWAQ6i3/9/5WU2PS6Doytd0MepaZ3ki+FxWHswwltaxoq9t7szlpKsGST0sjTsUk+md87 1sCbXKnPkGae8SFeu78b7bJ9EfsUgzQXJUMBPYCBrGBqdBgCHI1e/QRuSlJxgu1cUSaobx exoBAYAyyg9jFbivuamQ7UAhPirRTK2BjObG6eOkyNRAxzHyWypUiWjrwalAbLK50nlKzt rmeAohrYTvriLTE4b1p+fzNZsWSp92P3EjZOGk9ta7iCjlc7QFvF0STjCFLfyQ== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1604113190; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=6uiNh5DlF5wTnHdgy+YpD+SqJcx0IkmhXz5iicz0GMY=; b=sXLfoSJJWt0ILL0GgqzWEDIpCFjn9zuGoLx5jMOiMu1MtButFb/A3+GqydCSWzn0jsg0JO aw2KUI0cnUsxAUDA== To: Dongjiu Geng , Marc Zyngier Cc: Jason Cooper , linux-kernel@vger.kernel.org Subject: Re: Using fixed LPI number for some Device ID In-Reply-To: <04e31996-6eb8-3bb9-e333-bc46eebe3d7a@huawei.com> References: <0baed5b0-6cbe-6492-b4af-fe758f461602@huawei.com> <04e31996-6eb8-3bb9-e333-bc46eebe3d7a@huawei.com> Date: Sat, 31 Oct 2020 03:59:50 +0100 Message-ID: <87eelfksm1.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 able to respond within less than a day?