All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: Wally Yeh <wally.yeh@atrustcorp.com>
Cc: meta-freescale <meta-freescale@yoctoproject.org>
Subject: Re: linux-imx 3.10.17 can't build without CONFIG_SOC_IMX6SL selected.
Date: Fri, 06 Feb 2015 12:19:18 +0200	[thread overview]
Message-ID: <54D49526.5020606@mail.bg> (raw)
In-Reply-To: <CANdq1h+abdJpXRfgdgLmQ=Q=+p=qrpDXqNxxNjXQ8+5G=Bafzw@mail.gmail.com>

Hi Wally,

On 02/06/2015 11:33 AM, Wally Yeh wrote:
> Hi, guys:
>      Since my board is i.mx6Q sabresd. Only I wanna keep
> is CONFIG_SOC_IMX6Q, so I removed all other CONFIG_SOC_* .
>      But if I remove CONFIG_SOC_IMX6SL, linux-imx will never build
> successfully.
>
>      If this config is really necessary, shouldn't we just make
> CONFIG_SOC_IMX6SL always be selected with CONFIG_SOC_IMX6Q?

The config is needed, as there are hard-coded invocations of
mx6s-specific code in the kernel. If you remove the CONFIG_SOC_IMX6SL,
linkage will fail while looking for stuff like:

imx6sl_set_wait_clk()
init_mmdc_lpddr2_settings()
update_lpddr2_freq()

If you really insist on changing this, you can axe-hack all source
files which contain invocations of cpu_is_imx6sl(). Or, fix it and
submit a patch.

Probably you're right that it could have been implemented better, but
unless we improve it, that's what we have :D.

Kind regards,
Nikolay


  reply	other threads:[~2015-02-06 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06  9:33 linux-imx 3.10.17 can't build without CONFIG_SOC_IMX6SL selected Wally Yeh
2015-02-06 10:19 ` Nikolay Dimitrov [this message]
2015-02-06 11:00   ` Otavio Salvador
2015-02-06 11:12     ` Wally Yeh
2015-02-06 12:22       ` Otavio Salvador

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=54D49526.5020606@mail.bg \
    --to=picmaster@mail.bg \
    --cc=meta-freescale@yoctoproject.org \
    --cc=wally.yeh@atrustcorp.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 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.