[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1e15P6xRUgYLYxT8XUx7FREbs5mMbfL1Qj+qwoDfFX+Q@mail.gmail.com>
Date: Fri, 24 Apr 2020 10:24:09 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Lee Jones <lee.jones@...aro.org>
Cc: Baolin Wang <baolin.wang7@...il.com>,
Mark Brown <broonie@...nel.org>,
Orson Zhai <orsonzhai@...il.com>,
Lyra Zhang <zhang.lyra@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] mfd: syscon: Support physical regmap bus
On Fri, Apr 24, 2020 at 10:11 AM Lee Jones <lee.jones@...aro.org> wrote:
> On Fri, 17 Apr 2020, Baolin Wang wrote:
> > @@ -106,14 +107,25 @@ static struct syscon *of_syscon_register(struct device_node *np, bool check_clk)
> > syscon_config.val_bits = reg_io_width * 8;
> > syscon_config.max_register = resource_size(&res) - reg_io_width;
> >
> > - regmap = regmap_init_mmio(NULL, base, &syscon_config);
> > + /*
> > + * The Spreadtrum syscon need register a real physical regmap bus
> > + * with new atomic bits updating operation instead of using
> > + * read-modify-write.
> > + */
> > + if (IS_ENABLED(CONFIG_ARCH_SPRD) &&
> > + of_device_is_compatible(np, "sprd,atomic-syscon") &&
>
> Please find a more generic way of supporting your use-case. This is a
> generic driver, and as such I am vehemently against adding any sort of
> vendor specific code in here.
I suggested doing it this way, as all alternatives seemed worse than this.
Arnd
Powered by blists - more mailing lists