LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: "Linus Walleij" <linus.walleij@linaro.org>,
	"Sören Brinkmann" <soren.brinkmann@xilinx.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Grant Likely <grant.likely@arm.com>,
	Mark Brown <broonie@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
	boot-architecture@lists.linaro.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Michal Simek <michal.simek@xilinx.com>,
	Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [RFC PATCH] driver core: make deferring probe forever optional
Date: Mon, 14 May 2018 09:37:15 +0200	[thread overview]
Message-ID: <c6655f84-747f-c08b-7b9c-f76ff8857567@suse.de> (raw)
In-Reply-To: <CACRpkdaYN-wKErERP_65T2NH6L-+8O_ugSgg7pXfkaLkn1A2KQ@mail.gmail.com>

On 05/14/2018 12:01 AM, Linus Walleij wrote:
> On Wed, May 9, 2018 at 11:44 AM, Alexander Graf <agraf@suse.de> wrote:
>> On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
>>> Can you please name platform that has enough support for Alexander to
>>> care about backwards and forwards compatibility but lacks a pinctrl
>>> driver.
>> ZynqMP is one example that immediately comes to my mind. I'm sure there are
>> others too.
> Why isn't that using drivers/pinctrl/pinctrl-zynq.c?
>
> How is it so very different from (old) Zynq as it is already using
> the same GPIO driver?

That one is very simple: ZynqMP is usually an AMP system where Linux 
doesn't have full knowledge of the overall system. IIUC they have a tiny 
microblaze (PMU) that does the actual full system configuration for 
peripherals that may interfere with each other. This architecture also 
allows for safety critical code to run alongside a (less safe) Linux system.

I think we'll see architectures like this pop up more over time. TI 
Sitara has similar issues. I know that Jailhouse ran into exactly that 
problem before. I also know that during Linaro Connect Budapest even the 
OP-TEE people realized the current model is bad, because Linux may 
control pins/clocks/etc of devices that the secure world wants to use.

So I actually believe we will see more SoCs in the future that may even 
start with Linux controllable pinctrl or no pinctrl driver but then will 
move to firmware controlled drivers once it starts being necessary.


Alex

  reply	other threads:[~2018-05-14  7:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 21:31 Rob Herring
2018-05-01 22:08 ` Greg Kroah-Hartman
2018-05-02 11:40 ` Robin Murphy
2018-05-02 14:48   ` Rob Herring
2018-05-02 18:49     ` Robin Murphy
2018-05-05  1:25       ` Mark Brown
2018-05-07 13:37         ` Rob Herring
2018-05-02 13:16 ` Alexander Graf
2018-05-07 18:31 ` Bjorn Andersson
2018-05-07 19:55   ` Rob Herring
2018-05-07 22:34     ` Bjorn Andersson
2018-05-09  9:18       ` Mark Brown
2018-05-09  9:57       ` Alexander Graf
2018-05-09  9:44   ` Alexander Graf
2018-05-13 22:01     ` Linus Walleij
2018-05-14  7:37       ` Alexander Graf [this message]
2018-05-14 12:44         ` Michal Simek
2018-05-16 14:38           ` Linus Walleij

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=c6655f84-747f-c08b-7b9c-f76ff8857567@suse.de \
    --to=agraf@suse.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=boot-architecture@lists.linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jan.kiszka@siemens.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=soren.brinkmann@xilinx.com \
    --subject='Re: [RFC PATCH] driver core: make deferring probe forever optional' \
    /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

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).