Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp394664ybh; Sat, 7 Mar 2020 00:47:50 -0800 (PST) X-Google-Smtp-Source: ADFU+vsQdcF73ZoLNVNx5LcUsjm/w0XIYhVhV+sD6uk3ZvcqsfSiXfJNlSovBzVONW7URdHy80ex X-Received: by 2002:a05:6808:610:: with SMTP id y16mr5355253oih.89.1583570870038; Sat, 07 Mar 2020 00:47:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583570870; cv=none; d=google.com; s=arc-20160816; b=l2/RMVCOY9hciCVvj7n91HOX9GQlLQd2yPBlNA6UVb38WIAbBRNkBy9Ty31Eai//4P GLup0+sWFaJVFjQ83lWsPWlNoRgojGtBSixGOks8DrOZAagLZ+Pe1YLn1eDTzh+2nXA1 i2fIWfX6bR+4wzLY0BEEIbFoothdWGmApmY6v2hK3kx7dEGn4edCcJW3VA2xfgeEfr3t /BQb+GuEtF5oyf14zFhNtkgVT82FnPufE1gTnyFlmmerlGS9BaISDIiE0nyzQzJYGBHB rin2gN774LuRG13M2+cQFvBkahNRjVxO5f1RQuRus7lhGEIjT7x36VTixtSdFgtppLCo 9NGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=A5IBa7YS5pY2pXVAEyIKuPIpit5LygIzy6jjPBTccY0=; b=hQK/NiezTfDvIXsHSXSrHk5YprcE7aKJLife5AynQaSYn02J1dJ3MzZYHNsqHJKelV cUe8mSygkHL5M+nvRojE3xzJOtxQtHuJ1WfIzzkuRhoBSWpIwQC54/tir5rW6c4FycVS 2+MFLvJIukwC+HOe8mWgLzvj0vEOWm1WydzsQt9NTpLXnOjhkcghRwXrivo325cXn5wC ncqrPwaja+JVZukHPPPvjJKceyOHLzrNxX8WSgo1mCfAY4hFsyFNbSRyIVw+DozK4L4o mXkgbRAXlBf+hWtpoVyGBb+DBlhLJxvnj/rJTh1oaY3+s7sqYNsQZIVe1U/2xDzIz4vX Xz5w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=IsQNFpEO; 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 i1si3035250otk.2.2020.03.07.00.47.38; Sat, 07 Mar 2020 00:47:50 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=default header.b=IsQNFpEO; 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 S1726154AbgCGIrR (ORCPT + 99 others); Sat, 7 Mar 2020 03:47:17 -0500 Received: from mail.kernel.org ([198.145.29.99]:40944 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725907AbgCGIrQ (ORCPT ); Sat, 7 Mar 2020 03:47:16 -0500 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 60FAD2070A; Sat, 7 Mar 2020 08:47:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1583570833; bh=kj/tz8uKDDAeZwkPo7mMFm2l9KjE7wjG93hY1K6V3nc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=IsQNFpEObKzYDo79u4Ass2VY8Ixe4DZQB8f5a255DpEv5b4vgAh022s+uQ3hWvFiS 7bmkbPzO12ePSrDSCDkftCfwjO+WdB5Me6UPXoKKRId5MOkGO/P/KEkyfvOa5EU7gF fPVcEdE+mqifUE+y6kgJVcMAHYQDyLpBDBsqmDio= Date: Sat, 7 Mar 2020 09:47:11 +0100 From: 'Greg KH' To: Jolly Shah Cc: Rajan Vaja , "ard.biesheuvel@linaro.org" , "mingo@kernel.org" , "matt@codeblueprint.co.uk" , "sudeep.holla@arm.com" , "hkallweit1@gmail.com" , "keescook@chromium.org" , "dmitry.torokhov@gmail.com" , Michal Simek , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v2 1/4] firmware: xilinx: Add sysfs interface Message-ID: <20200307084711.GA3877697@kroah.com> References: <20200128062814.GA2097606@kroah.com> <4EF659A1-2844-46B9-9ED6-5A6A20401D9D@xilinx.com> <20200131061038.GA2180358@kroah.com> <20200131093646.GA2271937@kroah.com> <3ef20e9d-052f-665c-7fc8-69a1f8bc9bd2@xilinx.com> <20200214171005.GB4034785@kroah.com> <20200215005235.GA32359@kroah.com> <23a785fd-3874-b71a-c0f5-d117a9058abf@xilinx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <23a785fd-3874-b71a-c0f5-d117a9058abf@xilinx.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 06, 2020 at 03:55:46PM -0800, Jolly Shah wrote: > Hi Greg, > > > ------Original Message------ > > From: 'Greg Kh' > > Sent: Friday, February 14, 2020 4:52PM > > To: Jolly Shah > > Cc: Rajan Vaja , Ard.biesheuvel@linaro.org > , Mingo@kernel.org , > Matt@codeblueprint.co.uk , Sudeep.holla@arm.com > , Hkallweit1@gmail.com , > Keescook@chromium.org , Dmitry.torokhov@gmail.com > , Michal Simek , > Linux-arm-kernel@lists.infradead.org , > Linux-kernel@vger.kernel.org > > Subject: Re: [PATCH v2 1/4] firmware: xilinx: Add sysfs interface > > > > On Fri, Feb 14, 2020 at 04:37:16PM -0800, Jolly Shah wrote: > > > > Just make the direct call to the firmware driver, no need to muck around > > > > with tables of function pointers. In fact, with the spectre changes, > > > > you just made things slower than needed, and you can get back a bunch of > > > > throughput by removing that whole middle layer. > > > > > > > > > > arm,scpi is doing the same way and we thought this approach will be more > > > acceptable than direct function calls but happy to change as suggested. > > > > Just because one random tiny thing does it the wrong way does not mean > > to focus on that design pattern and ignore the thousands of other > > apis/interfaces in the kernel that do not do it that way :) > > > > > > So go do that first please, before adding any new stuff. > > > > > > > > Now for the ioctl, yeah, that's not a "normal" pattern either. But > > > > right now you only have 2 "different" ioctls that you call. So why not > > > > just turn those 2 into real function calls as well that then makes the > > > > "ioctl" call to the hardware? That makes things a lot more obvious on > > > > the kernel driver side exactly what is going on. > > > > > > > > > > Sure as i understand firmware driver will provide real function calls to be > > > used by user drivers and underneath it will call ioctl for desired > > > operation. Please correct if I misunderstood. > > > > You do not misunderstand. > > Submitted v3 with required changes. Please review. Will do, when I get to it, relax :)