linux-kernel - Re: [PATCH 1/2] mfd: syscon: Support physical regmap bus

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CADBw62pisHz=ejgnhL=Y_qufCoZjPDLT90X2bztTZzMgbNMvmQ@mail.gmail.com>
Date:   Fri, 24 Apr 2020 16:42:50 +0800
From:   Baolin Wang <baolin.wang7@...il.com>
To:     Lee Jones <lee.jones@...aro.org>
Cc:     Arnd Bergmann <arnd@...db.de>, 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 4:32 PM Lee Jones <lee.jones@...aro.org> wrote:
>
> On Fri, 24 Apr 2020, Arnd Bergmann wrote:
>
> > 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.
>
> If we're using a registration function (could probably be swapped out
> for or accompanied by a Device Tree property) anyway, then why conduct
> the vendor platform checks?

Actually I've send out the v3 patch according to Arnd's suggestion. In
v3 patch, I removed the registration function, but we agreed that
adding the vendor specific support in the syscon driver seems a better
way than others.

-- 
Baolin Wang