linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Consolidating the interface for camera components
Date: Fri, 06 Dec 2019 17:57:21 +0000	[thread overview]
Message-ID: <20191206175721.GC186026@kroah.com> (raw)
In-Reply-To: <MNGy0F8hmcJu26jxhZS9eQjsTAmh1Uh_zqVhTzSeFndBaPi2lEXsbCO99Wdja9-5yaBOihwddIZbD8NTDTwerYtAUQ89wckBymIFeG5-eD0=@philipmolloy.com>

On Fri, Dec 06, 2019 at 04:50:09PM +0000, Philip Molloy wrote:
> Hello,
> 
> I'm trying to consolidate the interface for several camera components into one place to represent a single camera.
> 
> Each of the camera modules includes a LED driver (0x63) and camera (0x3c) that sit behind a couple muxes. For example:
> 
> /sys/devices/platform/amba/ff030000.i2c/i2c-1/i2c-3/i2c-5/5-003c/
> /sys/devices/platform/amba/ff030000.i2c/i2c-1/i2c-3/i2c-7/7-0063/
> 
> The LEDs are also available under /sys/class/leds/ based on their labels as defined in the devicetree.
> 
> The image data captured by the camera passes through two soft IP blocks. The driver for the second block maps the image into memory and exposes it as a block device in /dev.
> 
> In #kernel-newbies on OFC it was suggested that I could use udev to symlink the above into one place in /dev, but I'm having trouble creating a symlink between /sys and /dev (e.g. /sys/.../5-003c -> /dev/camera-name/camera). Perhaps that isn't possible or intended? I've only seen symlinks between /dev and /dev in /usr/lib/udev/rules.d/*.rules on my development system.
> 
> If it is I can explain what I've tried in more detail, but basically I'd like to do something like the following:
> 
> DRIVER="aptina-ar0330", SYMLINK+="camera/$attr{../../of_node/name}/$env{OF_NAME}"
> 
> If it is not possible any other recommendations would be greatly appreciated.

Try asking on the linux-media mailing list as this is the API those
drivers expose.

thanks,

greg k-h

      reply	other threads:[~2019-12-06 17:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 16:50 Consolidating the interface for camera components Philip Molloy
2019-12-06 17:57 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191206175721.GC186026@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).