Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 12 2月, 2013 3 次提交
  3. 03 1月, 2013 1 次提交
  5. 14 12月, 2012 3 次提交
  7. 13 12月, 2012 3 次提交
    • M
      microblaze: Fix intc_enable_or_unmask function · 7958a689
      由 Michal Simek 提交于 
      Intc_enable_or_unmask() is called at the last stage of handle_level_irq().

This function enables the irq first (Write INTC.SIE) and clear ISR next (Write INTC.IAR).
This would create problems that processor will get into a new interrupt as soon as SIE
is written because the previous level interrupt has been captured by INTC.

If the description bring some puzzles, here is the details of how interrupt is handled
for MicroBlaze after Interrupt signal is detected:
1. disable INTC (INTC.CIE = 1)
2. Acknowledge INTC (INTC.IAR = 1)
3. gets into interrupt source's handler, for example, timer's handler
4. Timer is interrupt handler acknowledge Timer Interrupt Status (Timer.TCSR0[23] = 1), and return
5. Enable INTC (INTC.SIE = 1)
6. Acknowledge INTC (INTC.IAR = 1)

INTC continue to capture source inputs even if INTC is disabled (INTC.IER == 1).
So between the gap of step 2 and step 3, the level interrupt from source makes INTC captures
a new interrupt and thus the INTC.ISR = 1 during step 3, 4, and 5.
When INTC is enabled in step 5, INTC's interrupt output will go high immediately.

In summary, the driver should issue step 6 before step 5.
Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
      7958a689
    • M
      microblaze: Remove passing the second arg to schedule_tail · 1475b0f4
      由 Michal Simek 提交于 
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      1475b0f4
    • M
      microblaze: Remove BIP from childregs · 4336bac5
      由 Michal Simek 提交于 
      Not necessary to use BIP for protection.
Signed-off-by: NMichal Simek <monstr@monstr.eu>
      4336bac5
  9. 29 11月, 2012 3 次提交
  11. 16 11月, 2012 3 次提交
  13. 15 11月, 2012 1 次提交
  15. 13 10月, 2012 1 次提交
    • J
      vfs: define struct filename and have getname() return it · 91a27b2a
      由 Jeff Layton 提交于 
      getname() is intended to copy pathname strings from userspace into a
kernel buffer. The result is just a string in kernel space. It would
however be quite helpful to be able to attach some ancillary info to
the string.

For instance, we could attach some audit-related info to reduce the
amount of audit-related processing needed. When auditing is enabled,
we could also call getname() on the string more than once and not
need to recopy it from userspace.

This patchset converts the getname()/putname() interfaces to return
a struct instead of a string. For now, the struct just tracks the
string in kernel space and the original userland pointer for it.

Later, we'll add other information to the struct as it becomes
convenient.
Signed-off-by: NJeff Layton <jlayton@redhat.com>
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      91a27b2a
  17. 05 10月, 2012 1 次提交
  19. 04 10月, 2012 8 次提交
  21. 01 10月, 2012 1 次提交
  23. 27 6月, 2012 1 次提交
  25. 02 6月, 2012 5 次提交
  27. 25 5月, 2012 3 次提交
  29. 24 5月, 2012 1 次提交
  31. 22 5月, 2012 2 次提交