Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp5847625rwl; Tue, 4 Apr 2023 04:43:27 -0700 (PDT) X-Google-Smtp-Source: AKy350bORWN6RN6/g4CpwghhWIKAqN0fpr0cmSdA/WUOyLZzneY1EptJAmiZ5Us96lCunkoxEuwD X-Received: by 2002:a17:906:ee1:b0:862:c1d5:ea1b with SMTP id x1-20020a1709060ee100b00862c1d5ea1bmr1901688eji.8.1680608606619; Tue, 04 Apr 2023 04:43:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680608606; cv=none; d=google.com; s=arc-20160816; b=G0a8oTQY3inauOj/c+Fi/Mxi9T8yJ7mI6FoTjouRCB2IqiLTQbVf8pK32UJQfa4TUf t+7wFgU3w8em73jGjiESn++HX6A5Vgim4igZkRa/jSR8Y9m1vB8iM11eBG8SPpbAbDuB 6igf9jZMIF972VjDatdGKBWp+14kdBLpvERuClwATmtRk78UFKXE2Fhv6nzNKtwl/Hxs XtOpp/uHNzTCZQKs2TyxgLTOfnSlvKrl4KQffohQt4bZKdiE9Nmjr4Yd9d6pi+YooOLG szLHYE7wL4ABi3Y6L4CvgbpBAjIQDv9xj0bd4pgxzQKxf5nQC3XwtBxN7drQjHD8zSCy 0E1Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=GmjJsJm21oPHNo+PcdvGHfO5ln3XTZzt+nEvRYSWxSM=; b=r6/0t9ndy7NH/u11yVLngSm+DDzBLy30A6y2zaBrPm2C6/yZgFVYZFz1rlA8zUTm65 pP50V0/Y3MWP7GBYU8L3s8Zfy7dsyl/zhd3oM1doyP3Igsjk0K4AZ0d0vCS1ce72oxtR Jpk6dKd5FNtYJSZysUO2ESATSExUzs+sKjsbDkT9zyJ5rGo4Q3ab3IMmOqg6AJ1msO9U 28tpkYQA0GV1RT6/l2SdVsEe+uom98aHpQvrBt3wryulcjti0Kl4BCBVvV/UNAz7TVMq /muBqkDo6dDnq9PatI492bCCZV6knqn7tTM2lV3P2kX6NEMPwo+X7xwc1YpoznyGSrLW uR1g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=KetfXc+C; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m16-20020aa7c2d0000000b004fbe5ca598fsi10263713edp.643.2023.04.04.04.43.02; Tue, 04 Apr 2023 04:43:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=KetfXc+C; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234565AbjDDLl2 (ORCPT + 99 others); Tue, 4 Apr 2023 07:41:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46542 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234075AbjDDLl1 (ORCPT ); Tue, 4 Apr 2023 07:41:27 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4E77BD8; Tue, 4 Apr 2023 04:41:26 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D82AB63286; Tue, 4 Apr 2023 11:41:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BAB21C433EF; Tue, 4 Apr 2023 11:41:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1680608485; bh=LActs9cB9p0LQYEk8rDW9gaV5d6wDeHIvJjBxEW4Z9k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=KetfXc+CtxS3y+yBADDAT3q6MNhLMzEghU47hmbcUaKZIdblmbGA/DjkZArBws7D8 zM92aPI79ajJWYSUh2ithE/sjFtwsMVmZJH4po7yQIs0HcgUXB0Qoy9s/cqD5Em0mI 53HXpIKvQ+VuswMGWoNfTdSZtR6zeIA90TqTDZM6ZS2wKaZwKKnGulm+Tym4HtEDHE d2a/dxuLzjCd36MWbpSIBPd43SBwhnyma1I8rB9yyRdvMLDTYl2npgWkFENIr+jsT+ Muo+OqfEeLqAiz2V0YgL99aPcpKXAN3ilN3OyOFQSWagg/eK4VSrZ/HDcXopoMxCkS OZPJG1jDspUKg== Date: Tue, 4 Apr 2023 12:41:19 +0100 From: Mark Brown To: Jaewon Kim Cc: Krzysztof Kozlowski , Andi Shyti , Alim Akhtar , Rob Herring , linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Chanho Park Subject: Re: [PATCH 1/3] spi: s3c64xx: support spi polling mode using devicetree Message-ID: References: <20230404060011.108561-1-jaewon02.kim@samsung.com> <20230404060011.108561-2-jaewon02.kim@samsung.com> <4b652b3c-20e1-1d87-1ee3-3aab43507100@samsung.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qTiTBPXDz7t7Bp9O" Content-Disposition: inline In-Reply-To: <4b652b3c-20e1-1d87-1ee3-3aab43507100@samsung.com> X-Cookie: Being ugly isn't illegal. Yet. X-Spam-Status: No, score=-5.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,SPF_HELO_NONE, SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --qTiTBPXDz7t7Bp9O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 04, 2023 at 08:17:13PM +0900, Jaewon Kim wrote: > On 23. 4. 4. 19:54, Mark Brown wrote: > > On Tue, Apr 04, 2023 at 03:00:09PM +0900, Jaewon Kim wrote: > >> This patch adds new 'samsung,spi-polling' property to support polling mode. > >> In some environments, polling mode is required even if DMA is supported. > >> Changed it to support not only with quick but also optinally with > >> devicetree. > > Why would this be required if we can use DMA? If this is a performance > > optimisation for small messages the driver should just work out when to > > choose PIO over DMA like other drivers do. It is hard to see this as a > > hardware property which should be configured via DT. > We are providing a VM environment in which several Guest OSs are running. > If Host OS has DMA, GuestOS should use SPI as polling mode. This sounds like some sort of virtualised environment with passthrough? If that's the case then the host OS will be in control of the device tree provided to the guest so it simply shouldn't be describing the DMA configuration if it doesn't want the guest to use DMA for some reason. There's no value in describing the DMA the guest shouldn't use then providing an additional property telling the guest not to pay attention to the DMA when we could simply not do the first step. --qTiTBPXDz7t7Bp9O Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmQsDN4ACgkQJNaLcl1U h9C3KAf8DV4SXi2OjERrSCUUpD1ubMl2HYYT7sakdZVKmhuWQGTJTflIZrYSvRZa ay7Kj0GfvKczDNDmj0YFQXUc1XO2t6lvCwG6fOGAyLK/2yXk2hLuCxkQOSS0q+gr 2Rc79LUas5oAAPZtdJm9dSfqoJunAtG8367ZGGrAtDlf4NeQqOkudgVBoXw+mFV/ 4HCt0xk63edTgijrBS0ZKSBTvj2tjjWcww0HdF9rmuP020iBJ0rD91D3lXP/oKhk CNWHiFFM6KVADYL7O0Wk646L/4BC8AE9POkZXzns4d1hVHWVyIwz9gSEZpMZ764F ZgiLCU5fVdfqj9AR2V2m/kU/MorzUw== =lg0g -----END PGP SIGNATURE----- --qTiTBPXDz7t7Bp9O--