1. 31 Oct, 2014 2 commits
  2. 29 Oct, 2014 1 commit
  3. 28 Oct, 2014 2 commits
  4. 27 Oct, 2014 1 commit
  5. 25 Oct, 2014 1 commit
  6. 24 Oct, 2014 3 commits
  7. 23 Oct, 2014 2 commits
  8. 22 Oct, 2014 2 commits
  9. 21 Oct, 2014 4 commits
  10. 20 Oct, 2014 6 commits
  11. 19 Oct, 2014 1 commit
  12. 16 Oct, 2014 4 commits
  13. 15 Oct, 2014 3 commits
  14. 14 Oct, 2014 2 commits
    • Giuseppe CAVALLARO's avatar
      stmmac: dwmac-sti: review the glue-logic for STi4xx and STiD127 SoCs · 53b26b9b
      Giuseppe CAVALLARO authored
      This patch is to review the whole glue logic adopted on STi SoCs that
      was bugged.
      
      In the old glue-logic there was a lot of confusion when setup the
      retiming especially for STiD127 where, for example, the bits 6 and 7
      (in the GMAC  control register) have a different meaning of what is
      used for STiH4xx SoCs. So we cannot adopt the same glue for all these
      SoCs.
      Moreover, GiGa on STiD127 didn't work and, for all the SoCs, the RGMII
      couldn't run when the speed was 10Mbps (because the clock was not properly
      managed).
      Note that the phy clock needs to be provided by the platform as well as
      documented in the related binding file (updated as consequence).
      
      The old code supported too many configurations never adopted and validated.
      This made the code very complex to maintain and debug in case of issues.
      
      The patch simplifies all the configurations as commented in the tables
      inside the file and obviously it has been tested on all the boards
      based on the SoCs mentioned.
      
      With this patch, the dwmac-sti is also ready to support new configurations that
      will be available on next SoC generations.
      Signed-off-by: default avatarGiuseppe Cavallaro <peppe.cavallaro@st.com>
      Cc: Srinivas Kandagatla <srinivas.kandagatla@st.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      53b26b9b
    • Giuseppe CAVALLARO's avatar
      stmmac: make the STi Layer compatible to STiH407 · 160e1fd1
      Giuseppe CAVALLARO authored
      This adds the missing compatibility to the STiH407 SoC.
      Signed-off-by: default avatarGiuseppe Cavallaro <peppe.cavallaro@st.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      160e1fd1
  15. 13 Oct, 2014 6 commits
    • Andy Shevchenko's avatar
      lib/vsprintf: add %*pE[achnops] format specifier · 71dca95d
      Andy Shevchenko authored
      This allows user to print a given buffer as an escaped string.  The
      rules are applied according to an optional mix of flags provided by
      additional format letters.
      
      For example, if the given buffer is:
      
          1b 62 20 5c 43 07 22 90 0d 5d
      
      The result strings would be:
          %*pE            "\eb \C\a"\220\r]"
          %*pEhp          "\x1bb \C\x07"\x90\x0d]"
          %*pEa           "\e\142\040\\\103\a\042\220\r\135"
      
      Please, read Documentation/printk-formats.txt and lib/string_helpers.c
      kernel documentation to get further information.
      
      [akpm@linux-foundation.org: tidy up comment layout, per Joe]
      Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Suggested-by: default avatarJoe Perches <joe@perches.com>
      Cc: "John W . Linville" <linville@tuxdriver.com>
      Cc: Johannes Berg <johannes@sipsolutions.net>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      71dca95d
    • Oleg Nesterov's avatar
      coredump: add %i/%I in core_pattern to report the tid of the crashed thread · b03023ec
      Oleg Nesterov authored
      format_corename() can only pass the leader's pid to the core handler,
      but there is no simple way to figure out which thread originated the
      coredump.
      
      As Jan explains, this also means that there is no simple way to create
      the backtrace of the crashed process:
      
      As programs are mostly compiled with implicit gcc -fomit-frame-pointer
      one needs program's .eh_frame section (equivalently PT_GNU_EH_FRAME
      segment) or .debug_frame section.  .debug_frame usually is present only
      in separate debug info files usually not even installed on the system.
      While .eh_frame is a part of the executable/library (and it is even
      always mapped for C++ exceptions unwinding) it no longer has to be
      present anywhere on the disk as the program could be upgraded in the
      meantime and the running instance has its executable file already
      unlinked from disk.
      
      One possibility is to echo 0x3f >/proc/*/coredump_filter and dump all
      the file-backed memory including the executable's .eh_frame section.
      But that can create huge core files, for example even due to mmapped
      data files.
      
      Other possibility would be to read .eh_frame from /proc/PID/mem at the
      core_pattern handler time of the core dump.  For the backtrace one needs
      to read the register state first which can be done from core_pattern
      handler:
      
          ptrace(PTRACE_SEIZE, tid, 0, PTRACE_O_TRACEEXIT)
          close(0);    // close pipe fd to resume the sleeping dumper
          waitpid();   // should report EXIT
          PTRACE_GETREGS or other requests
      
      The remaining problem is how to get the 'tid' value of the crashed
      thread.  It could be read from the first NT_PRSTATUS note of the core
      file but that makes the core_pattern handler complicated.
      
      Unfortunately %t is already used so this patch uses %i/%I.
      
      Automatic Bug Reporting Tool (https://github.com/abrt/abrt/wiki/overview)
      is experimenting with this.  It is using the elfutils
      (https://fedorahosted.org/elfutils/) unwinder for generating the
      backtraces.  Apart from not needing matching executables as mentioned
      above, another advantage is that we can get the backtrace without saving
      the core (which might be quite large) to disk.
      
      [mmilata@redhat.com: final paragraph of changelog]
      Signed-off-by: default avatarJan Kratochvil <jan.kratochvil@redhat.com>
      Signed-off-by: default avatarOleg Nesterov <oleg@redhat.com>
      Cc: Alexander Viro <viro@zeniv.linux.org.uk>
      Cc: Denys Vlasenko <dvlasenk@redhat.com>
      Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
      Cc: Mark Wielaard <mjw@redhat.com>
      Cc: Martin Milata <mmilata@redhat.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      b03023ec
    • Pavel Machek's avatar
      rtc: bq32000: add trickle charger device tree binding · d5fae669
      Pavel Machek authored
      BQ32000 have "trickle chargers".  Introduce a device tree binding for
      specifying the trickle charger configuration for that.
      Signed-off-by: default avatarPavel Machek <pavel@denx.de>
      Reviewed-by: default avatarJason Cooper <jason@lakedameon.net>
      Cc: Matti Vaittinen <matti.vaittinen@nsn.com>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: Guenter Roeck <linux@roeck-us.net>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      d5fae669
    • Matti Vaittinen's avatar
      Documentation: dt-bindings: trickle charger dt binding document for ds1339 · 2ac848c0
      Matti Vaittinen authored
      Some DS13XX devices have "trickle chargers".  Introduce a device tree
      binding for the resistor and diode configuration for enabling trickle
      charger.
      Signed-off-by: default avatarMatti Vaittinen <matti.vaittinen@nsn.com>
      Acked-by: default avatarJason Cooper <jason@lakedaemon.net>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Guenter Roeck <linux@roeck-us.net>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Pavel Machek <pavel@denx.de>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      2ac848c0
    • Chanwoo Choi's avatar
      rtc: s3c: add support for RTC of Exynos3250 SoC · df9e26d0
      Chanwoo Choi authored
      Add support for RTC of Exynos3250 SoC.  The Exynos3250 needs source
      clock(32.768KHz) for RTC block.  If source clock of RTC is registerd on
      clock list of common clk framework, Exynos RTC drvier have to control
      this clock.
      
      Clock list for s3c-rtc device:
      - rtc : CLK_RTC of CLK_GATE_IP_PERIR is gate clock for RTC.
      - rtc_src : XrtcXTI is 32.768.kHz source clock for RTC.
       (XRTCXTI: Specifies a clock from 32.768 kHz crystal pad with XRTCXTI and
       XRTCXTO pins. RTC uses this clock as the source of a real-time clock.)
      Signed-off-by: default avatarChanwoo Choi <cw00.choi@samsung.com>
      Acked-by: default avatarKyungmin Park <kyungmin.park@samsung.com>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      df9e26d0
    • Chanwoo Choi's avatar
      rtc: s3c: remove warning message when checking coding style with checkpatch script · d67288da
      Chanwoo Choi authored
      Remove warning message when checking codeing style with checkpatch script
      and reduce un-necessary i2c read operation on s3c_rtc_enable.
      
          WARNING: line over 80 characters
          #406: FILE: drivers/rtc/rtc-s3c.c:406:
          +		if ((readw(info->base + S3C2410_RTCCON) & S3C2410_RTCCON_RTCEN) == 0) {
      
          WARNING: line over 80 characters
          #414: FILE: drivers/rtc/rtc-s3c.c:414:
          +		if ((readw(info->base + S3C2410_RTCCON) & S3C2410_RTCCON_CNTSEL)) {
      
          WARNING: line over 80 characters
          #422: FILE: drivers/rtc/rtc-s3c.c:422:
          +		if ((readw(info->base + S3C2410_RTCCON) & S3C2410_RTCCON_CLKRST)) {
      
          WARNING: Missing a blank line after declarations
          #451: FILE: drivers/rtc/rtc-s3c.c:451:
          +	struct s3c_rtc_drv_data *data;
          +	if (pdev->dev.of_node) {
      
          WARNING: Missing a blank line after declarations
          #453: FILE: drivers/rtc/rtc-s3c.c:453:
          +		const struct of_device_id *match;
          +		match = of_match_node(s3c_rtc_dt_match, pdev->dev.of_node);
      
          WARNING: DT compatible string "samsung,s3c2416-rtc" appears un-documented -- check ./Documentation/devicetree/bindings/
          #650: FILE: drivers/rtc/rtc-s3c.c:650:
          +		.compatible = "samsung,s3c2416-rtc",
      
          WARNING: DT compatible string "samsung,s3c2443-rtc" appears un-documented -- check ./Documentation/devicetree/bindings/
          #653: FILE: drivers/rtc/rtc-s3c.c:653:
          +		.compatible = "samsung,s3c2443-rtc",
      Signed-off-by: default avatarChanwoo Choi <cw00.choi@samsung.com>
      Acked-by: default avatarKyungmin Park <kyungmin.park@samsung.com>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      d67288da