From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Sun, 11 Feb 2018 19:06:32 -0500 Subject: [U-Boot] [PATCH v2 3/4] Convert socfpga: select CONFIG_HW_WATCHDOG support for ARCH_SOCFPGA In-Reply-To: <20180212003410.384dbbb3@jawa> References: <20180209221410.626-1-lukma@denx.de> <20180209221410.626-4-lukma@denx.de> <20180212003410.384dbbb3@jawa> Message-ID: <20180212000632.GL3061@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Feb 12, 2018 at 12:34:10AM +0100, Lukasz Majewski wrote: > Hi Simon, > > > On 09.02.2018 23:14, Lukasz Majewski wrote: > > > All Socfpga boards from ./include/configs/socfpga_* define > > > CONFIG_HW_WATCHDOG. > > > To ease CONFIG_HW_WATCHDOG conversion to Kconfig select it in > > > config ARCH_SOCFPGA (arch/arm/Kconfig) section. > > > > I do have board configs where the internal watchdog is not used and > > should be disabled (because there's an external one). Also, given > > that this is an FPGA, I suppose having non-upstreamed boards is not > > uncommon. > > I must admit that this patch I did after looking on the socfpga pattern > in the current upstream. > > It seems like all boards there use HW_WATCHDOG. > > > > > I'm not too familiar with these settings though: can I leave the > > watchdog disabled when CONFIG_HW_WATCHDOG is off? Before, I just > > haven't enabled this in my own board config... > > I think that I will prepare next revision of this patch with just simple > ./tools/moveconfig.py output (without blindly selecting HW_WATCHDOG on > all socfpga devices). > > In that way we will preserve the current behaviour. You should probably use imply for features that are common, but optional. -- Tom