On Thu, Apr 25, 2019 at 05:11:20PM -0700, Nadav Amit wrote:
> Yet another version, per PeterZ request, addressing the latest feedback.
>
Well, I would've been OK with just an updated to the one patch, but
thanks. Let me see if I can get all that to apply :-)
Yet another version, per PeterZ request, addressing the latest feedback.
This patchset improves several overlapping issues around stale TLB
entries and W^X violations. It is combined from "x86/alternative:
text_poke() enhancements v7" [1] and "Don't leave executable TLB entries
to freed pages v2"
This series implements support for YUV formats using the display engine
frontend in the sun4i DRM driver, with various fixes along the way.
Scaling is supported for every format handled by the frontend.
The tiling mode used by the VPU on Allwinner platforms is also supported
by this series and a d
Shared virtual address (SVA), a.k.a, Shared virtual memory (SVM) on Intel
platforms allow address space sharing between device DMA and applications.
SVA can reduce programming complexity and enhance security. To enable SVA
in the guest, i.e. shared guest application address space and physical
devic
From: Srinivas Kandagatla
Thankyou everyone for providing feedback on v4 patchset.
This patchset aims to provide a basic version of QCOM DSP based
audio support which is available in downstream andriod kernels.
This patchset support audio playback on HDMI-RX, MI2S, SLIMBus and
will add support to
On Thu, 8 Jun 2017 16:12:49 +0900
Masahiro Yamada wrote:
> 2017-06-08 15:16 GMT+09:00 Masahiro Yamada :
> > Hi Boris,
> >
> > 2017-06-07 20:52 GMT+09:00 Masahiro Yamada :
> >
> >> This patch series intends to solve various problems.
> >>
> >> [1] The driver just retrieves the OOB area as-is
>
This patchset adds support for the HiSilicon SAS controller
in the hip08 chipset.
The key difference compared to earlier chipsets is that the
controller is an integrated PCI endpoint in hip08.
As such, the controller is a pci device (not a platform device,
like v2 hw in hip07).
The driver is refa
Le Thu, 8 Jun 2017 16:12:49 +0900,
Masahiro Yamada a écrit :
> 2017-06-08 15:16 GMT+09:00 Masahiro Yamada :
> > Hi Boris,
> >
> > 2017-06-07 20:52 GMT+09:00 Masahiro Yamada :
> >
> >> This patch series intends to solve various problems.
> >>
> >> [1] The driver just retrieves the OOB area as-i
Le Thu, 8 Jun 2017 15:16:53 +0900,
Masahiro Yamada a écrit :
> Hi Boris,
>
> 2017-06-07 20:52 GMT+09:00 Masahiro Yamada :
> > This patch series intends to solve various problems.
> >
> > [1] The driver just retrieves the OOB area as-is
> > whereas the controller uses syndrome page layout.
>
2017-06-08 15:16 GMT+09:00 Masahiro Yamada :
> Hi Boris,
>
> 2017-06-07 20:52 GMT+09:00 Masahiro Yamada :
>> This patch series intends to solve various problems.
>>
>> [1] The driver just retrieves the OOB area as-is
>> whereas the controller uses syndrome page layout.
>> [2] Many NAND chip spe
Hi Boris,
2017-06-07 20:52 GMT+09:00 Masahiro Yamada :
> This patch series intends to solve various problems.
>
> [1] The driver just retrieves the OOB area as-is
> whereas the controller uses syndrome page layout.
> [2] Many NAND chip specific parameters are hard-coded in the driver.
> [3] ON
This patch series intends to solve various problems.
[1] The driver just retrieves the OOB area as-is
whereas the controller uses syndrome page layout.
[2] Many NAND chip specific parameters are hard-coded in the driver.
[3] ONFi devices are not working
[4] It can not read Bad Block Marker
Ou
Implementation of the IBM 'Flexible Support Interface' (FSI) bus device
driver. FSI is a high fan out serial bus consisting of a clock and a serial
data line capable of running at speeds up to 166 MHz.
This set provides the basic framework to add FSI extensions to the
Linux bus and device models.
On Tue, Oct 18, 2016 at 01:51:39PM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-10-18 02:31:40)
> > On Mon, Oct 17, 2016 at 06:56:13PM -0700, Stephen Boyd wrote:
> > > I've also sent separate patches for other minor pieces to make this
> > > all work. The full tree can be found here[2], ha
On Mon, Oct 17, 2016 at 06:56:13PM -0700, Stephen Boyd wrote:
> The state of USB ChipIdea support on Qualcomm's platforms is not great.
> The DT description of these devices requires up to three different nodes
> for what amounts to be the same hardware block, when there should really
> only be one
The state of USB ChipIdea support on Qualcomm's platforms is not great.
The DT description of these devices requires up to three different nodes
for what amounts to be the same hardware block, when there should really
only be one. Furthermore, the "phy" driver that is in mainline (phy-msm-usb.c)
du
The main purpose of this patchset is to dramatically reduce the time
spent in DTLB miss handler. This is achieved by:
1/ Mapping RAM with 8M pages
2/ Mapping IMMR with a fixed 512K page
On a live running system (VoIP gateway for Air Trafic Control), over
a 10 minutes period (with 277s idle), we ge
> On Oct 5, 2015, at 8:59 AM, Catalin Marinas wrote:
>
>> On Sat, Oct 03, 2015 at 02:18:57AM +, Kapoor, Prasun wrote:
>>> On 10/2/15, 2:37 AM, "Catalin Marinas" wrote:
>>> So, at the time, following x32 discussions, we thought of using the
>>> native ABI as much as possible. However, two i
On Fri, Oct 02, 2015 at 12:49:46AM +0300, Pinski, Andrew wrote:
[...]
> Ok, we will rewrite these patches using 32bit time_t and 32bit off_t and
> redo the toolchain support for them. Note this is going back to the abi
> I had originally done when I submitted my original version when it was
> as
On Sat, Oct 03, 2015 at 02:18:57AM +, Kapoor, Prasun wrote:
> On 10/2/15, 2:37 AM, "Catalin Marinas" wrote:
> >So, at the time, following x32 discussions, we thought of using the
> >native ABI as much as possible. However, two important things happened
> >since:
> >
> >1. libc community didn't
On 10/2/15, 2:37 AM, "Catalin Marinas" wrote:
>On Thu, Oct 01, 2015 at 09:49:46PM +, Pinski, Andrew wrote:
>> Ok, we will rewrite these patches using 32bit time_t and 32bit off_t
>> and redo the toolchain support for them. Note this is going back to
>> the abi I had originally done when I
On Thu, Oct 01, 2015 at 09:49:46PM +, Pinski, Andrew wrote:
> Ok, we will rewrite these patches using 32bit time_t and 32bit off_t
> and redo the toolchain support for them. Note this is going back to
> the abi I had originally done when I submitted my original version
> when it was asked to c
> On Oct 1, 2015, at 2:29 PM, Arnd Bergmann wrote:
>
>> On Thursday 01 October 2015 22:15:20 Yury Norov wrote:
>>
>> Regarding time_t, it, of course, doesn't takes much time to make it
>> 32-bit, but I think 64 bit is better because of Y2038. X32 and mips
>> n32 has time_t 64-bit (and ppc, not
On Thursday 01 October 2015 22:15:20 Yury Norov wrote:
> Regarding time_t, it, of course, doesn't takes much time to make it
> 32-bit, but I think 64 bit is better because of Y2038. X32 and mips
> n32 has time_t 64-bit (and ppc, not sure), and that's OK for them.
I'm pretty sure that n32 has 32-b
On Wed, Sep 30, 2015 at 05:41:03PM +0100, Mark Brown wrote:
> On Wed, Sep 30, 2015 at 11:19:19AM +0100, Catalin Marinas wrote:
> > On Wed, Sep 30, 2015 at 01:13:57AM +0300, Yury Norov wrote:
>
> > > - What for ILP32 on ARM64?
> > > See https://lkml.org/lkml/2015/4/13/814
> > > and http://perm
On Wed, Sep 30, 2015 at 11:19:19AM +0100, Catalin Marinas wrote:
> On Wed, Sep 30, 2015 at 01:13:57AM +0300, Yury Norov wrote:
> > V5 reincarnation for ILP32.
> >
> > This is mostly the same code as Andrew suggested in v3:
> > https://lkml.org/lkml/2014/9/3/704.
> >
> > V4 series and discussi
On 10/01/2015 02:36 PM, Mark Brown wrote:
On Thu, Oct 01, 2015 at 12:19:31PM +0100, Catalin Marinas wrote:
On Wed, Sep 30, 2015 at 05:41:03PM +0100, Mark Brown wrote:
Indeed. On that subject there was some discussion at Linaro Connect
last week about work (being done outside Linaro, not sure
On Thu, Oct 01, 2015 at 12:19:31PM +0100, Catalin Marinas wrote:
> On Wed, Sep 30, 2015 at 05:41:03PM +0100, Mark Brown wrote:
> > Indeed. On that subject there was some discussion at Linaro Connect
> > last week about work (being done outside Linaro, not sure how public it
> > is at this point)
On Wed, Sep 30, 2015 at 05:41:03PM +0100, Mark Brown wrote:
> On Wed, Sep 30, 2015 at 11:19:19AM +0100, Catalin Marinas wrote:
> > On Wed, Sep 30, 2015 at 01:13:57AM +0300, Yury Norov wrote:
>
> > > - What for ILP32 on ARM64?
> > > See https://lkml.org/lkml/2015/4/13/814
> > > and http://perm
On Wed, Sep 30, 2015 at 11:19:19AM +0100, Catalin Marinas wrote:
> On Wed, Sep 30, 2015 at 01:13:57AM +0300, Yury Norov wrote:
> > - What for ILP32 on ARM64?
> > See https://lkml.org/lkml/2015/4/13/814
> > and http://permalink.gmane.org/gmane.comp.lib.uclibc.buildroot/121100
> > Brief
On Wed, Sep 30, 2015 at 01:13:57AM +0300, Yury Norov wrote:
> V5 reincarnation for ILP32.
>
> This is mostly the same code as Andrew suggested in v3:
> https://lkml.org/lkml/2014/9/3/704.
>
> V4 series and discussion:
> https://lkml.org/lkml/2015/4/13/691
>
> Discussion on v3 and v4
V5 reincarnation for ILP32.
This is mostly the same code as Andrew suggested in v3:
https://lkml.org/lkml/2014/9/3/704.
V4 series and discussion:
https://lkml.org/lkml/2015/4/13/691
Discussion on v3 and v4 raised questions and some disagreement in community,
and therefore patches
On Friday 12 December 2014 14:06:51 Kevin Cernekee wrote:
> V4->V5:
>
> - Rebase on top of Linus' head of tree, converting BCM3384 platform code
>to Generic BMIPS platform code.
>
> - Fix a couple of #include's
>
> - Remove a couple of bogus entries from bmips_be_defconfig
>
> Compile-te
V4->V5:
- Rebase on top of Linus' head of tree, converting BCM3384 platform code
to Generic BMIPS platform code.
- Fix a couple of #include's
- Remove a couple of bogus entries from bmips_be_defconfig
Compile-tested only. Some BMIPS platforms may require acked-but-unmerged
changes in oth
On Sun, Feb 02, 2014 at 07:06:06PM +0100, Jean-Francois Moine wrote:
> - the .of_match_table is not needed because the i2c client is created by
> the i2c subsystem from the 'reg' in the DT,
It's generally better to have an explict set of OF IDs even if the
default does work - matching purely on
On Sun, 2 Feb 2014 19:15:05 +
Russell King - ARM Linux wrote:
> In which case, it may be better to reorder the remaining patches such
> that the DT changes are at the very end - which means we can still
> benefit from the rest of the patches if the DT solution remains an
> open question.
>
>
On Sun, Feb 02, 2014 at 07:54:00PM +0100, Jean-Francois Moine wrote:
> I explained how to use the tda998x in a DT context in a message to Jyri
> Sarha:
>
> http://lists.freedesktop.org/archives/dri-devel/2014-January/052936.html
Okay, so there's a bunch of changes required to the DRM slave suppor
On Sun, 2 Feb 2014 18:04:34 +
Russell King - ARM Linux wrote:
> So, in summary, I'm pretty happy with this again - and it's all been
> tested here with no apparant detrimental effects. All committed and
> queued up here:
>
> http://ftp.arm.linux.org.uk/cgit/linux-cubox.git/log/?h=tda998x-de
On Sun, 2 Feb 2014 18:23:49 +
Russell King - ARM Linux wrote:
> On Sun, Feb 02, 2014 at 07:06:06PM +0100, Jean-Francois Moine wrote:
> > On Sun, 2 Feb 2014 12:43:58 +
> > Russell King - ARM Linux wrote:
> >
> > > On Wed, Jan 29, 2014 at 10:01:22AM +0100, Jean-Francois Moine wrote:
> > >
On 02/02/2014 07:23 PM, Russell King - ARM Linux wrote:
On Sun, Feb 02, 2014 at 07:06:06PM +0100, Jean-Francois Moine wrote:
- on encoder_destroy(), the function drm_i2c_encoder_destroy()
unregisters the i2c client, so, with a DT, a second encoder_init()
would crash.
I think this is one
On Sun, Feb 02, 2014 at 07:06:06PM +0100, Jean-Francois Moine wrote:
> On Sun, 2 Feb 2014 12:43:58 +
> Russell King - ARM Linux wrote:
>
> > On Wed, Jan 29, 2014 at 10:01:22AM +0100, Jean-Francois Moine wrote:
> > > This patch set contains various extensions to the tda998x driver:
> > >
> >
On Sun, 2 Feb 2014 12:43:58 +
Russell King - ARM Linux wrote:
> On Wed, Jan 29, 2014 at 10:01:22AM +0100, Jean-Francois Moine wrote:
> > This patch set contains various extensions to the tda998x driver:
> >
> > - simplify the i2c read/write
> > - code cleanup and fix some small errors
> > -
On Sun, Feb 02, 2014 at 12:43:58PM +, Russell King - ARM Linux wrote:
> On Wed, Jan 29, 2014 at 10:01:22AM +0100, Jean-Francois Moine wrote:
> > This patch set contains various extensions to the tda998x driver:
> >
> > - simplify the i2c read/write
> > - code cleanup and fix some small errors
On Wed, Jan 29, 2014 at 10:01:22AM +0100, Jean-Francois Moine wrote:
> This patch set contains various extensions to the tda998x driver:
>
> - simplify the i2c read/write
> - code cleanup and fix some small errors
> - use global constants
> - don't read write-only registers
> - add DT support
> -
This patch set contains various extensions to the tda998x driver:
- simplify the i2c read/write
- code cleanup and fix some small errors
- use global constants
- don't read write-only registers
- add DT support
- use IRQ for connection status and EDID read
- v5
- remarks from Russell King
45 matches
Mail list logo
