From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.17]) (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 101073EFD25 for ; Tue, 30 Jun 2026 10:28:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.17 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782815296; cv=none; b=cnoDoqikQ037GPxits1rQH6hKqdntpPyQnWUL/cXXvLbAlb50sGoUFbXkl9gONyDQxS6TQssEsEA+x4p9ZgkkQkniLN2NaIYjq5693We8YFia20or/8v/3rGQHdpy0kZGcCdB3qzcNC2qgnm9qjEgPg1AIy4ZuZXIk3W31nt/Og= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782815296; c=relaxed/simple; bh=i5nO/jIZd0TtIDalodtoEW8qteZa4x1waL/+X1FSrDY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=pZ0N/bu2G7P1DkdBs0u3Ce3sKSTg6bYt2U2W4Ktj20AFHMXENT0kHYtNDZbz5OoVXDvmyVR2IHG0H+bYRxe8aOOE0LB50XVk91oV0Oj8b6oN05DuZJIj0UiDI90ApOneUYS24HJ1h7G3Z72ZXcMNt+h0dR+QDz2AQhCU/axvQBU= 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=Q25uPx2C; arc=none smtp.client-ip=192.198.163.17 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="Q25uPx2C" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1782815294; x=1814351294; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=i5nO/jIZd0TtIDalodtoEW8qteZa4x1waL/+X1FSrDY=; b=Q25uPx2Cr+AbvPCKqg9tI94SR+ZSgVctJt2ejRdVVsFlUqHrX6u994UM ywsVvOyy4csmZJUdOkR1JkUKXnFYhwSSiuKJfjyxft/nbEb2vC529gdX2 76OvcH270I3hAOTZ0wu9kOFtBZualEAojsB8T4lGJFdI/aG+IwABa8GJc VvHxlJqoCNIOGMo+goucnxqFtYGt85HBgjn0dyxzsNrYRH5K/asb8SqpG eSsxtS5k7BALzT1YomsjboCjjdip2Q/UEs/so6loVALgR3mVd4SQlL4TI BWa/PhCX/yY/ivGqMTDJTzyp5RwMDqQE2aFxqPHdv3AtXbCDA86//OzeM A==; X-CSE-ConnectionGUID: 0GqiY+5AS72BA/lrEWjazg== X-CSE-MsgGUID: urMB3s2kS2uVHNTEv/YNHw== X-IronPort-AV: E=McAfee;i="6800,10657,11832"; a="83395555" X-IronPort-AV: E=Sophos;i="6.24,233,1774335600"; d="scan'208";a="83395555" Received: from orviesa009.jf.intel.com ([10.64.159.149]) by fmvoesa111.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Jun 2026 03:28:14 -0700 X-CSE-ConnectionGUID: 9STfOcq+R8KH8gX4EHr2xA== X-CSE-MsgGUID: gH7hYvirTSiLAzw3S9Ydhw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.24,233,1774335600"; d="scan'208";a="252873969" Received: from black.igk.intel.com ([10.91.253.5]) by orviesa009.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Jun 2026 03:28:12 -0700 Date: Tue, 30 Jun 2026 12:28:08 +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 , Andi Shyti , dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 2/3] drm/xe/i2c: Handler for SMBus Alerts Message-ID: References: <20260625125939.429078-1-heikki.krogerus@linux.intel.com> <20260625125939.429078-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: <20260625125939.429078-3-heikki.krogerus@linux.intel.com> On Thu, Jun 25, 2026 at 02:59:38PM +0200, Heikki Krogerus wrote: > Some devices that are attached to the I2C controller use the > SMBus Alert signal for example to inform the host about > thermal events, so registering the default SMBus Alert > device for them. The alert device makes sure that the alert > is processed and passed to the correct I2C client driver. ... > +enum XE_I2C_CLIENT { > + XE_I2C_CLIENT_AMC, > + XE_I2C_CLIENT_ALERT, Forgot to add, with this I think you can move XE_I2C_MAX_CLIENTS define here. Raag > +};