linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: RFC: is SIM connector switch a case for pinmux ?
Date: Tue, 20 Aug 2019 12:17:47 +0200	[thread overview]
Message-ID: <a1bb9419-c499-dbd8-8e15-e7655b484d6e@metux.net> (raw)

Hello folks,


I'm currently thinking about what would be the best fit for the
APU board's sim-switch functionality.

The boards have two sim sockets, where only one can be active at
a time (the lines are routed to mpcie slot), which can be controlled
via a gpio line.

Extconn doesn't seem to fit, as it IMHO only does the exact opposite
direction - detect what external connector is currently active (eg.
on slots that support multiple conntor types and switch automatically)

Pinmux might be an option, as this HW is some pin multiplexer, but in
this case it's not related SoC pins and doesn't control which internal
devices are connected to the outside.

I've already thought about introducing a new class for the pretty much
the opposite of extconn (maybe call it extswitch ?). There also might
be an semantic overlap w/ other subsystems, eg. kvm's connector
switching. Not sure whether yet another subsystem is the optimal
solution here.

What's your oppinion on that ?


--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

                 reply	other threads:[~2019-08-20 10:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=a1bb9419-c499-dbd8-8e15-e7655b484d6e@metux.net \
    --to=lkml@metux.net \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).