From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Erling Ljunggren <hljunggr@cisco.com>
Cc: linux-media@vger.kernel.org, linux-i2c@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH v2 0/5] Add the cat24c208 EDID EEPROM driver + new EDID capability
Date: Wed, 3 Aug 2022 12:14:31 +0300 [thread overview]
Message-ID: <Yuo8d+16SREwT9J8@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20220803075850.1196988-1-hljunggr@cisco.com>
Hi Erling,
(CC'ing the linux-i2c mailing list and Srinivas, the maintainer of the
nvmem framework)
Thank you for the patches.
On Wed, Aug 03, 2022 at 09:58:45AM +0200, Erling Ljunggren wrote:
> This series adds support for the standalone cat24c208 EDID EEPROM i2c device.
> Usually EDID support is part of an HDMI receiver, but this is a standalone EEPROM.
>
> Note that EEPROMs for EDIDs are not regular EEPROM devices, these are dual port
> devices that follow the VESA E-DDC standard.
>
> Since this is a standalone device that does not capture any video a new
> V4L2_CAP_EDID_MEMORY capability is introduced to represent such devices.
> Note that such a device doesn't have to be an EEPROM, it can also be
> implemented using a microcontroller, for example. Hence the use of the generic
> word 'MEMORY'.
Why can't this be exposed as a nvmem device, like other types of eeproms
here ?
> The new capability uses the free bit 0x00000008. But we are running out of
> capability bits: only 0x40000000 and 0x00000008 are free at the moment.
>
> There is one other capability V4L2_CAP_ASYNCIO (0x02000000) that is not used
> at all, it was never implemented. Wouldn't it be better to define
> V4L2_CAP_ASYNCIO to 0, mark it as obsolete, and instead reuse it for this
> V4L2_CAP_EDID_MEMORY capability?
>
> v2:
> - fix dt binding example
> - rename i2c client variables in data struct
> - fix include: of_device.h -> mod_devicetable.h
> - Sorted makefile
> - used define EDID_OFFSET_EXT_FLAG instead of magic number
> - removed of_match_ptr
> - added bus_info
> - remove unneeded headers
> - add depends on OF to Kconfig
>
> Erling Ljunggren (4):
> media: videodev2.h: add V4L2_CAP_EDID_MEMORY
> media: docs: Add V4L2_CAP_EDID_MEMORY
> dt-bindings: media: add cat24c208 bindings
> media: v4l2-dev: handle V4L2_CAP_EDID_MEMORY
>
> Jonathan Selnes (1):
> media: i2c: cat24c208: driver for the cat24c208 EDID EEPROM
>
> .../bindings/media/i2c/onnn,cat24c208.yaml | 40 ++
> .../userspace-api/media/v4l/biblio.rst | 11 +
> .../media/v4l/vidioc-querycap.rst | 7 +
> .../media/videodev2.h.rst.exceptions | 1 +
> MAINTAINERS | 7 +
> drivers/media/i2c/Kconfig | 9 +
> drivers/media/i2c/Makefile | 1 +
> drivers/media/i2c/cat24c208.c | 421 ++++++++++++++++++
> drivers/media/v4l2-core/v4l2-dev.c | 8 +
> include/uapi/linux/videodev2.h | 1 +
> 10 files changed, 506 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/onnn,cat24c208.yaml
> create mode 100644 drivers/media/i2c/cat24c208.c
--
Regards,
Laurent Pinchart
next parent reply other threads:[~2022-08-03 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220803075850.1196988-1-hljunggr@cisco.com>
2022-08-03 9:14 ` Laurent Pinchart [this message]
2022-08-03 9:19 ` [PATCH v2 0/5] Add the cat24c208 EDID EEPROM driver + new EDID capability Hans Verkuil
2022-08-03 9:25 ` Laurent Pinchart
2022-08-03 10:37 ` Hans Verkuil
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=Yuo8d+16SREwT9J8@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=hljunggr@cisco.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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