mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Guillaume La Roque" <glaroque@baylibre.com>,
	"Nishanth Menon" <nm@ti.com>, "Tero Kristo" <kristo@kernel.org>
Cc: "Andrew Davis" <afd@ti.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] firmware: config: ti-sci: Default set to ARCH_K3 for the ti sci driver
Date: Wed, 19 Mar 2025 22:45:57 +0100	[thread overview]
Message-ID: <c506a805-9221-4afe-8d98-af0ca97a1fd2@app.fastmail.com> (raw)
In-Reply-To: <20250220-ti-firmware-v2-1-ff26883c6ce9@baylibre.com>

On Thu, Feb 20, 2025, at 14:31, Guillaume La Roque wrote:
> With ARCH_K3=y we cannot enable TI_SCI_PROTOCOL=m because
> ARCH_K3 selects TI_SCI_PROTOCOL.
>
> Modify the logic to enable TI_SCI_PROTOCOL by default when ARCH_K3=y
> allowing us to submit a future patch to remove select on ARCH_K3 without
> breaking existing users.
>
> Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
> ---
> Link to comment done on last serie [1] we come back on first version of
> series[2] to not use imply but set deps on ARCH_K3 in driver directly.
> An other patch will be sent to update Kconfig.platform when this patch
> is merged.

I just merged the patch and hadn't seen the earlier discussion,
just two small notes from me:

- thanks for doing it this way instead of the backwards 'imply'
- there is really no need to split it into two steps, since the
  change to the Kconfig.platforms file logically goes with this
  one and I would merge both through the SoC tree, having it
  as a single patch would make sense.

        Arnd

  parent reply	other threads:[~2025-03-19 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 13:31 Guillaume La Roque
2025-02-26 18:49 ` Nishanth Menon
2025-03-19 21:45 ` Arnd Bergmann [this message]
2025-03-20 13:41   ` Guillaume La Roque

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=c506a805-9221-4afe-8d98-af0ca97a1fd2@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=afd@ti.com \
    --cc=glaroque@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.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 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®