mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Johannes Zink <j.zink@pengutronix.de>, barebox@lists.infradead.org
Cc: patchwork-jzi@pengutronix.de, Juergen Borleis <j.borleis@pengutronix.de>
Subject: Re: [PATCH] ARM: i.MX8MP: add Koenig+Bauer Alphajet board
Date: Thu, 1 Jun 2023 11:14:33 +0200	[thread overview]
Message-ID: <0eafda1b-a0fe-5701-5ed2-c6e0b296c1f4@pengutronix.de> (raw)
In-Reply-To: <69f2ace5-cb7f-4dbb-3d24-9fc0a25693a1@pengutronix.de>

On 01.06.23 11:08, Johannes Zink wrote:
> On 6/1/23 10:49, Ahmad Fatoum wrote:
>> On 01.06.23 09:40, Johannes Zink wrote:
>>> +static const struct of_device_id kb_alphajet_of_match[] = {
>>> +    { .compatible = "kb,alphajet" },
>>
>> Is anything of the above really alphajet specific? If both PHY and QSPI flash
>> are on SOM, you should match against SoM compatible here.
> 
> No, the above can be moved to a generic SoM part. I assume though, that stuff will not work properly (TM) as long as the individual boards don't enable deep probe support (at least it did not work for my machine), though I think this should be kept in the baseboard-specific part, right?

I'd just enable deep probe for the SoM compatible. If someone else's
baseboard support clashes with deep probe, they should fix that.

>> We want to avoid future boards with Congatec modules needing to duplicate
>> code. Can you split this up:
>>
>> config MACH_CONGATEC_QX8MP
>>     bool "Koenig+Bauer AlphaJet Board"
> 
> I guess this should probably be
> bool "Congatec conga-QMX8-Plus"
> then?

Just drop the prompt altogether and add _SOM at the end of the
config symbol. If we ever add the Congatec baseboard, it would
just select the SoM, but there's no reason to be able to select
the SoM from menuconfig without a board.

> 
>>     select ARCH_IMX8MP
>>     select FIRMWARE_IMX_LPDDR4_PMU_TRAIN
>>     select FIRMWARE_IMX8MP_ATF
>>     select ARM_SMCCC
>>     select MCI_IMX_ESDHC_PBL
>>     select IMX8M_DRAM
>>     select I2C_IMX_EARLY
>>
>> config MACH_KB_ALPHAJET
>>     bool "Koenig+Bauer AlphaJet Board"
>>     select MACH_CONGATEC_QX8MP
>>
> 
> ack.
> 
>>> +
>>>   config MACH_PHYTEC_SOM_IMX8MQ
>>>       bool "Phytec i.MX8M SOM"
>>>       select ARCH_IMX8MQ
>>> diff --git a/images/Makefile.imx b/images/Makefile.imx
>>> index 9e70ba50a162..bfb2fcdd8ede 100644
>>> --- a/images/Makefile.imx
>>> +++ b/images/Makefile.imx
>>> @@ -473,6 +473,11 @@ CFG_start_variscite_imx8mp_dart.pblb.imximg = $(board)/variscite-dt8mcustomboard
>>>   FILE_barebox-variscite-imx8mp-dart-cb.img = start_variscite_imx8mp_dart.pblb.pimximg
>>>   image-$(CONFIG_MACH_VARISCITE_DT8MCUSTOMBOARD_IMX8MP) += barebox-variscite-imx8mp-dart-cb.img
>>>   +pblb-$(CONFIG_MACH_KB_ALPHAJET) += start_congatec_qx8p
>>
>> This is defined no where. Should this be qx8mp too?

Also, you should add the board to arch/arm/configs/{multi_v8_defconfig,imx_v8_defconfig}

>>
>>> +CFG_start_kb_alphajet.pblb.imximg = $(board)/kb-imx8mp-alphajet/flash-header-imx8mp-cgtqx8p.imxcfg
>>> +FILE_barebox-kb-alphajet.img = start_kb_alphajet.pblb.pimximg
>>> +image-$(CONFIG_MACH_KB_ALPHAJET) += barebox-kb-alphajet.img
>>> +
>>>   # ----------------------- i.MX8mq based boards --------------------------
>>>   pblb-$(CONFIG_MACH_NXP_IMX8MQ_EVK) += start_nxp_imx8mq_evk
>>>   CFG_start_nxp_imx8mq_evk.pblb.imximg = $(board)/nxp-imx8mq-evk/flash-header-imx8mq-evk.imxcfg
>>>
>>> ---
>>> base-commit: 64c528dd0bff0953192d90fbbc34b3d45d8116d0
>>> change-id: 20230601-koenigbauer-alphajet-upstreaming-2085dc8b9f77
>>>
>>> Best regards,
>>
> 
> Best regards
> Johannes
> 

-- 
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:[~2023-06-01  9:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01  7:40 Johannes Zink
2023-06-01  7:53 ` Marco Felsch
2023-06-01  8:28 ` Sascha Hauer
2023-06-01  8:40   ` Marco Felsch
2023-06-01  8:41   ` Johannes Zink
2023-06-01  8:50     ` Ahmad Fatoum
2023-06-01  8:49 ` Ahmad Fatoum
2023-06-01  9:08   ` Johannes Zink
2023-06-01  9:14     ` Ahmad Fatoum [this message]
2023-06-01  9:20       ` Johannes Zink

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=0eafda1b-a0fe-5701-5ed2-c6e0b296c1f4@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=j.borleis@pengutronix.de \
    --cc=j.zink@pengutronix.de \
    --cc=patchwork-jzi@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