On 2014년 08월 07일 15:58, Thierry Reding wrote: > On Thu, Aug 07, 2014 at 02:09:19AM +0900, Inki Dae wrote: >> 2014-08-06 16:43 GMT+09:00 Thierry Reding <thierry.reding@xxxxxxxxx>: >>> On Wed, Aug 06, 2014 at 04:11:54PM +0900, Inki Dae wrote: >>>> On 2014년 08월 05일 20:12, Thierry Reding wrote: >>> [...] >>>>> I think that low power mode is more often used for command transmission >>>>> (in host-driven mode). I'm not sure how much sense it really makes to >>>>> transmit video data in low power mode. It also seems like low power mode >>>>> is what all peripherals need to support (if they can do command mode). >>>>> Hence I'd like to propose the attached patch that makes all command >>>>> messages use low power mode. >>>> >>>> To use low power mode, I think SoC drivers should add more codes: >>>> checking xxx_MSG_LPM, and maybe disabling HS clock. My patch does >>>> exactly that, >>>> http://www.spinics.net/lists/linux-samsung-soc/msg34866.html >>> >>> I agree in general that DSI host drivers need to check the flags to make >>> a decision about which mode to enable. But your patch also introduces >>> additional flags that I don't think are necessary (at least for any of >>> the use-cases discussed so far). >>> >>> As I understand it the MIPI_DSI_MODE_CMD_LPM and MIPI_DSI_MODE_VIDEO_LPM >>> flags that you introduce would advertise that the device only supports >>> low power mode for command or video modes respectively. However, I doubt >> >> Not so. My intention is to add LPM support for video and command data >> transfers because mipi-dsi framework enforces implicitly using HS mode >> for by default. > > No, it doesn't enforce anything at this point. Everyone is free to use > whatever they see fit. Drivers that require low power mode for command > transmission can set the MIPI_DSI_MSG_USE_LPM flag in messages. For > video there's no way to specify what a given peripheral uses, so DSI > host controller drivers are free to do whatever they want. > > So for command data we already have a means, and for video data I don't > think it makes sense to use low power mode. Therefore I don't think > these new flags are necessary. > >>> that there really are devices that only support low power video mode. It >>> wouldn't make much sense because you'd get a maximum of 10 MHz for the >>> clock, which is about 1.6 frames per second at 1920x1080 resolution (not >>> counting blanking). And even with lower resolutions such as 1024x768 it >>> would be somewhere around 4 frames per second. And I think it's >>> reasonable to assume that we'll see that kind of resolution become very >>> rare in the future. >>> >>> So my point is that devices which support video mode will always support >>> high speed mode for video transmission too. Similarly, if a device >>> supports command mode, then it will likely support it in low-power mode, >>> and optionally in high speed mode too. >>> >>>> And what I and Andrzej don't make sure is non-continuous clock mode. Do >>>> you know how non-continuous clock mode is related to HS clock? >>> >>> As far as I can tell non-continuous mode simply means that the host can >>> turn off the HS clock after a high-speed transmission. I think Andrzej >>> mentioned this already in another subthread, but this is an optional >>> mode that peripherals can support if they have extra circuitry that >>> provides an internal clock. Peripherals that don't have such circuitry >>> may rely on the HS clock to perform in between transmissions and >>> therefore require the HS clock to be always on (continuous mode). That's >>> what the MIPI_DSI_CLOCK_NON_CONTINUOUS flag is: it advertises that the >>> peripheral supports non-continuous mode and therefore the host can turn >>> the HS clock off after high-speed transmissions. >> >> What I don't make sure is this sentence. With >> MIPI_DSI_CLOCK_NON_CONTIUOUS flag, I guess two possible operations. >> One is, >> 1. host controller will generates signals if a bit of a register >> related to non-contiguous clock mode is set or unset. >> 2. And then video data is transmitted to panel in HS mode. >> 3. And then D-PHY detects LP-11 signal (positive and negative lane all >> are high). >> 4. And then D-PHY disables HS clock of host controller. >> 5. At this time, operation mode of host controller becomes LPM. >> >> Other is, >> 1. host controller will generates signals if a bit of a register >> related to non-contiguous clock mode is set or unset. >> 2. And then D-PHY detects LP-11 signal (positive and negative lane all >> are high). >> 3. And then video data is transmitted to panel in LPM. >> 4. At this time, operation mode of host controller becomes LPM. >> >> It seems that you says latter case. > > No. High speed clock and low power mode are orthogonal. Non-continuous > mode simply means that the clock lane enters LP-11 between HS > transmissions (see 5.6 "Clock Management" of the DSI specification). > It seems that clock lane enters LP-11 regardless of HS clock enabled if non-continous mode is used. Right? And also it seems that non-continous mode is different from LPM at all because with non-continuous mode, command data is transmitted to panel in HS mode, but with LPM, command data is transmitted to panel in LP mode. Also right? If so, shouldn't the host driver disable HS clock, in case of LP mode, before the host driver transmits command data? And it seems that only one of these two flags, MSG_LPM and NON-CONTINUOUS, should be set by panel driver because with NON-CONTINUOUS clock mode, host controller generate clock and data lane signals regardless of controlling HS clock. Thanks, Inki Dae > For low power mode the clock is embedded in the signal on the data lane > and therefore independent of the high speed clock. > > A peripheral device will set the MIPI_DSI_CLOCK_NON_CONTINUOUS flag if > it supports non-continuous mode of operation. That is, it has own > circuitry to generate a clock that can be used for clocked operations > between high-speed transmissions (when the HS clock isn't available). > >> I really know that with non-contiguous clock mode, HS clock of host >> controller can be disabled. My question is who controls HS clock in >> this case. D-PHY or host controller? > > I suspect it's usually the host controller. But does it matter? From a > software perspective we usually only access the host controller, so the > D-PHY is usually completely hidden (except maybe for some registers in > the host controller to configure it). > >> In other words, with LPM and MIPI_DSI_CLOCK_NON_CONTIUOUS flags, >> should the host driver check these two flags to disable HS clock? or >> In this case, does the D-PHY disable HS clock regardless of host >> driver? > > Like I said, low power mode and non-continuous clock are not directly > related. Peripherals may require the HS clock to be always on and still > use low power mode for transmissions. > >>>> Do you intend to control transfer mode - HS or LPM - only for command >>>> data? If so, we would need only one flag, i.e., MIPI_DSI_MODE_HS. >>> >>> We already have that flag, it's called MIPI_DSI_MSG_USE_LPM. Given the >>> above discussion I think it may still be worthwhile to invert the >>> meaning of the flag and rename it MIPI_DSI_MSG_USE_HS, so that all >>> messages are indeed sent in low power mode by default. >> >> Yes, it may be reasonable. But I'm not sure that there is no any issue >> in case of transmitting always video data in HS mode. > > Like I said, with low power mode you can't meet the bandwidth > requirements of any reasonable resolution and framerate, so I would > assume that video data can always be transmitted in HS mode. So even if > some device required video data transmission to use low power mode, then > that should be considered the oddball peripheral and it could be handled > by an extra flag. > > By default we should still assume high-speed mode for video data packet > transmissions. We can address those quirks when we actually encounter > peripherals that don't work under those assumptions. > > Thierry > _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
