This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Sun Feb 26 05:00:22 CET 2017
media-tree git hash:e6b377dbbb944d5e3ceef4e5d429fc5c841e3692
media_build git
Moi! :-)
On Sat, Feb 25, 2017 at 10:53:22PM +0100, Pavel Machek wrote:
> Hi!
>
> > > Ok, I got the camera sensor to work. No subdevices support, so I don't
> > > have focus (etc) working, but that's a start. I also had to remove
> > > video-bus-switch support; but I guess it will be easier to use
Hi!
> > Making the sub-device bus configuration a pointer should be in a separate
> > patch. It makes sense since the entire configuration is not valid for all
> > sub-devices attached to the ISP anymore. I think it originally was a
> > separate patch, but they probably have been merged at some po
Hi!
> > On Mon 2017-02-20 15:56:36, Sakari Ailus wrote:
> > > On Mon, Feb 20, 2017 at 03:09:13PM +0200, Sakari Ailus wrote:
> > > > I've tested ACPI, will test DT soon...
> > >
> > > DT case works, too (Nokia N9).
> >
> > Hmm. Good to know. Now to figure out how to get N900 case to work...
> >
Hi!
> > Ok, I got the camera sensor to work. No subdevices support, so I don't
> > have focus (etc) working, but that's a start. I also had to remove
> > video-bus-switch support; but I guess it will be easier to use
> > video-multiplexer patches...
> >
> > I'll have patches over weekend.
>
> I
On Sat, Feb 25, 2017 at 1:07 AM, Ingo Molnar wrote:
>
> So, should we revert the hw-retrigger change:
>
> a9b4f08770b4 x86/ioapic: Restore IO-APIC irq_chip retrigger callback
>
> ... until we managed to fix CONFIG_DEBUG_SHIRQ=y? If you'd like to revert it
> upstream straight away:
>
> Acked-by:
--
Dear Sir/Madam
Re: Projects Finance & Business expansion.
Kindly be informed that we are investment company and we offer a wide range of
project finance packages/services to Private, Corporate & Government Agencies.
And Our Financing Options and services are well known for the following:
From: Sean Young
When the interrupt requested with devm_request_irq(), serial_ir.rcdev
is still null so will cause null deference if the irq handler is called
early on.
Also ensure that timeout_timer is setup.
Link:
http://lkml.kernel.org/r/ca+55afxsh2uf8gi5sn_guy3z+tilv7lpjykbw+y8vqlzp+t...@m
On Sat, Feb 25, 2017 at 04:50:53PM +0200, Sakari Ailus wrote:
> Although, the driver could try to work on the actual obtained frequency.
> This is unlikely to work though, but it won't be very easy to figure out
> why the device isn't working. Having the frequency in DT accessible for the
> driver
Hi Vladimir,
On Wed, Feb 22, 2017 at 12:37:51AM +0200, Vladimir Zapolskiy wrote:
> Hi Sakari,
>
> On 02/21/2017 11:48 PM, Sakari Ailus wrote:
> > Hi, Vladimir!
> >
> > How do you do? :-)
>
> deferring execution of boring tasks by doing code review :)
X-)
>
> > On Tue, Feb 21, 2017 at 10:48:0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
From: Sean Young
When the interrupt requested with devm_request_irq(), serial_ir.rcdev
is still null so will cause null deference if the irq handler is called
early on.
Also ensure that timeout_timer is setup.
Link:
http://lkml.kernel.org/r/ca+5
Em Sat, 25 Feb 2017 10:34:37 -0300
Mauro Carvalho Chehab escreveu:
> Em Sat, 25 Feb 2017 11:28:16 +
> Sean Young escreveu:
>
> > When the interrupt requested with devm_request_irq(), serial_ir.rcdev
> > is still null so will cause null deference if the irq handler is called
> > early on.
>
On Sat, Feb 25, 2017 at 01:09:18AM +0100, Pavel Machek wrote:
> On Tue 2017-02-21 13:11:04, Sakari Ailus wrote:
> > On Tue, Feb 21, 2017 at 12:07:21PM +0100, Pavel Machek wrote:
> > > On Mon 2017-02-20 15:56:36, Sakari Ailus wrote:
> > > > On Mon, Feb 20, 2017 at 03:09:13PM +0200, Sakari Ailus wrot
Em Sat, 25 Feb 2017 11:28:16 +
Sean Young escreveu:
> When the interrupt requested with devm_request_irq(), serial_ir.rcdev
> is still null so will cause null deference if the irq handler is called
> early on.
>
> Also ensure that timeout_timer is setup.
>
> Link:
> http://lkml.kernel.org/
This introduces a new lirc mode: scancode. Any device which can send raw IR
can also send scancodes.
int main()
{
int fd, mode, rc;
fd = open("/dev/lirc0", O_RDWR);
mode = LIRC_MODE_SCANCODE;
if (ioctl(fd, LIRC_SET_SEND_MODE, &mode)) {
// kernel too
Since a lirc char device can only be opened once, there can only be one
reader. By using a plain kfifo we don't need a spinlock and we can use
kfifo_to_user. The code is much simplified.
Unfortunately we cannot eliminate lirc_buffer from the tree yet, as there
are still some staging lirc drivers w
According to the documentation, a timeout of 0 turns off timeouts,
which is not the case.
Signed-off-by: Sean Young
---
drivers/media/rc/gpio-ir-recv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/rc/gpio-ir-recv.c b/drivers/media/rc/gpio-ir-recv.c
index 4a48
lirc_register_driver() takes a struct lirc_driver argument, it then
allocates a new struct irctl which contains another struct lirc_driver
and then copies it over.
By moving the members of struct irctl to struct lirc_driver, we avoid the
extra allocation and we can remove struct irctl completely.
The lirc bridge exists as a raw decoder. We would like to make the bridge
to also work for scancode drivers in further commits, so it cannot be
a raw decoder.
Note that rc-code, lirc_dev, ir-lirc-codec are now calling functions of
each other, so they've been merged into one module rc-core to avoid
The lirc keymap existed once upon a time to select the lirc protocol.
Since '275ddb4 [media] rc-core: remove the LIRC "protocol"', IR is
always passed to the lirc decoder so this keymap is no longer needed.
Signed-off-by: Sean Young
---
drivers/media/rc/keymaps/Makefile | 1 -
drivers/media/rc
This has been broken for a long time, so presumably it is not used. I
have no hardware to test this on.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=61401
Fixes: 90ab5ee ("module_param: make bool parameters really bool")
Signed-off-by: Sean Young
---
drivers/media/rc/serial_ir.c | 4 +
This feature was never set. The ioctl should fail if no resolution
is set.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/media/rc/ir-lirc-codec.c b/drivers/media/rc/ir-lirc-codec.c
index 235d74a..
Split the protocol into two variants, one for keyboard and one for mouse
data.
Note that the mce_kbd protocol cannot be used on the igorplugusb, since
the IR is too long.
Signed-off-by: Sean Young
---
drivers/media/rc/igorplugusb.c| 2 +-
drivers/media/rc/ir-mce_kbd-decoder.c | 49
If a lirc device is unplugged, the struct rc_dev is freed even though
userspace can still have a file descriptor open on the lirc chardev. The
rc_dev structure can be used in a subsequent, or even currently executing
ioctl, read or write.
Signed-off-by: Sean Young
---
drivers/media/rc/lirc_dev.c
Lirc supports a new mode which requires documentation.
Signed-off-by: Sean Young
---
Documentation/media/lirc.h.rst.exceptions | 49 ++
Documentation/media/uapi/rc/lirc-dev-intro.rst | 25 +++
Documentation/media/uapi/rc/lirc-get-features.rst | 15 ++
This implements LIRC_MODE_SCANCODE reading from the lirc device. The
scancode can be read from the input device too, but with this interface
you get the rc protocol, toggle and repeat status in addition too just
the scancode.
int main()
{
int fd, mode, rc;
fd = open("/dev/lirc0", O
If the lirc device supports it, set the carrier for the protocol.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-jvc-decoder.c | 1 +
drivers/media/rc/ir-lirc-codec.c | 28
drivers/media/rc/ir-mce_kbd-decoder.c | 1 +
drivers/media/rc/ir-nec-decoder.c
When sending scancodes, load the encoder if we need it.
Signed-off-by: Sean Young
---
drivers/media/rc/rc-core-priv.h | 1 +
drivers/media/rc/rc-ir-raw.c| 2 ++
drivers/media/rc/rc-main.c | 2 +-
3 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/media/rc/rc-core-priv
Now that the lirc interface supports scancodes, RC scancode devices
can also have a lirc device, except for cec devices which have their
own /dev/cecN interface.
Signed-off-by: Sean Young
---
drivers/media/rc/rc-main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drive
If timeouts or carrier range is not supported, return proper error.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/media/rc/ir-lirc-codec.c b/drivers/media/rc/ir-lirc-codec.c
index 637b583..235d74a 100644
--- a/dri
The drivers sets the hardware to idle when a timeout occurs. This can
be any reasonable value.
Signed-off-by: Sean Young
---
drivers/media/rc/winbond-cir.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/media/rc/winbond-cir.c b/drivers/media/rc/winbond-cir.c
index
LIRC_MODE_MODE2 and LIRC_MODE_LIRCCODE were not covered at all.
Signed-off-by: Sean Young
---
Documentation/media/lirc.h.rst.exceptions | 1 -
Documentation/media/uapi/rc/lirc-dev-intro.rst | 53 +++---
Documentation/media/uapi/rc/lirc-get-features.rst | 13 --
We shouldn't be using ENOSYS when a feature is not available. I've tested
lirc; nothing is broken as far as I can make out.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 20 ++--
drivers/media/rc/lirc_dev.c | 2 +-
2 files changed, 11 insertions(+), 11 de
This patch series has some general cleanup work, then the lirc scancode
interface (v3) and lirc documentation fixes. The cleanups are needed for
the new scancode interface.
lirc already supports LIRC_MODE_LIRCCODE, but that mode is entirely
driver dependant and makes no provision for protocol info
When the interrupt requested with devm_request_irq(), serial_ir.rcdev
is still null so will cause null deference if the irq handler is called
early on.
Also ensure that timeout_timer is setup.
Link:
http://lkml.kernel.org/r/ca+55afxsh2uf8gi5sn_guy3z+tilv7lpjykbw+y8vqlzp+t...@mail.gmail.com
Cc:
On Fri, Feb 24, 2017 at 11:15:51AM -0800, Linus Torvalds wrote:
> Added more relevant people. I've debugged the immediate problem below,
> but I think there's another problem that actually triggered this.
>
> On Fri, Feb 24, 2017 at 10:28 AM, kernel test robot
> wrote:
> >
> > 0day kernel testing
* Linus Torvalds wrote:
> I'm pretty sure that the thing that triggered this is once more commit
> a9b4f08770b4 ("x86/ioapic: Restore IO-APIC irq_chip retrigger
> callback") which seems to retrigger stale irqs that simply should not
> be retriggered.
>
> They aren't actually active any more, if
Add new usbid eb1a:5051 for the Ion Video 2 PC MKII, Startech svid2usb23 and
Raygo R12-41373.
Hopefully this time tabs didn't get replaced with spaces. I also used this as
an occasion to add the concerned devices in comment beside the IDs.
No need to mention this is the first time I'm doing th
Le 24/02/2017 à 22:19, Javier Martinez Canillas a écrit :
Thanks for the patch, but Krzysztof sent the exact same patch before
[0]. There
was feedback from Sylwester at the time that you can also look at [0]. Could you
please take that into account and post a patch according to what he suggested
39 matches
Mail list logo
