From: Dan O'Donovan <dan@emutex.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
platform-driver-x86@vger.kernel.org
Cc: "Darren Hart (Google+)"
<reply-101378268367730737515@profiles.google.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: UP Board and similar
Date: Mon, 4 Jul 2016 16:33:45 +0100 [thread overview]
Message-ID: <577A81D9.4010800@emutex.com> (raw)
In-Reply-To: <CAHp75VcOMFygekkhCEtWigW+JaKOgNQrM9M-3MtKemBF3arBOQ@mail.gmail.com>
Hi Andy
On 06/30/2016 09:36 PM, Andy Shevchenko wrote:
> Hi!
>
> Thank you for the series and sorry to answer as a new mail, just
> subscribed to the list and didn't manage to retrieve archives (seems
> VGER doesn't have them).
Thanks very much for your reply. I appreciate you kick-starting a
discussion on these patches. :-)
>
> So, regarding to enabling UP Board and similar open connected boards
> (Galileo, Edison/Arduino, etc.).
>
> The mentioned boards are x86. There is currently no way to handle
> pinctrl on them since they are ACPI-based. Moreover pinctrl doesn't
> have a way to configure stuff for customer needs!
>
> What is my vision on the issue. Currently we have pending ACPI patches
> from Octavian that help us to load ACPI DSDT overlays in a way as it
> works for DT. This will make possible to create a blob to configure
> pins. Thus, part of the patch series which hard codes the mappings is
> not needed. And therefore your drivers should go somewhere under
> drivers/pinctrl/intel folder which Mika (mostly) and I are supporting.
Yes, I think that makes sense. This is essentially a pin control driver
(except for some LED control functionality).
>
> We still need to agree on the above: which folder and how those
> drivers should look like.
Darren has suggested that I re-post the patches for review, so I'll do
that next and see where the discussion takes us.
>
> P.S. Dan, next time please include me and Mika into Cc list for such
> things. Thanks!
>
Will do, thanks!
prev parent reply other threads:[~2016-07-04 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 20:36 UP Board and similar Andy Shevchenko
2016-07-04 15:33 ` Dan O'Donovan [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=577A81D9.4010800@emutex.com \
--to=dan@emutex.com \
--cc=andy.shevchenko@gmail.com \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=reply-101378268367730737515@profiles.google.com \
/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.