Skip to content

i.MX6 (DQ/DLS): consolidate mux and pad names

Eric Nelson u-boot 5 versions – New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest posting 4/40 of 5 patches 0 repliesNew
  2. v2 posting 3/40 of 5 patches 0 repliesSuperseded
  3. v2 posting 2/40 of 5 patches 0 repliesSuperseded
Earlier versions · 2
VersionPostedPatchesRepliesStatus
v2 posting 1/45 patches0 repliesSuperseded
v10 of 5 patches0 repliesSuperseded

Patches in v2 posting 4/4 No applies recorded yet

None of the 5 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [U-Boot] [PATCH V2 0/5] i.MX6 (DQ/DLS): consolidate mux and pad names

Hi Fabio,

Quoted 13 lines · Fabio Estevam

Hi Eric,

Quoted 8 lines · Eric Nelson

In the RFC e-mail change regarding README.imx6-something, I proposed that we replace the pad declaration form currently in use:

enum {
         MX6_PAD_SD3_DAT2__USDHC3_DAT2 = IOMUX_PAD(...)
};
Quoted 9 lines
Quoted 5 lines

with macros of this form so that they can be pre-pended with MX6Q_ and MX6DL_ when we need both in an image (SPL?) that can run on either variant of processor.

         MX6_PAD_DECL(SD3_DAT2__USDHC3_DAT2, ...)

I thinks this macro approach should work fine. Do we see any objections?

Not so far.

I think everybody would rather not have so much macro-fu, but the only real alternatives are either lots of duplication or an immediate "big bang" switch to have all boards support all CPU variants.

Since we have some boards that are expected to be Solo-Only or Quad-Only forever, we'd like to retain the single-variant build without explicitly listing the pads as MX6Q_ or MX6DL_.

Quoted 6 lines
Quoted 3 lines

If we do this, then lining up the columns based on the first form doesn't make much sense.

Understood it now. Thanks for clarifying.

Cool.

I'll re-base the macro patch I have floating here and submit it officially.

It's mostly mechanical and easy to validate.

I'll also submit an updated patch for README.imx6, but will keep it separate because I expect more suggestions regarding the wording.

Regards,

Eric