All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 03/26] imx8mm_evk: Switch to new imx8mm evk board
Date: Fri, 14 May 2021 09:30:30 -0300	[thread overview]
Message-ID: <CAOMZO5C6CeF0ed3fn09cRLkKA-25ZZyHYNSp8c0D_Rg+_N3Lvw@mail.gmail.com> (raw)
In-Reply-To: <AM6PR06MB46915ED2D2EDDA224D2DB731A6529@AM6PR06MB4691.eurprd06.prod.outlook.com>

Hi Andrey,

On Wed, May 12, 2021 at 6:47 PM ZHIZHIKIN Andrey
<andrey.zhizhikin@leica-geosystems.com> wrote:

> > Update PMIC to use PCA9540, the legacy board not supported by NXP
>
> This commit seems rather a "nuclear" to me, as de-facto it drops the initialization of ROMH PMIC in
> favor of PCA one, leaving all the previous board revisions not to be properly sourced.
>
> I know that there might be no intention to provide a support for earlier revisions of i.MX8M Mini
> EVKs from NXP, but providing no backward compatibility to those boards which are still in use by
> a lot of people for development purposes is highly undesirable either.
>
> TBH, I've tested this patch on the old EVK where ROMH PMIC is present, and apart from having some
> error messages in SPL regarding the register writes - it does boots. What worries me the most though
> is that DTS changes some voltage settings, which I'm not sure how the SOC would react on.
>
> To my opinion, this patch should either be complemented with the mechanism to provide a
> level of backward compatibility (where the PMIC can be dynamically identified and instantiated),
> or the separate implementation should be presented which would make the old board type not to
> be bootable at all if it is considered not to be supported any longer. Or this patch should be reverted
> in an effort to come up with a solution which covers new revision without "damaging" the currently
> integrated one.
>
> Fabio / Stefano,
> Do you have any thoughts here on how this should be handled further, considering the fact that the
> backward compatibility of 2021.07 release is not kept for this board type across multiple revisions?
>
> I'd really like to get your opinion here as I do have those boards in development and would need to
> come up with the idea on what to do with them.
>
> Also, this should be taken care of in the Yocto, since there is only one definition of the i.MX8MM EVK
> machine which does not make any distinction regarding the revision.

You bring a good point.

What about adding a new defconfig to support the old imx8mm-evk with
the Rohm PMIC?

Then we could have imx8mm_evk_defconfig for the new version and
imx8mm_evk_rohm_defconfig for the old one.

What do you think?

Thanks

  reply	other threads:[~2021-05-14 12:30 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  7:56 [PATCH 00/26] imx: update for i.MX8M Peng Fan
2021-03-19  7:56 ` [PATCH 01/26] tools: imx image: fix write warning Peng Fan
2021-03-19  7:56 ` [PATCH 02/26] imx8mm_evk: Update to latest LPDDR4 script Peng Fan
2021-03-24 21:19   ` Tim Harvey
2021-03-25  1:15     ` Peng Fan
2021-03-19  7:56 ` [PATCH 03/26] imx8mm_evk: Switch to new imx8mm evk board Peng Fan
2021-05-12 21:47   ` ZHIZHIKIN Andrey
2021-05-14 12:30     ` Fabio Estevam [this message]
2021-05-14 15:29       ` Ricardo Salveti
2021-05-14 15:59         ` Fabio Estevam
2021-05-16 14:31         ` ZHIZHIKIN Andrey
2021-05-18 13:14           ` Vanessa Maegima
2021-05-18 19:51             ` ZHIZHIKIN Andrey
2021-05-16 14:21       ` ZHIZHIKIN Andrey
2021-05-17  0:34     ` Peng Fan
2021-03-19  7:56 ` [PATCH 04/26] imx8mm/p: remove boot.cmd Peng Fan
2021-03-19  7:56 ` [PATCH 05/26] imx8mm_evk: add/cleanup variable for distro Peng Fan
2021-03-19  7:56 ` [PATCH 06/26] imx8mp_evk: " Peng Fan
2021-03-19  7:56 ` [PATCH 07/26] imx8mp: ddr: Add inline ECC feature support Peng Fan
2021-03-19  7:57 ` [PATCH 08/26] imx8mp_evk: Update LPDDR4 timing for new FW 202006 Peng Fan
2021-03-19  7:57 ` [PATCH 09/26] imx8mp_evk: Update LPDDR4 refresh time Peng Fan
2021-03-19  7:57 ` [PATCH 10/26] imx8mp: refine power on imx8mp board Peng Fan
2021-03-19  7:57 ` [PATCH 11/26] imx8mp_evk: spl: clean up including headers Peng Fan
2021-03-19  7:57 ` [PATCH 12/26] imx8mp_evk: Increase VDD_ARM to 0.95v Overdrive voltage Peng Fan
2021-03-19  7:57 ` [PATCH 13/26] imx8mn: Update the DDR4 timing script on imx8mn ddr4 evk Peng Fan
2021-03-19  7:57 ` [PATCH 14/26] power: pca9450: add a new parameter for power_pca9450_init Peng Fan
2021-03-21 22:41   ` Jaehoon Chung
2021-03-19  7:57 ` [PATCH 15/26] imx8mn_evk: drop duplicated code Peng Fan
2021-03-19  7:57 ` [PATCH 16/26] imx8mn: Add LPDDR4 EVK board support Peng Fan
2021-03-19  7:57 ` [PATCH 17/26] imx8mn: Add low drive mode support for DDR4/LPDDR4 EVK Peng Fan
2021-03-19  7:57 ` [PATCH 18/26] imx: logos: use NXP logo Peng Fan
2021-03-19  7:57 ` [PATCH 19/26] imx8mn: Add support for 11x11 UltraLite part number Peng Fan
2021-03-19  7:57 ` [PATCH 20/26] imx8m: Update thermal and PMU kernel nodes for dual/single cores Peng Fan
2021-03-19  7:57 ` [PATCH 21/26] imx8m: soc: update fuse path Peng Fan
2021-03-19  7:57 ` [PATCH 22/26] imx8m: ddr: Disable CA VREF Training for LPDDR4 Peng Fan
2021-03-24 21:25   ` Tim Harvey
2021-03-25  8:14     ` Stefano Babic
2021-03-25  8:35       ` Peng Fan
2021-03-19  7:57 ` [PATCH 23/26] arch: mach-imx: imx8m: fix unique_id read error for imx8mp Peng Fan
2021-03-19  7:57 ` [PATCH 24/26] iMX8MQ: Recognize the B2 revision Peng Fan
2021-03-19  7:57 ` [PATCH 25/26] misc: ocotp: Update OCOTP driver for iMX8MQ B2 Peng Fan
2021-03-19  7:57 ` [PATCH 26/26] imx8mq_evk: Applying default LPDDR4 script for B2 Peng Fan

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=CAOMZO5C6CeF0ed3fn09cRLkKA-25ZZyHYNSp8c0D_Rg+_N3Lvw@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=u-boot@lists.denx.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 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.