From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
robh@kernel.org, linux-serial@vger.kernel.org,
ribalda@kernel.org, johan@kernel.org
Subject: Re: Cutiepi, serdevs, and right way to handle its power button
Date: Thu, 22 Sep 2022 13:11:37 +0300 [thread overview]
Message-ID: <Yyw02TpYzlVfg0op@smile.fi.intel.com> (raw)
In-Reply-To: <20220921171707.GA8443@duo.ucw.cz>
On Wed, Sep 21, 2022 at 07:17:07PM +0200, Pavel Machek wrote:
> On Wed 2022-09-21 17:45:33, Andy Shevchenko wrote:
> > On Tue, Sep 20, 2022 at 10:56:37PM +0200, Pavel Machek wrote:
> > > Hi!
> > >
> > > Cutiepie is a small handheld tablet. It has embedded controller
> > > connected via serial to the main system, handling stuff such as power
> > > button and battery percentage. Currently they are using userland
> > > deamon for communication, but I believe that should eventually go into
> > > kernel.
> > >
> > > For debugging, it would be really nice to be able to attach my module
> > > to given serdev. Is such thing possible? I see "[PATCH v2 00/19]
> > > Dynamically load/remove serdev devices via sysfs*" series
> > > (https://www.spinics.net/lists/linux-serial/msg30732.html) but I'm not
> > > sure if equivalent functionality exists in mainline kernel?
> > >
> > > Is there some kind of similar hardware already supported by mainline?
> > > Using driver as a reference might be easier than starting from
> > > scratch.
> >
> > Is it arm or x86 based tablet?
>
> arm64, but CPU architecture really should not matter.
It makes sense on the usual practices done for the platform as a whole, e.g.
ACPI vs. DT. So, I believe this one is DT based.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-09-22 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 20:56 Pavel Machek
2022-09-21 14:45 ` Andy Shevchenko
2022-09-21 17:17 ` Pavel Machek
2022-09-22 10:11 ` Andy Shevchenko [this message]
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=Yyw02TpYzlVfg0op@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=ribalda@kernel.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®