[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200117042409.GE47797@dtor-ws>
Date: Thu, 16 Jan 2020 20:24:09 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Input <linux-input@...r.kernel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [PATCH] input: max77650-onkey: add of_match table
On Sat, Jan 11, 2020 at 11:22:55AM +0100, Bartosz Golaszewski wrote:
> pt., 10 sty 2020 o 19:28 Dmitry Torokhov <dmitry.torokhov@...il.com> napisaĆ(a):
> >
> > On Tue, Dec 10, 2019 at 11:07:53AM +0100, Bartosz Golaszewski wrote:
> > > From: Bartosz Golaszewski <bgolaszewski@...libre.com>
> > >
> > > We need the of_match table if we want to use the compatible string in
> > > the pmic's child node and get the onkey driver loaded automatically.
> >
> > Do we really need of_match table or adding
> >
>
> Not really. Technically not anyway but we merged bindings that define
> it (at the time I didn't know any better) and seems we're stuck with
> it. Please see the discussion below a similar patch for regulator
> subsystem[1].
>
> > MODULE_ALIAS("platform:max77650-onkey");
> >
>
> This is already in there, but if someone defines the compatible in the
> device tree as per bindings, the module won't be loaded despite the
> MODULE_ALIAS() definition.
I see. Applied, thank you.
--
Dmitry
Powered by blists - more mailing lists