Hi Doug,
On Tue, Jan 7, 2025 at 6:27 PM Doug Anderson wrote:
> On Wed, Dec 11, 2024 at 12:27 AM Geert Uytterhoeven
> wrote:
> > On Tue, Dec 10, 2024 at 6:09 PM Doug Anderson wrote:
> > > On Tue, Dec 10, 2024 at 6:19 AM Geert Uytterhoeven
> > > wrote:
> > > > Each bridge instance creates up to
Hi
On Wed, Dec 11, 2024 at 12:27 AM Geert Uytterhoeven
wrote:
>
> Hi Doug,
>
> On Tue, Dec 10, 2024 at 6:09 PM Doug Anderson wrote:
> > On Tue, Dec 10, 2024 at 6:19 AM Geert Uytterhoeven
> > wrote:
> > > Each bridge instance creates up to four auxiliary devices with different
> > > names. Howe
Hi Doug,
On Tue, Dec 10, 2024 at 6:09 PM Doug Anderson wrote:
> On Tue, Dec 10, 2024 at 6:19 AM Geert Uytterhoeven
> wrote:
> > Each bridge instance creates up to four auxiliary devices with different
> > names. However, their IDs are always zero, causing duplicate filename
> > errors when a sy
Hi,
On Tue, Dec 10, 2024 at 6:19 AM Geert Uytterhoeven
wrote:
>
> Each bridge instance creates up to four auxiliary devices with different
> names. However, their IDs are always zero, causing duplicate filename
> errors when a system has multiple bridges:
>
> sysfs: cannot create duplicate f
On Tue, Dec 10, 2024 at 03:18:46PM +0100, Geert Uytterhoeven wrote:
> Each bridge instance creates up to four auxiliary devices with different
> names. However, their IDs are always zero, causing duplicate filename
> errors when a system has multiple bridges:
>
> sysfs: cannot create duplicat
Each bridge instance creates up to four auxiliary devices with different
names. However, their IDs are always zero, causing duplicate filename
errors when a system has multiple bridges:
sysfs: cannot create duplicate filename
'/bus/auxiliary/devices/ti_sn65dsi86.gpio.0'
Fix this by using a
