Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp1363402ybg; Wed, 29 Jul 2020 12:09:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxw+1t9H4oRUu5uIVsEZEhfMpcL5V3gvD/DDOpV0tglELPXgTppG92wXS7hB0w6UbY3UJKX X-Received: by 2002:a17:906:698:: with SMTP id u24mr29635642ejb.57.1596049767201; Wed, 29 Jul 2020 12:09:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596049767; cv=none; d=google.com; s=arc-20160816; b=nYUOuEPqkeE0mU81pIez6AEpCdtnG76JNusmIpgAqjP0fIQ3iRTYZAig2EcQ1d8Nh7 7OVWx18S7HNJ9wAua8kFs9Vo6MNUqhILJEyQZ4Df761AAcAgCciLsyVVgb/u38m1z31F 6UPCL3vBPXjssFFJTU1mO0pMyJ8We4gUV6ovC92L89gc3ENVH3km8IzknBry+Tg5TGIx XZtMS52fgQ1KzJe7SWZVH5T4zBqfPKLLe4LkVkkdCBpHsEskgaQ0Pr1/4SUcKnToZK3S Wt8XiDl+WHkOcn1ESYe2k5Xn6Pihk/Bkic8mA2RspxXKICRg46ud0TdXiJVXsgAD3dwI TOFg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=5TjtwLJ/4JawmtgXRGSuispnAI6GsCMfaOz6eumDkrM=; b=ItIG3X8VsEl1jdXksB73k8X2QDX6ZqPSt2dHlGQ24U9fLL3WZVJu4uPCil8/aAjDs8 XWDUcLPVjThCDkv9d8gKe0thmLKBsmlMHb9nKE6dITwxJC1MQQfMtNIgGVnCYcwCMH6V gB/Ay8hOUX01jtI4Zbl8OBDXU4R+/sE+9QFGKy4dpCoEjJOtKsnmc5cpLVsaD9oP+VWe XZs6ox523Zr89/71u4cWAcRklnCfGdKDOGO7OwiqRZnVaipTJ51V72kieN7sBPCYJRuM DSNKNCRH5sRR1OaGhZLpd+Euq4W14obFuJlcpdvXf/LrMRSg2bOm9aGMY0Sp3Rc+NiFW wasw== 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v22si1943094eds.73.2020.07.29.12.09.02; Wed, 29 Jul 2020 12:09:27 -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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726588AbgG2TI7 convert rfc822-to-8bit (ORCPT + 99 others); Wed, 29 Jul 2020 15:08:59 -0400 Received: from mail-ej1-f67.google.com ([209.85.218.67]:38955 "EHLO mail-ej1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726365AbgG2TI6 (ORCPT ); Wed, 29 Jul 2020 15:08:58 -0400 Received: by mail-ej1-f67.google.com with SMTP id f24so4972711ejx.6; Wed, 29 Jul 2020 12:08:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=Kk6GZ/lJmAXVSU51HkWJo7PA9w7q1gYfnsyVr0WMPOk=; b=JLMz2iC/vIPVcWWEm4JrUKpTuusef8Vp/EgxzHIqjTRyD4XJ3GUnlMaun8M/Jq/Peo YsR5JQ9XKUHfb4lZwLrt2aFCgWs+iwZGyxTJgIfqaAsCRie/kLQ6/8r+foY0mG+ezcLD zVgT5fO5KoHXE0XpkqzTUI5YB39q69Kl3McHzaMbCJhpTYlH9eQ29nSt0CUxb0Xa93NI Upa+TZivwyME//onZqU9B4Tfv69Rs7ha5FiFK77w0nG4utKXX2oJLZbQA+C3sA7TP/jx HVyCAEM6yXlOZXsrL9UDt27rHAE4CW5yMSpLcVPkpejpexhHYMfAhuYPDZQqUqESpnPl /ikg== X-Gm-Message-State: AOAM533P9pkJ+1eDzMCIzKbOUX0WgS3tNOpRjVs4eDAu7wajH9dBS+Vt 3kGYKAP2ttdGI2/XcgZvGrA= X-Received: by 2002:a17:906:6d4d:: with SMTP id a13mr31002287ejt.146.1596049736098; Wed, 29 Jul 2020 12:08:56 -0700 (PDT) Received: from kozik-lap ([194.230.155.213]) by smtp.googlemail.com with ESMTPSA id m5sm2616809edr.59.2020.07.29.12.08.53 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Wed, 29 Jul 2020 12:08:55 -0700 (PDT) Date: Wed, 29 Jul 2020 21:08:52 +0200 From: Krzysztof Kozlowski To: Tomasz Figa Cc: Guenter Roeck , Russell King , Kukjin Kim , Vincent Sanders , Simtec Linux Team , Kyungmin Park , Catalin Marinas , Will Deacon , Sylwester Nawrocki , Chanwoo Choi , Michael Turquette , Stephen Boyd , Wim Van Sebroeck , Arnd Bergmann , Linus Walleij , linux-kernel , linux-arm-kernel , "moderated list:SAMSUNG SOC CLOCK DRIVERS" , linux-stm32@st-md-mailman.stormreply.com, patches@opensource.cirrus.com, "open list:COMMON CLK FRAMEWORK" , linux-watchdog@vger.kernel.org, Sergio Prado , Marek Szyprowski , Sylwester Nawrocki , Cedric Roux , Lihua Yao Subject: Re: [PATCH 5/7] ARM: samsung: Kill useless HAVE_S3C2410_WATCHDOG Message-ID: <20200729190852.GA5822@kozik-lap> References: <20200729160942.28867-1-krzk@kernel.org> <20200729160942.28867-6-krzk@kernel.org> <20200729170245.GA177035@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 29, 2020 at 07:36:38PM +0200, Tomasz Figa wrote: > 2020年7月29日(水) 19:02 Guenter Roeck : > > > > On Wed, Jul 29, 2020 at 06:09:40PM +0200, Krzysztof Kozlowski wrote: > > > A separate Kconfig option HAVE_S3C2410_WATCHDOG for Samsung SoCs does > > > not have sense, because: > > > 1. All ARMv7 and ARMv8 Samsung SoCs have watchdog, > > > 2. All architecture Kconfigs were selecting it (if WATCHDOG framework is > > > chosen), > > > 3. HAVE_S3C2410_WATCHDOG is doing nothing except being a dependency of > > > actual Samsung SoC watchdog driver, which is enabled manually by > > > specific defconfigs. > > > > > > HAVE_S3C2410_WATCHDOG can be safely removed. > > > > > > > That is not really correct. HAVE_S3C2410_WATCHDOG is used to ensure > > that users can only enable S3C2410_WATCHDOG if the watchdog actually > > exists in a system. With this change, it can be enabled for all > > architectures and platforms. > > > > NACK. > > > > Guenter > > > > I'd side with Guenter on this. We better not flood users' screens with > options that are not relevant to their hardware. > > An alternative here could be making CONFIG_S3C2410_WATCHDOG depend on > a general symbol for Samsung SoC support if there is such, but then, > are we 100% sure that all the Samsung SoCs would actually have exactly > this watchdog? If a new one shows up, one would have to bring back > this HAVE_S3C2410_WATCHDOG symbol. Ah, good points. Indeed for all of such SoC drivers we usually just depend on architecture to limit the choices on other architectures. In this case it would be: depends on ARCH_EXYNOS || ARCH_S3C24XX || ARCH_S3C64XX || ARCH_S5PV210 || COMPILE_TEST I admit it is pretty long, but we already use this pattern. In shorter version (less ARCH*) for all drivers, in full version also in: drivers/iio/adc/Kconfig drivers/gpu/drm/exynos/Kconfig Have in mind that in general we follow the first approach and only three drivers have still the HAVE_xxx option (also HAVE_S3C2410_I2C and HAVE_S3C_RTC). I can update therefore the "depends" while removing the HAVE_S3C2410_WATCHDOG option or just keep it. Best regards, Krzysztof