mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Lars Schmidt <l.schmidt@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: k3: beagleplay: Enable 32k crystal
Date: Thu, 12 Jun 2025 09:40:57 +0200	[thread overview]
Message-ID: <aEqEiWXb6jB0h9yz@pengutronix.de> (raw)
In-Reply-To: <13ed49a0-3e05-4fe7-9966-231229600f94@pengutronix.de>

On Wed, Jun 11, 2025 at 08:24:22PM +0200, Ahmad Fatoum wrote:
> Hello Lars,
> 
> On 6/11/25 11:36, Lars Schmidt wrote:
> > Signed-off-by: Lars Schmidt <l.schmidt@pengutronix.de>
> 
> Would it make sense to describe the existence of the external 32K
> crystal in the DT, so we don't need to add code for every board?

Yes. For now it's ok though.

Sascha

> 
> Thanks,
> Ahmad
> 
> > ---
> >  arch/arm/boards/beagleplay/Makefile |  1 +
> >  arch/arm/boards/beagleplay/board.c  | 30 +++++++++++++++++++++++++++++
> >  2 files changed, 31 insertions(+)
> >  create mode 100644 arch/arm/boards/beagleplay/board.c
> > 
> > diff --git a/arch/arm/boards/beagleplay/Makefile b/arch/arm/boards/beagleplay/Makefile
> > index a8c7320bdb..2d257fb4b2 100644
> > --- a/arch/arm/boards/beagleplay/Makefile
> > +++ b/arch/arm/boards/beagleplay/Makefile
> > @@ -1,2 +1,3 @@
> >  pbl-y += lowlevel.o
> > +obj-y += board.o
> >  pbl-$(CONFIG_MACH_K3_CORTEX_R5) += entry-r5.o ddr.o
> > diff --git a/arch/arm/boards/beagleplay/board.c b/arch/arm/boards/beagleplay/board.c
> > new file mode 100644
> > index 0000000000..dd42f0b7f0
> > --- /dev/null
> > +++ b/arch/arm/boards/beagleplay/board.c
> > @@ -0,0 +1,30 @@
> > +// SPDX-License-Identifier: GPL-2.0-only
> > +
> > +#define pr_fmt(fmt) "beagleplay: " fmt
> > +
> > +#include <linux/kernel.h>
> > +#include <mach/k3/common.h>
> > +#include <driver.h>
> > +#include <bbu.h>
> > +
> > +static int beagleplay_probe(struct device *dev)
> > +{
> > +	am625_enable_32k_crystal();
> > +
> > +	return 0;
> > +}
> > +
> > +static __maybe_unused struct of_device_id beagleplay_ids[] = {
> > +	{
> > +		.compatible = "beagle,am625-beagleplay",
> > +	}, {
> > +		/* sentinel */
> > +	}
> > +};
> > +
> > +static struct driver beagleplay_driver = {
> > +	.name = "beagleplay",
> > +	.probe = beagleplay_probe,
> > +	.of_compatible = beagleplay_ids,
> > +};
> > +coredevice_platform_driver(beagleplay_driver);
> 
> -- 
> Pengutronix e.K.                  |                             |
> Steuerwalder Str. 21              | http://www.pengutronix.de/  |
> 31137 Hildesheim, Germany         | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-06-12  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11  9:36 Lars Schmidt
2025-06-11 18:24 ` Ahmad Fatoum
2025-06-12  7:40   ` Sascha Hauer [this message]
2025-06-12  7:40 ` Sascha Hauer

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=aEqEiWXb6jB0h9yz@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=l.schmidt@pengutronix.de \
    /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