The whole rounding stuff really depends on a specific resolution.

This reverts commit 4dd83942b418b937e3da02746baabf63f37fe682.

Force round down in division calculating required logo height as
preceding code did round up as follows:

logo_lines = DIV_ROUND_UP(logo_height, vc->vc_font.height);

Which resulted in no boot-logo shown at all due to not enough lines
being available.

Additionally disable cursor for custom boot logo.

Using this unconditionally cuts the birds feet (;-p).

This reverts commit 491f263ebfb338c59abfbde6d4e0e7256a0150fa.

This works around a issue we see when using eMMC 4.5 on tegra
SDHCI host controller.

The 1.8V quirk also affected the internal eMMC which disabled newer
modes such as SDR50, SDR104 and DDR50. This in turn lead to an
out of spec usage since the clock was still 50MHz.

By creating a no_1v8 field in the platform data we can now enable
this work around on a per-instance basis. Hence we enable the
quirk only on the controllers which are connected to the external
SD-slots.

Force round down in division calculating required logo height as
preceding code did round up as follows:

logo_lines = DIV_ROUND_UP(logo_height, vc->vc_font.height);

Which resulted in no boot-logo shown at all due to not enough lines
being available.

This commit resolves an issue of non-working vi camera driver
on Colibri T20 occured after a l4t-r16-r4 merge.

Don't initialize the whole display controller (dc) when framebuffer
mode is set to off.

This avoids creation of the /dev/tegra_dc_x device. The tegra X
driver requires for each tegra_dc_x device an framebuffer device
with the same id. This patch avoids creation of both, which makes
the tegra X driver load correctly.

Note: Turning off tegrafb0 still leads to kernel crash due to
hard coded device enumeration.