On Mon, Jan 14, 2019 at 8:57 PM Daniel Lezcano
wrote:
>
> On 13/01/2019 03:17, Samuel Holland wrote:
> > This is the third version of a patch series to fix system clock jumps
> > and other timer instability on the Allwinner A64 SoC. It has now been
> > tested for a week, and I've received no
On Sat, Jan 12, 2019 at 12:08 AM Jagan Teki wrote:
>
> Chen-Yu and Rask,
>
> On Fri, Jan 11, 2019 at 4:46 PM Jagan Teki wrote:
> >
> > Update all A80 devicetree dtsi and dtsi files from
> > Linux-v4.18-rc3 with below commits.
> >
> > arch/arm/boot/dts/sun9i-a80*:
> >
> > commit
Hi Samuel,
On 13/01/2019 02:17, Samuel Holland wrote:
> The Allwinner A64 SoC is known[1] to have an unstable architectural
> timer, which manifests itself most obviously in the time jumping forward
> a multiple of 95 years[2][3]. This coincides with 2^56 cycles at a
> timer frequency of 24 MHz,
On Fri, Jan 11, 2019 at 11:34:07PM +0530, Jagan Teki wrote:
> I thought of waiting this till CLK framework gets Mainline,
> but migration deadline for DM_MMC and BLK seems expiring in
> next release. So instead of doing so huddle and make some last
> minute changes, I have managed to add CLK,
On Mon, Jan 14, 2019 at 3:05 PM Priit Laes wrote:
>
> On Fri, Jan 11, 2019 at 11:34:07PM +0530, Jagan Teki wrote:
> > I thought of waiting this till CLK framework gets Mainline,
> > but migration deadline for DM_MMC and BLK seems expiring in
> > next release. So instead of doing so huddle and
On Mon 14 Jan, 2019, 3:53 PM Priit Laes On Mon, Jan 14, 2019 at 03:40:37PM +0530, Jagan Teki wrote:
> > On Mon, Jan 14, 2019 at 3:05 PM Priit Laes wrote:
> > >
> > > On Fri, Jan 11, 2019 at 11:34:07PM +0530, Jagan Teki wrote:
> > > > I thought of waiting this till CLK framework gets Mainline,
>
Heya!
I have a somewhat curious case with one HDMI/DVI screen that fails
to initialize properly every 6-7 boots. The display itself is also
somewhat flawed (missing HPD pin and the VSYNC/HSYNC pulse width
is set to 0 in EDID), but I suspect there could be some issues
regarding timing in A20 HDMI
This is a first attempt at implementing proper access to buffers
imported with dma-buf and used as reference frames for decoding
subsequent frames.
The main concern associated with this scenario was that memory could be
liberated while the buffer is not in a queued state. After careful
checking,
Access to reference frames that were imported from dma-buf was taken
care of and is no longer a pending item on the driver's TODO list.
Signed-off-by: Paul Kocialkowski
---
drivers/staging/media/sunxi/cedrus/TODO | 5 -
1 file changed, 5 deletions(-)
diff --git
Introduce helpers to request and release access to buffers that are
not currently selected as current output or capture buffers.
This is useful to ensure proper access to buffers imported via dma-buf
that are used as reference and thus require associated map/unmap calls
before access.
Introduce a new optional job_done operation, which allows calling back
to the driver when a job is done. Since the job might be completed
from interrupt context where some operations are not available, having
a callback from non-atomic context allows performing these operations
upon completion of
Because we need to request and release access to reference buffers
that are backed by a dma-buf import, keep track of the buffers used
as reference and add the appropriate calls in the device_run and
job_done m2m callbacks. The latter is introduced for this purpose.
Signed-off-by: Paul
On Mon, Jan 14, 2019 at 03:40:37PM +0530, Jagan Teki wrote:
> On Mon, Jan 14, 2019 at 3:05 PM Priit Laes wrote:
> >
> > On Fri, Jan 11, 2019 at 11:34:07PM +0530, Jagan Teki wrote:
> > > I thought of waiting this till CLK framework gets Mainline,
> > > but migration deadline for DM_MMC and BLK
On Mon, Jan 14, 2019 at 04:00:44PM +0530, Jagan Teki wrote:
> On Mon 14 Jan, 2019, 3:53 PM Priit Laes
> > On Mon, Jan 14, 2019 at 03:40:37PM +0530, Jagan Teki wrote:
> > > On Mon, Jan 14, 2019 at 3:05 PM Priit Laes wrote:
> > > >
> > > > On Fri, Jan 11, 2019 at 11:34:07PM +0530, Jagan Teki
On Mon, Jan 14, 2019 at 10:39:37AM +, Priit Laes wrote:
> On Mon, Jan 14, 2019 at 04:00:44PM +0530, Jagan Teki wrote:
> > On Mon 14 Jan, 2019, 3:53 PM Priit Laes >
> > > On Mon, Jan 14, 2019 at 03:40:37PM +0530, Jagan Teki wrote:
> > > > On Mon, Jan 14, 2019 at 3:05 PM Priit Laes wrote:
> >
On 13/01/2019 03:17, Samuel Holland wrote:
> This is the third version of a patch series to fix system clock jumps
> and other timer instability on the Allwinner A64 SoC. It has now been
> tested for a week, and I've received no reports of date jumps with this
> version. So this is, as far as I
16 matches
Mail list logo
