Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965180AbcKNXj2 (ORCPT ); Mon, 14 Nov 2016 18:39:28 -0500 Received: from mail-ua0-f196.google.com ([209.85.217.196]:33857 "EHLO mail-ua0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754630AbcKNXjZ (ORCPT ); Mon, 14 Nov 2016 18:39:25 -0500 MIME-Version: 1.0 In-Reply-To: <9560d7a2-98b2-732d-c91a-944ae381107c@denx.de> References: <9560d7a2-98b2-732d-c91a-944ae381107c@denx.de> From: Fabio Estevam Date: Mon, 14 Nov 2016 21:39:23 -0200 Message-ID: Subject: Re: [PATCH v9 1/5] mfd: mxs-lradc: Add support for mxs-lradc MFD To: Marek Vasut Cc: Ksenija Stanojevic , linux-kernel , Lee Jones , Dmitry Torokhov , linux-input@vger.kernel.org, Jonathan Cameron , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald , linux-iio@vger.kernel.org, Harald Geyer , Stefan Wahren , Fabio Estevam Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 298 Lines: 8 On Mon, Nov 14, 2016 at 4:43 PM, Marek Vasut wrote: >> +#define MXS_LRADC_BASE 0x80050000 > > Just for my understanding, why is this hardware address hard-coded here? > Shouldn't that be fetched from DT ? Yes, this base address should be retrieved from device tree.