Clock management for linux Device Drivers (4) ---- it turns out to be a child

Clock management for linux Device Drivers (4) ---- it turns out to be a child

When I was a child, I saw a TV series called "Little Dragon man". You don't have to mention it. It's actually very inspirational. To find my mother, it's a great TV series, what are the children watching? Xuanyuan sword, god of every day, magic, illusion, and flashy stuff. Apart from commercial value, what kind of stuff can be useful to children?

I think of that sentence again. People are fucking born, and the demon is fucking born. So what exactly do we have when we use clk_get to get the clock? It must be impossible. How can we have nothing to do with science ???

Lens steering s3c2410-clock.c

Yes, you didn't see it wrong. It was defined here. I saw what name, parent, and it was all defined here. If you were careful enough, you would find that, there is one more member in the uart. What is it? Yes, it's devname, huh, huh .. A device may have many serial ports? How do we know which serial port? Hey. If you are lucky, you can use devname to drive the score.

Maybe you will be as curious as I am. Who is their father? Well, if you are satisfied, then the dream will return to clock. c.

I will go. As you can see, this is what we talked about in the first article. fclk, pclk, and hclk are the clock's parents .. Of course, if you are confident enough, you must also see clk_mpll. What is mpll? upll doesn't need to be repeated. If you can't remember it, read the first article in this series, okay? Dear user. The two of them are the parents of clk_f and clk_usb_bus.

Okay, we found it. You may have thought about it again. When did they get registered? When were they born? I am responsible for telling you that they have registered another one called s3c24xx_register_baseclocks. I will go .. You didn't want to ask where to call the s3c24xx_register_baseclocks? I can only say whether you can move the mouse or not.

Let me explain the order of the calls here: note that the blue part is the order .. Remember

See the smdk2410_map_io function.

We can see that it is the s3c24xx_init_io function:

We can see that, in the end, cpu_ids is not analyzed inside the function. Let's take a look at it later,

We can see that it is the s3c2410_init_clocks function.

See? Is s3c24xx_register_baseclocks

I finally got to the end .. Brother, if you still don't know about this process, please come to me. Let's cry, and then let's change it!