Received: by 10.213.65.68 with SMTP id h4csp3697934imn; Tue, 3 Apr 2018 09:15:13 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+wk2GdVMLkYAuT/DAlRwvJ7BfYPH30HLimp29DXW4yvpPkxmlla2nAvQKEmVFz2tmnGkU3 X-Received: by 10.99.144.199 with SMTP id a190mr9439265pge.359.1522772113517; Tue, 03 Apr 2018 09:15:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522772113; cv=none; d=google.com; s=arc-20160816; b=Pu7ZZVWDUQuTIygEmud6TpHor2GnBl29Yh0Gm8YViNj9rIMI6wN0r4nnlhu1SFnxpL SUSdmLexbeT9Ed/JcUtIaa0K1oG7lSes8zkV8UCR6yUDIpcGmEeXolwXacQCjFShDz8f IVS8OUS0Bwv8nqqw7/yeZ7NAGG54YRIPS3F8DM5pu1ks99vkX5CfbQyW4Tx0XbkZAiQ4 XLpl7tt9hwA29sWuvHOTZ7XI4RwaccDWfvd/u3jmfDChl83yML2vVZeOT+jGMm7c/3J+ Ct5lFzCsjlRxDoqfJujCOZmM1IKPMM14+1ILu7xc/UKXwPx49m5mX3gx9GNDSqSTsgKk otxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature :arc-authentication-results; bh=uH2ZRiOxbRAHM7zrCk2p+lEPWoWsJfL1WBJvHWbOFZQ=; b=ZYypKtHJ5f9/TggGLRZ/Ckw1gcCF9p4G/QXH8Bbutc56bjSxe5iwuOPXGn/6CbEAPu YtlBx+Rc9BJE0FPd638k8ZbNayi/quSaaS0FVhXx+wM0WJ3NcxbJ+IBwsVkNSQcIT4n/ LnY5E59Mg/+pSqJhlZQ8dxw5VtH+U3JD09dE1LDgma1sStvIT0l5mq8oTRp7hDYZkD3f fxXxu0trro8O3cKmDEGbtiRRurIRt0QUCV6eSroFxEQBG1aQTMYI9zhTvFNpC1dG1/SD dkKUaFpbaOq3tpDXmci7d8IowfwNIIz8NRKK1wQ8U+Ag3qgoFfMy69TAj4ARRK9/urhO oBWA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=OcAvU4SI; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k191si2190752pgd.449.2018.04.03.09.14.59; Tue, 03 Apr 2018 09:15:13 -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; dkim=pass header.i=@chromium.org header.s=google header.b=OcAvU4SI; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752525AbeDCQMC (ORCPT + 99 others); Tue, 3 Apr 2018 12:12:02 -0400 Received: from mail-ua0-f194.google.com ([209.85.217.194]:45941 "EHLO mail-ua0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751461AbeDCQMB (ORCPT ); Tue, 3 Apr 2018 12:12:01 -0400 Received: by mail-ua0-f194.google.com with SMTP id j18so11329647uae.12 for ; Tue, 03 Apr 2018 09:12:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uH2ZRiOxbRAHM7zrCk2p+lEPWoWsJfL1WBJvHWbOFZQ=; b=OcAvU4SI/VSn5nGCSXONG3bmnE7oYgdN1IIBSctVT1K7ZfY9P62rKF8l4iw40R+jso /1/+MH4XRiPfwwiT2g5Jb3Gr/5nf449bGzSnIe20ASK4QIa40EMzd73Krpyje0bcwJvk P2ZSyHQCrm6z2Dpy4W7PqYZvWjbUixuc7vysA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uH2ZRiOxbRAHM7zrCk2p+lEPWoWsJfL1WBJvHWbOFZQ=; b=mHo3xzBlGSulPMV5iOy0R2mPGcgz1Dxr65MJXAj8K81ymkLOolilo4rPjJMHVXXoJk CRRq/8b45rIW/ZRD0kcrE87oTwW0MYM9N1QiV0aPUEG6M/LL80QKxGE4EMZtpH+TqwMS AA5rAmX9cEAuCgQI2oYCvQuiNSkmLNw9yzg0m+v9FGsBDQLF4tckwklYCvsm5hVr7zQW XqshIcOAC50EDy/6g6pXQC6uJJiqpJJ1g5lu5JphdCZpTr3CsnhqPiCWLBaAoQHSBqbO t3/tSuthSqDvCZ41SA3/ZEp50fiFZeEAD4AXUoClD0zSkPBrxBa2r5DN/CCuD+ppaZ4B 8ftA== X-Gm-Message-State: AElRT7HYYYtDXGR7OjLoZB/grabOkN8h7UaxWMq2jT8FYzfZKA7Jgo+m g+HlwXk2MIMMZ4VG/90EBwsc7Fz0xurZsSliP4guWw== X-Received: by 10.176.19.115 with SMTP id h48mr8564577uae.135.1522771919888; Tue, 03 Apr 2018 09:11:59 -0700 (PDT) MIME-Version: 1.0 References: <20180323073814.5802-1-jeffy.chen@rock-chips.com> <20180323073814.5802-12-jeffy.chen@rock-chips.com> <5AB8A7F0.1090305@rock-chips.com> In-Reply-To: <5AB8A7F0.1090305@rock-chips.com> From: Daniel Kurtz Date: Tue, 03 Apr 2018 16:11:49 +0000 Message-ID: Subject: Re: [PATCH v8 11/14] iommu/rockchip: Use OF_IOMMU to attach devices automatically To: Jeffy Cc: linux-kernel@vger.kernel.org, Ricky Liang , Robin Murphy , xxm , Tomasz Figa , Heiko Stuebner , "open list:ARM/Rockchip SoC..." , open@263.net, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jeffy, Sorry for delayed response. On Mon, Mar 26, 2018 at 1:58 AM JeffyChen wrote: > Hi Daniel, > Thanks for your reply. > On 03/26/2018 02:31 PM, Daniel Kurtz wrote: > >> >+struct rk_iommudata { > >> >+ struct rk_iommu *iommu; > >> >+}; > > Why do we need this struct? Can't we just assign a pointer to struct > > rk_iommu directly to dev->archdata.iommu? > > > hmmm, i was trying to add more device related data in patch[13]: > struct rk_iommudata { > + struct device_link *link; /* runtime PM link from IOMMU to master */ > struct rk_iommu *iommu; > }; > > Can't you just add link to rk_iommu directly?