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: <CAK8P3a2-AQx6iuNeWOFfru3H21pv4Gg7Qt00uUghbnPDzwF4_g@mail.gmail.com>
Date:   Fri, 17 Apr 2020 17:03:19 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Baolin Wang <baolin.wang7@...il.com>
Cc:     Lee Jones <lee.jones@...aro.org>, 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 2/2] soc: sprd: Add Spreadtrum special bits updating support

On Fri, Apr 17, 2020 at 4:10 PM Baolin Wang <baolin.wang7@...il.com> wrote:
> On Fri, Apr 17, 2020 at 9:39 PM Arnd Bergmann <arnd@...db.de> wrote:
> > On Fri, Apr 17, 2020 at 4:14 AM Baolin Wang <baolin.wang7@...il.com> wrote:
> > > +static int sprd_syscon_init(void)
> > > +{
> > > +       syscon_register_phys_regmap_bus(&sprd_syscon_regmap);
> > > +
> > > +       return 0;
> > > +}
> > > +core_initcall_sync(sprd_syscon_init);
> >
> > This no longer breaks at runtime based on the changes in the other
> > patch, but I still don't like how you have to manually load this module
> > on spreadtrum platforms.
> >
> > What I meant to suggest in my previous reply was to add the regmap_bus
> > instance into drivers/mfd/syscon.c itself.
>
> Sorry, I misunderstood your meaning before, but what you suggested
> will add some vendor-specific things into the common syscon driver, if
> other platforms have different update bits method, we will add another
> vendor-specific regmap bus into the syscon.c, which will make syscon.c
> more complicated.

I think we can always deal with this once it gets too complex, as long
as the DT binding allows it.

> But if you still prefer to add these vendor-specific things into the
> syscon.c, I will follow your suggestion in next version. Thanks.

Yes, please do.

       Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ