From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C6D9B385D8C for ; Tue, 23 Jun 2026 14:39:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.20 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782225553; cv=none; b=e3FnsXSBJqZMkPEpqVWUvx7bzmbX4ynBghmLoeq94upDgkHlMWGzaebvM7TodAiy4p1wmey5nB8h6NcdwaKTVvFphJV5mMZS2X5EBtOOse8odeIVKcVw+05H+tnuekRoQ5ujmasglsv7FBbFZnyqgm/on8VFgbJ5NmOvb+yPzg4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782225553; c=relaxed/simple; bh=dImJFPzxH/4Wshq1scD91Jr8EQJjWmN3JFUnfWJNQRc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=BzoNzhHqsMkfpNlx7Ox2vBkm4HsoAwnEaTZp8FYA/lEHlv2zjWQa+IjJdBCb6z3VBKe9fcfLmGjQeTuOxH+6MGQdOzljp+u7qTGR9mtjmfwKjOQKWhMIQ4GEMYjECxht70Pxuds3JwhshOezIBAVbW0zKfCcPWJY2WLxR17qPZU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=JSClM7pR; arc=none smtp.client-ip=198.175.65.20 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="JSClM7pR" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1782225552; x=1813761552; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=dImJFPzxH/4Wshq1scD91Jr8EQJjWmN3JFUnfWJNQRc=; b=JSClM7pRSK+poZ88C5LK0HsuUFaONpI4ganseGoVjiswXS7+54xCz09L OMXucJSMbtXg7OgYUh7pWFfEWshJ/GiI/HSct/QCbSQlDC1W4KWr5Oz2J jp28uyDCVu1h2VUo+2+8CGjBhn1kh6E2ZVYLBjR5IBB+F74FsIhsXQOJ4 my/x6+20nxGpd6R4YH8mK7tOUxOY+F3f6AH29kf4C9zRVbFPQZ8M/9ZLC zWPCYt2APgwwiw5tRQGWItsxtfNDG1anXxC3U4NzCUnK+UPGynGYACMXA 4nOHlg/1xNd6B1okXpHszzGz3jrHWsed+xMJysTvDyrfSmwCPDEEP7A8u Q==; X-CSE-ConnectionGUID: GN7G7YiQRLeI+ZTTCRbieg== X-CSE-MsgGUID: Kg+sQq1BQRWCDNYx82teIg== X-IronPort-AV: E=McAfee;i="6800,10657,11826"; a="82737312" X-IronPort-AV: E=Sophos;i="6.24,220,1774335600"; d="scan'208";a="82737312" Received: from orviesa001.jf.intel.com ([10.64.159.141]) by orvoesa112.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Jun 2026 07:39:12 -0700 X-CSE-ConnectionGUID: AdCqRy2dTQS/slZH/nscEw== X-CSE-MsgGUID: rf7WIfAISQ6Oo/uTRJqshQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.24,220,1774335600"; d="scan'208";a="287667559" Received: from black.igk.intel.com ([10.91.253.5]) by orviesa001.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Jun 2026 07:39:09 -0700 Date: Tue, 23 Jun 2026 16:39:05 +0200 From: Raag Jadav To: Heikki Krogerus Cc: Rodrigo Vivi , Matthew Brost , Thomas =?iso-8859-1?Q?Hellstr=F6m?= , "Michael J . Ruhl" , Andy Shevchenko , Mika Westerberg , Riana Tauro , David Airlie , Simona Vetter , dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 2/2] drm/xe/mcu_i2c: Take over control of the controller enabling Message-ID: References: <20260622114759.3464047-1-heikki.krogerus@linux.intel.com> <20260622114759.3464047-3-heikki.krogerus@linux.intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260622114759.3464047-3-heikki.krogerus@linux.intel.com> On Mon, Jun 22, 2026 at 01:47:59PM +0200, Heikki Krogerus wrote: > Some platforms make an assumption that the i2c controller's > enabled state indicates also the power state of the > controller. This can create a problem when the controller is > in disabled state, because the hardware may assume > incorrectly that it is then also in low-power state. > > To fix this, the controller is kept enabled by taking over > the IC_ENABLE register. The controller has to be disabled > when the configuration is updated and when the target > address or the slave address are assigned, so disabling it > when IC_CON, IC_TAR or IC_SAR registers are programmed, and > then re-enabling it again. ... > static int xe_i2c_read(void *context, unsigned int reg, unsigned int *val) > { > struct xe_i2c *i2c = context; > > - *val = xe_mmio_read32(i2c->mmio, XE_REG(reg + I2C_MEM_SPACE_OFFSET)); > + switch (reg) { Curious, should I expect DW_IC_INTR_MASK case here which skips the MMIO? > + case IC_ENABLE: > + *val = i2c->ic_enable; > + break; > + case IC_ENABLE_STATUS: > + *val = i2c->ic_enable & 1; /* NOTE: Checking only the enable bit */ > + break; > + default: > + *val = xe_mmio_read32(i2c->mmio, XE_REG(reg + I2C_MEM_SPACE_OFFSET)); > + break; > + } > > return 0; > } > @@ -273,8 +312,30 @@ static int xe_i2c_read(void *context, unsigned int reg, unsigned int *val) > static int xe_i2c_write(void *context, unsigned int reg, unsigned int val) > { > struct xe_i2c *i2c = context; > + int ret; > > - xe_mmio_write32(i2c->mmio, XE_REG(reg + I2C_MEM_SPACE_OFFSET), val); > + switch (reg) { Ditto. Raag > + case IC_CON: > + case IC_TAR: > + case IC_SAR: > + /* Disable the controller. */ > + ret = xe_i2c_disable(i2c); > + if (ret) > + return ret; > + > + /* Write the register. */ > + xe_mmio_write32(i2c->mmio, XE_REG(reg + I2C_MEM_SPACE_OFFSET), val); > + > + /* Enable the controller. */ > + xe_mmio_rmw32(i2c->mmio, XE_REG(IC_ENABLE + I2C_MEM_SPACE_OFFSET), 0, 1); > + break; > + case IC_ENABLE: > + i2c->ic_enable = val; > + break; > + default: > + xe_mmio_write32(i2c->mmio, XE_REG(reg + I2C_MEM_SPACE_OFFSET), val); > + break; > + } > > return 0; > }