tegra_cpufreq_cpu_emc_map_dt_init() didn't consider the case that
cpu_emc_map provided in DT can be incomplete, e.g. like this:

cpu_emc_map = <2112000  2133000>,
                <1881600 800000>,
                <1574400 665000>,
                <1267200>;

We should strip incomplete entry as we already do for tegra194_cpufreq
so that driver won't have unknown/undefined behavior.

Bug 200512604
Bug 200551611

Change-Id: Ifad5e8a987bbd92b83cfd4cb1a649c3b61dfd072
Signed-off-by: Leon Yu <leoyu@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/2212825
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Bo Yan <byan@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>

We've been using duplicate code and incompatible format/name/type for
CPU to EMC frequency mapping table related stuffs on different SoCs.
This not only confuses users but also makes it difficult to customize
and maintain these mapping tables.

This change aims to provide unified interfaces and structures that can
be used by existing (and also future) cpufreq drivers.

Bug 200512604

Change-Id: I380235c05ac045fe09ecdf4bd313e8c40286260a
Signed-off-by: Leon Yu <leoyu@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/2183389
Reviewed-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>