From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752560AbdEHXfC (ORCPT ); Mon, 8 May 2017 19:35:02 -0400 Received: from mail-qt0-f177.google.com ([209.85.216.177]:36531 "EHLO mail-qt0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751087AbdEHXfA (ORCPT ); Mon, 8 May 2017 19:35:00 -0400 MIME-Version: 1.0 In-Reply-To: <20170424181818.2754-5-brendanhiggins@google.com> References: <20170424181818.2754-1-brendanhiggins@google.com> <20170424181818.2754-5-brendanhiggins@google.com> From: Brendan Higgins Date: Mon, 8 May 2017 16:34:58 -0700 Message-ID: Subject: Re: [PATCH v7 4/5] i2c: aspeed: added driver for Aspeed I2C To: Wolfram Sang , Rob Herring , Mark Rutland , Thomas Gleixner , Jason Cooper , Marc Zyngier , Joel Stanley , Vladimir Zapolskiy , Kachalov Anton , =?UTF-8?Q?C=C3=A9dric_Le_Goater?= , Benjamin Herrenschmidt Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, Linux Kernel Mailing List , OpenBMC Maillist , Brendan Higgins , Ryan Chen Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sorry for the spam everyone, email client did not do what I expected it to do. I would like to release another version this week or next week, and I think that we are pretty closed to having something we can apply, but before I do that, I want to get something resolved: > +static int __aspeed_i2c_init(struct aspeed_i2c_bus *bus, > + struct platform_device *pdev) > +{ > + int ret; > + > + /* Disable everything. */ > + writel(0, bus->base + ASPEED_I2C_FUN_CTRL_REG); > + > + ret = __aspeed_i2c_init_clk(bus, pdev); > + if (ret < 0) > + return ret; > + > + /* Enable Master Mode */ > + writel(readl(bus->base + ASPEED_I2C_FUN_CTRL_REG) | > + ASPEED_I2CD_MASTER_EN | > + /* TODO: provide device tree option for multi-master mode. */ I am curious what everyone thinks about this. It seemed that, earlier on, people did not like me disabling multi-master mode, but I think that it would make bus recovery not work as well. Given that, I think it makes the most sense to provide a device tree option either to enable multi-master support or disable it. Thoughts? > + ASPEED_I2CD_MULTI_MASTER_DIS, > + bus->base + ASPEED_I2C_FUN_CTRL_REG); > + > + /* Set interrupt generation of I2C controller */ > + writel(ASPEED_I2CD_INTR_ALL, bus->base + ASPEED_I2C_INTR_CTRL_REG); > + > + return 0; > +}