Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp2790893pxb; Tue, 13 Apr 2021 10:11:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw73Kcgn5Kip/E7uD8XA0/HuaAq8xE688gmqAVtbYetIW+vUD1PXUk2pVxGlNxPGqpgOV0D X-Received: by 2002:a05:6402:5146:: with SMTP id n6mr21700948edd.299.1618333912477; Tue, 13 Apr 2021 10:11:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618333912; cv=none; d=google.com; s=arc-20160816; b=Ivo/kvcb1Hz7FGJ/V6c11l1r3wDAIZOSBku4v/3UoBJD4xOAn0IMXM6X11UOQr7vcY 75665KH1FAjKn0kdhglHm0tCo2sysq2+dnxnvS52a21ba36KCb1X+oyWOVjQCj8UKsAR AopFujc06BzGd0fcFT6ih2ADYgBi+IZxfTeyCQULsOxeozfnDKEmFE3Gip4ud4YQGvjX Jb73o0lItNGM4Jmy2xyezNB6IQZjzPa+9UoCI8JaJrlfyRcq/DvBzX9uEt/wCJP6lqO1 abI26TYRoUG4Pmx10F4xY/Vh65V3CWE5I7LIDfYKzoyXGNV+QcH9c9CVx1OZRe6OZYv1 KF0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=BPCwCEu/tlD0sPdVV7Acf3Q88fdnLj8wuh/uaB99fZ0=; b=lp9ZjoaHWh95/ZuFNkI5VUD3u7Xrs+P3/r80x5yVw3ldCZOOP4WmWsLRKZt10HUHUs PQijarL4Se/w6Byiqjcg7COVDKnaaZ04/pBMsQpWq+DINPqKyqo3UYkvCgSN3ewIhgYC t9bJ0FscKpQOKPi6rcKdFq7fuXoBs2jWM/KIvldg+CzciVjQ39keNpfgMAaiyvwEkSm3 YiyRPuqPiqG9LIkPf0/8G5Q3m0LicGSKU+1G+t2OMobaJu/bYSDtWlrzOSyiT5kAdIhW 5VHTG4+WHqtyA96Ogst633VpS7l7NjyUKcUsQ0CjxsYavngSg35Sxw69AfsfZPllEfx2 V0+g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ne7si10647429ejc.604.2021.04.13.10.11.27; Tue, 13 Apr 2021 10:11:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345776AbhDMMvR (ORCPT + 99 others); Tue, 13 Apr 2021 08:51:17 -0400 Received: from mail-vk1-f172.google.com ([209.85.221.172]:37510 "EHLO mail-vk1-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345905AbhDMMsq (ORCPT ); Tue, 13 Apr 2021 08:48:46 -0400 Received: by mail-vk1-f172.google.com with SMTP id p206so1060810vkd.4; Tue, 13 Apr 2021 05:48:26 -0700 (PDT) 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=BPCwCEu/tlD0sPdVV7Acf3Q88fdnLj8wuh/uaB99fZ0=; b=SxSg1XYx4RyYpuIGG8o9w0PpfCiC/84tJy6jumMgo888duy0YbQFzbvt4yUji2H89h lBLyIUiruh+dIMQC/YPCPiL90s5aEBe5FjsjaZHc1WN1MBxrP2112yy4sMTxd8csHGFm 404tXIc9leiIb04bO+lm+hudoOnhTdiRhLg0wdE9y/7/oi1hvTV/oUdoQxnZkpjnquuy Gt+tebNdPfwmPubPrIx3beAxjjT8yOKLqNuqe+6cM/5K+PVv6mwqIopJebHkY7OjtHRG oRwM7PUSk/wXn8HsvSBuj99IJXx9AlZM/89fONfmo4ciKOHy3UaaF1/i+63/BFLxWZQW fEdg== X-Gm-Message-State: AOAM5311/P1x8gka0sSnmoDXvIXdG6qLTn1U6Xp0C61SZ6QrrCp9y/HZ DCPM8CqhMv/aWp8eg/sii9q/xnWTiQDqzF14icg= X-Received: by 2002:a1f:1f81:: with SMTP id f123mr567276vkf.6.1618318106468; Tue, 13 Apr 2021 05:48:26 -0700 (PDT) MIME-Version: 1.0 References: <26db9291095c1dfd81c73b0f5f1434f9b399b1f5.1618316565.git.geert+renesas@glider.be> In-Reply-To: From: Geert Uytterhoeven Date: Tue, 13 Apr 2021 14:48:15 +0200 Message-ID: Subject: Re: [PATCH] i2c: I2C_HISI should depend on ARCH_HISI && ACPI To: Andy Shevchenko Cc: Yicong Yang , Wei Xu , Wolfram Sang , Dmitry Osipenko , Linux I2C , Linux ARM , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Andy, On Tue, Apr 13, 2021 at 2:37 PM Andy Shevchenko wrote: > On Tue, Apr 13, 2021 at 02:26:15PM +0200, Geert Uytterhoeven wrote: > > The HiSilicon Kunpeng I2C controller is only present on HiSilicon > > Kunpeng SoCs, and its driver relies on ACPI to probe for its presence. > > Hence add dependencies on ARCH_HISI and ACPI, to prevent asking the user > > about this driver when configuring a kernel without Hisilicon platform > > or ACPI firmware support. > > I don't by the ACPI dependency, sorry. > > The driver is a pure platform driver that can be enumerated on ACPI enabled > devices, but otherwise it can be used as a platform one. Sure, you can manually instantiate a platform device with a matching name, and set up the "clk_rate" device property. But would it make sense to do that? Would anyone ever do that? The corresponding SPI_HISI_KUNPENG depends on ACPI, too. > If you remove ACPI dependency, feel free to add my > Reviewed-by: Andy Shevchenko Thanks! ;-) Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds