All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Michael Walle <michael@walle.cc>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	Jonas Gorski <jonas.gorski@gmail.com>,
	Necip Fazil Yildiran <fazilyildiran@gmail.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 03/15] pinctrl: bcm: add bcm63xx base code
Date: Thu, 11 Mar 2021 00:59:11 +0100	[thread overview]
Message-ID: <CACRpkdbP7kAVR9ORQuj7W9iT3EDE1S3iZ-1q+kBoQ8R0TUVMJA@mail.gmail.com> (raw)
In-Reply-To: <EC7F8938-63CB-43D9-AE75-644B2E647360@gmail.com>

On Wed, Mar 10, 2021 at 8:25 AM Álvaro Fernández Rojas
<noltari@gmail.com> wrote:

> > // for now, since we have not an analogue (yet)

> > node ==> to_of_node(fwnode)
>
> So you want me to convert everything to fwnode, but then I would need to use of_node here…
> It makes more sense to me to use of_node for now and convert it to fwnode in the future…
> @Linus, what do you think?

I am aware of the ambition to use fwnode more to more things.

To me it is most important on things that will potentially run with
both OF and ACPI.
Typical example: ARM Qualcomm SoCs. New drivers for Aarch64 platforms.

This is a legacy MIPS platform, and we have tons of legacy platforms for ARM
etc which will never get converted to fwnode, sadly.

Is it realistic that these MIPS platforms will run ACPI in addition to
OF? Is ACPI even available on MIPS? Isn't OF the preferred HW description
language for anything MIPS?

Yours,
Linus Walleij

WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Michael Walle <michael@walle.cc>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	 Florian Fainelli <f.fainelli@gmail.com>,
	 bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	 Jonas Gorski <jonas.gorski@gmail.com>,
	Necip Fazil Yildiran <fazilyildiran@gmail.com>,
	 "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 03/15] pinctrl: bcm: add bcm63xx base code
Date: Thu, 11 Mar 2021 00:59:11 +0100	[thread overview]
Message-ID: <CACRpkdbP7kAVR9ORQuj7W9iT3EDE1S3iZ-1q+kBoQ8R0TUVMJA@mail.gmail.com> (raw)
In-Reply-To: <EC7F8938-63CB-43D9-AE75-644B2E647360@gmail.com>

On Wed, Mar 10, 2021 at 8:25 AM Álvaro Fernández Rojas
<noltari@gmail.com> wrote:

> > // for now, since we have not an analogue (yet)

> > node ==> to_of_node(fwnode)
>
> So you want me to convert everything to fwnode, but then I would need to use of_node here…
> It makes more sense to me to use of_node for now and convert it to fwnode in the future…
> @Linus, what do you think?

I am aware of the ambition to use fwnode more to more things.

To me it is most important on things that will potentially run with
both OF and ACPI.
Typical example: ARM Qualcomm SoCs. New drivers for Aarch64 platforms.

This is a legacy MIPS platform, and we have tons of legacy platforms for ARM
etc which will never get converted to fwnode, sadly.

Is it realistic that these MIPS platforms will run ACPI in addition to
OF? Is ACPI even available on MIPS? Isn't OF the preferred HW description
language for anything MIPS?

Yours,
Linus Walleij

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-03-11  0:00 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06 15:56 [PATCH v5 00/15] pinctrl: add BCM63XX pincontrol support Álvaro Fernández Rojas
2021-03-06 15:56 ` Álvaro Fernández Rojas
2021-03-06 15:56 ` [PATCH v5 01/15] gpio: guard gpiochip_irqchip_add_domain() with GPIOLIB_IRQCHIP Álvaro Fernández Rojas
2021-03-06 15:56   ` Álvaro Fernández Rojas
2021-03-09 23:08   ` Michael Walle
2021-03-09 23:08     ` Michael Walle
2021-03-06 15:56 ` [PATCH v5 02/15] gpio: regmap: set gpio_chip of_node Álvaro Fernández Rojas
2021-03-06 15:56   ` Álvaro Fernández Rojas
2021-03-06 16:26   ` Andy Shevchenko
2021-03-06 16:26     ` Andy Shevchenko
2021-03-20  1:47   ` kernel test robot
2021-03-06 15:57 ` [PATCH v5 03/15] pinctrl: bcm: add bcm63xx base code Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-07 19:05   ` Andy Shevchenko
2021-03-07 19:05     ` Andy Shevchenko
2021-03-10  7:25     ` Álvaro Fernández Rojas
2021-03-10  7:25       ` Álvaro Fernández Rojas
2021-03-10 23:59       ` Linus Walleij [this message]
2021-03-10 23:59         ` Linus Walleij
2021-03-06 15:57 ` [PATCH v5 04/15] dt-bindings: add BCM6328 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-08 22:44   ` Rob Herring
2021-03-08 22:44     ` Rob Herring
2021-03-06 15:57 ` [PATCH v5 05/15] pinctrl: add a pincontrol driver for BCM6328 Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-06 15:57 ` [PATCH v5 06/15] dt-bindings: add BCM6358 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-06 15:57 ` [PATCH v5 07/15] pinctrl: add a pincontrol driver for BCM6358 Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-06 15:57 ` [PATCH v5 08/15] dt-bindings: add BCM6362 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-06 15:57 ` [PATCH v5 09/15] pinctrl: add a pincontrol driver for BCM6362 Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-06 15:57 ` [PATCH v5 10/15] dt-bindings: add BCM6368 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-06 15:57 ` [PATCH v5 11/15] pinctrl: add a pincontrol driver for BCM6368 Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-06 15:57 ` [PATCH v5 12/15] dt-bindings: add BCM63268 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-06 15:57 ` [PATCH v5 13/15] pinctrl: add a pincontrol driver for BCM63268 Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-06 15:57 ` [PATCH v5 14/15] dt-bindings: add BCM6318 pincontroller binding documentation Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas
2021-03-08 22:50   ` Rob Herring
2021-03-08 22:50     ` Rob Herring
2021-03-06 15:57 ` [PATCH v5 15/15] pinctrl: add a pincontrol driver for BCM6318 Álvaro Fernández Rojas
2021-03-06 15:57   ` Álvaro Fernández Rojas

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=CACRpkdbP7kAVR9ORQuj7W9iT3EDE1S3iZ-1q+kBoQ8R0TUVMJA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=fazilyildiran@gmail.com \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=noltari@gmail.com \
    --cc=robh+dt@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.