Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 14 12月, 2009 4 次提交
    • R
      ARM: fix lh7a40x build · 9074e144
      由 Russell King 提交于 
      No idea if this platform actually uses cpufreq_get(), but it doesn't
have any cpufreq drivers.  That's not to say it doesn't use cpufreq_get()
in its drivers.  LH7a40x is unmaintained anyhow, and should probably
be killed off.
Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      9074e144
    • R
      ARM: fix sa1100 build · 1937f5b9
      由 Russell King 提交于 
      Fix:

arch/arm/mach-sa1100/generic.c:117: error: redefinition of 'cpufreq_get'
include/linux/cpufreq.h:299: error: previous definition of 'cpufreq_get' was here

cpufreq_get() is used on these platforms to tell drivers what the CPU
frequency is, and therefore the bus frequency - which is critical for
setting the PCMCIA and LCD timings.  Adding ifdefs to these drivers to
select cpufreq_get() or some other interface adds confusion.  Making
these drivers use some other interface for the normal paths and cpufreq
stuff for the cpufreq notifier is insane as well.

(Why x86 can't provide a version of cpufreq_get() which returns the
CPU frequency when CPUFREQ is disabled is beyond me, rather than
requiring a dummy zero-returning cpufreq_get().  Especially as they
do:

			unsigned long khz = cpufreq_get(cpu);
			if (!khz)
				khz = tsc_khz;

In other words, if CPUFREQ is disabled, get it from tsc_khz - why
not provide a dummy cpufreq_get() which returns tsc_khz?)
Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      1937f5b9
    • R
      ARM: fix clps711x, footbridge, integrator, ixp2000, ixp2300 and s3c build bug · c7baab5d
      由 Russell King 提交于 
      Anders Grafström reports that footbridge fails to build after 1c4a4f48.
Fix this by adding the necessary definitions for __pfn_to_bus and
__bus_to_pfn.
Reported-by: NAnders Grafström <anders.grafstrom@netinsight.net>
Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      c7baab5d
    • R
      ARM: VFP: fix vfp thread init bug and document vfp notifier entry conditions · 0d782dc4
      由 Russell King 提交于 
      When the VFP notifier is called for flush_thread(), we may be
preemptible, meaning we might migrate to another CPU, which means
referencing the current CPU number without some form of locking is
invalid, and can cause data corruption.

For the most cases, this isn't a problem since atomic notifiers are run
under rcu lock, which for most configurations results in preemption
being disabled - except when the preemptable tree-based rcu
implementation is selected.

Let's make it safe anyway.
Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      0d782dc4
  3. 13 12月, 2009 4 次提交
  5. 12 12月, 2009 32 次提交