[HW_RNG] How to use generic rng in kernel space

Hi

I developped a HW RNG for a custom board and several
other drivers are using it through a special entry I made.
I was planning to move the code in order to use the generic
the RNG layer but I encounter an issue.

Currently it seems not possible for a driver to use HW RNG,
because there's no entry point for that. Is that something
deliberate ?

Another question about the implementation. If O_NONBLOCK
flag is passed when opening /dev/hw_random, how does the
read method ensure that the caller won't sleep since it calls
mutex_lock_interruptible() function unconditiannaly ? I must
miss something but don't know what...

Thanks

Francis



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [HW_RNG] How to use generic rng in kernel space
  - From: Michael Buesch <[email protected]>
- Re: [HW_RNG] How to use generic rng in kernel space
  - From: Alan Cox <[email protected]>

Prev by Date: Re: rt_mutex_timed_lock() vs hrtimer_wakeup() race ?
Next by Date: Re: [PATCH 1 of 13] Add apply_to_page_range() which applies a function to a pte range
Previous by thread: [patch] x86_64: remove lock prefix from is_at_popf() tests
Next by thread: Re: [HW_RNG] How to use generic rng in kernel space
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]