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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 35B38C433DB for ; Thu, 21 Jan 2021 07:52:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D286423356 for ; Thu, 21 Jan 2021 07:51:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727383AbhAUHv2 (ORCPT ); Thu, 21 Jan 2021 02:51:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51036 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726652AbhAUHvL (ORCPT ); Thu, 21 Jan 2021 02:51:11 -0500 Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EC29EC061757 for ; Wed, 20 Jan 2021 23:50:30 -0800 (PST) Received: by mail-pf1-x433.google.com with SMTP id q20so1016979pfu.8 for ; Wed, 20 Jan 2021 23:50:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=ArpukKqgHaMQZrpxDemmGF/e2k0kfVvSSfm28/4Eajg=; b=DxdlftMrvjU0fFdVCZUiVxOENUjQAxQ5q3grNRXS2DaVvl5XJ8zzLYQBo95qvUEk36 Uz+SkBigXiXTjaaQp6MNHvohSlPS2ZxLRX8M1qW88yORg2sNbUMpwe5n7ie6d5C4Yw+J lu2FE6i9VcYG4M0esNqxuhVcTKzjpO46JIFEsa2yNTi6ReS7ms7kgSH7ygTBsM6KuFCA EdjACO5nPmVvNkQKUwZzHb0hd/yMr8LujBfJ/QenS5hiFWRfWtVwdP/EQJwAzSnwrpcx jfbYDXnnRff/7G0Uv2EdJMSRFC9tc1xZ9mw5meLiJiXyVWWsvTlYouO3zoIQKkN6PHGX M1Og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=ArpukKqgHaMQZrpxDemmGF/e2k0kfVvSSfm28/4Eajg=; b=iZab9kKUKEUM7BR2KTMHVaRX5FTnpEXzvFvLot59F1lArt4DX2XmKd096YhdyTwNoD ztaAM2rsXw0vz79Tpn1wMS7dpBkRVeef6dPdO6EUJwJ7CnmE2Jx/dRvgUQpW3Cxtnk/1 I+Wvmd6JEnbWZ/5NRvIBerMJ77TXvbO4xvrhxWDEswbQHjXklR1DX6ssLzArNo8j4Dr4 in7SctSBnyCVZYzjWAVbli/b+hizoRSj1SLBIEPx39gyR5zRt+iogq+Y0Ce71gllAw67 0DjGF/iaL/4DjcGhzGSmPNsRZjz8/VLWK8nVPvIuYgbA+4/xfqBj/1vkc2tso1OPX0IJ yRPA== X-Gm-Message-State: AOAM531Xy5NpOA0UTpjbKPe3DGXSpmMUayJh/s7ZFOLKgNpp9VwAmAY8 1Y4i4mZXs4L9vmVo+F6OT43X X-Google-Smtp-Source: ABdhPJzLO4YjHwLIXAeASc3SG0WAxtF3gM2EPAuV/kqvQN0pQASMkju6ZWl5Pdiq14ij4kWWNA+zNg== X-Received: by 2002:a62:528c:0:b029:19e:4a39:d9ea with SMTP id g134-20020a62528c0000b029019e4a39d9eamr12954725pfb.20.1611215430389; Wed, 20 Jan 2021 23:50:30 -0800 (PST) Received: from thinkpad ([2409:4072:6182:23c4:4d5:e6d9:fc7e:c8e2]) by smtp.gmail.com with ESMTPSA id w20sm5139557pga.90.2021.01.20.23.50.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Jan 2021 23:50:29 -0800 (PST) Date: Thu, 21 Jan 2021 13:20:22 +0530 From: Manivannan Sadhasivam To: Bhaumik Bhatt Cc: linux-arm-msm@vger.kernel.org, hemantk@codeaurora.org, carl.yin@quectel.com, naveen.kumar@quectel.com, jhugo@codeaurora.org, linux-kernel@vger.kernel.org, loic.poulain@linaro.org Subject: Re: [PATCH v2 1/3] bus: mhi: core: Clear devices when moving execution environments Message-ID: <20210121075022.GA30041@thinkpad> References: <1610651795-31287-1-git-send-email-bbhatt@codeaurora.org> <1610651795-31287-2-git-send-email-bbhatt@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1610651795-31287-2-git-send-email-bbhatt@codeaurora.org> Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On Thu, Jan 14, 2021 at 11:16:33AM -0800, Bhaumik Bhatt wrote: > When moving from SBL to mission mode execution environment, there > is no remove callback notification to MHI client drivers which > operate on SBL mode only. Client driver devices are being created > in SBL or AMSS(mission mode) and only destroyed after power down > or SYS_ERROR. If there exist any SBL-specific channels, those are > left open and client drivers are thus unaware of the new execution > environment where those channels cannot operate. Close the gap and > issue remove callbacks to SBL-specific client drivers once device > enters mission mode. > What are the SBL specific channels and the client drivers operating on them? If this is something going to come in future, then this patch can come later. Thanks, Mani