Skip to content
  1. Apr 09, 2013
  2. Apr 03, 2013
  3. Apr 01, 2013
    • Rajendra Nayak's avatar
      ARM: OMAP: dpll: enable bypass clock only when attempting dpll bypass · 469d633d
      Rajendra Nayak authored
      
      
      omap3_noncore_dpll_set_rate() attempts an enable of bypass clk as well
      as ref clk for every .set_rate attempt on a noncore DPLL, regardless of
      whether the .set_rate results in the DPLL being locked or put in bypass.
      Early at boot, while some of these DPLLs are programmed and locked
      (using .set_rate for the DPLL), this causes an ordering issue.
      
      For instance, on OMAP5, the USB DPLL derives its bypass clk from ABE DPLL.
      If a .set_rate of USB DPLL which programmes the M,N and locks it is called
      before the one for ABE, the enable of USB bypass clk (derived from ABE DPLL)
      then attempts to lock the ABE DPLL and fails as the M,N values for ABE
      are yet to be programmed.
      
      To get rid of this ordering needs, enable bypass clk for a DPLL as part
      of its .set_rate only when its being put in bypass, and only enable the
      ref clk when its locked.
      
      Reported-by: default avatarRoger Quadros <rogerq@ti.com>
      Signed-off-by: default avatarRajendra Nayak <rnayak@ti.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      469d633d
    • Paul Walmsley's avatar
      ARM: OMAP2+: powerdomain: avoid testing whether an unsigned char is less than 0 · bd70f6eb
      Paul Walmsley authored
      
      
      _pwrdm_save_clkdm_state_and_activate() tried to test one of its
      unsigned arguments to determine whether it was less than zero.  Fix by
      moving the error test to the caller.
      
      Reported-by: default avatarChen Gang <gang.chen@asianux.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      bd70f6eb
    • Rajendra Nayak's avatar
      ARM: OMAP2+: hwmod: Remove unused _HWMOD_WAKEUP_ENABLED flag · 4280943b
      Rajendra Nayak authored
      
      
      _HWMOD_WAKEUP_ENABLED is currently unused across the hwmod
      framework. Just get rid of it, so we have one less flag to
      worry about.
      
      Tested-by: default avatarVaibhav Bedia <vaibhav.bedia@ti.com>
      Signed-off-by: default avatarRajendra Nayak <rnayak@ti.com>
      Signed-off-by: default avatarSantosh Shilimkar <santosh.shilimkar@ti.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      4280943b
    • Vaibhav Hiremath's avatar
      ARM: OMAP2+: am335x: Change the wdt1 func clk src to per_32k clk · da91b89e
      Vaibhav Hiremath authored
      
      
      WDT1 module can take one of the below clocks as input functional
      clock -
           - On-Chip 32K RC Osc [default/reset]
           - 32K from PRCM
      
      The On-Chip 32K RC Osc clock is not an accurate clock-source as per
      the design/spec, so as a result, for example, timer which supposed
      to get expired @60Sec, but will expire somewhere ~@40Sec, which is
      not expected by any use-case.
      
      The solution here is to switch the input clock-source to PRCM
      generated 32K clock-source during boot-time itself.
      
      Signed-off-by: default avatarVaibhav Hiremath <hvaibhav@ti.com>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Benoit Cousson <benoit.cousson@linaro.org>
      Cc: Paul Walmsley <paul@pwsan.com>
      da91b89e
    • Vaibhav Hiremath's avatar
      ARM: OMAP2+: AM33xx: hwmod: Add missing sysc definition to wdt1 entry · 05cf03b6
      Vaibhav Hiremath authored
      
      
      This patch adds sysc definitions to the wdt1 hwmod entry, which in-turn
      makes sure that sysc idle bit-fields are configured to valid state on
      enable/disable callbacks.
      
      With the recent submitted patch from Santosh Shilimkar,
      "ARM: OMAP2+: hwmod: Don't call _init_mpu_rt_base if no sysc"
      (commit: 4a98c2d89), it is required to add sysconf
      information to each valid hwmod entry, else device will not be
      come out from idle state properly and leads to below kernel
      crash  -
      
      [2.190237] Unhandled fault: external abort on non-linefetch (0x1028) at
      0xf9e35034
      [2.198325] Internal error: : 1028 [#1] SMP ARM
      [2.203101] Modules linked in:
      [2.206334] CPU: 0    Not tainted  (3.9.0-rc3-00059-gd114294#1)
      [2.212679] PC is at omap_wdt_disable.clone.5+0xc/0x60
      [2.218090] LR is at omap_wdt_probe+0x184/0x1fc
      
      Signed-off-by: default avatarVaibhav Hiremath <hvaibhav@ti.com>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Benoit Cousson <benoit.cousson@linaro.org>
      Cc: Paul Walmsley <paul@pwsan.com>
      05cf03b6
  4. Mar 23, 2013
  5. Mar 19, 2013
    • Shawn Guo's avatar
      ARM: imx: add dependency check for DEBUG_IMX_UART_PORT · 287939a3
      Shawn Guo authored
      
      
      While adding i.MX DEBUG_LL selection, commit f8c95fe6 (ARM: imx: support
      DEBUG_LL uart port selection for all i.MX SoCs) leaves Kconfig symbol
      DEBUG_IMX_UART_PORT there without any dependency check.  This results in
      that everyone gets the symbol in their config, which is someting
      undesirable.  Add "depends on ARCH_MXC" for the symbol to prevent that.
      
      Reported-by: default avatarKarl Beldan <karl.beldan@gmail.com>
      Signed-off-by: default avatarShawn Guo <shawn.guo@linaro.org>
      287939a3
    • Marek Vasut's avatar
      ARM: video: mxs: Fix mxsfb misconfiguring VDCTRL0 · 6a15075e
      Marek Vasut authored
      
      
      The issue fixed by this patch manifests only then using X11
      with mxsfb driver. The X11 will display either shifted image
      or otherwise distorted image on the LCD.
      
      The problem is that the X11 tries to reconfigure the framebuffer
      and along the way calls fb_ops.fb_set_par() with X11's desired
      configuration values. The field of particular interest is
      fb_info->var.sync which contains non-standard values if
      configured by kernel. These are either FB_SYNC_DATA_ENABLE_HIGH_ACT,
      FB_SYNC_DOTCLK_FAILING_ACT or both, depending on the platform
      configuration. Both of these values are defined in the
      include/linux/mxsfb.h file.
      
      The driver interprets these values and configures the LCD controller
      accordingly. Yet X11 only has access to the standard values for this
      field defined in include/uapi/linux/fb.h and thus, unlike kernel,
      omits these special values. This results in distorted image on the
      LCD.
      
      This patch moves these non-standard values into new field of the
      mxsfb_platform_data structure so the driver can in turn check this
      field instead of the video mode field for these specific portions.
      
      Moreover, this patch prefixes these values with MXSFB_SYNC_ prefix
      instead of FB_SYNC_ prefix to prevent confusion of subsequent users.
      
      Signed-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>
      Cc: Linux FBDEV <linux-fbdev@vger.kernel.org>
      Cc: Lothar Waßmann <LW@karo-electronics.de>
      Cc: Sascha Hauer <kernel@pengutronix.de>
      Tested-by: default avatarFabio Estevam <fabio.estevam@freescale.com>
      Signed-off-by: default avatarShawn Guo <shawn.guo@linaro.org>
      6a15075e
  6. Mar 18, 2013
    • Arnd Bergmann's avatar
      ARM: fix CONFIG_VIRT_TO_BUS handling · b4811bac
      Arnd Bergmann authored
      
      
      887cbce0 "arch Kconfig: centralise CONFIG_ARCH_NO_VIRT_TO_BUS"
      and  4febd95a "Select VIRT_TO_BUS directly where needed" from
      Stephen Rothwell changed globally how CONFIG_VIRT_TO_BUS is
      selected, while my own a5d533ee "ARM: disable virt_to_bus/
      virt_to_bus almost everywhere" was merged at the same time and
      changed which platforms select it on ARM.
      
      The result of this conflict was that we again see CONFIG_VIRT_TO_BUS
      on all ARM systems. This patch fixes up the problem and removes
      CONFIG_ARCH_NO_VIRT_TO_BUS again on ARM.
      
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Stephen Rothwell <sfr@canb.auug.org.au>
      b4811bac
  7. Mar 16, 2013
  8. Mar 15, 2013
    • Sascha Hauer's avatar
      ARM: i.MX35: enable MAX clock · 5dc2eb7d
      Sascha Hauer authored
      
      
      The i.MX35 has two bits per clock gate which are decoded as follows:
            0b00 -> clock off
            0b01 -> clock is on in run mode, off in wait/doze
            0b10 -> clock is on in run/wait mode, off in doze
            0b11 -> clock is always on
      
      The reset value for the MAX clock is 0b10.
      
      The MAX clock is needed by the SoC, yet unused in the Kernel, so the
      common clock framework will disable it during late init time. It will
      only disable clocks though which it detects as being turned on. This
      detection is made depending on the lower bit of the gate. If the reset
      value has been altered by the bootloader to 0b11 the clock framework
      will detect the clock as turned on, yet unused, hence it will turn it
      off and the system locks up.
      
      This patch turns the MAX clock on unconditionally making the Kernel
      independent of the bootloader.
      
      Signed-off-by: default avatarSascha Hauer <s.hauer@pengutronix.de>
      5dc2eb7d
    • Stephen Boyd's avatar
      ARM: Scorpion is a v7 architecture, not v6 · 8dda05cc
      Stephen Boyd authored
      
      
      Scorpion processors have always been v7 CPUs. Fix the Kconfig
      text to reflect this.
      
      Reported-by: default avatarStepan Moskovchenko <stepanm@codeaurora.org>
      Signed-off-by: default avatarStephen Boyd <sboyd@codeaurora.org>
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      8dda05cc
    • Haojian Zhuang's avatar
      ARM: mmp: add platform_device head file in gplugd · e71dc5f7
      Haojian Zhuang authored
      
      
      arch/arm/mach-mmp/gplugd.c: In function ‘gplugd_init’:
      arch/arm/mach-mmp/gplugd.c:188:2: error: implicit declaration of
      function ‘platform_device_register’
      [-Werror=implicit-function-declaration]
      cc1: some warnings being treated as errors
      make[1]: *** [arch/arm/mach-mmp/gplugd.o] Error 1
      make: *** [arch/arm/mach-mmp] Error 2
      
      So append platform_device.h to resolve build issue.
      
      Signed-off-by: default avatarHaojian Zhuang <haojian.zhuang@linaro.org>
      e71dc5f7
    • Arnd Bergmann's avatar
      [media] s5p-fimc: fix s5pv210 build · 01ffe957
      Arnd Bergmann authored
      
      
      56bc911a "[media] s5p-fimc: Redefine platform data structure for fimc-is"
      changed the bus_type member of struct fimc_source_info treewide, but
      got one instance wrong in mach-s5pv210, which was evidently not
      even build tested.
      
      This adds the missing change to get s5pv210_defconfig to build again.
      Applies on the Mauro's media tree.
      
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
      Cc: Kyungmin Park <kyungmin.park@samsung.com>
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      Cc: Mauro Carvalho Chehab <mchehab@redhat.com>
      01ffe957
  9. Mar 14, 2013