Received: by 10.213.65.68 with SMTP id h4csp3209102imn; Tue, 3 Apr 2018 00:21:03 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+bodzM7uXzf4E33Prjl3a9StiIjqJJacDRgJROhskrh23X8QsPpkTNZhyzHJLiBsj6MvHK X-Received: by 10.101.69.4 with SMTP id n4mr8474207pgq.101.1522740063884; Tue, 03 Apr 2018 00:21:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522740063; cv=none; d=google.com; s=arc-20160816; b=JiHpMvxAqobabNN+Ah85MsZsvu0+4ajJWqVLHfBBnlv5B+oktfSC2X2HJjHPM3dPTZ DpMI7U1yDpZArd6VwZ7GYo+YlTQOeXXhflqH/Tuu89bmMOQLBf3SLIUkcOR4Y5n3BHGW xuSlmqsqCGkjYXyrH2h/YnR4UrHy5sgRxROf9b7Xq2n1pImUdYlcjRXko8uSG8MBgGpo mZ4VVPj20k62rIUswnsJM0RU8qYkFPFh0+qabI0rlU4RMghBRhQBztTLreEDrJl90ErE JKogkx1nudQmi2k0rCZmUf+k6LeEPovXBZFviziV5NU26q0FhszyW4FO6umPu6vmNXqJ tz7A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=LIcJNfCw9LHXF8va94GletnGDrPrftTz4026S2lo1fc=; b=L7Fbei2YN05bgtE2sQHbezuYlgMoNhTVGnCklfXbiC+dElJZgTg6Ari8uGArV2HVfK kqqbysbL9Vwui/B+PcN+oynTLhi6c9LUZHaIhUNUUcSJGGBhmHLf8Tg3byEXyz7Vpay2 2lcwZ/eYzJFAPByDR5PIHdQwjO1iwLzeTRDCBxkwiC0Zridvni3vVuMAzmUk65624VXL azqq7GudcdrCIOPaTB1LdFidlXY0MpKLVCFCJ5w/HyMldugx4HgF7bBeO348IgpPavCM RfOoXPuN1g5hOYOsc9bE0aU3jldsIyyI68ubmNOrI97MoCEs//LWQ12bsEpi78OCM7/E Huog== ARC-Authentication-Results: i=1; mx.google.com; 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 d2-v6si2219152plh.121.2018.04.03.00.20.50; Tue, 03 Apr 2018 00:21:03 -0700 (PDT) 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; 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 S1754972AbeDCHSr (ORCPT + 99 others); Tue, 3 Apr 2018 03:18:47 -0400 Received: from mail.bootlin.com ([62.4.15.54]:37025 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754938AbeDCHSp (ORCPT ); Tue, 3 Apr 2018 03:18:45 -0400 Received: by mail.bootlin.com (Postfix, from userid 110) id 2B6F62075F; Tue, 3 Apr 2018 09:18:44 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.bootlin.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT, URIBL_BLOCKED shortcircuit=ham autolearn=disabled version=3.4.0 Received: from localhost (242.171.71.37.rev.sfr.net [37.71.171.242]) by mail.bootlin.com (Postfix) with ESMTPSA id 049B020713; Tue, 3 Apr 2018 09:18:44 +0200 (CEST) Date: Tue, 3 Apr 2018 09:18:43 +0200 From: Alexandre Belloni To: Peter Rosin Cc: Boris Brezillon , Josh Wu , Cyrille Pitchen , linux-kernel@vger.kernel.org, Nicolas Ferre , Marek Vasut , linux-mtd@lists.infradead.org, Richard Weinberger , Brian Norris , David Woodhouse , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] mtd: nand: raw: atmel: add module param to avoid using dma Message-ID: <20180403071843.GI14180@piout.net> References: <20180329131054.22506-1-peda@axentia.se> <20180329153322.5e2fc1e7@bbrezillon> <20180329154416.5c1a0013@bbrezillon> <20180402142249.7e076a64@bbrezillon> <20180402212843.164d5d21@bbrezillon> <8e35701f-1bfa-c9c0-62e6-48ed19d7ba37@axentia.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8e35701f-1bfa-c9c0-62e6-48ed19d7ba37@axentia.se> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/04/2018 at 22:23:17 +0200, Peter Rosin wrote: > >> No, but did it again and checked, see transcript below. > > > > I don't use devmem2. Is 'readback' information accurate or is it > > always what's been written? Because when you write 0x33 to 0xFFFFECBC, > > 0x33 is read back, but just after that, when you read it again it's 0. > > Looking at the devmem2 source, it seems very likely that the compiler > optimizes out the read and thus outputs what has been written. > At least on x86, it is not optimized out. -- Alexandre Belloni, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com