All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Dhruva Gole <d-gole@ti.com>
Cc: linux-omap@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Keerthy <j-keerthy@ti.com>, Kevin Hilman <khilman@baylibre.com>,
	Nishanth Menon <nm@ti.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] bus: ti-sysc: Build driver for TI K3 SoCs
Date: Wed, 9 Aug 2023 12:26:48 +0300	[thread overview]
Message-ID: <20230809092648.GE11676@atomide.com> (raw)
In-Reply-To: <20230805052052.zjamrxarn6uc4i5l@dhruva>

* Dhruva Gole <d-gole@ti.com> [230805 05:20]:
> On Aug 04, 2023 at 13:38:58 +0300, Tony Lindgren wrote:
> > Allow building ti-sysc also for K3 SoCs. This allows configuring the wkup
> > domain devices for SYSCONFIG register wake-up events in a generic way.
> 
> If possible, can we add explanation also on why it now needs to be default y
> in the Kconfig?

Sure will add that for v2.

Thanks,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Dhruva Gole <d-gole@ti.com>
Cc: linux-omap@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Keerthy <j-keerthy@ti.com>, Kevin Hilman <khilman@baylibre.com>,
	Nishanth Menon <nm@ti.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] bus: ti-sysc: Build driver for TI K3 SoCs
Date: Wed, 9 Aug 2023 12:26:48 +0300	[thread overview]
Message-ID: <20230809092648.GE11676@atomide.com> (raw)
In-Reply-To: <20230805052052.zjamrxarn6uc4i5l@dhruva>

* Dhruva Gole <d-gole@ti.com> [230805 05:20]:
> On Aug 04, 2023 at 13:38:58 +0300, Tony Lindgren wrote:
> > Allow building ti-sysc also for K3 SoCs. This allows configuring the wkup
> > domain devices for SYSCONFIG register wake-up events in a generic way.
> 
> If possible, can we add explanation also on why it now needs to be default y
> in the Kconfig?

Sure will add that for v2.

Thanks,

Tony

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

  reply	other threads:[~2023-08-09  9:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 10:38 [PATCH 1/3] bus: ti-sysc: Fix build warning for 64-bit build Tony Lindgren
2023-08-04 10:38 ` Tony Lindgren
2023-08-04 10:38 ` [PATCH 2/3] bus: ti-sysc: Build driver for TI K3 SoCs Tony Lindgren
2023-08-04 10:38   ` Tony Lindgren
2023-08-05  5:20   ` Dhruva Gole
2023-08-05  5:20     ` Dhruva Gole
2023-08-09  9:26     ` Tony Lindgren [this message]
2023-08-09  9:26       ` Tony Lindgren
2023-08-04 10:38 ` [PATCH 3/3] bus: ti-sysc: Configure uart quirks for k3 SoC Tony Lindgren
2023-08-04 10:38   ` Tony Lindgren
2023-08-05  5:17 ` [PATCH 1/3] bus: ti-sysc: Fix build warning for 64-bit build Dhruva Gole
2023-08-05  5:17   ` Dhruva Gole
2023-08-05 17:23   ` Nishanth Menon
2023-08-05 17:23     ` Nishanth Menon
2023-08-09  7:27     ` Tony Lindgren
2023-08-09  7:27       ` Tony Lindgren

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=20230809092648.GE11676@atomide.com \
    --to=tony@atomide.com \
    --cc=d-gole@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=j-keerthy@ti.com \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@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 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.