Hi Kieran / Mauro,
On Fri, May 05, 2017 at 06:33:22PM +0100, Kieran Bingham wrote:
> Hi Sakari,
>
> On 04/01/17 08:57, Sakari Ailus wrote:
> > Hi Kieran,
> >
> > Thanks for the patch!
> >
> > On Tue, Jan 03, 2017 at 05:05:58PM +, Kieran Bingham wrote:
> >> On 03/01/17 13:36, Laurent Pinchar
On Fri, Apr 28, 2017 at 09:52:35PM +0300, Sergei Shtylyov wrote:
> Renesas RZ/G1E (R8A7745) is pin compatible with R-Car E2 (R8A7794),
> however it doesn't have several automotive specific peripherals.
> Annotate all the items that only exist on the R-Car SoCs...
>
> Signed-off-by: Sergei Shtylyov
Hi Sakari,
On 04/01/17 08:57, Sakari Ailus wrote:
> Hi Kieran,
>
> Thanks for the patch!
>
> On Tue, Jan 03, 2017 at 05:05:58PM +, Kieran Bingham wrote:
>> On 03/01/17 13:36, Laurent Pinchart wrote:
>>> Hi Kieran,
>>>
>>> Thank you for the patch.
>>>
>>> On Tuesday 03 Jan 2017 13:12:11 Kiera
To be able to perform page flips in DRM without flicker we need to be
able to notify the rcar-du module when the VSP has completed its
processing.
We must not have bidirectional dependencies on the two components to
maintain support for loadable modules, thus we extend the API to allow
a callback
The RCAR-DU utilises a running VSPD pipeline to perform processing for the
display pipeline. This presents the opportunity for some race conditions to
affect the quality of the display output.
To prevent reporting page flips early, we must track this timing through the
VSP1, and only allow the rca
Currently we process page flip events on every display interrupt,
however this does not take into consideration the processing time needed
by the VSP1 utilised in the pipeline.
Register a callback with the VSP driver to obtain completion events, and
track them so that we only perform page flips wh
From: Laurent Pinchart
The page flip event is armed in the atomic begin handler, creating a
race condition with the frame end interrupt that could send the event
before the atomic operation actually completes. To avoid that, arm the
event in the atomic flush handler after queuing the page flip.
If we try to commit the display list while an update is pending, we have
missed our opportunity. The display list manager will hold the commit
until the next interrupt.
In this event, we skip the pipeline completion callback handler so that
the pipeline will not mistakenly report frame completion
Hi Sricharan, Robin,
On Wed, May 3, 2017 at 12:24 PM, Sricharan R wrote:
> On 5/3/2017 3:24 PM, Robin Murphy wrote:
>> On 02/05/17 19:35, Geert Uytterhoeven wrote:
>>> On Fri, Feb 3, 2017 at 4:48 PM, Sricharan R
>>> wrote:
From: Laurent Pinchart
Failures to look up an IOMMU when
On Friday, May 05, 2017, Linus Walleij wrote:
> > This is the part of the whole "DT is for hardware description only" that
> doesn't really make sense to me.
>
> OK yeah we do hardware description AND configuration.
>
> And we never do interpreted languages.
>
> And then there is a bunch of gray
Hi Linus,
On Fri, May 5, 2017 at 2:06 PM, Linus Walleij wrote:
> On Fri, Apr 28, 2017 at 4:48 PM, Chris Brandt
> wrote:
>
> I think this was written by me, not Geert...
>
>>> DT describes hardware, not software limitations.
Na, I did write it.
I can understand you sometimes mix up things, esp
Hi Ramesh,
Looks good. I replied to patch 3/7 requesting a small change, but otherwise
I'm OK.
The only thing missing is an Ack from Rob for patch 6/7 (R-car DRIF bindings).
Once I have that + an updated patch 3/7 I can make a pull request for this.
Regards,
Hans
On 05/02/17 15:26, Ra
On 05/02/17 15:26, Ramesh Shanmugasundaram wrote:
> This patch adds driver support for the MAX2175 chip. This is Maxim
> Integrated's RF to Bits tuner front end chip designed for software-defined
> radio solutions. This driver exposes the tuner as a sub-device instance
> with standard and custom co
On Fri, Apr 28, 2017 at 4:48 PM, Chris Brandt wrote:
I think this was written by me, not Geert...
>> DT describes hardware, not software limitations.
>
> Describing things is fine, but the kernel code takes the DT and then start
> configuring things based on it.
>
> For example, on the RSK boar
On Thu, May 4, 2017 at 7:45 PM, Geert Uytterhoeven
wrote:
> From: Hisashi Nakamura
>
> Add slave mode support to the MSIOF driver, in both PIO and DMA mode.
>
> For now this only supports the transmission of messages with a size
> that is known in advance.
>
> Signed-off-by: Hisashi Nakamura
> S
On Thu, May 4, 2017 at 7:45 PM, Geert Uytterhoeven
wrote:
> --- a/include/linux/spi/spi.h
> +++ b/include/linux/spi/spi.h
> @@ -447,6 +448,8 @@ struct spi_master {
> #define SPI_MASTER_MUST_TX BIT(4) /* requires tx */
> #define SPI_MASTER_GPIO_SS BIT(5) /* GPIO CS must
16 matches
Mail list logo
