| Message ID | 20200108052337.65916-5-drinkcat@chromium.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | Add dts for mt8183 GPU (and misc panfrost patches) | expand |
On Wed, Jan 08, 2020 at 01:23:34PM +0800, Nicolas Boichat wrote: > Some GPUs, namely, the bifrost/g72 part on MT8183, have a second > regulator for their SRAM, let's add support for that. > + pfdev->regulator_sram = devm_regulator_get_optional(pfdev->dev, "sram"); > + if (IS_ERR(pfdev->regulator_sram)) { This supply is required for the devices that need it so I'd therefore expect the driver to request the supply non-optionally based on the compatible string rather than just hoping that a missing regulator isn't important. Though I do have to wonder given the lack of any active management of the supply if this is *really* part of the GPU or if it's more of a SoC thing, it's not clear what exactly adding this code is achieving.
On Wed, Jan 8, 2020 at 9:23 PM Mark Brown <broonie@kernel.org> wrote: > > On Wed, Jan 08, 2020 at 01:23:34PM +0800, Nicolas Boichat wrote: > > > Some GPUs, namely, the bifrost/g72 part on MT8183, have a second > > regulator for their SRAM, let's add support for that. > > > + pfdev->regulator_sram = devm_regulator_get_optional(pfdev->dev, "sram"); > > + if (IS_ERR(pfdev->regulator_sram)) { > > This supply is required for the devices that need it so I'd therefore > expect the driver to request the supply non-optionally based on the > compatible string rather than just hoping that a missing regulator isn't > important. That'd be a bit awkward to match, though... Currently all bifrost share the same compatible "arm,mali-bifrost", and it'd seem weird/wrong to match "mediatek,mt8183-mali" in this driver? I have no idea if any other Mali implementation will require a second regulator, but with the MT8183 we do need it, see below. > Though I do have to wonder given the lack of any active > management of the supply if this is *really* part of the GPU or if it's > more of a SoC thing, it's not clear what exactly adding this code is > achieving. Well if devfreq was working (see patch 7 https://patchwork.kernel.org/patch/11322851/ for a partial implementation), it would adjust both mali and sram regulators, see the OPP table in patch 2 (https://patchwork.kernel.org/patch/11322825/): SRAM voltage needs to be increased for frequencies >=698Mhz. Now if you have some better idea how to implement this, I'm all ears! Thanks.
On 08/01/2020 22:52, Nicolas Boichat wrote: > On Wed, Jan 8, 2020 at 9:23 PM Mark Brown <broonie@kernel.org> wrote: >> >> On Wed, Jan 08, 2020 at 01:23:34PM +0800, Nicolas Boichat wrote: >> >>> Some GPUs, namely, the bifrost/g72 part on MT8183, have a second >>> regulator for their SRAM, let's add support for that. >> >>> + pfdev->regulator_sram = devm_regulator_get_optional(pfdev->dev, "sram"); >>> + if (IS_ERR(pfdev->regulator_sram)) { >> >> This supply is required for the devices that need it so I'd therefore >> expect the driver to request the supply non-optionally based on the >> compatible string rather than just hoping that a missing regulator isn't >> important. > > That'd be a bit awkward to match, though... Currently all bifrost > share the same compatible "arm,mali-bifrost", and it'd seem > weird/wrong to match "mediatek,mt8183-mali" in this driver? I have no > idea if any other Mali implementation will require a second regulator, > but with the MT8183 we do need it, see below. > >> Though I do have to wonder given the lack of any active >> management of the supply if this is *really* part of the GPU or if it's >> more of a SoC thing, it's not clear what exactly adding this code is >> achieving. > > Well if devfreq was working (see patch 7 > https://patchwork.kernel.org/patch/11322851/ for a partial > implementation), it would adjust both mali and sram regulators, see > the OPP table in patch 2 > (https://patchwork.kernel.org/patch/11322825/): SRAM voltage needs to > be increased for frequencies >=698Mhz. > > Now if you have some better idea how to implement this, I'm all ears! I'm not sure if it's better, but could we just encode the list of regulators into device tree. I'm a bit worried about special casing an "sram" regulator given that other platforms might have a similar situation but call the second regulator a different name. Steve > Thanks. > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel >
On Thu, Jan 09, 2020 at 02:14:42PM +0000, Steven Price wrote: > On 08/01/2020 22:52, Nicolas Boichat wrote: > > That'd be a bit awkward to match, though... Currently all bifrost > > share the same compatible "arm,mali-bifrost", and it'd seem > > weird/wrong to match "mediatek,mt8183-mali" in this driver? I have no > > idea if any other Mali implementation will require a second regulator, > > but with the MT8183 we do need it, see below. This doesn't sound particularly hard, just new. Plenty of other devices have quirks done based on the SoC they're in or the IP revision, this would just be another of those quirks. > > Well if devfreq was working (see patch 7 > > https://patchwork.kernel.org/patch/11322851/ for a partial > > implementation), it would adjust both mali and sram regulators, see > > the OPP table in patch 2 > > (https://patchwork.kernel.org/patch/11322825/): SRAM voltage needs to > > be increased for frequencies >=698Mhz. > > Now if you have some better idea how to implement this, I'm all ears! Set a flag based on the compatible, then base runtime decisions off that. > I'm not sure if it's better, but could we just encode the list of > regulators into device tree. I'm a bit worried about special casing an > "sram" regulator given that other platforms might have a similar > situation but call the second regulator a different name. Obviously the list of regulators bound on a given platform is encoded in the device tree but you shouldn't really be relying on that to figure out what to request in the driver - the driver should know what it's expecting. Bear in mind that getting regulator stuff wrong can result in physical damage to the system so it pays to be careful and to consider that platform integrators have a tendency to rely on things that just happen to work but aren't a good idea or accurate representations of the system. It's certainly *possible* to do something like that, the information is there, but I would not in any way recommend doing things that way as it's likely to not be robust. The possibility that the regulator setup may vary on other platforms (which I'd expect TBH) does suggest that just requesting a bunch of supply names optionally and hoping that we got all the ones that are important on a given platform is going to lead to trouble down the line. Steve, please fix your mail client to word wrap within paragraphs at something substantially less than 80 columns. Doing this makes your messages much easier to read and reply to.
On 09/01/2020 16:28, Mark Brown wrote: > On Thu, Jan 09, 2020 at 02:14:42PM +0000, Steven Price wrote: >> On 08/01/2020 22:52, Nicolas Boichat wrote: > >>> That'd be a bit awkward to match, though... Currently all bifrost >>> share the same compatible "arm,mali-bifrost", and it'd seem >>> weird/wrong to match "mediatek,mt8183-mali" in this driver? I have no >>> idea if any other Mali implementation will require a second regulator, >>> but with the MT8183 we do need it, see below. > > This doesn't sound particularly hard, just new. Plenty of other devices > have quirks done based on the SoC they're in or the IP revision, this > would just be another of those quirks. > >>> Well if devfreq was working (see patch 7 >>> https://patchwork.kernel.org/patch/11322851/ for a partial >>> implementation), it would adjust both mali and sram regulators, see >>> the OPP table in patch 2 >>> (https://patchwork.kernel.org/patch/11322825/): SRAM voltage needs to >>> be increased for frequencies >=698Mhz. > >>> Now if you have some better idea how to implement this, I'm all ears! > > Set a flag based on the compatible, then base runtime decisions off > that. > >> I'm not sure if it's better, but could we just encode the list of >> regulators into device tree. I'm a bit worried about special casing an >> "sram" regulator given that other platforms might have a similar >> situation but call the second regulator a different name. > > Obviously the list of regulators bound on a given platform is encoded in > the device tree but you shouldn't really be relying on that to figure > out what to request in the driver - the driver should know what it's > expecting. From a driver perspective we don't expect to have to worry about power domains/multiple regulators - the hardware provides a bunch of power registers to turn on/off various parts of the hardware and this should be linked (in hardware) to a PDC which sorts it out. The GPU/PDC handles the required sequencing. So it *should* be a case of turn power/clocks on and go. However certain integrations may have quirks such that there are physically multiple supplies. These are expected to all be turned on before using the GPU. Quite how this is best represented is something I'm not sure about. > Bear in mind that getting regulator stuff wrong can result > in physical damage to the system so it pays to be careful and to > consider that platform integrators have a tendency to rely on things > that just happen to work but aren't a good idea or accurate > representations of the system. It's certainly *possible* to do > something like that, the information is there, but I would not in any > way recommend doing things that way as it's likely to not be robust. > > The possibility that the regulator setup may vary on other platforms > (which I'd expect TBH) does suggest that just requesting a bunch of > supply names optionally and hoping that we got all the ones that are > important on a given platform is going to lead to trouble down the line. Certainly if we miss a regulator the GPU isn't going to work properly (some cores won't be able to power up successfully). However at the moment the driver will happily do this if someone provides it with a DT which includes regulators that it doesn't know about. So I'm not sure how adding special case code for a SoC would help here. > Steve, please fix your mail client to word wrap within paragraphs at > something substantially less than 80 columns. Doing this makes your > messages much easier to read and reply to. Sorry about that - I switched to my laptop to escape the noisy work going on outside the office, and apparently that was misconfigured. Hopefully fixed now, thanks for letting me know! Steve
On Wed, Jan 8, 2020 at 4:52 PM Nicolas Boichat <drinkcat@chromium.org> wrote: > > On Wed, Jan 8, 2020 at 9:23 PM Mark Brown <broonie@kernel.org> wrote: > > > > On Wed, Jan 08, 2020 at 01:23:34PM +0800, Nicolas Boichat wrote: > > > > > Some GPUs, namely, the bifrost/g72 part on MT8183, have a second > > > regulator for their SRAM, let's add support for that. > > > > > + pfdev->regulator_sram = devm_regulator_get_optional(pfdev->dev, "sram"); > > > + if (IS_ERR(pfdev->regulator_sram)) { > > > > This supply is required for the devices that need it so I'd therefore > > expect the driver to request the supply non-optionally based on the > > compatible string rather than just hoping that a missing regulator isn't > > important. > > That'd be a bit awkward to match, though... Currently all bifrost > share the same compatible "arm,mali-bifrost", and it'd seem > weird/wrong to match "mediatek,mt8183-mali" in this driver? I have no > idea if any other Mali implementation will require a second regulator, > but with the MT8183 we do need it, see below. The current number of supported bifrost platforms is 0. It's only a matter of time until SoC specific compatibles need to be used in the driver. This is why we require them. It could very well be that all bifrost implementations need 2 supplies. On chip RAMs are very frequently a separate thing which are synthesized differently from logic. At least within a specific IP model, I somewhat doubt there's a variable number of supplies. It could be possible to connect both to the same supply, but the correct way to handle that is both -supply properties point to the same regulator. Rob
On Thu, Jan 09, 2020 at 04:53:02PM +0000, Steven Price wrote: > On 09/01/2020 16:28, Mark Brown wrote: > > On Thu, Jan 09, 2020 at 02:14:42PM +0000, Steven Price wrote: > > > I'm not sure if it's better, but could we just encode the list of > > > regulators into device tree. I'm a bit worried about special casing an > > > "sram" regulator given that other platforms might have a similar > > > situation but call the second regulator a different name. > > Obviously the list of regulators bound on a given platform is encoded in > > the device tree but you shouldn't really be relying on that to figure > > out what to request in the driver - the driver should know what it's > > expecting. > From a driver perspective we don't expect to have to worry about power > domains/multiple regulators - the hardware provides a bunch of power > registers to turn on/off various parts of the hardware and this should be > linked (in hardware) to a PDC which sorts it out. The GPU/PDC handles the > required sequencing. So it *should* be a case of turn power/clocks on and > go. Ah, the well abstracted and consistent hardware with which we are all so fortunate to work :) . More seriously perhaps the thing to do here is create a driver that provides a soft PDC and then push all the special case handling into that? It can then get instantiated based on the compatible or perhaps represented directly in the device tree if that makes sense. > However certain integrations may have quirks such that there are physically > multiple supplies. These are expected to all be turned on before using the > GPU. Quite how this is best represented is something I'm not sure about. If they're always on and don't ever change then that's really easy to represent in the DT without involving drivers, it's when you need to actively manage them that it's more effort. > > Bear in mind that getting regulator stuff wrong can result > > in physical damage to the system so it pays to be careful and to > > consider that platform integrators have a tendency to rely on things > > that just happen to work but aren't a good idea or accurate > > representations of the system. It's certainly *possible* to do > > something like that, the information is there, but I would not in any > > way recommend doing things that way as it's likely to not be robust. > > The possibility that the regulator setup may vary on other platforms > > (which I'd expect TBH) does suggest that just requesting a bunch of > > supply names optionally and hoping that we got all the ones that are > > important on a given platform is going to lead to trouble down the line. > Certainly if we miss a regulator the GPU isn't going to work properly (some > cores won't be able to power up successfully). However at the moment the > driver will happily do this if someone provides it with a DT which includes > regulators that it doesn't know about. So I'm not sure how adding special > case code for a SoC would help here. I thought this SoC neeed to vary the voltage on both rails as part of the power management? Things like that can lead to hardware damage if we go out of spec far enough for long enough - there can be requirements like keeping one rail a certain voltage above another or whatever.
On 09/01/2020 19:49, Mark Brown wrote: > On Thu, Jan 09, 2020 at 04:53:02PM +0000, Steven Price wrote: >> On 09/01/2020 16:28, Mark Brown wrote: >>> On Thu, Jan 09, 2020 at 02:14:42PM +0000, Steven Price wrote: > >>>> I'm not sure if it's better, but could we just encode the list of >>>> regulators into device tree. I'm a bit worried about special casing an >>>> "sram" regulator given that other platforms might have a similar >>>> situation but call the second regulator a different name. > >>> Obviously the list of regulators bound on a given platform is encoded in >>> the device tree but you shouldn't really be relying on that to figure >>> out what to request in the driver - the driver should know what it's >>> expecting. > >> From a driver perspective we don't expect to have to worry about power >> domains/multiple regulators - the hardware provides a bunch of power >> registers to turn on/off various parts of the hardware and this should be >> linked (in hardware) to a PDC which sorts it out. The GPU/PDC handles the >> required sequencing. So it *should* be a case of turn power/clocks on and >> go. > > Ah, the well abstracted and consistent hardware with which we are all so > fortunate to work :) . More seriously perhaps the thing to do here is > create a driver that provides a soft PDC and then push all the special > case handling into that? It can then get instantiated based on the > compatible or perhaps represented directly in the device tree if that > makes sense. That makes sense to me. >> However certain integrations may have quirks such that there are physically >> multiple supplies. These are expected to all be turned on before using the >> GPU. Quite how this is best represented is something I'm not sure about. > > If they're always on and don't ever change then that's really easy to > represent in the DT without involving drivers, it's when you need to > actively manage them that it's more effort. Sorry, I should have been more clear. They are managed as a group - so either the entire GPU is powered off, or powered on. There's no support in Panfrost or mali_kbase for attempting to power part of the GPU. >>> Bear in mind that getting regulator stuff wrong can result >>> in physical damage to the system so it pays to be careful and to >>> consider that platform integrators have a tendency to rely on things >>> that just happen to work but aren't a good idea or accurate >>> representations of the system. It's certainly *possible* to do >>> something like that, the information is there, but I would not in any >>> way recommend doing things that way as it's likely to not be robust. > >>> The possibility that the regulator setup may vary on other platforms >>> (which I'd expect TBH) does suggest that just requesting a bunch of >>> supply names optionally and hoping that we got all the ones that are >>> important on a given platform is going to lead to trouble down the line. > >> Certainly if we miss a regulator the GPU isn't going to work properly (some >> cores won't be able to power up successfully). However at the moment the >> driver will happily do this if someone provides it with a DT which includes >> regulators that it doesn't know about. So I'm not sure how adding special >> case code for a SoC would help here. > > I thought this SoC neeed to vary the voltage on both rails as part of > the power management? Things like that can lead to hardware damage if > we go out of spec far enough for long enough - there can be requirements > like keeping one rail a certain voltage above another or whatever. Yes, you are correct. My concern is that a DT which specifies a new regulator (e.g. "sram2") would be accepted by an old kernel (because it wouldn't know to look for the new regulator) but wouldn't know to control the regulator. It could then create a situation which puts the board out of spec - potentially in a damaging way. Hence I'd like to express the regulator structure in such a way that old kernels wouldn't "half-work". Your "soft-PDC" approach would seem to fit that requirement. Steve
On 09/01/2020 16:56, Rob Herring wrote: > On Wed, Jan 8, 2020 at 4:52 PM Nicolas Boichat <drinkcat@chromium.org> wrote: >> >> On Wed, Jan 8, 2020 at 9:23 PM Mark Brown <broonie@kernel.org> wrote: >>> >>> On Wed, Jan 08, 2020 at 01:23:34PM +0800, Nicolas Boichat wrote: >>> >>>> Some GPUs, namely, the bifrost/g72 part on MT8183, have a second >>>> regulator for their SRAM, let's add support for that. >>> >>>> + pfdev->regulator_sram = devm_regulator_get_optional(pfdev->dev, "sram"); >>>> + if (IS_ERR(pfdev->regulator_sram)) { >>> >>> This supply is required for the devices that need it so I'd therefore >>> expect the driver to request the supply non-optionally based on the >>> compatible string rather than just hoping that a missing regulator isn't >>> important. >> >> That'd be a bit awkward to match, though... Currently all bifrost >> share the same compatible "arm,mali-bifrost", and it'd seem >> weird/wrong to match "mediatek,mt8183-mali" in this driver? I have no >> idea if any other Mali implementation will require a second regulator, >> but with the MT8183 we do need it, see below. > > The current number of supported bifrost platforms is 0. It's only a > matter of time until SoC specific compatibles need to be used in the > driver. This is why we require them. > > It could very well be that all bifrost implementations need 2 > supplies. On chip RAMs are very frequently a separate thing which are > synthesized differently from logic. At least within a specific IP > model, I somewhat doubt there's a variable number of supplies. It > could be possible to connect both to the same supply, but the correct > way to handle that is both -supply properties point to the same > regulator. To be honest I've no idea what different SoC designs have done, but one of the intentions of core stacks was that sets of GPU cores would be on different power supplies. (I think this is to avoid issues with inrush current etc, but I'm not a hardware engineer). So I would expect designs with a large number of cores to have more physical supplies than designs with fewer cores. However, from a driver perspective this is all meant to be hidden by the hardware PDC which the GPU talks to. So the actual power up/down of the supplies may be completely automatic and therefore not described in the DT. So the actual number of software-controllable supplies could be 1 or could be more if the individual physical supplies are visible to software. The Hikey960 for instance hides everything behind a mailbox interface, and it's simply a case of requesting a frequency. Steve
On Fri, Jan 10, 2020 at 7:30 PM Steven Price <steven.price@arm.com> wrote: > > On 09/01/2020 19:49, Mark Brown wrote: > > On Thu, Jan 09, 2020 at 04:53:02PM +0000, Steven Price wrote: > >> On 09/01/2020 16:28, Mark Brown wrote: > >>> On Thu, Jan 09, 2020 at 02:14:42PM +0000, Steven Price wrote: > > > >>>> I'm not sure if it's better, but could we just encode the list of > >>>> regulators into device tree. I'm a bit worried about special casing an > >>>> "sram" regulator given that other platforms might have a similar > >>>> situation but call the second regulator a different name. > > > >>> Obviously the list of regulators bound on a given platform is encoded in > >>> the device tree but you shouldn't really be relying on that to figure > >>> out what to request in the driver - the driver should know what it's > >>> expecting. > > > >> From a driver perspective we don't expect to have to worry about power > >> domains/multiple regulators - the hardware provides a bunch of power > >> registers to turn on/off various parts of the hardware and this should be > >> linked (in hardware) to a PDC which sorts it out. The GPU/PDC handles the > >> required sequencing. So it *should* be a case of turn power/clocks on and > >> go. > > > > Ah, the well abstracted and consistent hardware with which we are all so > > fortunate to work :) . More seriously perhaps the thing to do here is > > create a driver that provides a soft PDC and then push all the special > > case handling into that? It can then get instantiated based on the > > compatible or perhaps represented directly in the device tree if that > > makes sense. > > That makes sense to me. > > >> However certain integrations may have quirks such that there are physically > >> multiple supplies. These are expected to all be turned on before using the > >> GPU. Quite how this is best represented is something I'm not sure about. > > > > If they're always on and don't ever change then that's really easy to > > represent in the DT without involving drivers, it's when you need to > > actively manage them that it's more effort. > > Sorry, I should have been more clear. They are managed as a group - so > either the entire GPU is powered off, or powered on. There's no support > in Panfrost or mali_kbase for attempting to power part of the GPU. > > >>> Bear in mind that getting regulator stuff wrong can result > >>> in physical damage to the system so it pays to be careful and to > >>> consider that platform integrators have a tendency to rely on things > >>> that just happen to work but aren't a good idea or accurate > >>> representations of the system. It's certainly *possible* to do > >>> something like that, the information is there, but I would not in any > >>> way recommend doing things that way as it's likely to not be robust. > > > >>> The possibility that the regulator setup may vary on other platforms > >>> (which I'd expect TBH) does suggest that just requesting a bunch of > >>> supply names optionally and hoping that we got all the ones that are > >>> important on a given platform is going to lead to trouble down the line. > > > >> Certainly if we miss a regulator the GPU isn't going to work properly (some > >> cores won't be able to power up successfully). However at the moment the > >> driver will happily do this if someone provides it with a DT which includes > >> regulators that it doesn't know about. So I'm not sure how adding special > >> case code for a SoC would help here. > > > > I thought this SoC neeed to vary the voltage on both rails as part of > > the power management? Things like that can lead to hardware damage if > > we go out of spec far enough for long enough - there can be requirements > > like keeping one rail a certain voltage above another or whatever. > > Yes, you are correct. My concern is that a DT which specifies a new > regulator (e.g. "sram2") would be accepted by an old kernel (because it > wouldn't know to look for the new regulator) but wouldn't know to > control the regulator. It could then create a situation which puts the > board out of spec - potentially in a damaging way. Hence I'd like to > express the regulator structure in such a way that old kernels wouldn't > "half-work". Your "soft-PDC" approach would seem to fit that requirement. FYI, I sent a v3 here: https://patchwork.kernel.org/patch/11331373/ that addresses _some_ of these concerns. I'm not quite sure how to describe the regulators in a way that we can check that the device tree does not specific extra ones (apart from doing some string matching on all properties?), and I don't think I'm best placed to implement the soft-PDC idea. See my comment on that patch. Thanks!
diff --git a/drivers/gpu/drm/panfrost/panfrost_device.c b/drivers/gpu/drm/panfrost/panfrost_device.c index 238fb6d54df4732..a0b0a6fef8b4e63 100644 --- a/drivers/gpu/drm/panfrost/panfrost_device.c +++ b/drivers/gpu/drm/panfrost/panfrost_device.c @@ -102,12 +102,33 @@ static int panfrost_regulator_init(struct panfrost_device *pfdev) return ret; } + pfdev->regulator_sram = devm_regulator_get_optional(pfdev->dev, "sram"); + if (IS_ERR(pfdev->regulator_sram)) { + ret = PTR_ERR(pfdev->regulator_sram); + dev_err(pfdev->dev, "failed to get SRAM regulator: %d\n", ret); + goto err; + } + + if (pfdev->regulator_sram) { + ret = regulator_enable(pfdev->regulator_sram); + if (ret < 0) { + dev_err(pfdev->dev, + "failed to enable SRAM regulator: %d\n", ret); + goto err; + } + } + return 0; + +err: + regulator_disable(pfdev->regulator); + return ret; } static void panfrost_regulator_fini(struct panfrost_device *pfdev) { regulator_disable(pfdev->regulator); + regulator_disable(pfdev->regulator_sram); } int panfrost_device_init(struct panfrost_device *pfdev) diff --git a/drivers/gpu/drm/panfrost/panfrost_device.h b/drivers/gpu/drm/panfrost/panfrost_device.h index 06713811b92cdf7..a124334d69e7e93 100644 --- a/drivers/gpu/drm/panfrost/panfrost_device.h +++ b/drivers/gpu/drm/panfrost/panfrost_device.h @@ -60,6 +60,7 @@ struct panfrost_device { struct clk *clock; struct clk *bus_clock; struct regulator *regulator; + struct regulator *regulator_sram; struct reset_control *rstc; struct panfrost_features features;
Some GPUs, namely, the bifrost/g72 part on MT8183, have a second regulator for their SRAM, let's add support for that. Signed-off-by: Nicolas Boichat <drinkcat@chromium.org> --- drivers/gpu/drm/panfrost/panfrost_device.c | 21 +++++++++++++++++++++ drivers/gpu/drm/panfrost/panfrost_device.h | 1 + 2 files changed, 22 insertions(+)