search for: hotreset

Displaying 4 results from an estimated 4 matches for "hotreset".

Did you mean: comreset
2015 Jan 06
2
[PATCH nouveau 06/11] platform: complete the power up/down sequence
...hr_clients; > >> unsigned int num_hr_clients; > >Why do you still need these? > This part is added in "[PATCH 2/11] memory: tegra: add mc flush support" and > "[PATCH 3/11] memory: tegra: add flush operation for Tegra124 memory > clients" > for the hotreset registers. Right. Perhaps calling this structure tegra_mc_hotreset and the variables *_hotresets would be a good idea to clarify that they aren't actually per-client but per-SWGROUP. > >>Created one function to build the swgroup list. > >> > >>static int tegra_mc_bu...
2015 Jan 06
2
[PATCH nouveau 06/11] platform: complete the power up/down sequence
On Tue, Jan 06, 2015 at 05:34:01PM +0800, Vince Hsu wrote: > > On 01/05/2015 11:25 PM, Thierry Reding wrote: > >* PGP Signed by an unknown key > > > >On Thu, Dec 25, 2014 at 10:42:58AM +0800, Vince Hsu wrote: > >>On 12/24/2014 09:23 PM, Lucas Stach wrote: > >>>Am Dienstag, den 23.12.2014, 18:39 +0800 schrieb Vince Hsu: > >>>>This patch
2015 Jan 06
0
[PATCH nouveau 06/11] platform: complete the power up/down sequence
...struct tegra_mc_hr *hr_clients; >> unsigned int num_hr_clients; > Why do you still need these? This part is added in "[PATCH 2/11] memory: tegra: add mc flush support" and "[PATCH 3/11] memory: tegra: add flush operation for Tegra124 memory clients" for the hotreset registers. > >> struct list_head swgroups; > This doesn't belong in struct tegra_mc_soc because that's meant to be > static information about the specific variant of the memory-controller. > Put it in struct tegra_mc instead. Okay. > >> ... >> >&gt...
2015 Jan 06
0
[PATCH nouveau 06/11] platform: complete the power up/down sequence
...unsigned int num_hr_clients; > > >Why do you still need these? > > This part is added in "[PATCH 2/11] memory: tegra: add mc flush support" and > > "[PATCH 3/11] memory: tegra: add flush operation for Tegra124 memory > > clients" > > for the hotreset registers. > > Right. Perhaps calling this structure tegra_mc_hotreset and the > variables *_hotresets would be a good idea to clarify that they aren't > actually per-client but per-SWGROUP. Okay. > > > >>Created one function to build the swgroup list. > > &g...