> I think postponing merge of patches is one thing but I don't think
> dropping them forever is a long term solution. I think we should have
Just to make sure because you wrote 'them': I talked about one patch of
the series, not the whole series, namely DVFS. Because Lager is the only
board we
On Wednesday, November 9, 2016 6:19:06 PM CET Geert Uytterhoeven wrote:
> On Wed, Nov 9, 2016 at 5:56 PM, Arnd Bergmann wrote:
> > On Wednesday, November 9, 2016 2:34:33 PM CET Geert Uytterhoeven wrote:
> >> > And Samsung.
> >> > Shall I create the immutable branch now?
> >>
> >>
Hi Florian,
On Wed, Nov 9, 2016 at 8:17 PM, Florian Fainelli wrote:
> On 11/08/2016 11:50 AM, Geert Uytterhoeven wrote:
>> On Tue, Nov 8, 2016 at 8:42 PM, Florian Fainelli
>> wrote:
>>> On 11/08/2016 11:35 AM, Geert Uytterhoeven wrote:
Currently
Hi Sergei,
On Wed, Nov 9, 2016 at 8:02 PM, Sergei Shtylyov
wrote:
> On 10/31/2016 08:13 PM, Geert Uytterhoeven wrote:
>
>> The limitation to 10/100Mbit speeds on R-Car Gen3 is valid for R-Car H3
>> ES1.0 only. Check for the exact SoC model to allow 1Gbps on
Hello.
On 10/31/2016 08:13 PM, Geert Uytterhoeven wrote:
The limitation to 10/100Mbit speeds on R-Car Gen3 is valid for R-Car H3
ES1.0 only. Check for the exact SoC model to allow 1Gbps on newer
revisions of R-Car H3, and on R-Car M3-W.
Signed-off-by: Geert Uytterhoeven
On Wed, Nov 9, 2016 at 3:35 PM, Simon Horman wrote:
>> Will you get access to these boards in the foreseeable future?
>
> As mentioned by Geert, there is a porter in Magnus's board farm.
> Unforunately I have never had much luck in getting it to boot.
>From the point of view
On Mon, Oct 31, 2016 at 12:30:53PM +0100, Geert Uytterhoeven wrote:
> Add device tree binding documentation for the Common Chip Code Register
> and Product Register, which provide SoC product and revision
> information.
>
> Signed-off-by: Geert Uytterhoeven
> ---
> v2:
>
Hello.
On 11/07/2016 06:27 PM, Simon Horman wrote:
From: Kazuya Mizuguchi
The kernel panic occurs with "swiotlb buffer is full" message
after repeating suspend and resume, because dma_map_single of
ravb_ring_format and ravb_start_xmit is not released.
> ARM: dts: lager: use demuxer for IIC3/I2C3
I think the sanest solution is to drop this patch forever. The WARN from
the regulator core is sparse in describing the problem yet it is
correct: The regulator is needed, by the CPU! :) And this will probably
be the smallest problem when trying to
Hi Arnd,
On Wed, Nov 9, 2016 at 5:56 PM, Arnd Bergmann wrote:
> On Wednesday, November 9, 2016 2:34:33 PM CET Geert Uytterhoeven wrote:
>> > And Samsung.
>> > Shall I create the immutable branch now?
>>
>> Arnd: are you happy with the new patches and changes?
>
> I still had some
On Wednesday, November 9, 2016 2:34:33 PM CET Geert Uytterhoeven wrote:
> >
> > And Samsung.
> > Shall I create the immutable branch now?
>
> Arnd: are you happy with the new patches and changes?
I still had some comments for patch 7, but that shouldn't stop
you from creating a branch for the
On Monday, October 31, 2016 12:30:55 PM CET Geert Uytterhoeven wrote:
> v2:
> - Drop SoC families and family names; use fixed "Renesas" instead,
I think I'd rather have seen the family names left in there, but it's
not important, so up to you.
> - Use "renesas,prr" and "renesas,cccr" device
This patch adds driver support for 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 controls to configure the device.
Signed-off-by: Ramesh
Hi All,
This patch set contains two drivers
- R-Car Digital Radio Interface (DRIF) driver
- Maxim's MAX2175 RF to Bits tuner driver
These patches were based on top of media-next repo
commit: 778de01402328ca88cda84491d819bfc949935ff
These two drivers combined together expose a V4L2 SDR device
This patch adds support for the three new SDR formats. These formats
were prefixed with "sliced" indicating I data constitutes the top half and
Q data constitutes the bottom half of the received buffer.
V4L2_SDR_FMT_SCU16BE - 14-bit complex (I & Q) unsigned big-endian sample
inside 16-bit. V4L2
This patch adds documentation for the three new SDR formats
V4L2_SDR_FMT_SCU16BE
V4L2_SDR_FMT_SCU18BE
V4L2_SDR_FMT_SCU20BE
Signed-off-by: Ramesh Shanmugasundaram
---
.../media/uapi/v4l/pixfmt-sdr-scu16be.rst | 80 ++
On Wed, Nov 09, 2016 at 09:59:54AM +0100, Wolfram Sang wrote:
> Hi Simon,
>
> > I have tested these patches on alt, gose, lager and koelsch.
>
> Wow, that was quick. Thank you!
>
> > The switching part seems to work fine, in so far as my test script
> > succeeds. However, it seems that some IP
On Tue, Nov 08, 2016 at 09:35:46AM +0900, Cao Minh Hiep wrote:
> From: Hiep Cao Minh
>
> This patch rewrites the name of rspi_pio_transfer_in_or_out
> function.
This doesn't apply against current code, please check and resend.
signature.asc
Description: PGP signature
Hi Arnd,
On Mon, Nov 7, 2016 at 10:35 AM, Geert Uytterhoeven
wrote:
> On Mon, Oct 31, 2016 at 12:30 PM, Geert Uytterhoeven
> wrote:
>> Some Renesas SoCs may exist in different revisions, providing slightly
>> different functionalities (e.g. R-Car
Hi Geert,
On 08/11/16 19:35, Geert Uytterhoeven wrote:
> Currently the renesas-irqc driver uses postcore_initcall().
>
> However, the new CPG/MSSR driver uses subsys_initcall(). Hence the
> IRQC's probe will be deferred, which causes the Micrel Ethernet PHY to
> not find its interrupt on R-Car
Hi Simon,
> I have tested these patches on alt, gose, lager and koelsch.
Wow, that was quick. Thank you!
> The switching part seems to work fine, in so far as my test script
> succeeds. However, it seems that some IP blocks are not able to handle
> this switching. In particular I needed to
Hi Simon,
On Wed, Nov 9, 2016 at 9:44 AM, Simon Horman wrote:
> I am not in a position to test silk or porter at this time.
FWIW, Magnus has a Porter in his farm.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32
Hi Wolfram,
On Sun, Nov 06, 2016 at 09:20:18PM +0100, Wolfram Sang wrote:
> So, here is the newest series for using the I2C demuxer on Gen2 boards.
> Initially done by Simon. The intention of this series is to extend use of the
> demuxer for I2C on the lager, koelsch, porter, koelsch, alt and
Hi Simon,
On 09.11.2016 10:44, Simon Horman wrote:
On Tue, Nov 08, 2016 at 05:14:21PM +0300, Vladimir Barinov wrote:
This supports SDHI0 on M3ULCB board SD card slot
Signed-off-by: Vladimir Barinov
Reviewed-off-by: Simon Horman
24 matches
Mail list logo