public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Roger Quadros <rogerq@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Kevin Hilman <khilman@baylibre.com>,
	linux-omap@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	devicetree@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH v2 1/2] ARM: dts: omap4: panda: fix resources needed for Panda
Date: Thu, 10 Apr 2025 10:16:06 +0200	[thread overview]
Message-ID: <20250410101512.5b4c12b2@kemnade.info> (raw)
In-Reply-To: <7aefa588-9f64-4bb4-8782-05eb1ef9d5b2@kernel.org>

On Wed, 2 Apr 2025 15:11:47 +0300
Roger Quadros <rogerq@kernel.org> wrote:

> On 30/03/2025 18:14, Andreas Kemnade wrote:
> > The Pandaboard needs a 32k clock in the TWL6030 to be enabled
> > to work. With some luck, it is enabled by some U-Boot fork.
> > Do not rely on it and properly specify the requirement.  
> 
> It would be nice to mention who exactly needs the 32K clock.
> From your changes it looks like the wl12xx module needs it?
> 
correct, I will send a better descrption.

Regards,
Andreas

  reply	other threads:[~2025-04-10  8:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-30 15:13 [PATCH v2 0/2] ARM: dts: omap4: panda: TiWilink improvements Andreas Kemnade
2025-03-30 15:14 ` [PATCH v2 1/2] ARM: dts: omap4: panda: fix resources needed for Panda Andreas Kemnade
2025-04-02 12:11   ` Roger Quadros
2025-04-10  8:16     ` Andreas Kemnade [this message]
2025-03-30 15:14 ` [PATCH v2 2/2] ARM: dts: omap4: panda: cleanup bluetooth Andreas Kemnade
2025-04-02 11:54   ` Roger Quadros
2025-04-02 18:06     ` Andreas Kemnade

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=20250410101512.5b4c12b2@kemnade.info \
    --to=andreas@kemnade.info \
    --cc=aaro.koskinen@iki.fi \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.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