<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/media/rc/lirc_dev.c, branch linux-6.10.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.10.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.10.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2024-08-03T07:01:04Z</updated>
<entry>
<title>lirc: rc_dev_get_from_fd(): fix file leak</title>
<updated>2024-08-03T07:01:04Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2024-05-31T03:58:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=47ff960f0e460f7ab6522de851edc48dcd19b877'/>
<id>urn:sha1:47ff960f0e460f7ab6522de851edc48dcd19b877</id>
<content type='text'>
[ Upstream commit bba1f6758a9ec90c1adac5dcf78f8a15f1bad65b ]

missing fdput() on a failure exit

Fixes: 6a9d552483d50 "media: rc: bpf attach/detach requires write permission" # v6.9
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: lirc_dev: Make lirc_class constant</title>
<updated>2024-03-25T09:13:44Z</updated>
<author>
<name>Ricardo B. Marliere</name>
</author>
<published>2024-03-05T13:26:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8d93d0674bb1b3770d96e585248f0d5856bf0f64'/>
<id>urn:sha1:8d93d0674bb1b3770d96e585248f0d5856bf0f64</id>
<content type='text'>
Since commit 43a7206b0963 ("driver core: class: make class_register() take
a const *"), the driver core allows for struct class to be in read-only
memory, so move the lirc_class structure to be declared at build time
placing it into read-only memory, instead of having to be dynamically
allocated at boot time.

Cc: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
Suggested-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
Signed-off-by: Ricardo B. Marliere &lt;ricardo@marliere.net&gt;
Signed-off-by: Sean Young &lt;sean@mess.org&gt;
Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
</content>
</entry>
<entry>
<title>media: rc: bpf attach/detach requires write permission</title>
<updated>2024-02-01T12:48:57Z</updated>
<author>
<name>Sean Young</name>
</author>
<published>2023-04-13T08:50:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6a9d552483d50953320b9d3b57abdee8d436f23f'/>
<id>urn:sha1:6a9d552483d50953320b9d3b57abdee8d436f23f</id>
<content type='text'>
Note that bpf attach/detach also requires CAP_NET_ADMIN.

Cc: stable@vger.kernel.org
Signed-off-by: Sean Young &lt;sean@mess.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: lirc: drop trailing space from scancode transmit</title>
<updated>2023-10-11T14:26:16Z</updated>
<author>
<name>Sean Young</name>
</author>
<published>2023-10-06T21:31:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c8a489f820179fb12251e262b50303c29de991ac'/>
<id>urn:sha1:c8a489f820179fb12251e262b50303c29de991ac</id>
<content type='text'>
When transmitting, infrared drivers expect an odd number of samples; iow
without a trailing space. No problems have been observed so far, so
this is just belt and braces.

Fixes: 9b6192589be7 ("media: lirc: implement scancode sending")
Cc: stable@vger.kernel.org
Signed-off-by: Sean Young &lt;sean@mess.org&gt;
Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
</content>
</entry>
<entry>
<title>driver core: class: remove module * from class_create()</title>
<updated>2023-03-17T14:16:33Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
</author>
<published>2023-03-13T18:18:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1aaba11da9aa7d7d6b52a74d45b31cac118295a1'/>
<id>urn:sha1:1aaba11da9aa7d7d6b52a74d45b31cac118295a1</id>
<content type='text'>
The module pointer in class_create() never actually did anything, and it
shouldn't have been requred to be set as a parameter even if it did
something.  So just remove it and fix up all callers of the function in
the kernel tree at the same time.

Cc: "Rafael J. Wysocki" &lt;rafael@kernel.org&gt;
Acked-by: Benjamin Tissoires &lt;benjamin.tissoires@redhat.com&gt;
Link: https://lore.kernel.org/r/20230313181843.1207845-4-gregkh@linuxfoundation.org
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>media: rc: Directly use ida_free()</title>
<updated>2022-06-20T09:30:33Z</updated>
<author>
<name>keliu</name>
</author>
<published>2022-05-27T10:30:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cd54ff938091d890edf78e6555ec30c63dcd2eb5'/>
<id>urn:sha1:cd54ff938091d890edf78e6555ec30c63dcd2eb5</id>
<content type='text'>
Use ida_alloc() and ida_free() instead of the deprecated
ida_simple_get() and ida_simple_remove().

Signed-off-by: keliu &lt;liuke94@huawei.com&gt;
Signed-off-by: Sean Young &lt;sean@mess.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: lirc: report ir receiver overflow</title>
<updated>2022-01-28T18:32:50Z</updated>
<author>
<name>Sean Young</name>
</author>
<published>2022-01-15T10:19:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=68a99f6a0ebfe9101ea79ba5af1c407a5ad4f629'/>
<id>urn:sha1:68a99f6a0ebfe9101ea79ba5af1c407a5ad4f629</id>
<content type='text'>
If the driver reports that the hardware had an overflow, report this to
userspace. It would be nice to know when this happens, and not just get
a long space.

This change has been tested with lircd, ir-ctl, and ir-keytable.

Signed-off-by: Sean Young &lt;sean@mess.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: rc-core: rename ir_raw_event_reset to ir_raw_event_overflow</title>
<updated>2022-01-28T18:32:50Z</updated>
<author>
<name>Sean Young</name>
</author>
<published>2022-01-15T10:12:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=950170d6d2a5d3c0c959696d2440e5c8dfd02896'/>
<id>urn:sha1:950170d6d2a5d3c0c959696d2440e5c8dfd02896</id>
<content type='text'>
The driver report a reset event when the hardware reports and overflow.
There is no reason to have a generic "reset" event.

Signed-off-by: Sean Young &lt;sean@mess.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: lirc: simplify gap calculation</title>
<updated>2022-01-24T00:38:32Z</updated>
<author>
<name>Sean Young</name>
</author>
<published>2022-01-13T11:29:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d49a14a946db0a8e0713aa43034879f967ab75e2'/>
<id>urn:sha1:d49a14a946db0a8e0713aa43034879f967ab75e2</id>
<content type='text'>
When a driver reports a timeout, no more IR activity will be reported
until the next pulse. A space is inserted between the timeout and the
next pulse, based on ktime.

The timeout reports already a duration, so this duration should not be
added to the gap. Otherwise there is no change to the functionality.

Signed-off-by: Sean Young &lt;sean@mess.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: lirc: always send timeout reports</title>
<updated>2021-12-14T14:09:12Z</updated>
<author>
<name>Sean Young</name>
</author>
<published>2021-11-27T11:46:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=74747dda582dc7ddd8aac6841954e84b0d28e56c'/>
<id>urn:sha1:74747dda582dc7ddd8aac6841954e84b0d28e56c</id>
<content type='text'>
Without timeout reports, it is impossible to decode many protocols since
it is not known when the transmission ends. timeout reports are sent by
default, but can be turned off. There is no reason to turn them off, and
I cannot find any software which does this, so we can safely remove it.

This makes the ioctl LIRC_SET_REC_TIMEOUT_REPORTS a no-op.

Signed-off-by: Sean Young &lt;sean@mess.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
</feed>
