1. 24 6月, 2013 2 次提交
    • A
      ARM: mxs: don't select HAVE_PWM · ab182463
      Arnd Bergmann 提交于
      The HAVE_PWM symbol is only for legacy platforms that provide
      the PWM API without using the generic framework. MXS actually
      uses that framework, and selecting the symbol anyway might
      cause build errors like
      
      drivers/built-in.o: In function `pwm_beeper_resume':
      :(.text+0x1f4fc0): undefined reference to `pwm_config'
      :(.text+0x1f4fc8): undefined reference to `pwm_enable'
      drivers/built-in.o: In function `pwm_beeper_suspend':
      :(.text+0x1f4ffc): undefined reference to `pwm_disable'
      
      when CONFIG_PWM is disabled.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Shawn Guo <shawn.guo@linaro.org>
      ab182463
    • A
      ARM: mxs: stub out mxs_pm_init for !CONFIG_PM · 7a9caf59
      Arnd Bergmann 提交于
      When building a kernel without CONFIG_PM, we get a link
      error from referencing mxs_pm_init in the machine
      descriptor. This defines a macro to NULL for that case.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NShawn Guo <shawn.guo@linaro.org>
      7a9caf59
  2. 04 4月, 2013 5 次提交
  3. 01 4月, 2013 21 次提交
  4. 19 3月, 2013 1 次提交
    • M
      ARM: video: mxs: Fix mxsfb misconfiguring VDCTRL0 · 6a15075e
      Marek Vasut 提交于
      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: NMarek 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: NFabio Estevam <fabio.estevam@freescale.com>
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      6a15075e
  5. 07 3月, 2013 1 次提交
  6. 04 3月, 2013 3 次提交
  7. 05 2月, 2013 2 次提交
  8. 29 1月, 2013 1 次提交
  9. 26 1月, 2013 1 次提交
  10. 15 1月, 2013 1 次提交
  11. 11 1月, 2013 1 次提交
  12. 25 12月, 2012 1 次提交