[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZioleGboe_YYtm3d@smile.fi.intel.com>
Date: Thu, 25 Apr 2024 12:42:16 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Florian Fainelli <florian.fainelli@...adcom.com>
Cc: linux-kernel@...r.kernel.org,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Jan Dabros <jsd@...ihalf.com>, Andi Shyti <andi.shyti@...nel.org>,
Lee Jones <lee@...nel.org>, Jiawen Wu <jiawenwu@...stnetic.com>,
Mengyuan Lou <mengyuanlou@...-swift.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Maciej Fijalkowski <maciej.fijalkowski@...el.com>,
Andrew Lunn <andrew@...n.ch>,
Duanqiang Wen <duanqiangwen@...-swift.com>,
"open list:SYNOPSYS DESIGNWARE I2C DRIVER" <linux-i2c@...r.kernel.org>,
"open list:WANGXUN ETHERNET DRIVER" <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 3/4] mfd: intel_quark_i2c_gpio: Utilize
i2c-designware.h
On Wed, Apr 24, 2024 at 05:26:41PM -0700, Florian Fainelli wrote:
> Rather than open code the i2c_designware string, utilize the newly
> defined constant in i2c-designware.h.
..
> +++ b/drivers/mfd/intel_quark_i2c_gpio.c
> @@ -17,6 +17,7 @@
> #include <linux/clk-provider.h>
> #include <linux/dmi.h>
> #include <linux/i2c.h>
> +#include <linux/platform_data/i2c-designware.h>
Make it a separate group after linux/* ...
> #include <linux/property.h>
>
..here.
..
> -#define INTEL_QUARK_I2C_CONTROLLER_CLK "i2c_designware.0"
> +#define INTEL_QUARK_I2C_CONTROLLER_CLK I2C_DESIGNWARE_NAME ".0"
I'm not fan of this, but I think creating another macro to help with
constant device instance naming might be more cumbersome and overkill.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists