From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 33F31C433EF for ; Tue, 18 Jan 2022 13:50:54 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id CF39D83818; Tue, 18 Jan 2022 14:50:51 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; unprotected) header.d=ti.com header.i=@ti.com header.b="qgK0M0x+"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 4A8F98381F; Tue, 18 Jan 2022 14:50:50 +0100 (CET) Received: from lelv0142.ext.ti.com (lelv0142.ext.ti.com [198.47.23.249]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 9250783180 for ; Tue, 18 Jan 2022 14:50:46 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=nm@ti.com Received: from lelv0266.itg.ti.com ([10.180.67.225]) by lelv0142.ext.ti.com (8.15.2/8.15.2) with ESMTP id 20IDoZdn121084; Tue, 18 Jan 2022 07:50:35 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1642513835; bh=LPRFv781P8oHlbrz4xT8XfF1Muh3gUXhrK0zg2PumPE=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=qgK0M0x+VREpE7lbSdRJPMa3H0hd0pNsur6ufhmXY444RSobknoRGytbdAfUV/G0M HKrIrX/41MfH+Pj4g+HAb1p1+miTbabWwjLN9EXpmRy5/LoBDItLReAIquFELTRB/4 Z6Pd2KwDqOocCiKwVpn4PWxwtJ/c5U/BZunjAtZs= Received: from DFLE100.ent.ti.com (dfle100.ent.ti.com [10.64.6.21]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 20IDoZXc113571 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 18 Jan 2022 07:50:35 -0600 Received: from DFLE109.ent.ti.com (10.64.6.30) by DFLE100.ent.ti.com (10.64.6.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.14; Tue, 18 Jan 2022 07:50:34 -0600 Received: from lelv0326.itg.ti.com (10.180.67.84) by DFLE109.ent.ti.com (10.64.6.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.14 via Frontend Transport; Tue, 18 Jan 2022 07:50:34 -0600 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by lelv0326.itg.ti.com (8.15.2/8.15.2) with ESMTP id 20IDoYMw090939; Tue, 18 Jan 2022 07:50:34 -0600 Date: Tue, 18 Jan 2022 07:50:34 -0600 From: Nishanth Menon To: Tom Rini CC: Aswath Govindraju , , Wolfgang Denk , Hari Nagalla , David Huang , Keerthy , Dave Gerlach , Suman Anna , Tero Kristo , Kishon Vijay Abraham I , Vignesh Raghavendra , Christian Hewitt , Tim Harvey , Peter Robinson , Kever Yang , Neil Armstrong , Fabio Estevam , Andre Przywara , Jaehoon Chung , Sean Anderson , Lukasz Majewski Subject: Re: [PATCH v2 01/20] remoteproc: k3_system_controller: Support optional boot_notification channel Message-ID: <20220118135034.drqsredv6y7xxuyl@sandpit> References: <20220111075545.1880-1-a-govindraju@ti.com> <20220111075545.1880-2-a-govindraju@ti.com> <20220113141228.GO9207@bill-the-cat> <8e646a92-daf9-6457-d8dc-94b226647442@ti.com> <39a92323-8c8f-32aa-60b2-b4c43739a9f3@ti.com> <20220117135413.GM9207@bill-the-cat> <87211b68-1cf5-c105-ba4c-2b61ddb56764@ti.com> <20220118125028.GM2631111@bill-the-cat> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20220118125028.GM2631111@bill-the-cat> User-Agent: NeoMutt/20171215 X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean On 07:50-20220118, Tom Rini wrote: > On Tue, Jan 18, 2022 at 11:26:50AM +0530, Aswath Govindraju wrote: > > Hi Tomi, > > > > On 17/01/22 7:24 pm, Tom Rini wrote: > > > On Mon, Jan 17, 2022 at 12:22:52PM +0530, Aswath Govindraju wrote: > > >> Hi Tom, > > >> > > >> On 17/01/22 11:01 am, Aswath Govindraju wrote: > > >>> Hi Tom, > > >>> > > >>> On 13/01/22 7:42 pm, Tom Rini wrote: > > >>>> On Tue, Jan 11, 2022 at 01:25:26PM +0530, Aswath Govindraju wrote: > > >>>> > > >>>>> From: Nishanth Menon > > >>>>> > > >>>>> If there is an optional boot notification channel that an SoC uses > > >>>>> separate from the rx path, use the same. > > >>>>> > > >>>>> Signed-off-by: Nishanth Menon > > >>>>> --- > > >>>>> .../remoteproc/k3-system-controller.txt | 3 +++ > > >>>>> drivers/remoteproc/k3_system_controller.c | 20 ++++++++++++++++++- > > >>>>> 2 files changed, 22 insertions(+), 1 deletion(-) > > >>>> > > >>>> Binding docs are rst these days, so we should sync with upstream and > > >>>> then this property is already there, right? > > >>>> > > >>> > > >>> I will create a followup patch to convert documentation to rst. Also, > > >>> about the property, mbox-names property is already present but > > >>> "boot_notify" is a newly added channel and not are required property. > > >>> So, this was additionally added. > > >>> > > >> > > >> One more question regarding documentation, should it be changed to rst > > >> or yaml, as this is a device tree binding? > > > > > > I mis-spoke, yeah. It should be yaml and pushed upstream first, then > > > brought back here. > > > > > > > I am sorry, I have one more question. This above documentation file is > > not present in kernel documentation, so I did not understand how can > > this be pushed there first. > > > > Also, as converting to yaml would be a different work. Wouldn't it be > > better to separate that work from this series? > > Sigh, it should have been upstreamed first. So yeah, make the changes > you need here now and then please start pushing it upstream, thanks. Just catching up, but, this goes back to the same question -> this has no relevance beyond R5. what is our current state of sending non-linux dt pieces to upstream kernel? There wont be a driver for sure, neither will there be a direct user in kernel.. -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D