From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] touchscreen: stmpe-ts: enable module autoload
Date: Fri, 22 May 2015 11:29:22 -0700 [thread overview]
Message-ID: <20150522182922.GF40101@dtor-ws> (raw)
In-Reply-To: <555EBFF3.1010602@gmail.com>
On Fri, May 22, 2015 at 07:34:43AM +0200, Heiner Kallweit wrote:
> Am 22.05.2015 um 01:06 schrieb Dmitry Torokhov:
> > Hi Heiner,
> >
> > On Thu, May 21, 2015 at 11:19:52PM +0200, Heiner Kallweit wrote:
> >> Even with poper DT config the module didn't autoload.
> >> That's fixed by this additional alias.
> >>
> >> Tested successfully with a STMPE610-based Adafruit PITFT Plus 3.5"
> >> on RPI2 under Arch Linux ARM (kernel 3.18.13).
> >>
> >> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> >> ---
> >> drivers/input/touchscreen/stmpe-ts.c | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/drivers/input/touchscreen/stmpe-ts.c b/drivers/input/touchscreen/stmpe-ts.c
> >> index e4c3125..1940e3c 100644
> >> --- a/drivers/input/touchscreen/stmpe-ts.c
> >> +++ b/drivers/input/touchscreen/stmpe-ts.c
> >> @@ -393,4 +393,5 @@ module_platform_driver(stmpe_ts_driver);
> >> MODULE_AUTHOR("Luotao Fu <l.fu@pengutronix.de>");
> >> MODULE_DESCRIPTION("STMPEXXX touchscreen driver");
> >> MODULE_LICENSE("GPL");
> >> +MODULE_ALIAS("spi:" STMPE_TS_NAME);
> >> MODULE_ALIAS("platform:" STMPE_TS_NAME);
> >
> > Bit this is not an SPI driver, it is a platform driver for a MFD cell.
> > Why does adding SPI alias help?
> >
> > Thanks.
> >
> The STMPE610 in my case is used on a small touchscreen for the Raspberry Pi
> and touchscreen controller as well as display controller are connected via
> SPI + a few GPIOs to the RPI.
>
> The display controller is supported by the fbtft driver and the drivers
> for the respective display controllers have similar aliases.
> see e.g. drivers/staging/fbtft/fb_hx8353d.c
>
> MODULE_ALIAS("spi:hx8353d");
> MODULE_ALIAS("platform:hx8353d");
I understand why both platform and spi aliases are needed for
fb_hx8353d: FBTFT_REGISTER_DRIVER macro does register 2 separate
drivers, one SPI and another platform, and so needs both aliases. You
still have not explained why we need SPI alias for stmpe-ts which is MFD
cell represented by a platform device/driver no matter what bus is used
to connect stmpe itself, I2C or SPI.
What is the modalias on the stmpe-ts device in sysfs?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2015-05-22 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 21:19 [PATCH] touchscreen: stmpe-ts: enable module autoload Heiner Kallweit
2015-05-21 23:06 ` Dmitry Torokhov
2015-05-22 5:34 ` Heiner Kallweit
2015-05-22 18:29 ` Dmitry Torokhov [this message]
2015-05-22 19:01 ` Heiner Kallweit
2015-05-22 20:17 ` Dmitry Torokhov
2015-05-22 21:02 ` Heiner Kallweit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150522182922.GF40101@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.