1. 08 3月, 2014 3 次提交
    • P
      staging: imx-drm-core: use of_graph_parse_endpoint · b6babdd9
      Philipp Zabel 提交于
      Using of_graph_parse_endpoint recovers the port id from an endpoint device
      tree node. This just replaces an open coded read of the "reg" property.
      Signed-off-by: NPhilipp Zabel <p.zabel@pengutronix.de>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      b6babdd9
    • P
      staging: imx-drm-core: Use OF graph to find components and connections between encoder and crtcs · 655b43cc
      Philipp Zabel 提交于
      This patch adds support to find the involved components connected to
      the IPU display interface ports using the OF graph bindings documented
      in Documentation/devicetree/bindings/media/video-interfaces.txt.
      It makes use of the of_graph (formerly v4l2_of) parsing helpers and
      thus depends on the patch that moves those out to drivers/of.
      
      Each display interface needs to have an associated port node in the
      device tree. We can associate this node with the crtc platform device
      and use it to find the crtc corresponding to a given port node instead
      of using a combination of parent device node and id number, as before.
      
      Explicitly converting the void* cookie to the port device tree node
      allows to get rid of the ipu_id and di_id fields. The multiplexer
      setting on i.MX6 now can be obtained from the port id (reg property)
      in the device tree.
      
      The imx-drm node now needs a ports property that contains phandles
      to each of the IPU display interface port nodes. From there, all
      attached encoders are scanned and enabled encoders are added to a
      waiting list.
      The bind order makes sure that once all components are probed, crtcs
      are bound before encoders, so that imx_drm_encoder_parse_of can be
      called from the encoder bind callbacks.
      
      For parsing the OF graph, temporary copies of the V4L2 OF graph
      helpers are used, that can be removed again once those are available
      at a generic place.
      Signed-off-by: NPhilipp Zabel <p.zabel@pengutronix.de>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      655b43cc
    • R
      Merge branch 'topic/of-graph' of git://git.pengutronix.de/git/pza/linux into imx-drm-staging · 73f2662b
      Russell King 提交于
      Merge the of-graph dependency for imx-drm.  These will be the basis of
      the new DT bindings for imx-drm.
      73f2662b
  2. 07 3月, 2014 7 次提交
  3. 03 3月, 2014 8 次提交
  4. 02 3月, 2014 8 次提交
  5. 01 3月, 2014 10 次提交
  6. 28 2月, 2014 4 次提交
    • S
      arm64: mm: Add double logical invert to pte accessors · 84fe6826
      Steve Capper 提交于
      Page table entries on ARM64 are 64 bits, and some pte functions such as
      pte_dirty return a bitwise-and of a flag with the pte value. If the
      flag to be tested resides in the upper 32 bits of the pte, then we run
      into the danger of the result being dropped if downcast.
      
      For example:
      	gather_stats(page, md, pte_dirty(*pte), 1);
      where pte_dirty(*pte) is downcast to an int.
      
      This patch adds a double logical invert to all the pte_ accessors to
      ensure predictable downcasting.
      Signed-off-by: NSteve Capper <steve.capper@linaro.org>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NCatalin Marinas <catalin.marinas@arm.com>
      84fe6826
    • H
      dm cache: fix truncation bug when mapping I/O to >2TB fast device · e0d849fa
      Heinz Mauelshagen 提交于
      When remapping a block to the cache's fast device that is larger than
      2TB we must not truncate the destination sector to 32bits.  The 32bit
      temporary result of from_cblock() was being overflowed in
      remap_to_cache() due to the logical left shift.
      
      Use an intermediate 64bit type to store the 32bit from_cblock() result
      to fix the overflow.
      Signed-off-by: NHeinz Mauelshagen <heinzm@redhat.com>
      Signed-off-by: NMike Snitzer <snitzer@redhat.com>
      Cc: stable@vger.kernel.org
      e0d849fa
    • J
      perf tools: Fix strict alias issue for find_first_bit · b39c2a57
      Jiri Olsa 提交于
      When compiling perf tool code with gcc 4.4.7 I'm getting
      following error:
      
          CC       util/session.o
        cc1: warnings being treated as errors
        util/session.c: In function ‘perf_session_deliver_event’:
        tools/perf/util/include/linux/bitops.h:109: error: dereferencing pointer ‘p’ does break strict-aliasing rules
        tools/perf/util/include/linux/bitops.h:101: error: dereferencing pointer ‘p’ does break strict-aliasing rules
        util/session.c:697: note: initialized from here
        tools/perf/util/include/linux/bitops.h:101: note: initialized from here
        make[1]: *** [util/session.o] Error 1
        make: *** [util/session.o] Error 2
      
      The aliased types here are u64 and unsigned long pointers, which is safe
      for the find_first_bit processing.
      
      This error shows up for me only for gcc 4.4 on 32bit x86, even for
      -Wstrict-aliasing=3, while newer gcc are quiet and scream here for
      -Wstrict-aliasing={2,1}. Looks like newer gcc changed the rules for
      strict alias warnings.
      
      The gcc documentation offers workaround for valid aliasing by using
      __may_alias__ attribute:
      
        http://gcc.gnu.org/onlinedocs/gcc-4.4.0/gcc/Type-Attributes.html
      
      Using this workaround for the find_first_bit function.
      Signed-off-by: NJiri Olsa <jolsa@redhat.com>
      Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>
      Cc: David Ahern <dsahern@gmail.com>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Namhyung Kim <namhyung@kernel.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Link: http://lkml.kernel.org/r/1393434867-20271-1-git-send-email-jolsa@redhat.comSigned-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      b39c2a57
    • B
      powerpc/powernv: Fix indirect XSCOM unmangling · e0cf9576
      Benjamin Herrenschmidt 提交于
      We need to unmangle the full address, not just the register
      number, and we also need to support the real indirect bit
      being set for in-kernel uses.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      CC: <stable@vger.kernel.org> [v3.13]
      e0cf9576