Re: [PATCH] OMAP2/3 PM: Add OMAP PM no-op layer
Hi Paul, Perhaps something similar to an OMAP PM function omap_pm_dsp_get_opp_table() that DSPBridge could call on startup? Can you please provide tentative dates for the patches available with above function? thanks Ramesh Gupta G -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] OMAP2/3 PM: Add OMAP PM no-op layer
Hello Ramesh, On Thu, 3 Jul 2008, Ramesh Gupta G wrote: Perhaps something similar to an OMAP PM function omap_pm_dsp_get_opp_table() that DSPBridge could call on startup? Can you please provide tentative dates for the patches available with above function? DSPBridge already has all of that OPP/frequency information inside its code, so that's what you should use until that function becomes available. - Paul -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] OMAP2/3 PM: Add OMAP PM no-op layer
Hello Ramesh, On Wed, 18 Jun 2008, Ramesh Gupta G wrote: Will this interface provides information of max number if OPPs supported and the frequency corresponding to eah OPP level? It could be added. This is for DSPBridge use, not for the MPU, correct? Is the idea essentially to replace the vdd1_dsp_freq[] array in mpu_driver/src/rmgr/linux/common/drv_interface.c? Can you tell me what each of the 4 fields in vdd1_dsp_freq[] means? Perhaps something similar to an OMAP PM function omap_pm_dsp_get_opp_table() that DSPBridge could call on startup? MPU Bridge is required to inform the DSP about OPP level change for load predictor use in DSP; this is done as part of in post notification in dspbridge. Do we have support for Post Notification in this framework? I just posted some patches for that a few days ago. You should be able to use those to notify DSPBridge of changes to iva2_ck. - Paul -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] OMAP2/3 PM: Add OMAP PM no-op layer
Hello Paul, Will this interface provides information of max number if OPPs supported and the frequency corresponding to eah OPP level? It could be added. This is for DSPBridge use, not for the MPU, correct? Is the idea essentially to replace the vdd1_dsp_freq[] array in mpu_driver/src/rmgr/linux/common/drv_interface.c? Yes, this is to replace the table in drv_interface.c Can you tell me what each of the 4 fields in vdd1_dsp_freq[] means? The 4 fileds of vdd1_freq[] are as below. voltage opp frequency min frequency max frequency we are currently not using the field 'voltage', this is for future usage. the min_frequency and max_frequency are threshold frequencies set by DSP and are configurable. Perhaps something similar to an OMAP PM function omap_pm_dsp_get_opp_table() that DSPBridge could call on startup? Sure, we can call this function on startup. MPU Bridge is required to inform the DSP about OPP level change for load predictor use in DSP; this is done as part of in post notification in dspbridge. Do we have support for Post Notification in this framework? I just posted some patches for that a few days ago. You should be able to use those to notify DSPBridge of changes to iva2_ck. Thanks for that, we will look into that. Also can you please provide the tentative dates these patches are avialable with above changes. Please let us know your comments. regards Ramesh Gupta G -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] OMAP2/3 PM: Add OMAP PM no-op layer
Hi Paul,
- Original Message -
From: Paul Walmsley [EMAIL PROTECTED]
To: linux-omap@vger.kernel.org
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 8:31 PM
Subject: [PATCH] OMAP2/3 PM: Add OMAP PM no-op layer
+/**
+ * omap_pm_cpu_get_freq_table - return a cpufreq_frequency_table array
ptr
+ *
+ * Provide a frequency table usable by CPUFreq for the current
chip/board.
+ * Returns a pointer to a struct cpufreq_frequency_table array or NULL
+ * upon error.
+ */
+struct cpufreq_frequency_table **omap_pm_cpu_get_freq_table(void)
+{
+ pr_debug(OMAP PM: CPUFreq request for frequency table\n);
+
+ /*
+ * Allocate and build CPUFreq frequency table here: loop over
+ * all VDD1 clkrates, pull out the mpu_ck frequencies, build
+ * table
+ */
+
+ return NULL;
+}
+
Will this interface provides information of max number if OPPs supported and
the frequency corresponding to eah OPP level?
Notification of OPP level change to DSP
--
MPU Bridge is required to inform the DSP about OPP level change for load
predictor use in DSP;
this is done as part of in post notification in dspbridge. Do we have
support for Post Notification in this framework?
Please let us know your comments.
Thanks regards
Ramesh Gupta G
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
