> -----Original Message----- > From: Menon, Nishanth [mailto:nm@xxxxxx] > Sent: Tuesday, March 15, 2011 9:08 PM > To: Vishwanath BS > Cc: linux-omap@xxxxxxxxxxxxxxx > Subject: Re: [RFC][PATCH 3/3] OMAP PM: Add Board specific parameters > for OMAP Volatge layer > > On Tue, Mar 15, 2011 at 20:03, Vishwanath BS > <vishwanath.bs@xxxxxx> wrote: > > This patch adds board specific parameters for ZOOM3 and OMAP4430 > SDP Boards. > > The same needs to be done for other OMAP3 and OMAP4 boards once > the approach > > is accepted. > > Would have been great to see this info in 0/0 - what happens without > these changes on other boards? Ok will fix it. > > [...] > > +union omap_volt_board_data zoom_mpu_volt_data = { > > + .omap3_board_data = { > > + .vdd_setup_ret = { > > + .voltsetup = OMAP3_VOLTSETUP_VDD1_RET, > I disagree this is a board specific param - the help says "setup time > of the VDDregulators in us" - seems to me that it is PMIC information Yes. This should be PMIC parameter. Thanks for catching it. > > > + .clksetup = OMAP3_CLKSETUP_RET, > ????? why cant i just give oscillator ramp time in uSec? Clksetup = PRM_VOLTOFFSET + PRM_VOLTSETUP2.. So it is not just oscillator ramp time. > > > + .voltsetup2 = 0, > why should I as a board developer give this as well, why cant voltage > layer do addition and save me a param? Do you want to give 5 other parameters just to save one parameter? >From the patch, it is very clear how this parameter is calculated. Board developer just needs to change the values of other required parameters and this parameter is automatically calculated. > > > + }, > > + > > + .vdd_setup_off = { > > + .voltsetup = OMAP3_VOLTSETUP_VDD1_OFF, > > + .clksetup = OMAP3_CLKSETUP_OFF, > > + .voltsetup2 = OMAP3_VOLTSETUP2, > > + }, > > + .voltoffset = OMAP3_VOLTOFFSET_OFF > "offset-time to de-assert sys_offmode when exiting the OFF mode" - how > am I supposed to measure that? again - why cant voltage layer add > numbers? It is not question of mathematical computation here. There are the parameters that have to be measured manually to find the actual delay. If your concern is lack of documentation on how to measure it, I can provide relevant links. > > > + } > > +}; > > + > > my overall suggestion - when I fill in board file params - I should say: > I use PMIC x, i have oscillator with ramp "y" uSec - the params should > talk my language as a board developers - I dont want to know indepth > details of voltage VP/VC registers and what they should contain. it is > upto voltage layer to translate, add, bit shift or do what ever is > necessary to take my board and pmic level details to register details. > > Sorry, even though this is a good start for abstraction, the overall > motivation is missed, I think we need to work on it more. The motivation here is to enable different kinds of PMIC and Boards to work with OMAP Voltage layer (and not just board file params). For your concern on board file abstraction, I do not think there are magical formulae to calculate all these parameters based on one parameter. Some have to be measured manually and probably documentation would help as to how and what to measure. Pls let me know if you have any such formulae to calculate these parameters. Also note that these board file params are required only for OMAP3. Vishwa > > > Regards, > Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
